Traty Privacy Policy
Effective date: 6 November 2026
Traty turns a photograph of a paper receipt, or a purchase you dictate, into a list of purchases, so that spending can be read month by month and category by category. What follows is what the app does with data, who receives it, and how to take it back or delete it. This document describes what the app actually does, not what it intends to.
1. Who we are
The controller of the data described here is Oleksii Charoian, an individual, at vul. Lesia Serdiuka 44, Kharkiv, Kharkiv Oblast, 61184, Ukraine, reachable at contact@traty.app. There is no company behind the app and no data protection officer: it is one person, and that person answers your requests.
The app is developed and operated from Ukraine, which is outside the European Economic Area. Where the GDPR applies to you, the section on transfers below covers what that means.
2. What we process
Account. Signing up with an email address stores that address; signing in with Google also stores the name as Google supplies it. The profile photo is not stored: its address used to be written to the account record and was never shown anywhere, so it is now deleted from records that still hold it. Authentication is performed by Firebase Authentication (Google LLC). The app neither sees nor stores your password.
Receipts. A saved receipt holds the merchant's name (both shortened to the chain and as printed), the date and time of purchase, the currency code, the total, the list of items — name, quantity, unit, unit price, line total, category — and where those items came from: entered by hand or read by a model, and if by a model, then which provider, which model, when, and whether the purchase was dictated rather than photographed. Each item may also carry the product type and brand taken from the product dictionary, and the receipt carries words to find it by, derived from the merchant's name and those product types. Receipts are stored in Cloud Firestore (Google LLC).
Product dictionary. So that the price of an item can be followed from one purchase to the next, and so that every item can be shown and found under one everyday name in the language of the app, the app keeps a dictionary of what the lines printed on your receipts mean. For each line it has seen in a shop, a record holds the shop, the line in a normalised form with one printed sample of it, what the line names (a product type such as milk, the unit a price is compared in, the pack size, the brand and traits such as fat percentage, where they can be told), whether the reader was unsure of it, whether you marked it as a different product, and which model made the record and when. It has no field for a price or an amount paid, though a printed sample of the line may carry one. The dictionary is made by sending the names of the lines — printed, or typed by hand — with the shop's name, the unit and the category, to the same model provider as a receipt (see "Receipt recognition"), and the answers are saved as records. Lines of goods are sent: food, drink, household, hygiene and pet items — the ones that can have a price history — and, since 6 November 2026, clothing, shoes, electronics, home goods, medicines and other pharmacy items, tobacco, children's items, fuel and car items, leisure and education items and other goods, which get a product type and an everyday name but no price history. Lines of discounts, services, meals out, housing, health and beauty services, transport and travel never leave the phone for this. Receipts saved before that date had their lines of the newly added categories sent once by a maintenance run on 6 November 2026. They live in Cloud Firestore next to the receipts: one dictionary in your personal area and, if you belong to a household, another one in the household's.
Everyday names of products. A product type is an English identifier such as phone_charger. The app shows it under an everyday name in English, Polish, Russian or Ukrainian. The names of common types come with the app. For a type the model coined while building someone's dictionary, the handler asks the same model provider for its names once — sending the identifier alone, never a receipt line, a shop or an account — and keeps the names in the Cloudflare D1 database described under "Operational data", where they serve every user. To learn names it does not have, your phone sends the handler the identifiers of types on your receipts, at most a few times a day; the handler does not keep which account asked about which type.
Your corrections of names. If an everyday name is wrong, you can correct it on the receipt: give a product type a name of your own, or say that a line of a shop is a different product. The corrections — your names, which type a line of which shop counts as, when they were last changed and the account identifier of whoever changed them — are stored in Cloud Firestore, once in your personal area and, if you belong to a household, once more in the household's. A name you type is sent once through the handler to the same model provider, with the printed line and its category for context, to be put into the four languages of the app; the handler keeps nothing of it but the record of what that cost, and the names are stored in your area only. Nobody outside your household sees your corrections.
Monthly budget. If you set a budget, the app stores the sum and its currency from the month you set it; a month without an entry of its own takes the last one before it. The document also holds when it was last changed and the account identifier of whoever changed it. It is stored in Cloud Firestore, once in your personal area and, if you belong to a household, once more in the household's.
Connected bank. If you connect a bank: the outgoing operations on the cards you chose and the link to the bank (the cards and how far they were read), stored in Cloud Firestore in your personal area. The access token itself stays on your phone and goes only to the bank. Details are in the section "Bank payments" below.
Device identifier. So that the free recognition allowance cannot be reset by creating another account on the same phone, requests carry a device identifier (Google Play services' app_set_id, or, where that is unavailable, an identifier the app generates and keeps on the device only).
Subscription. Buying the subscription happens inside Google Play; we never see your card, your billing address or your name as it appears on the card. Google Play returns a purchase token, the app sends that token to our handler, and the handler verifies it with the Google Play Developer API. Two things are then stored in Cloudflare Workers KV: the token bound to your account identifier — so that one purchase cannot serve two accounts — and a record that the account is a subscriber, holding the token, the source (play) and the expiry date if the store reports one.
What we do not collect. The app receives no audio: when you dictate, your phone's speech service turns speech into text and only the text reaches the app (see "Dictating a purchase"). The app reads no location from the device, no contacts, no list of installed applications, no browsing history and no advertising identifiers. It contains no analytics and no advertising libraries. The one place a location appears at all is an error report, where it is inferred from the network address rather than read from the device; see "Diagnostics" below.
3. Receipt recognition
Recognition happens in two steps, and only the second one leaves the phone.
A receipt can come from three places: the camera, an image already in your gallery, or a PDF file — an electronic receipt as the shop issued it. A PDF is turned into a single image on the device, and from there all three are treated identically; wherever this section says "the photograph", it means whichever of the three you chose.
The total, the date and the currency are read on the device. Right after the photograph is taken, text recognition built into the app reads them from it. That step needs no network and sends nothing anywhere.
The list of items is read in an external service. That is the only part that needs the photograph to leave the device, and it is what the rest of this section describes.
When you start recognition, the photograph is downscaled on the device and sent to our handler hosted on Cloudflare Workers (Cloudflare, Inc.). The handler passes the image to a model provider, receives the parsed contents of the receipt, and returns them to the app. A receipt too tall for the provider to read whole is cut into parts by Cloudflare Images, which is the same processor and the same transit: the parts are not stored either.
The image is not stored — not on the device once the operation ends, not on our server, and not as part of the saved receipt. The handler holds it in memory for the duration of the request and drops it once it answers, on success and on failure alike. The original PDF is never sent anywhere: only the image rendered from it is.
Model provider. The provider in use is OpenAI, Inc. and the model in use is gpt-5.6-luna. OpenAI retains data submitted through the API for up to 30 days for abuse monitoring and does not train on it. We may change the provider or the model; whichever is in use is named in this section, and every recognised receipt records which provider and model read it.
Sending the photograph is optional. If you would rather not send a receipt to a third party, do not start recognition on it — neither from the camera, nor from the gallery, nor from a file: items can be entered by hand, and the rest of the app works without restriction. One thing stays: once a receipt is saved, however it was entered, the names of its items go to the model provider to build the product dictionary (see "What we process"), and the app has no switch for that.
4. Dictating a purchase
A purchase without a paper receipt — a market stall, a coffee on the go — can be dictated instead: "Market, strawberries 12.50, cucumbers 6".
Speech is turned into text by your phone, not by us. The app asks Android's speech recognition service — usually Google's, on some phones the manufacturer's — to listen and hands over the words it hears. That service decides where to recognise: on the phone itself when the language is installed there, otherwise on its own servers, under its own terms. The app never receives, stores or sends the audio. The microphone permission is asked for the first time you press the microphone, not before, and dictation works without it: the purchase can be typed into the same field.
The text is treated like the photograph. You see the recognised words and can correct them before anything is sent. When you press the button to read it, the text is sent to our handler on Cloudflare Workers and passed to the same model provider as a photograph (see "Receipt recognition"), which returns the items. OpenAI's retention of up to 30 days without training applies to the text as it does to an image.
The text is not stored. The handler holds it in memory for the duration of the request; its logs record only how long the text was, never the words. On the phone it stays in memory while the receipt screen is open, so that a closed dictation sheet does not lose it, and is gone once you save the receipt or leave the screen. What is kept is the saved receipt itself, marked as dictated.
Dictation is optional, like recognition of a photograph: the same items can be typed by hand.
5. Bank payments
Connecting a bank is optional: the app works the same without it. If you connect one (at present: monobank), Traty reads the outgoing card operations you have made and lists the ones that have no receipt yet. Below, these are called bank payments. You can match each with a receipt you already saved, or record it as a receipt without items.
What you give access to. You create a personal access token in the bank's own service and paste it into the app. The app uses it only to read: it does not make payments or transfers. It asks the bank for the list of your cards, so that you can choose which of them to follow, and then for the operations on the chosen cards. By default it reads one month back; more only when you ask for it on the connection screen, as far back as your plan allows (one month on the free plan, up to a year with the subscription).
What is kept. Of each outgoing operation — every spend except cash withdrawals — the app keeps the time, the description the bank gives, the merchant category code, the sum in the currency of the purchase, the sum in the card's currency, whether the bank still holds the sum, the bank's identifier of the operation, when it was imported, and what became of it in the app: still waiting, matched with a receipt (the receipt's identifier is kept), recorded as a receipt, or hidden by you. Money that comes in is read and dropped. Operations include transfers to other people, whose description may be the recipient's name as the bank shows it, and shop names and category codes can say a good deal about a person's life; the app keeps them as the bank gives them, so connect a card only if you are comfortable with that. Of each chosen card the app keeps the number as the bank masks it (the first six and the last four digits), the currency, the bank's identifier of the account, how far its statement has been read, and whether the bank has refused the token. Balances are not kept. Your name as the bank holds it is shown on the connection screen and is not stored by us.
The token stays on your phone and is sent only to the bank. It is kept in the phone's protected storage and is not sent to our handler or written to Cloud Firestore. The app talks to the bank directly from your phone; the requests do not pass through us, and error reports carry no token and no bank data.
Where the bank payments are kept. In Cloud Firestore, in your personal area, next to your account. They are visible to you only, not to the other members of a household you belong to. Bank payments themselves are not sent to the model provider: matching one with a receipt compares the sum, the currency and the date on your phone. A receipt you make from a bank payment is an ordinary receipt, though: if you later add its items, by photograph or by hand, they are processed as described in "Receipt recognition", and the shop's name, which here is the bank's description, goes with them to build the product dictionary. When the app looks for the receipt a payment belongs to, it searches the receipts you can see, including a household's, so the receipt it offers may be another member's.
If you are in a household, receipts made from bank payments become household receipts, and the other members can see them, with your name as their author (see "What we process" and "Households"). It happens when you press "Add" on a payment, when you fill a receipt in from one, and — without a question about each — when you mark a shop "Always file here": the mark files that shop's payments already waiting, as far back as you imported, and the ones that arrive later. A saving made without a question after a bank read has no "Undo" button, and deleting such a receipt does not return the payment to the waiting list. Other members may have seen the receipt before you delete it. Such receipts count toward the household's shared budget. Matching a payment with a receipt you had already saved adds nothing to the household: that receipt was there already, and the payment itself stays private. Every member of a household connects their own bank with their own token on their own phone and sees only their own bank payments.
What stays on the phone. The group you gave to a shop, the shops you marked "Always file here" (by name) and a note that a bank was once connected are kept in the app's own storage on the phone and are not uploaded. Signing out of the app and deleting the account erase the token and the marks, so that the next person to sign in on the phone does not see your cards or have their payments filed by your marks; the groups and the note stay until you clear the app's data or remove the app.
Disconnecting. "Disconnect" on the connection screen erases the token from the phone and deletes the link to the bank (the chosen cards and how far they were read). Bank payments already imported stay in your account until you delete the account; receipts made from them are ordinary receipts and are deleted like any other. You can also revoke the token in the bank's own service at any time: the app then can no longer read anything.
6. Operational data
To bound what recognition costs, the handler keeps counters keyed to your account identifier, to your device identifier, and — if you belong to a household — to that household's identifier. These counters live in Cloudflare Workers KV. Building the product dictionary has a counter of its own, keyed to your account identifier and counting lines per day, and so does naming new product types, counting types per day; both live in the Cloudflare D1 database described below and are deleted two days after their day ends. Counters for a period are deleted once the period ends. They contain no images and no receipt contents.
The handler also keeps a record of what each recognition cost us: your account identifier, the moment, which model read the receipt, whether it was a photograph or a dictation, how much work it took and what that came to in money; building the product dictionary leaves such a record too. The record lives in a Cloudflare D1 database and is what tells us the price of running the service. It holds no image, no dictated text and no receipt contents — not the shop, not the items, not the amount you paid.
To establish that a request comes from a signed-in user, the app attaches a Firebase token. The token is verified and not stored; when the handler writes the product dictionary after answering, it uses that same token and nothing else.
A recognition request also carries hints that help read the receipt: the language of the app's interface, the currency code the app would use if the receipt does not print one, and, for a dictation, today's date on your phone, so that "yesterday" means your yesterday. None of them is stored.
7. Diagnostics: what happens when something breaks
When the app or the handler fails, a report of that failure is sent to Sentry (Functional Software, Inc.) and stored in Sentry's European region. A report carries the error and the place in the code it happened, the version of the app and of the operating system, the identifier of your account, and technical facts about the device that usually explain the failure: model, interface language, time zone, free memory and storage, battery level, and which permissions you have granted the app.
It carries no receipt image, no dictated text, no receipt contents, no email address and no name.
It does carry an approximate location — the country, and often the city — which Sentry derives from the IP address the report arrived from. This is not the location of your device as a map would give it, and it is not read from the device at all; it is what any server can tell about any visitor. The IP address itself is discarded and not stored.
Only a failure that means something on our side is broken is reported. A spent allowance, a missing subscription, or a photo that holds no receipt are the app working as designed, and nothing about them is sent anywhere. Reports are kept for as long as Sentry's own retention allows and are not used for anything but fixing defects.
8. Households: one shared receipt base
The app lets several accounts join a household with a single shared base of receipts. This is voluntary: without joining one, your receipts are visible only to you.
What it means for your data. While you are in a household, every member sees all of its receipts in full — merchant, date, total, every item and category — and may edit and delete them. Each receipt shows who entered it. The receipts you accumulated before joining are moved into the shared base when you join and become visible to the other members.
The household also has a dictionary, a budget and corrections of names of its own. They are shared the same way: every member reads and changes them. When you create a household, your personal budget and your corrections of names are copied into it, unless it already has them; your personal copies stay where they were. Your personal dictionary is not moved: it stays in your personal area, and the household builds its own from the receipts in it.
What happens when you leave. If you leave a household yourself, a copy of the receipts you entered returns to your own history, while the household keeps everything it had — including those receipts, its dictionary and its budget. The household's dictionary and budget are not copied back: you keep your own personal ones. If the owner removes you, access to the shared base ends at once and you get no copy: the removed member no longer has access, and the owner has none to your personal area, so there is nobody left who could make one.
Who decides what. Only the owner — whose subscription opened the household — can invite and remove. An invitation is a short code that lives for fifteen minutes and is spent on first use. Any member may leave at any time. If the owner disbands the household, its receipts pass to the owner's personal area and the household's budget and corrections of names become the owner's personal ones. The household's dictionary is not passed on: it stays in storage, where no account can open it any more, and you can ask us in writing to erase it.
Storage enforces the boundary. Access to a household's receipts, dictionary, budget and corrections of names is granted only to the accounts in its roster, and that is checked by Cloud Firestore security rules on Google's side, not by the app on the device.
9. Who receives data
| Recipient | What they receive | Why |
|---|---|---|
| Google LLC (Firebase Authentication, Cloud Firestore) | account data, receipts, product dictionary, monthly budget, corrections of names, bank payments and the link to the bank | signing in and storing your data |
| The other members of your household | all of the household's receipts, including yours, its product dictionary, its monthly budget and its corrections of names, with the identifier of whoever last changed them | the shared spending base, if you joined one |
| Cloudflare, Inc. | the receipt image or the dictated text (in transit), the names, categories and shop of items sent for the product dictionary (in transit), identifiers of product types your phone asks names for (in transit), account, device and household identifiers | the recognition handler, the allowance counters, the record of what recognition cost and the shared everyday names of product types |
| OpenAI, Inc. | the receipt image or the dictated text; the names of items, printed or typed, with the shop's name, unit and category; identifiers of new product types, without anything else; names you type for your products | reading the contents of the purchase, building the product dictionary, naming new product types and translating your own names |
| Universal Bank JSC (monobank), Ukraine | the access token and the requests the app makes to read your cards and operations — sent from your phone, not through us | reading the cards and operations you chose to connect |
| Google LLC (Google Play Billing, Play Developer API) | the purchase token, and whatever the payment itself requires — that part happens inside Google Play and does not pass through us | selling and verifying the subscription |
| Functional Software, Inc. (Sentry) | the error, the version of the app, technical facts about the device and its operating system, the account identifier, an approximate location inferred from the network address | finding and fixing what breaks |
We do not sell data, do not share it for advertising, and do not use it for profiling.
10. Transfers outside the EEA
Most of the recipients listed above are companies in the United States, and the app is operated from Ukraine, so data is processed outside the European Economic Area. Error reports are the exception: Sentry stores them in its European region, so they stay inside the EEA. Transfers to the recipients rely on the European Commission's standard contractual clauses and, where applicable, on the recipient's participation in the Data Privacy Framework. Ukraine has no adequacy decision, and requests you send to the address above are answered from there.
The bank connection is between your phone and the bank in Ukraine; it does not pass through our handler or through any of the recipients above.
11. Legal bases
- Performance of a contract (Art. 6(1)(b) GDPR) — the account, storing and showing your receipts, your product dictionary and your monthly budget, recognition at your request, the bank connection you ask for (reading the cards you choose and listing their payments), and the household.
- Performance of a contract (Art. 6(1)(b) GDPR) — the subscription: the purchase token is what proves the subscription is yours and still current.
- Legitimate interest (Art. 6(1)(f) GDPR) — the allowance counters and abuse protection: without them nothing bounds what recognition costs.
12. Retention
Account data, receipts, the product dictionary, the monthly budget and corrections of names are kept for as long as your account exists. Bank payments and the link to the bank are kept the same way: while the account exists, and disconnecting erases the token and the link but not the operations already imported (see "Bank payments"). A receipt entered into a household is kept for as long as the household exists or until any of its members deletes it; your leaving does not remove it from there. The household's dictionary, budget and corrections of names are kept while the household exists and are not deleted when one member leaves; the dictionary of a household that was disbanded stays in storage until we erase it on request. Receipt images and dictated text are not kept at all. Period counters live no longer than their period — a day or a calendar month; the free-recognition counter has no expiry while the account exists, because the allowance itself has none. The record of what recognition cost outlives the account, but not the link to you: deleting the account replaces your identifier in it with a marker, so what remains is a cost with nobody attached to it and is no longer data about a person. The subscription record and the purchase-token binding are kept while the account exists. When you delete the account, none of these is deleted at that moment; each expires on its own: the period counters at the end of their day or month, the free-recognition counter and the subscription record 30 days after the deletion. This is so that deleting an account cannot be used to start the allowance over, and so that a deletion interrupted halfway leaves a working account behind. The purchase-token binding is replaced by a note that the purchase was released by your account identifier, kept for 35 days, so that someone who buys, deletes the account and signs up again can restore what they paid for — with that month's use carried over. On the model provider's side: up to 30 days, see "Receipt recognition".
13. Your rights
You may request access to your data, its rectification, erasure, portability, restriction of processing, and you may object to processing based on legitimate interest. Write to contact@traty.app and we will answer within the period the GDPR sets (one month).
You also have the right to lodge a complaint with the data protection authority of your place of residence.
14. Deleting your account and data
You can delete your account in the app: Settings → Delete account. The app asks you to confirm it is you — with your password, or by consenting again at your sign-in provider — and then deletes the account data: every receipt in your personal area, your personal product dictionary, your personal monthly budget, your personal corrections of names, the bank payments imported into your account and the link to the bank; the allowance counters, the subscription record and the purchase-token binding expire as described under "Retention". Deletion is irreversible.
If the app is already off your phone, write to contact@traty.app from the address the account is registered to. The procedure and the timing are on a page of their own: deleting your account.
Receipts you entered into a household stay with the household — the other members can see them, and deleting your account does not remove them. That includes receipts made from bank payments: once saved, they are household receipts like any other. The household's dictionary and budget stay with it as well. In the app, an owner's deletion is refused while the household exists: it has to be disbanded first, so the shared base does not vanish for everyone else without their knowing. If you ask us in writing instead, the household passes to one of its remaining members and its shared base stays intact — unless you are its only member, in which case it is deleted along with you. If you want to take your history with you, leave the household before deleting the account: a voluntary departure returns a copy of your receipts to your own history.
15. Children
The app is not directed at children under 16, and we deliberately collect no data about age.
16. Security
Data travels over TLS only. Access to receipts, the product dictionary, the monthly budget and bank payments is bounded by Cloud Firestore security rules on Google's side: they are visible to the account that owns them, and a household's only to its members. Model provider keys live on the server and never reach the app.
17. Contact
Questions about this policy and data requests: contact@traty.app.
18. Changes
If what we process changes — should receipt images start being stored, say, or should the model provider change — we will update this policy and the Data safety declaration in Google Play before the change takes effect. The effective date at the top of this document identifies the edition in force.