Clamsy Budgets Privacy Policy
Clamsy is built so that your money stays with you. Your personal budget lives only on your phone, and we never receive it. A family budget (a budget you keep with other people) goes through our server, but its records are encrypted on your phone with a key the server never gets: the key passes from phone to phone in a QR code or an invitation link.
This policy shows what that means in practice: what leaves your phone, when, where it goes and how long it is kept. It covers the Clamsy Budgets app (shown as Clamsy on your phone) for Android and iPhone.
Who we are
Clamsy is published by Viachaslau Melnik, Republic of Armenia ("we" in this policy). Questions about your data and requests: clamsy@buckleup.tech.
In short
- Your personal budget stays on your phone. Only what you choose leaves it: a backup or a table you save or send, a letter you write to us and, with automatic rates, the codes of the currencies you use. Nothing of it goes into a family budget, which has accounts of its own.
- Family budgets sync through the Clamsy server. It cannot read amounts, comments, categories or names. It does see who is in a budget, when items are created and changed, and some details in plain text — all listed below.
- You need an account only for family budgets: sign-in with Google, or with Apple on iPhone.
- No ads, no analytics of our own, no tracking. On Android, the QR scanner sends Google usage figures (see the camera below). Crash reports go to Google only if you allow them.
- A backup can be opened by anyone who has Clamsy, and a CSV or Excel table is plain text. Keep both where only you can reach them.
- Deleting your account does not remove the records you added to other people's family budgets and does not cancel your subscription. See "Deleting your account".
What stays on your phone
Your personal budget: income, expense and transfer records with their amounts, dates and comments; accounts and balances; categories, limits, recurring payments, exchange rates and settings. We do not receive any of it, and there is no copy on our server.
- It is kept in the app's private storage, closed to other apps. The app does not encrypt it on top of the phone's own protection, so anyone who can use your unlocked phone can open it — the app lock below closes that.
- It is left out of the automatic Google and Apple backups: on Android the system backup is off for the app; on iPhone the app's database and its own backup folder are excluded from iCloud backup. If you lose the phone or uninstall the app, the personal budget is gone unless you saved a backup.
- The app lock uses the phone's own check: Face ID, Touch ID or fingerprint, then the phone's passcode. The app learns only whether the check passed, never your fingerprint, face or passcode. While the lock is on, the app's screen is hidden in the list of recent apps.
- The camera is used only to scan a family budget's QR code. Frames are read on the phone and are not saved or sent. On Android the scanner is Google's ML Kit library: when you scan, it sends Google usage and performance figures, the phone model, system and app versions and an installation identifier — never the picture. On iPhone the scanner is Apple's own (Vision) and sends nothing.
What leaves your phone, and why
Each of these happens only when you use the feature. Every connection is encrypted (HTTPS).
| What | When | Where it goes |
|---|---|---|
| A family budget's records, names and settings, encrypted | you create or join a family budget | the Clamsy server and the members' phones |
| Your email address and account identifier | you sign in for family budgets | Firebase Authentication (Google); our server keeps only the identifier |
| A device identifier and a push token | you sign in | the Clamsy server; Google, and Apple on iPhone, deliver the messages |
| Proof of a purchase | you have Clamsy Pro and are signed in | the Clamsy server, which checks it with Google Play or Apple |
| Currency codes | automatic exchange rates are on | public rate services, or the Clamsy server for a family budget |
| Scanner usage figures (Android) | you scan a QR code | Google (ML Kit) |
| A crash report | you allowed crash reports | Firebase Crashlytics (Google) |
| A backup, a CSV or Excel table | you save or send it | wherever you put it |
| A letter to support | you send it | our mail service at Hoster.by, which forwards it to our Gmail mailbox |
How long each is kept — "How long we keep data" below.
Family budgets
The budget's key is made on the owner's phone and reaches members only in a QR code or an invitation link. Everything in the budget — records, accounts, categories, limits, recurring payments, the budget's name and settings, typed rates and members' names — is encrypted on the phone (AES-256-GCM) before it is sent. The server stores it encrypted and has no key. Each member's phone keeps a readable copy.
What the server sees in plain text, to deliver changes to the right people:
- who is in each budget: the members' account identifiers, who owns it and when each member joined;
- your devices: a random identifier the app makes for itself (not a hardware identifier), the app's build number, and when each device first and last connected;
- for every change: its type (record, account, category, limit, recurring payment, budget mode, member name, budget, exchange rate), its identifier, who made it, whether it is a deletion, and when it was made, edited and received;
- what the identifiers tell: they are built from the phone's clock and a short label (for example rec-…, transfer-…, cat-…, acc-…), so the server can see when each item was created, which records are transfers and which records belong to one recurring payment. A rate's identifier is the two currencies and the day (for example USD:EUR:2026-10-16), a limit's is the month and the category's identifier;
- who added each record first (the server keeps this note, but it no longer limits who can change a record);
- how far each member's phone has received the budget's changes;
- the budget's currency and every currency used in it, when phones ask for the day's exchange rates;
- a note that you left a budget, were removed or the budget was deleted: your account identifier, the budget, the reason and the time.
What other members see. Everything in the budget, the name you give yourself there, your account identifier, your role (owner or member), when you joined, and how far your phone has received the budget's changes (the "received by" marks in the change log). If you leave or are removed, the members see who left or was removed and when, for 90 days.
Invitations. The part of an invitation link after the "#" sign holds the budget's identifier, the invitation code, the key, the budget's name (up to 40 characters) and its currency. Browsers do not send this part to any website; when you join, the app sends only the invitation code to our server. Anyone who sees the link, in a chat or a screenshot, holds the key and can join within 24 hours while there is a free place, so send it only to the people you invite. The server keeps only a fingerprint (SHA-256) of the invitation code, the budget, who created it and when it expires. Without Clamsy installed, the link opens a page (Firebase Hosting, Google) that only sends you to Google Play or the App Store; like any website, it sees your IP address.
Leaving and removal. When you leave or the owner removes you, the server stops sending you the budget's changes, and the records you added stay in the budget. When you leave, the budget is erased from your phone after you confirm; when the owner removes you, it stays on your phone, read-only, until you delete it. The key does not change: what a former member's phone has already received stays on it.
Exchange rates
Personal budget. With Clamsy Pro and "Update rates automatically" on, the app fetches rates once a day when you open it. It asks Frankfurter (api.frankfurter.dev, an open-source service of central banks' rates, running on Cloudflare) for your main currency, the other currencies you use and the dates. If Frankfurter does not answer, the app downloads whole rate tables from the National Bank of the Republic of Belarus (api.nbrb.by), the European Central Bank (ecb.europa.eu) and, for rarer currencies, the open currency-api data set (cdn.jsdelivr.net or currency-api.pages.dev). No request carries an account, a device identifier or an amount, but like any website these services see your phone's IP address — so Frankfurter can tell that someone at that address uses these currencies. Without Pro, or with the switch off, the app fetches no rates for your personal budget.
Family budget. Phones ask the Clamsy server instead, naming the budget, the day, the budget's currency and every currency used in it. The server asks the same public sources with only currency codes and a day, so they see the server's address, not yours. It keeps these public rates with no link to any budget or person and sends members a silent push when new ones arrive. The owner can turn automatic rates off for the budget; then no phone asks.
Account and sign-in
You sign in only to use family budgets.
- Google (Firebase Authentication, Google LLC, USA): Google processes your email address, account identifier, the name and profile photo link of your Google account, and the IP address of the sign-in. The app does not show or use the name or the photo.
- Apple (on iPhone, Apple Inc., USA, through Firebase Authentication): Apple gives the app your Apple Account's identifier and email address, or a hidden relay address if you choose to hide your email. The app asks for nothing else.
With every request the app proves who you are with a sign-in token. Our server reads only your account identifier from it and stores no email address or name.
Purchases
Google Play or the App Store handle installation, updates and Clamsy Pro purchases under their own rules; payment details stay with them. If you sign in, the app sends the Clamsy server the store's proof of your purchase (a free trial is the store's own, part of that purchase). The server asks Google Play or Apple whether the purchase is valid and until when, and keeps the product, the purchase token or transaction identifier, the expiry date and whether it was refunded — so that family budgets open on every member's phone.
Push messages
After you sign in, the app gets a push token from Firebase Cloud Messaging (Google LLC; on iPhone also Apple Push Notification service) and sends it to the Clamsy server with the platform and the device identifier. When a family budget changes or new rates arrive, the server sends your phone a silent message and the app syncs. The message carries only the budget's identifier and the kind of news, and nothing shows on the screen. No push token exists before you sign in. When you sign out, it is deleted on the phone and, if the phone is online, removed from the server; otherwise the server drops it once Google reports it no longer works.
Crash reports
Only if you answered "Send" when the app asked, or turned on "Send crash reports" in Settings. A report goes to Firebase Crashlytics (Google) and contains the type of the error and where in the code it happened, the phone model, the system and app versions and an installation identifier; Google also sees the IP address. It contains no amounts, records, comments, email address or the text of the error, and it is not tied to your account.
Server logs
Google Cloud logs the IP address, time and address of each request to the Clamsy server, to protect it from attacks and failures. Our own server log has no IP addresses and no request bodies, but it records each request's address, which can include a budget's identifier, the account identifier of a member being removed and, for rates, currency codes. The server holds IP addresses only in memory, to limit how many requests come from one address and to block repeated failed attempts.
Support email
If you write to us, we receive your email address and your message. "Contact support" in the app adds the app version, the phone model and the system version to the draft; you can delete them before sending. The app itself sends nothing: the letter goes from your mail app to our address at buckleup.tech; our mail provider Hoster.by (Belarus) forwards it to our Gmail mailbox (Google LLC, USA).
Backups and export
You make backups and CSV or Excel tables yourself and decide where they go: a folder on your phone, your own cloud storage, a message to yourself. We do not receive them.
- A backup holds everything in the app: your personal budget and every family budget on the phone, with its records readable, and the names other members gave themselves. The keys of family budgets are not included.
- A backup is not protected by a password. It is sealed with a key built into the app, the same in every copy of Clamsy: that stops a casual look, but anyone who has the file and Clamsy can open it. Treat a backup like your budget itself: keep it where only you can reach it and do not share it. (Early versions of the app could set a backup password; one set then keeps protecting backups until you remove it.)
- A CSV or Excel table is plain text, comments included. It goes to the app you choose.
- Automatic backup, if you turn it on, saves to a folder: on Android the one you choose; on iPhone the app's own folder (Files → On My iPhone → Clamsy) or one you choose. If that folder is in a cloud storage, that service keeps the backups.
Who receives data
We do not sell your data or share it with anyone beyond the services below. Each of them receives only what is listed here, only to provide its part of the app. Google and Apple provide the same or equal protection of your data as this policy describes: Google Cloud and Firebase process data on our behalf under Google's data processing terms; Google Play, Gmail and ML Kit handle data under Google's own privacy policy, and Apple handles Sign in with Apple, push delivery and App Store purchases under its own privacy policy. The exchange-rate services receive no personal data beyond the IP address any website sees.
- Google — Google Cloud (the Clamsy server and its logs), Firebase Authentication, Firebase Cloud Messaging, Firebase Crashlytics, Firebase Hosting (the invitation and policy pages), ML Kit (the QR scanner on Android), Google Play, and Gmail for support letters.
- Hoster.by (Belarus) — our mail provider: receives support letters sent to our address at buckleup.tech and forwards them to Gmail.
- Apple — Sign in with Apple, Apple Push Notification service, the App Store.
- Exchange-rate services — Frankfurter (on Cloudflare), the National Bank of the Republic of Belarus, the European Central Bank, the currency-api data set (jsDelivr, Cloudflare Pages): currency codes, dates and the IP address of your phone or of our server.
- Members of your family budgets — what you add to a budget, as described above. You choose them.
Where data is stored and transferred
The Clamsy server runs in Google Cloud, region europe-west1 (Belgium, European Union). Google and Apple sign-in, push messages, crash reports, scanner figures and support letters are processed in Google and Apple data centers, including in the USA. A support letter first passes through our mail provider Hoster.by in Belarus, which forwards it to Gmail. The rate services are in Belarus (National Bank), Germany (European Central Bank) and on worldwide networks (Cloudflare, jsDelivr). The USA has its own personal data protection rules, and your rights there are protected differently than in Armenia or the European Union.
By signing in with Google or Apple you agree to your email address, account identifier and your phone's push token being transferred to the USA. Crash reports are sent only after you answer "Send" or turn them on in Settings.
How long we keep data
| Data | How long |
|---|---|
| Your personal budget | on your phone, until you delete it or the app |
| Family budget content | while the budget exists. When something changes, the old version's content is erased at once; its empty row is removed after at least 30 days, at the budget's next change |
| Who added each record first | until the budget is deleted |
| Membership and how far your phone has received changes | until you leave, are removed, delete the account, or the budget is deleted |
| A note that you left, were removed or the budget was deleted | shown to the budget's other members for 90 days, then removed at the server's next clean-up of such notes; removed at once if you rejoin or delete your account |
| Invitation fingerprint | until the owner makes a new invitation, removes a member or deletes the budget; the code works 24 hours |
| Devices and push tokens | the push token — until you sign out (see "Push messages"); devices — until you delete the account (beyond 20 devices, the oldest is dropped) |
| Pro status | until you delete the account |
| Your account identifier on the server | after the account is deleted, the identifier alone stays, with no email address or name, because records in other people's budgets refer to it |
| Sign-in data at Google | until you delete the account, then up to 180 days in Google's backups; the sign-in IP address — a few weeks |
| Firebase installation ID used for push | kept by Google; the app does not delete it |
| Public exchange rates on the server | without a time limit; they are not tied to anyone |
| Server request logs (IP address, time) | 30 days |
| Invitation page visits (IP address) | a few months, by Google |
| Crash reports | 90 days |
| Support letters | until your question is resolved, then deleted within one year |
Deleted data may stay in the database's automatic backups for up to 7 days, until those backups are replaced by newer ones.
Your rights and choices
- View and change your data — in the app.
- Export — a backup, a CSV or Excel table.
- Delete records — in the app; uninstalling the app deletes the personal budget. In a family budget any member can change or delete any record; the budget's change log shows who did it.
- Sign out — Your budgets → Account → Sign out. Family budgets stay on the phone, read-only, until you sign in again; the push token is deleted.
- Crash reports — turn them off in Settings.
- Delete the account — see below.
For questions about your data or requests about your rights (Law of the Republic of Armenia "On Protection of Personal Data", Articles 15, 20 and 21), write to clamsy@buckleup.tech. A request for information about which of your data is processed is answered within five working days. Incomplete, inaccurate or unnecessary data is corrected or deleted within three working days. If you withdraw consent or ask to delete your account, processing stops and the data is deleted within ten working days; we confirm the deletion within three working days after it.
If you believe your data is processed unlawfully, you can complain to the Personal Data Protection Agency of the Ministry of Justice of the Republic of Armenia or to a court.
Deleting your account
In the app: Your budgets → Account → Delete account. The phone must be online; if the server cannot be reached, nothing is deleted and the app says so. Without the app, see the account deletion page.
What is deleted: family budgets you own, for all members; your membership in other people's budgets and the names you gave yourself there; your devices, push tokens, Pro status and notes about leaving; your sign-in in Firebase (with Apple, the app also withdraws its access to your Apple Account). Family budgets are erased from your phone; the personal budget stays.
What stays:
- Records and accounts you added to other people's family budgets stay there, encrypted, under your account identifier with no email address or name. To remove them, delete them in those budgets before you delete the account. An account that an earlier version of the app copied from your personal budget into a family budget is now an ordinary account of that budget, with no balance from your personal records; any member can delete it.
- What other members' phones have already received stays with them, and in their backups and tables.
- Your Clamsy Pro subscription. Deleting the account does not cancel it: cancel it in Google Play or the App Store.
If you are in the European Union or the United Kingdom
We process your data on these legal grounds (GDPR and UK GDPR, Article 6(1)): your account, family budgets, push tokens and Pro status — to provide the service you asked for (point b); crash reports — your consent (point a), which you can withdraw at any time in Settings; server request logs, visits to our web pages, the IP address the rate services see and the scanner figures ML Kit sends — our legitimate interest in keeping the app and the server safe and working (point f); support letters — our legitimate interest in answering you (point f), or the service you use when the letter is about it (point b). We do not receive your personal budget.
Data goes from the European Union and the United Kingdom to the USA under the standard contractual clauses that Google offers. Letters from the European Union and the United Kingdom pass through Belarus only because you send them to us: the transfer is needed to answer your request.
You have the right to access your data, to have it corrected or erased, to restrict or object to its processing, and to receive the data you gave us in a portable form (a backup or a CSV or Excel table from the app; for server data, write to us). Write to clamsy@buckleup.tech; we answer within one month at the latest.
You can also complain to the data protection authority of the country where you live or work, or, in the United Kingdom, to the Information Commissioner's Office (ico.org.uk).
Do Not Track
The app does not track you across other companies' apps or websites, so it has nothing to change when your browser or phone sends a "Do Not Track" signal.
Children
Clamsy is not intended for children under 16, and we do not knowingly collect data about children.
Changes
If this policy changes, the new version will appear on this page with a new effective date. Significant changes — new data, new services, transfer of data to other countries — will be announced in the app in advance, before they take effect.
Contact
Viachaslau Melnik, clamsy@buckleup.tech