Document
Privacy Policy
Effective from 24 September 2026 · Brymble for Android
Brymble is an external brain for people with ADHD: you say whatever is on your mind, and the app sorts it into tasks, events, ideas, notes and — if you allow it — helps with money and answers in chat. A log of your thoughts and feelings is deeply personal, so this page is written plainly, without legal fog: what stays on your phone, what leaves it, to whom, why, on what legal basis, and how to erase all of it.
Brymble is not a medical product. It does not diagnose, does not treat, and does not replace a living professional.
Who processes the data
Developer and data controller: Adilkhan Zhussip, a private individual, Italy. For any question about your data: brymble.app@gmail.com. We reply within 30 days.
If you have a concern we could not resolve, you may contact the supervisory authority in Italy, Garante per la protezione dei dati personali (www.garanteprivacy.it), or your own country's supervisory authority within the EU.
Short version: four promises
These four sentences hold true at the same time in the app, on this site, and in the Google Play Data safety form:
- "We do not record audio." Brymble never stores sound; speech is recognised by the Android system service (on most phones, Google's), under its own rules.
- "Notes live on your phone, and — only if you turn on sync yourself — also in the cloud."
- "Never sold, never used to train someone else's model." Parsing and chat run only on Google Gemini's paid tier, where Google does not use submitted data to train its models. There are no ads, trackers or analytics in the app.
- "Until you turn sync on, your notes stay on your phone only. The only things that leave are the text you send for parsing, and whatever you type into the AI chat (together with the task and note context, if you agreed to share it) — in transit, never stored on our servers."
"Delete everything" remains a verifiable action at any time: without sync it wipes the phone; with sync on, you choose "wipe this phone" or "wipe everywhere"; the whole account can be deleted in the app or at brymble.app/delete-account.
Three modes of use
- Phone-only (default, no account). Everything — notes, tasks, emotions, finances — lives in an encrypted database on your phone. What leaves is exactly what sections 4–6 describe (parsing, chat, exchange rates) — in transit, never stored server-side.
- With an account, without sync. Same as above, plus your email address (or Google ID) and your sign-in session — so you can turn on sync or delete your account remotely. The content of your notes does not reach the cloud until you enable sync separately.
- With sync (Plus tier, separate consent). A copy of part of your content is stored on our server in the EU — see section 8.
Parsing your notes: text goes to Gemini
When a recording is finished, the app checks it for signs of crisis right on the phone (section 13), then sends the text of the note to our server function (Supabase, Frankfurt — section 10), which forwards it to Google Gemini on a paid tier. Gemini returns a breakdown: what is a task, an event, a note, an idea, an emotion or a money entry here; it also flags signs of self-harm-related thoughts.
Sent along with the note text:
- up to eight short fragments of your past category corrections (text ≤160 characters + category) — so parsing learns from how you fix its mistakes;
- a random installation identifier (16 random bytes generated on the phone, not tied to you, your phone number or hardware) — to count the daily AI request limit (shared between parsing and chat). Right now the limit is counted only by this identifier, even if you're signed in: tying the limit to your account itself isn't in place yet;
- with voice-entered money on: the same text, additionally typed as "money" (amount, currency, direction, category hint).
The text is in transit only: neither our server function nor our database stores it — only a request counter (section 12). Parsing runs on Gemini's paid tier precisely because on that tier Google does not use submitted data to train its models (Google's terms).
You make the decisions: parsing is a suggestion, not a command, any mistake can be fixed by hand, and the app makes no automated decision with legal or similarly significant effects on you (GDPR Art. 22 does not apply here — the only "decision" the AI makes, sorting a note into a category, always needs your confirmation on the review screen).
AI chat: messages and context
In chat you can ask Brymble about your day, ask it to draft a plan, or create a task. Every message is first checked for crisis signs on the phone; if the app proceeds, the message and context go to our chat server function, which forwards them to Google Gemini on the same paid tier as parsing.
The first time you open chat, you're asked for a separate consent. If you agree:
- Gemini receives your messages (up to the last 20, each ≤2000 characters) and context — your tasks and notes (titles, dates, completion status) over a reasonable date window, excluding emotions and crisis entries, which never enter chat context at all;
- a separate toggle in chat settings can additionally include finance — only this month's totals and up to five largest categories (no individual transactions, no account names, no transaction notes) — with its own separate consent;
- if you didn't consent to context, chat replies without it — it sees neither tasks nor notes.
Any reply and any proposed action ("Create task", "Plan the day") only apply after your explicit confirmation on a card. The conversation is stored on your phone only and never syncs, even with sync turned on; you can erase it any time ("Clear conversation" in the chat menu) — the same way "Delete everything" clears it.
If a reply seems unacceptable, you can flag it right in the app — a long press on the reply's bubble (or a separate TalkBack action, since a long press isn't discoverable blind) opens a "Report this reply" sheet. Submitting a report sends us only the text of that one reply, the reason you picked, an anonymous device identifier, and your account identifier if you're signed in — the rest of the conversation and your own messages are never sent. The report is kept for up to 90 days and deleted sooner together with your account (section 12, "Retention periods").
Finance and exchange rates
Accounts, transactions, limits and categories live on your phone (and in the cloud if sync is on, section 8). To convert between currencies, the app asks our own exchange-rate server function once a day, which in turn fetches rates from a public source (open.er-api.com). This request carries no personal data — no note text, no device identifier, no account balances: only a currency code. Source attribution ("Rates By Exchange Rate API") is shown next to converted amounts, per that source's terms of use.
Account: email or Google
An account is not required — the app, including parsing and chat (within the free limit), works fully without one. An account only matters for syncing across devices.
Two sign-in methods:
- Email, six-digit code — we send the code through a third-party email service, Resend (Resend, Inc., USA; emails are sent from its server in Ireland, EU);
- Google — via Google's own system sign-in screen (Credential Manager). We only receive your email address and account identifier, which we need to sign you in; the app never requests or stores your Google profile name or photo.
The sign-in session is kept in the phone's secure storage (not in ordinary app settings) and is excluded from Android backup.
A demo login for the Google Play reviewer (the only password-based account) is set up manually and is for review purposes only, not for regular users.
Sync (Plus): two levels of consent
Sync is a paid feature (Plus tier and above) and entirely your choice. It stores a copy of part of your content on our server — Supabase, Frankfurt region, European Union — so you can see it on a second phone or (later) in a web companion.
There is no end-to-end encryption. Data is protected at the access level (row-level security — you only ever see your own rows) and by disk-level encryption at Supabase, but technically our server could read what you choose to send. We don't do that in routine operation — but claiming technical impossibility of access would not be true.
Consent applies to the whole account: give it on one phone, it applies on the others too; revoke it, and sync stops everywhere. There are two independent levels:
- Level ① — tasks, events, ideas, notes, steps and finances. Titles and structure travel: task text, dates, amounts, categories. The verbatim text of what you dictated or typed does not travel — a note syncs as metadata only.
- Level ② — a separate checkbox, only available together with or after ①: verbatim note text and emotions. This is data about your emotional state — legally, health data (GDPR, Art. 9). It needs a separate explicit consent, taken with its own checkbox rather than folded into a general statement.
What never syncs, at any level: crisis entries; AI chat history; the app's panel layout; drafts and unparsed notes.
You can uncheck level ② at any time — verbatim text and emotions are then deleted from the cloud on every device (they stay on the phone). You can turn sync off entirely, choosing to keep the cloud copy of tasks/finance or wipe it too. Deleted content is kept in the cloud for a limited time in case of error (section 12), not indefinitely.
Legal bases for processing
| What we process | GDPR basis |
|---|---|
| Parsing note text (in transit to Gemini) | Performance of a contract (Art. 6(1)(b)) — a feature you invoke yourself, plus explicit consent given at onboarding |
| Parsing notes that happen to contain emotional or crisis-adjacent content | Explicit consent (Art. 9(2)(a)) — the same onboarding checkbox for sending text to Gemini; not stored |
| AI request counter (device/account identifier, date, count) | Legitimate interest (Art. 6(1)(f)) — abuse protection, minimal data, 7-day retention |
| AI chat: messages and context (tasks, notes) | Performance of a contract (Art. 6(1)(b)) + explicit consent to context (separate checkbox on first chat open) |
| AI chat: finance context | Same, plus a separate explicit consent (separate toggle) |
| Exchange rates | No personal data — outside GDPR (aside from Supabase's own infrastructure-level logs) |
| Account (email or Google ID) | Performance of a contract (Art. 6(1)(b)) — needed for sign-in and sync, which you request yourself |
| Sync, level ① (structure: tasks, finance) | Explicit consent (Art. 6(1)(a)), revocable at any time |
| Sync, level ② (verbatim text, emotions) | Explicit consent for a special category of data (Art. 9(2)(a)), separate checkbox, revocable at any time |
| Subscription (once enabled) | Performance of a contract (Art. 6(1)(b)) — billing and subscription management |
Recipients and subprocessors
The complete list of who receives your data:
| Recipient | What it receives | Region | Why |
|---|---|---|---|
| Supabase (database and server function hosting) | Text sent for parsing/chat — in transit, not stored. Request counter. With sync, content per your consent. Email and session on sign-in. | Frankfurt, EU for accounts and sync created from September 2026 onward. People still on old app builds (0.1.3/0.1.4 from Google Play), until phased out, keep reaching the old project in US, Ohio — parsing only, no accounts or sync | The app's core server |
| Google Gemini (Google LLC) | Note text or chat messages (and context, if consented) — in transit, not stored, not used to train models (paid tier) | Google's servers (see section 11) | Parsing and AI chat |
| Google Sign-In (Google LLC) | Email address, Google account identifier — if you choose Google sign-in | Google's servers | Account sign-in |
| Resend (Resend, Inc.) | Email address and the six-digit sign-in code | USA (company), sending — Ireland, EU | Sign-in code email |
| open.er-api.com | Nothing personal — our server only requests a currency code | — | Currency exchange rates |
| Cloudflare Turnstile | A technical browser token — only on the website (the account-deletion page, brymble.app/delete-account); not used inside the app itself | Cloudflare's network | Bot protection for code requests/deletion on the website |
| RevenueCat and Google Play Billing | Nothing yet — subscriptions are disabled; everyone is on the Free tier. They will start receiving data once paid subscriptions are switched on | — | Will apply once paid subscriptions launch — this section will be updated at that point |
Nobody else. No ad networks. No analytics. No in-app crash reporting. We do not sell your data and do not pass it to third parties, for money or for free, beyond what's listed above, and only to the extent needed for the feature you chose to use.
Transfers outside the EU
Our main server (Supabase) is in the EU (Frankfurt). Two recipients are not:
- Google Gemini and Google Sign-In — processing happens on Google's infrastructure, which may extend beyond the EU.
- Resend — a US company; sign-in code emails are sent from its server in Ireland, EU.
Transfers happen under these companies' data processing agreements (DPAs).
People on old app versions (0.1.3/0.1.4), until they update or are phased out on Google Play, still reach the server in US, Ohio — effectively a cross-border transfer for everyone still on them; see also section 17 on Russia and Kazakhstan.
Retention periods
| What | Where | How long |
|---|---|---|
| Notes, tasks, finances, chat history | On the phone | Until you delete it — no expiry, no automatic clean-up |
| Text sent for parsing / a chat message | Server (Supabase, Gemini) | Not stored — in transit only |
| AI request counter | Server | 7 days, then deleted automatically |
| Reports on AI replies | Server | up to 90 days, then deleted automatically; sooner if the account is deleted |
| Sign-in session | Phone's secure storage | Until sign-out or app uninstall |
| Synced content (level ①/②) | Server (Frankfurt) | Until you revoke consent, turn off sync with cloud wipe, or delete your account |
| What you deleted (tombstone) | Server | 90 days — a technical safeguard so multi-device sync doesn't accidentally "resurrect" something you deleted; purged afterwards |
| Sync consents | Server | As long as the account exists; cascade-deleted with the account |
| The account itself | Server | Until you request deletion — then erased immediately (in-app or on the website) |
We do not promise an automatic deletion of an "inactive" cloud copy after a set period — no such mechanism exists right now. If it is built later, this policy will be updated together with it, not ahead of it.
Crisis entries
If a note or chat message shows signs of thoughts of self-harm, the app shows a card with helpline numbers. Those signs are looked for in two ways: the phone itself checks the text against a list of explicit phrases (works offline), and Gemini additionally flags them during parsing/chat. The crisis flag stays on the phone only: it never syncs at any consent level, never enters chat context, is never exported as a separate marker, and alerts no one. A crisis entry never becomes a task.
If you're struggling right now, please reach out to a professional or a crisis line in your country: 112 (the shared emergency number across the EU, Russia and Kazakhstan), national helplines, or the directory at findahelpline.com.
Subscriptions
There are currently no paid subscriptions — purchasing is disabled in the app. Once subscriptions launch:
- cancel in one tap, through Google Play's Subscriptions section;
- advance notice before any charge, not after;
- no retention tricks or pleading at the moment of cancellation;
- cancelling a subscription does not delete your notes — they stay on your phone (and in the cloud, if that was your own deliberate choice — section 8).
Age
The app is intended for people 18 and over. Consent is confirmed with an explicit checkbox at first launch. We deliberately do not collect children's data and do not design the product for them.
Your rights
Under GDPR and generally, you have the right to:
- access and a copy of your data — the "Export everything" button in the app hands you a file with all your content immediately, without asking us;
- rectification — right in the app: any note, category or amount can be fixed by hand;
- erasure — "Delete all notes and tasks" on the phone; "Delete account" in the app or at brymble.app/delete-account for the cloud part;
- withdraw consent — separately for parsing (uninstall), for chat context (chat menu), for each sync level (the "Sync" section in settings) — at any time, no explanation needed;
- restriction and objection — write to us and we'll look at your specific case;
- data portability — export is already machine-readable JSON;
- lodge a complaint with a supervisory authority — Garante per la protezione dei dati personali (Italy, www.garanteprivacy.it) or your own EU country's authority.
Because most of your data lives on your phone rather than with us, you exercise most of these rights yourself, in the app, without asking anyone's permission.
Russia and Kazakhstan
If you use Brymble from Russia or Kazakhstan: those countries' data localisation laws (Federal Law 152-FZ in Russia, Kazakhstan's law on personal data) generally require certain personal data of their citizens to be processed using databases physically located in that country. Brymble's server is in the European Union (Frankfurt), and some people on older app versions reach a server in the US. This means personal data (your email on sign-in, your content if you sync) is physically stored outside Russia and Kazakhstan.
Brymble does not claim compliance with 152-FZ or Kazakhstan's personal data law — we only describe honestly where the data physically sits, and that signing in or turning on sync is an explicit choice to send it to the EU/US.
If you don't create an account and don't turn on sync, the only thing that leaves your phone about you is an anonymous device identifier for the request counter (section 12); localisation doesn't come into play, because there's no personal data to localise.
The website (not the app)
Separately from the app, this website (brymble.app):
- loads fonts from Google's servers (Google Fonts) — visiting any page makes your browser contact Google's servers, standard web practice but technically a transfer of your IP address to Google;
- uses Cloudflare Turnstile on the account-deletion page — a bot-protection widget that processes a technical browser token to tell a human apart from an automated request;
- the waitlist stores an email address, platform and a note up to 500 characters in a separate Supabase table; the site's public key can only add rows, not read the list.
Changes
If what leaves the app and where it goes changes, we'll update this page and the date at the top, and surface material changes inside the app as well. Earlier editions are available on request at brymble.app@gmail.com.
Contact
brymble.app@gmail.com — any question about your data, answered within 30 days.