Privacy policy
isna holds one family’s passports, health details and invoices. This page says exactly what happens to them, without generalities.
Last updated: 18 October 2026 · If anything on this page does not match what you see in the app, write to info@isna.app — that is a mistake and it will be corrected.
Who processes the data
The controller is EDVIN KOVAČEVIĆ PR EK IT SOLUTIONS 2020, Generala Živkovića bb, 36300 Novi Pazar, Serbia, email info@isna.app.
No data protection officer has been appointed, because the conditions in Article 37 GDPR are not met. Every question about data goes to the address above and is answered by the same person who writes the code.
What we collect
Account. Email address, password in hashed form (bcrypt — we never see the original and cannot recover it), language, timezone, and a TOTP secret if you turn on two-factor sign-in.
What you enter. Household members, events, tasks and lists, documents and files you upload, expenses and invoices, vehicles, contacts and health records. This is the data you enter and control.
Technical data. IP address and access time in server logs, for security and abuse detection. Logs roll by size and older files are discarded; they feed no analytics of any kind.
Billing. Once paid plans are switched on, payment is handled by Lemon Squeezy as a separate controller. We receive the subscription status and what an invoice needs — never a card number.
Health data
Records in the Health module are health data within the meaning of Article 9 GDPR. They are processed solely on your explicit consent, which you give by entering them into the module built for them, and you can delete them at any moment.
By default they are visible only to the adults in the household, they do not appear in search or in the edit history unless you ask for it, and they are used for nothing except showing them back to you.
Children’s data
Children in isna usually have no account — a parent or guardian keeps their records. When a teenager does get an account, it is a limited role: they see their own and the household’s, not anyone else’s health records and not the finances.
A parent entering a child’s data is responsible for having the right to enter it. The age at which a child can consent for themselves differs by country — 16 in Germany, 15 in Serbia.
Why we process it
- Providing the service you asked for — performance of a contract, Article 6(1)(b).
- Security and preventing abuse — legitimate interest, Article 6(1)(f).
- Accounting and tax obligations — Article 6(1)(c).
- Health data, browser notifications and email digests — explicit consent, Article 6(1)(a) and Article 9(2)(a).
Consent is withdrawn as easily as it was given, and withdrawing it does not affect what was processed beforehand.
Who else sees it
Every subprocessor is listed on its own page, with where the data sits and whether it leaves the EU. There is no sale of data, no advertisers, no training of models on user content, and no internal tool for browsing families’ contents.
Administrative access to one household’s data exists technically, as it does at any service somebody maintains, and is used only when you ask for support.
How long we keep it
- Content — for as long as the account exists.
- Trash — 30 days, then permanent removal.
- Deleting a household — a 7-day wait during which it can be cancelled, then removal.
- Backups — 30 days.
- An account nobody has signed into for a long time — a warning by email, then deletion after 30 days.
- Invoices — for as long as tax law requires.
Where the data is
The database, the files and the backups sit on a server in Helsinki, Finland (Hetzner Online GmbH) — inside the European Union.
Transfer outside the EU happens only where the Subprocessors page says so, and relies on the European Commission’s standard contractual clauses and, where it applies, the EU-US Data Privacy Framework.
Your rights
- Access, rectification, erasure, restriction, portability, objection, and withdrawal of consent.
- A complaint to a supervisory authority — in the EU, the authority in your own country.
Exporting everything is a button in the app rather than a request you have to send: one ZIP with every record as JSON and every file you uploaded, in a format readable without isna. Deleting the household is a button too.
Cookies
This site sets no cookies and loads no third-party script. The application sets only what signing in requires. Details are on the Cookies page.
Security
- Transport is encrypted (TLS) and the session lives in an HttpOnly cookie rather than as a token in browser memory.
- Households are separated by a filter applied in the database itself rather than in the interface; automated tests deliberately try to read another household’s data and must fail.
- An uploaded file’s type is determined by reading its bytes, not by what the browser claims; antivirus scanning is available.
- Backups run nightly, and the restore script fills a scratch database first, so restoring is tested without risk to production.
Changes to this policy
When something material changes, notice goes to the account’s email address at least 30 days beforehand. Smaller corrections are published here, and the edit history on GitHub carries the dates.
Start with the one deadline you cannot afford to miss.
Set your family up in two minutes. Thirty days of everything, and it does not ask for a card.