RU

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:

  1. "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.
  2. "Notes live on your phone, and — only if you turn on sync yourself — also in the cloud."
  3. "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.
  4. "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

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:

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:

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:

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:

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.

What we processGDPR 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 contentExplicit 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 contextSame, plus a separate explicit consent (separate toggle)
Exchange ratesNo 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:

RecipientWhat it receivesRegionWhy
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 syncThe 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-inGoogle's serversAccount sign-in
Resend (Resend, Inc.)Email address and the six-digit sign-in codeUSA (company), sending — Ireland, EUSign-in code email
open.er-api.comNothing personal — our server only requests a currency code—Currency exchange rates
Cloudflare TurnstileA technical browser token — only on the website (the account-deletion page, brymble.app/delete-account); not used inside the app itselfCloudflare's networkBot protection for code requests/deletion on the website
RevenueCat and Google Play BillingNothing 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:

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

WhatWhereHow long
Notes, tasks, finances, chat historyOn the phoneUntil you delete it — no expiry, no automatic clean-up
Text sent for parsing / a chat messageServer (Supabase, Gemini)Not stored — in transit only
AI request counterServer7 days, then deleted automatically
Reports on AI repliesServerup to 90 days, then deleted automatically; sooner if the account is deleted
Sign-in sessionPhone's secure storageUntil 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)Server90 days — a technical safeguard so multi-device sync doesn't accidentally "resurrect" something you deleted; purged afterwards
Sync consentsServerAs long as the account exists; cascade-deleted with the account
The account itselfServerUntil 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:

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:

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

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.