Privacy Policy
This policy covers the website asienta.app, the web app at app.asienta.app and the Asienta apps for iPhone and Android. Questions and requests: support@asienta.app.
In short
- We collect only what is needed to run your account and your ledger. Nothing for advertising, and we don’t sell data.
- Your financial records are visible only to the people in your household. Platform administrators have no technical access to them.
- We never ask for bank logins and don’t connect to banks.
- No third-party analytics and no tracking — on the website or in the apps. We count visits and usage ourselves, without cookies, and look only at totals.
What we collect and why
Account data. Your name, email address, password, interface language and overview layout — needed to provide your account. The password is stored only as an Argon2id hash; we can’t read it.
Your financial records. Everything you enter, with a history of who changed what. We store them only to show them to you and the members of your household.
Sessions and security. For each sign-in we store the IP address and the browser or app description, which you see as your list of devices, and we count sign-in attempts to stop password guessing. This keeps accounts secure.
Usage statistics. On which days you used Asienta and with which app (web, iPhone, Telegram), and whether you signed up from a link on our website. We look at these only as totals — how many people sign up and come back — never per person, and they contain no pages, amounts or entries.
Website visits. When you open a page on asienta.app, your browser sends us the page address and the website you came from (only its address, without the path or search terms). Your IP address and browser description are turned into a code that changes every day and can’t be traced back; they are not stored. No cookies are used; the address you came from is kept in your tab only until the next page opens. Nothing is sent if your browser asks not to be tracked (Do Not Track or Global Privacy Control).
Server logs. Requests and errors, so we can keep the service running. They contain no amounts or entries.
Emails. We send only service emails: confirming an address and resetting a password.
On your iPhone
The session token is kept in the iOS Keychain. Face ID is checked by iOS; the app learns only whether it matched. Entries recorded offline wait on the phone until they are sent, and the Home Screen widget keeps your net worth and this month’s spending on the phone — never while Face ID is on — and erases them when you sign out.
On your Android phone
The session token is encrypted with a key from the Android Keystore and stays on the phone: it is not included in backups or moved to a new phone. Biometric sign-in (fingerprint, face or the phone’s screen lock) is checked by Android; the app learns only whether it matched. To read a receipt the app uses your phone’s camera app or a photo you pick; it has no camera permission of its own. Entries recorded offline wait on the phone until they are sent, and the Home Screen widget keeps your net worth and this month’s spending on the phone — never while biometric sign-in is on — and erases them when you sign out.
Telegram bot
The @AsientaAppBot bot is optional: Settings → Telegram. While a chat is connected, we keep its Telegram chat ID, your Telegram username at the time you connected, and the household and account chosen in the bot. Everything you send the bot and its replies — amounts, descriptions, account and category names — goes through Telegram’s servers and is kept there under Telegram’s privacy policy. You can unlink the chat in the same settings or with /stop; deleting your account erases the link at once.
Receipt recognition
In the iPhone and Android apps and in the Telegram bot you can send a photo of a receipt or a screenshot from your banking app, and Asienta reads the amount, date and shop. To do that, the picture, together with the names of your categories and currencies, is sent to the Claude model through the API of Anthropic (USA): Anthropic processes the request on our behalf, does not use it to train models and keeps it only for a limited time under its security rules. The request may be processed outside the EU, including in the USA; the transfer is covered by the EU Standard Contractual Clauses in our data processing agreement with Anthropic. We don’t store the pictures or what was read from them: they immediately become a draft (in the app) or an entry (in the bot), and from then on it is an ordinary record. A photo sent to the bot first goes through Telegram and is kept there under its rules. For the monthly recognition limit we keep, for each recognition, only its time, the app, the outcome (read, not a receipt, failure), the model and the number of tokens — no picture and nothing from it; these rows are deleted with your account. Recognition is optional: you can always record entries without it.
Cookies
Only the cookies the service needs: to keep you signed in and to remember your language and theme. No analytics or advertising cookies.
Who else processes data
Our hosting provider, our email delivery provider and our email provider for support mail process data on our behalf, only to run the service. If you connect the Telegram bot, your conversation with it goes through Telegram (see above). Receipt photos, if you send them, are read by Anthropic’s Claude model (see “Receipt recognition”). We don’t sell, rent or share your data with anyone else.
Monitoring. To notice failures in time, our server sends technical metrics and operational logs to Grafana Cloud, a service of Grafana Labs (USA) that processes them on our behalf. The data is stored in the EU region (Germany) for 14 days and then deleted. What is sent: server load and availability, the number of requests, errors and response times per part of the app (without page addresses), the state of the mail queues and of exchange-rate loading, and service log lines. There are no amounts, names, titles or transactions in it; IP addresses, email addresses and identifiers of people are replaced with placeholders on our server, before anything is sent. In addition, Grafana opens our pages from the EU every few minutes to check that they respond.
How long we keep it
- Your records stay while your household exists; voided entries and archived items can be restored until then.
- Deleting a household. Ask us: members lose access at once, and all its data is permanently erased 30 days later.
- Server logs — 14 days on the server and as long in Grafana Cloud (without IP or email addresses, see “Monitoring”).
- Deleting your account — see the next section.
Deleting your account
You can delete your account yourself at any time:
- on iPhone and Android — More → “Delete account” at the bottom;
- on the web — Settings → “Delete account” → “Delete account…”.
Before deleting, we show what will happen to each of your households and ask for your password. The account is closed at once: every sign-in is revoked, and your email, name and password are erased. Households where you are the only owner are deleted entirely — their members lose access at once, and the data is permanently erased 30 days later; to keep such a household for its members, first make one of them an owner. In other households you just leave, and your entries stay with the members without your name or email. You can later register again with the same address — as a new, empty account. On iPhone and Android, the app erases everything it kept on the phone.
If you cannot sign in, write to support@asienta.app from the account’s address and we will delete it on request.
Your rights
You can ask us to give you a copy of your data, correct it, delete it, restrict or object to its use, or hand it over in a machine-readable format. Write to support@asienta.app. You can also complain to your data protection authority.
Changes
When we change this policy, we update the date at the top. If a change materially affects how we use your data, we tell you in the app first.