Security and data
Invoices and the KPO ledger are business data. This page says exactly where they are stored, who can access them and how you get them back — without legal jargon. The binding documents are the Privacy Policy and Terms (the Serbian version prevails).
Logging in
- The easiest is a Google account (on iPhone also an Apple account) — then Stavka never sees a password, and the two-factor authentication you have on that account protects Stavka too.
- No such account? Create one with any e-mail address and password. The password is never stored as it is — the database holds only a scrypt hash with its own salt, from which the password cannot be recovered.
- You confirm your address with a link from an e-mail; until then the account cannot be used — so nobody can open an account on someone else’s address.
- Confirmation and password-reset links are single-use and short-lived (24 hours and 1 hour), and only their hash is stored.
- Two-factor authentication (code from an app) can be turned on for any account in Options — turning it on asks for your password, you scan a QR code with an app such as Google Authenticator, and from then on a six-digit code is required with the password. For accountants it is mandatory: without it they cannot enter a client’s account.
- When it is on, the code is required at every login — even after a “forgotten password”. Recovery works only with the one-time codes you get when turning it on; no e-mail can switch the protection off.
- A session is tied to your browser or phone and ends when you log out. A new password or turning on 2FA logs out all other sessions, and you can do that yourself (“Log out all devices”).
- Wrong passwords and codes are counted per account and per IP address; after several misses, login pauses for a while.
Where the data is
- The data is on a server in a data centre in the European Union (OVH, Gravelines, France), under our control. It does not pass through third-party data processing platforms.
- The database is copied on the server every hour, and every night an encrypted copy goes to another location (outside that data centre) and is kept for 14 days; production has no access to those copies, so even a break-in cannot delete them. We test restoring from a copy once a month.
- All traffic goes over HTTPS (TLS), on the web and in the apps. The web app has a Content Security Policy: the browser may load code and send data only to stavka.rs (and to Google when logging in), so an injected foreign script cannot run.
- The server is accessed only with an SSH key, no passwords; the firewall lets in only HTTPS, SSH and mail for bank statements, and the database is not reachable from the internet.
- Server logs record the IP address, time and path of a request — no tokens, passwords or content; they rotate and in practice last about two weeks.
- Each account sees only its own data. An accountant sees a client only after the client explicitly grants access — and the client can revoke it at any time.
SEF key and sensitive data
- The SEF API key is stored encrypted (AES-256-GCM) with a key that exists only on the server. It is never returned to the app and never goes into backups or logs.
- Account numbers, tax IDs and client details are used only for what you see: the invoice, the payment slip, the KPO ledger.
- Plans are paid by bank transfer against a proforma invoice — Stavka does not collect card details.
- Statements by e-mail (if you turn them on): Stavka has no access to your mailbox — it sees only the e-mails you forward to your secret address. Only the payments read from them are kept, not the e-mail or attachment; nothing is booked without your confirmation, and received statements are deleted after 90 days.
- E-mails Stavka sends (invoices to clients, notifications, confirmations) are sent by Brevo (France, EU) on behalf of noreply@stavka.rs; Brevo sees the recipient and content and may not use them for anything else.
Your data is yours
- Export everything whenever you want: invoices as PDF, the KPO ledger as PDF and Excel, the whole account as an XML backup you can import back.
- Pro and Biznis make an automatic nightly backup; every account can make a backup by hand at any time.
- An expired plan never locks your data: overview, KPO ledger and every export work in the free plan too.
- You delete your account yourself, in Options — no support ticket, no waiting. Invoices, the KPO ledger, companies, templates, clients, expenses, backups and accountant access disappear at once and for good. Only a record of paid subscriptions (number, amount and date) remains, without your name, address, tax ID and e-mail — tax accounting requires it.
- Export an XML backup before deleting: after that we have no copy we could send you. By law you must keep invoices and the KPO ledger for 10 years — even after deleting the account.
What Stavka does not do
- We do not sell your data or share it with third parties.
- No third-party analytics or advertising scripts. The only measurement is our own Umami on the same server, without cookies and without storing IP addresses, and only on public pages — the logged-in part of the app is not measured.
- E-mails you send to clients from Stavka carry a tiny image that records that the e-mail was opened, so you can see whether the invoice was seen; you can switch it off in Settings. E-mails we send to you do not have even that.
- We do not send ads or third-party offers.
Who else can see the data
- Your accountant — only the one you granted access in Options, and only until you revoke it. They must have two-factor authentication on. In your account they cannot delete the company, invoices or backups, cannot see or change the SEF key, bank account, tax and registration numbers, and do not see personal finances. You get an e-mail when you grant access and when the accountant first enters.
- Your client — only the documents you send them (PDF, view or payment link).
- The Stavka administrator — for support and billing sees account data, with mandatory two-factor authentication; does not share it with anyone and does not access it without a reason.
GDPR and the Serbian data protection law
Stavka processes personal data (name, e-mail, data on invoices) only to provide the service, in line with the Serbian Law on Personal Data Protection (ZZPL) and the EU General Data Protection Regulation (GDPR), on which the ZZPL is based. Your rights: access, correction, deletion, restriction of processing and portability (XML export of the whole account at any time). You delete the account yourself in Options, immediately; for everything else write through the contact form and we reply within the legal deadline of 30 days. If data were ever compromised, we notify affected users and the Commissioner within 72 hours of finding out.
Found a security issue?
- Write to boris@stavka.rs with the subject “Stavka security”: what you found, how to reproduce it, and which data you may have seen. Please do not download, change or share it.
- We reply within 48 hours and tell you what we found and when it was fixed. We do not report or pursue good-faith reports.
Last updated: 8 November 2026