Under the Law of the Republic of Armenia "On Protection of Personal Data" (HO-49-N), we are the processor of personal data — the party that decides why and how your data is processed.
a. Your uploaded statement (in-session only). The CSV or Excel file you upload may contain your name, account number, balances, dates, transaction amounts, and transaction descriptions. To analyze it, the file is sent to our server (hosted by Supabase in the European Union — Ireland), where it is read into a transaction list, categorized, and shown back to you on your screen. Purpose: to build your categorized report and spending dashboards. This data exists only for the duration of your session and is then deleted (see section 8).
b. Merchant descriptions sent for AI categorization. When a merchant description is not recognized by our internal lookup list, we send the description text and the transaction direction (money in or out) to Anthropic (Claude API), a US-based AI provider, to determine a spending category. We do not send names (see section 4), account numbers, amounts, dates, or balances. Purpose: to categorize your transactions.
c. Retained merchant records — the one thing we keep. When a category is assigned, or when you correct one, we may save a record containing only: the merchant description text; the assigned category; the direction (in/out); the latest transaction amount seen for that description; a technical origin tag (whether the category came from the AI, our internal list, or a user correction); and a count of how often that description has been seen. Purpose: to build an internal merchant-to-category dictionary that makes categorization more accurate over time. These records are reviewed by the operator before entering the dictionary. They are not linked to you, your session, or any account.
About the amount field. The amount stored in a merchant record is the latest amount observed for that merchant description across all uses of the tool. It helps judge which category fits a merchant. It is not tied to any person, account, statement, or date.
Transfer descriptions sometimes contain a person's name (for example, "Transfer to Anna Sargsyan"). Before any description is sent to our AI provider or saved to our database, an automated check identifies transfer descriptions that appear to contain a personal name. When one is identified, it is not sent to the AI service and is not stored — the transaction is simply categorized as a transfer and shown to you on your screen during your session. This check runs within our own systems and involves no third party.
Honest limits: the check reliably detects names written in Latin letters in standard transfer formats; it may not detect names written in Armenian or Russian script, or names in unusual phrasing. It reduces, but does not eliminate, the possibility that a personal name is processed. If you believe a name slipped through, contact us (section 14) and we will review and delete it.
Registered businesses — including sole proprietors whose registered business name includes a personal name (marked "IE"/"PE" or Armenian "ԱՁ") — are treated as merchants, not private individuals, and may be retained as merchant records.
We process your data on the basis of your consent (HO-49-N, Article 8), which you give by ticking the consent box before uploading. Nothing is processed before you consent, and our system will not accept an upload without it. You may decline — the tool simply will not analyze a statement. You may withdraw consent at any time by ending your session (closing the page); because we keep no data linked to you, ending your session removes everything except the de-identified merchant records described in section 3(c).
Both providers act on our instructions under written terms. We do not share your data with anyone else. We do not sell data and do not use it for advertising or marketing.
Your data is processed outside Armenia:
At the end of your session (when you leave or close the page), we delete: your uploaded statement file; your balances, dates, and account or card numbers; your transactions as a set; and any personal names identified by the filter — these are never saved at all. The only data that remains is the de-identified merchant records described in section 3(c).
We keep the de-identified merchant records for as long as they are useful for improving categorization. Because they contain no identifying information and are not linked to any person, they cannot be traced back to you.
Under Armenian law you have the right to receive information about the processing of your personal data, to access it, to request rectification, blocking, or destruction, and to complain to the Personal Data Protection Agency (pdpa.am) or to a court.
An honest limitation: we have no accounts and keep nothing linked to you. Once your session ends, we cannot find, identify, or single out "your" data — the retained merchant records are de-identified and shared across all users. In practice this means there is usually nothing identifiable left for us to hand over or delete. For anything still in your session: close the page and it is deleted.
If you believe a retained merchant record contains a personal name our filter missed, contact us at [CONTACT EMAIL] and we will review and delete it.
This service is intended for adults. If you are under 16, you may use it only with the consent of a parent or legal guardian.
We may update this policy. The current version, with its "last updated" date, is always available on this page. If we ever change what data we keep, we will update this policy and the consent notice before the change takes effect.
[CONTACT EMAIL — to be added]