← Back to upload

Privacy Policy — aeria sense

Last updated: 14.10.2026

1. Who we are

æria sense is a service operated from Armenia. 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. Contact: contact@aeriasense.am.

2. The short version

  • No account, no login, no password. We do not know who you are.
  • You upload a bank statement (CSV, Excel or PDF). We analyse it, show you the results, then delete it when you leave.
  • How your file is read depends on its type. CSV and Excel files from banks we recognise are read by our own code on our server in the EU. CSV and Excel files from other banks — and recognised files our code cannot read completely — are read by our code after our AI service provider identifies the file's structure from a short sample with long numbers hidden. PDFs are read by our AI service provider from the whole file. Details in section 3.
  • We do not keep your statement, your balances, dates, amounts or account details.
  • We keep one thing: a de-identified merchant list — the merchant description text, its category and the direction (money in/out). It is not linked to you or to any account.
  • Before anything is saved or sent to our AI provider, an automated filter removes transfer descriptions that appear to contain a personal name.
  • Your data is never sold and never used for advertising.

3. The data we process, and why

a. Your uploaded statement (deleted when you leave). The CSV, Excel (including password-protected Excel) or PDF 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 (run by our cloud infrastructure provider in the European Union — Ireland), where it is read into a transaction list, categorised, and shown back to you on your screen. Purpose: to build your categorised report and spending dashboards. This data is deleted when you close the page (see section 8). If your Excel file is password-protected, the password you enter is used once, in memory on our server, to open the file; it is deleted after use, not logged or sent to anyone.

b. How the statement is read.

  • Recognised CSV/Excel formats (currently the exports of Ameriabank, Converse Bank, Evocabank and Ardshinbank): read entirely by our own code on our server. Nothing from the file is sent to our AI service provider at this step. If our code cannot read such a file completely, it is handled as described in the next point.
  • Other banks' CSV/Excel files, and recognised files our code cannot read completely: our code sends a short sample — the first and last rows of the file, up to about 55 rows, with long numbers such as account and card numbers hidden — to our AI service provider in the United States, which identifies the file's structure (which column holds the date, the description, the amounts). Our code then reads every transaction itself and checks the result against the totals printed in your statement. We do not store the sample.
  • PDF statements: the whole PDF, including the name and account details printed on it, is sent to our AI service provider to transcribe the transactions. Our code then checks the result against the totals and text printed in your statement. PDFs are limited to 10 pages and 10 MB. We do not store the file, and it is not used to train AI models.

c. Merchant descriptions sent for AI categorisation. 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 our AI service provider in the United States, to determine a spending category. We do not send names (see section 4), account numbers, amounts, dates, or balances. Purpose: to categorise your transactions.

d. 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); 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 categorisation more accurate over time. These records are reviewed by the operator before entering the dictionary. They are not linked to you or any account.

e. Abuse prevention. To prevent automated abuse of the free service, our server keeps a hashed (one-way scrambled) form of your IP address together with the time of each upload for 24 hours, then deletes it. It cannot be turned back into your IP address and is not linked to your statement.

f. Usage analytics. We use an analytics provider (hosted in the EU) to count anonymous page views and usage events such as "upload started" or "results shown" — without cookies, without recording your activity on the page, and never with statement content. Our website hosting provider also collects anonymous visit statistics.

4. Name protection in transfers

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 categorised as a transfer and shown to you on your screen until you close the page. 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.

5. Legal basis: your consent

We process your data on the basis of your consent (HO-49-N, Article 8), which you give by ticking the consent box shown before your statement is analyzed. Nothing is processed before you consent, and our system will not analyze a statement without it. You may decline — the tool simply will not analyze a statement. You may withdraw consent at any time by closing the page; because we keep no data linked to you, closing the page removes everything except the de-identified merchant records described in section 3(d).

6. Who processes your data

We use a small number of service providers to run AeriaSense. Each acts only on our instructions and under its own data-protection terms.

Provider typeLocationPurpose
Cloud infrastructureEuropean UnionRuns our servers and database. Your file is processed here until you close the page.
AI service providerUnited StatesHelps read statements and categorise transactions. May receive statement content for this purpose. It is not stored by us and is not used to train AI models.
AnalyticsEuropean UnionAnonymous usage statistics. No cookies, no statement content.

We do not share your data with anyone else, sell it, or use it for advertising. A list of our providers is available on request at contact@aeriasense.am.

7. International transfers

Your data is processed outside Armenia. Hosting and storage are in the EU (Ireland); EU countries are recognized by the Armenian Personal Data Protection Agency as ensuring an adequate level of protection. Depending on the file type, our AI service provider (United States) receives filtered merchant descriptions, a short sample of a CSV/Excel file with long numbers hidden, or a whole PDF, as set out in section 3. These transfers are disclosed here and in the consent notice and take place on the basis of your consent.

8. What we delete, and when

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).

9. How long we keep the merchant records

We keep the de-identified merchant records for as long as they are useful for improving categorisation. Because they contain no identifying information and are not linked to any person, they cannot be traced back to you.

10. Your rights

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 you close the page, 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 on the page: 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@aeriasense.am and we will review and delete it.

11. Security

  • Data is transmitted over encrypted connections (HTTPS).
  • The AI provider's access key is stored server-side only and is never exposed to your browser.
  • Database access is restricted: the merchant dictionary is locked to operator review, and the app can write only the non-identifying candidate records described in section 3(c).
  • Statement files and personal transaction data are not persisted — they exist only while being processed.
  • Per-visitor upload limits protect the service against automated abuse (section 3e).
  • Excel passwords are used once in memory, deleted after use and not logged.

12. Age

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.

13. Changes to this policy

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.

14. Contact

contact@aeriasense.am

← Back to aeria sense