How Ankrito protects your data

Access

Database rules on every table limit each customer to their own records. Staff use personal accounts with role-based permissions.

Encryption

HTTPS for every connection. The database and stored files are encrypted at rest by our hosting provider. Personal identity numbers are encrypted again by Ankrito before storage.

Files

Kept in private storage. Opened only through links that expire.

Location

Accounting database in the EU (Ireland); POS database in the EU (Sweden); backup copies in Finland.

Backups

An encrypted copy of the accounting database every hour, kept in a separate Google Cloud account in Finland, plus the hosting provider’s daily backups. Restoring a backup has been tested.

Records

Posted entries and filed VAT periods cannot be changed; corrections are new entries. Every change leaves a trail.

Report an issue

support@ankrito.com, subject “Security”.

• For your account, profile and our customer relationship, Ankrito Oy is the controller under the GDPR. The Privacy Policy describes this processing.
• For personal data in your business’s accounting material — for example customers, suppliers and employees named on invoices and receipts — your business is the controller and Ankrito acts as processor on your behalf, under the Data Processing Agreement.
• Under the Finnish Accounting Act, your business remains responsible for its bookkeeping and for keeping its accounting material. Ankrito provides the service and keeps the material it holds safe and available to you.
• Ankrito uses a small number of service providers to run the service. They are listed, with what each one does, in the Subprocessor List.

• Access to data in the Ankrito app database is controlled by row-level security rules on every table, so a signed-in customer can reach only the records their access allows. These rules are enforced by the database itself, not only by the app.
• Ankrito staff use the back office with personal accounts and role-based permissions; there are no shared logins. Actions such as approving documents or finalising a VAT period require the matching permission.
• Our working rule: staff open a customer’s data only to do work for that customer, or when the law requires it.
• Entries in the books record who made them.
• The Ankrito POS till checks staff, manager and owner roles on the server, not just in the menu.

• Posted ledger entries cannot be changed or deleted. A mistake is corrected with a new, visible correcting entry, as good accounting practice requires.
• When a VAT period is filed, it is locked in the database and a fixed record of what was filed is kept.
• Changes to invoices, expenses, bank reconciliation and VAT periods are written to activity trails that are only ever added to.
• Amounts are stored as whole cents, so totals do not drift through rounding.
• Refunds in Ankrito POS keep the original sale; nothing is overwritten.

• In transit: the website, the app and their services are used over encrypted HTTPS connections, and browsers are told to use HTTPS only (HSTS).
• At rest: our database and file-storage provider, Supabase, states that all customer data is encrypted at rest with AES-256 and in transit with TLS.
• Personal identity numbers are additionally encrypted by Ankrito with AES-256-GCM before they are stored.
• Backup copies are encrypted before they are written to storage. The key needed to read them is kept offline, apart from the backups.
• Passwords are handled by our authentication service; Ankrito does not store them in readable form and cannot see them.

• Uploaded receipts, invoices, statements and support attachments are kept in private storage. They are never available at a public address.
• A file is opened through a signed link that works only for a short time and then expires.
• Storage rules limit each file to the customer it belongs to and to authorised staff.

Accounting database and files

Supabase, EU (Ireland).

POS database

Supabase, EU (Sweden).

Backup copies

Google Cloud, Finland (europe-north1).

Some service providers — for example for website hosting, email, text recognition and push notifications — are based in, or may process data outside, the EU. The Subprocessor List names each one and the safeguards that apply, and the Privacy Policy explains how such transfers are protected.

• Every hour, an encrypted copy of the accounting database is made and stored in Finland, in a Google Cloud account kept separate from the live service, with its own access rights.
• Our hosting provider also takes its own daily backups of the database.
• We have restored a backup into a separate, isolated environment and checked it against the live data: every table present and the books still balancing to the cent. The test copy was then destroyed.
• A backup is never restored over the live service without the owner’s explicit approval.

• Ankrito builds its app, POS and back office itself. Each change is checked by automated tests before release, including tests of the money rules such as balanced entries and VAT period locks.
• Every change is scanned automatically for passwords or keys accidentally left in the code.
• Changes reach the live service only through a release that a person approves.
• Development and test work uses separate environments from the live service.

• In the Ankrito app you can turn on app lock, which uses your device’s fingerprint, face or passcode check. The check happens on your device.
• Deleting an account in the app requires you to confirm your password again.
• Account deletion requests made on the website never delete anything by themselves: Ankrito first verifies that the request comes from the account holder. The requester’s IP address is stored only as a keyed hash.
• The website’s contact and deletion forms limit repeated submissions to reduce misuse.
• The website sends security headers that stop it being embedded in other sites and limit what browsers may do on it.

Finnish law requires accounting material to be kept for set periods: the Accounting Act (kirjanpitolaki, chapter 2, section 10) sets longer periods for financial statements and the books themselves, and shorter ones for receipts, invoices and other vouchers. Tax law can require some material to be kept longer.

When a customer leaves or deletes their account, Ankrito keeps the accounting material it must keep for those periods. Before you close your account, you can export your reports from the app. The Account Deletion page and the Privacy Policy explain what is kept and why.

• Use a strong password that you don’t use elsewhere, and don’t share it.
• Turn on app lock on the phone you use for Ankrito, and keep the phone’s own software up to date.
• Tell us at once at support@ankrito.com if you think someone else has used your account.
• Never send passwords or full bank card numbers by email, WhatsApp or in support messages. Ankrito will never ask for them.
• Be careful with messages that claim to be from Ankrito and ask you to sign in through a link. If in doubt, open the app yourself instead.

If a personal data breach occurs, Ankrito handles it as the GDPR requires. For data where Ankrito is the controller — such as your account and profile — that can include notifying the Office of the Data Protection Ombudsman within the time limit in Article 33 of the GDPR, where the breach is likely to risk people’s rights and freedoms, and telling the people affected, where the risk is high (Article 34). Not every incident reaches either threshold; the GDPR sets them deliberately, and Ankrito follows them rather than a fixed promise to report everything.

For personal data Ankrito processes as a processor on a business customer's behalf — see the Data Processing Agreement — Ankrito notifies the customer without undue delay, and it is then the customer's responsibility as controller to assess the risk and notify the authority or the people affected where the law requires it.

If you believe you have found a security issue in an Ankrito service, email support@ankrito.com with “Security” in the subject line. Describe what you found and how to reproduce it. We confirm that we have received your report and keep you informed while we look into it.

• Don’t test or exploit the issue further than needed to show it exists.
• Don’t access, change or delete other people’s data, and don’t disrupt the service.
• Give us reasonable time to fix the issue before telling anyone else about it.

You can ask to see, correct or delete your personal data, or object to how it is used, as described in the Privacy Policy. If you think we have handled your personal data wrongly, you can complain to the Office of the Data Protection Ombudsman (tietosuoja.fi). We’d appreciate the chance to put it right first: support@ankrito.com.

No online service can guarantee absolute security. We describe what we actually do, we don’t claim certifications we don’t hold, and we update this page when our measures change.