What this holds, and what it does not do

It is not tax advice and not an accountant. Every figure is computed from what you enter and from published statutory parameters, and each one names its source — the gazette it came from or, for the rare figure the state publishes only through its own calculator, that calculator and the date it was read. Where it cannot source a number it refuses to show one.

It files nothing and signs nothing — no submission to Poreska uprava, no SEF e-invoice, no payment. Your filing obligations are unchanged, and you remain the taxpayer. It does not issue SEF e-invoices at all, so invoices to Serbian businesses still go through the state system.

It is beta software: incomplete, changing, and free. Check anything you act on.

Your email, name, date of birth, and a photo if you upload one — and, if you sign in with Google, what Google sends for it, set out below. The birth date is not decoration — several Serbian tax reliefs depend on age, and this app will not guess at a figure it cannot source.

Your business records: businesses and companies, clients, engagements, income, costs, invoices, payroll and tax assessments, including what the APR and NBS registers return for a matični broj.

Data about other people that you enter — your clients’ details, and for anyone on your payroll their name, birth date and salary history. For that data you decide what happens and we act on your instructions.

If you ask for an invitation on several.app, we keep your email address, what you tell us you run, the page’s language and when you asked, only to decide on your invitation and to write to you about it. We delete the request when you get an account, when we decline it, or a year after you sent it, whichever comes first, and sooner whenever you ask.

We do not collect JMBG, health data or biometric data anywhere in this product.

Nobody, beyond the five suppliers that run it: Supabase (database and credentials, Frankfurt), Railway (application server, Amsterdam), Vercel (web hosting), Sentry (reports of software failures, EU region) and Resend (emails with sign-in and password links, EU region) — and Google, only if you choose to sign in with it.

What Sentry receives. When the software itself fails — a crash rather than a mistake you made — the failure is reported so we hear about it without waiting for you to tell us. What goes is the technical error and where in the code it happened. The address of the record you were looking at does not: not the page, not the invoice, not the client. Errors that happen in your browser are not sent there at all — those we record ourselves, which is what the paragraph below describes.

What Vercel receives. It hosts the site, so every request passes through it in order to be answered at all. On top of that it measures how quickly pages really load for the people using them. What goes is the shape of the page — /c/[companyId]/invoices — the browser’s own timings for it, and a rough class of device and connection. Not the address of the record, not which invoice, client or employee, no cookie, and no identifier that follows you anywhere else. It does not run at all until you have accepted.

What Resend receives. The address an email goes to and the email itself — a sign-in, password or new-account link, in your language — and, when someone asks for an invitation, our own note about the request, with their address and answers. Nothing about your records.

What Google receives. Continue with Google takes you to Google’s own sign-in, which Google’s own privacy policy governs, and Google learns that you are signing in to Several. What comes back is what that sign-in shares: your name, your email address and whether Google has confirmed it, the identifier Google uses for your account, and the address of your Google profile photo, which Several does not show. Several uses it to find your account and to keep its name and email address current, and the credential provider keeps it with your sign-in details. Several asks Google for nothing else — not your contacts, mail, files or calendar — and sends it nothing about you or your records. A password or an emailed link signs you in without Google.

We do not sell your data, share it for advertising, or use it to train machine-learning models. Nobody is watching what you do here to build a profile of you: there is no advertising network and nothing that tracks you across other sites — the two measurements named here count pages and time them, and that is the whole of it — and the only cookies are the one that keeps you signed in and the one that remembers the language you chose.

Nothing is recorded against your account before you have accepted — the measurement below starts only after your yes, and an error reported before it stays anonymous. Signing in is the yes, and it also writes the sign-in record: each session keeps the identification string your browser sends and the address you connected from, so a session you do not recognise can be found and ended. Both go when the session does — immediately when you sign out or end it, and once it has expired, at the next sign-in on the account at the latest — and our hosting providers’ request logs hold the same address for a few days as part of running the service.

During the beta we do record, ourselves, which screen you opened and when and any error that happens in your browser, so we can tell which parts of the product are used and hear about failures you would otherwise have to report by hand. It stores the shape of the page — /c/[companyId]/invoices — and never which invoice, client or employee you had open. It sets no cookie of its own, it goes nowhere else, and all of it is in the workspace’s data export — the owner’s download; an invited member can ask, and we produce their records by hand within the same 30 days.

How you accept. Signing in is the acceptance: the sign-in screen says so, under the button, beside a link to this page. There is nothing to tick, nothing to sign and nothing to send back. What is recorded is the account, the moment the server received the sign-in, and the version of this page the sign-in screen showed — the number above. When we change something that matters to you we raise that version, say here what changed, and your next sign-in accepts the new one. Your earlier acceptance is not overwritten: each one stays on record as its own event, and every one of them is in your data export. Before 10 September 2026 no version was recorded, so those acceptances read as “unversioned” — which is why everyone was asked once more on that date.

Two outward requests, so they are not a surprise: entering a matični broj looks it up in our own copy of the APR’s public register (refreshed by us; nothing is sent to the APR) and sends that number and nothing else to the National Bank’s public register of accounts, to read back what it already publishes; and exchange rates are read from a public mirror that receives a currency and a date. Nothing about you goes with either.

Passwords are held by the credential provider and never by us. Sessions are opaque random identifiers stored hashed, with an idle timeout and an absolute cap, revoked immediately on sign-out. Every query is scoped to your own workspace, and a request for someone else’s record is answered “not found” rather than “forbidden”, so the existence of other people’s data cannot be probed. The application server answers only requests that carry a secret held by this web app, and anything else as if the route did not exist.

What is not yet true: backups are taken by hand rather than on a schedule, and are held unencrypted on a company machine. That is being fixed. Until it is, it is a fair thing to weigh before entering a full year of records.

You can take a copy whenever you like, without asking: Account → Your data downloads everything a workspace holds, as a spreadsheet-readable folder and an exact record side by side. For a correction or a deletion, write to us and we will do it within 30 days.

Whether you ask or not, we keep nothing for more than one year after your account ends or the beta finishes, whichever comes first.

Some of what you record has its own statutory retention period — the revenue book and issued invoices among them. Deleting it here does not discharge that, so keep your own copies.

The beta is free and provided as it is, with no warranty that it is available, correct or complete. To the fullest extent Serbian law allows we are not liable for any tax, contribution, penalty or interest arising from a figure this software produced or failed to produce, nor for lost profit or lost data. Serbian law governs, and the courts of Belgrade have jurisdiction.

This notice is written in Serbian and in English. If the two ever differ, the Serbian version prevails.

Anything at all, including a forgotten password or a request above: support@several.app. You may also complain to the Poverenik za informacije od javnog značaja i zaštitu podataka o ličnosti.