Privacy and security

Українською

Updated 2 November 2026 · Version 8

This page says what data Brain Buffer needs, where it goes and how long it lives. "In development" means a feature doesn't exist yet or hasn't been verified: a plan is not a promise, and we don't pass one off as the other.

In short

1. Who is responsible for your data

The service is provided, and your personal data handled, by ФОП Ощипок О. В., Україна.

You can download a copy of all your data yourself: on the web — Settings → “All my data”, in the Telegram bot — the /mydata command. Questions and requests for a copy or deletion of your data: privacy@telegramaireminder.com. We reply within 30 days.

A dedicated "Data request" item in the app, on the website and in the bot is in development.

2. What we collect, why, where and for how long

DataWhyStored at / sent toHow long
Account: name, email, handle, Telegram id and username, Google id, language, time zonesign-in, notifications, family invitationsour database (Supabase, EU)while the account exists
Password, if you set onesign-inonly an Argon2id hash in our databaseuntil you change it or delete the account
Your messages, bot replies, history of fired remindersthe core of the service: one history across app, web and botour database; message text goes to Anthropic (USA) for parsingwhile the account exists. Choosing a period (1, 3 or 12 months) and automatic cleanup are in development
Reminders, notes, timetables, coursesthe core of the serviceour databaseuntil you delete them. A deleted reminder (and a one-off that has fired) disappears from every list at once and is erased from the database 30 days later; so is a deleted timetable or course, with its lessons (lesson notes stay in your notes archive). Notes are not deleted but archived: you can restore them, and they go with the account
Photos and files: timetables, pictures and files in chatread the document and create remindersAnthropic (USA) for reading; our databaseas you choose: don't keep, 30, 90, 365 days, or forever (365 days by default). A photo in a note is kept as long as the note
Saved places: name, coordinates, radius, Wi-Fi and Bluetooth hashes, NFC tag idsso places work on all your devicesour databaseuntil you delete the place; a deleted one is erased from the database 30 days later
Current position for "near a supermarket / fuel station / ATM…" remindersfind the nearest such placesour server; where we hold no copy of the OpenStreetMap data (currently outside Ukraine), also the Overpass servicenot written to your account — the position lives in the server's memory for the length of the lookup. Your history keeps a record of the fired reminder with the place name and distance
Movement type, battery level, charging, steps; the Wi-Fi network name only from an app older than 1.0.31 or as a condition of another reminderfire the matching remindersour servernot stored if nothing fires; a fired reminder goes into your history
Google Calendar events: title and time, up to 50 events at a timereminders for eventsour databaseonly if you turned sync on; stored as ordinary reminders
Family: members, names, invitations (the invitee's email, handle or Telegram), messages and reactionsshared remindersour database; names also go to Anthropic as context for the modelwhile the family exists or you're in it. An invitation lasts 7 days, a six-digit code 7 days
Requests to send no more invitations (the link in an invitation email)never write to that address againour database — only a hash of the address, not the address itselffor as long as the request stands
Notification tokens (Firebase, Web Push)deliver notificationsour database; Google Firebase; your browser's push servicewhile the token is valid on the device
Payments: plan and Premium expiry date; a record of each payment — amount, plan, date, Telegram payment idPremium; refunds; tax recordsour database; Telegram (Stars)the plan — while the account exists; payment records — 3 years and 3 months, also after the account is deleted: Ukrainian tax law requires it (Tax Code, Art. 44.3)
App technical data: version, CPU architecture, update result, enabled featuresupdates and supportour databasewhile the account exists
Acceptance of the Terms of Use: the version, the date, where from (app, website or bot), the app version, the languageto know which terms you use the service underour databasewhile the account exists
Phone key: a hash of the identifier Android gives this app on this phone (the phone does not send the identifier itself). A hash makes recovery harder, but not impossibleso free requests to the assistant are counted per phone rather than per new account; protection against abuse. Not for advertising and not to recognise you in other appsour databasewhile the account exists
Failed sign-ins: address, IP, browserprotection against password guessingour database, the admin's audit log90 days, then deleted automatically
Server technical logsfixing bugsFly.io (Sweden)they hold no message text. Fly.io keeps them for 7 days; a single line cannot be taken back out of them
Encrypted tester recordsfixing bugs during betaour databaseup to 14 days (section 8)
Feedback you send (the "Feedback" form in the app and on the website, /feedback in the bot) and reports about a bot reply — with that reply and your commentreply and fixour database; the feedback text also arrives in the developer's Telegram (for a reply report, only a notice that there is one)in the database — while the account exists; the developer deletes the Telegram copy by hand
"Report a problem" (app, website, /problem in the bot): your description; app version, phone model, Android version and permission states; the technical log only if you switch it on after seeing its full text (place checks, fired reminders, the movement type behind automatic quiet mode and app errors — without coordinates, place or network names). On the website, browser details — also only if you tick the boxfind and fix the problemour database, encrypted; the developer's Telegram gets only a notice that a report arrived, without its text30 days from sending; at once when the account is deleted
Emails: sign-in links, invitations, email changesdeliveryour mail service (currently Resend)the mail service keeps a letter's data for 30 days; we keep no archive of sent mail. The address a link was sent to is kept while the link is valid, plus a day
Messages a business sends you through our API (if you are its customer): the text and your Telegram numberdelivery and the business's recordsour database90 days
Language-model cost records: the cost of each call, no textbilling and spend controlour databaseamounts — no end date; after 12 months they are no longer linked to your account
Letters you write to our address: sender, subject, textreply to you; sort out spam; briefly label what the letter is about (a category and a one-line summary) — done by Anthropic's language modelour database; the letter's text goes to Anthropic (USA) for the label; the developer gets a Telegram notice with the sender's address, the subject and that one-line summary (not for spam)in the database — 12 months from arrival, then deleted automatically; the developer deletes the Telegram notice by hand

We don't collect phone numbers.

Inactive accounts. We don't delete an account just because you haven't signed in for a while: yearly reminders have to keep working.

Backups. Every night we make an encrypted copy of the database (without the map reference data) and keep it for 14 days in private Supabase storage (EU); older copies are deleted automatically. So what is deleted from the database may remain in these copies for up to 14 days. We use them only to restore the database after a failure — and then we delete again the accounts their owners deleted after the copy was made: for that, an encrypted list of deleted account numbers sits beside the copies for 14 days.

Legal basis

Anthropic, Google and our mail service (currently Resend) are in the USA, so some data leaves Ukraine and the EU. Transfers to Anthropic are protected by the EU Standard Contractual Clauses (Commission Decision 2021/914) built into its data processing agreement; Anthropic is not part of the EU-U.S. Data Privacy Framework. Google and Resend are certified under the EU-U.S. Data Privacy Framework, and Resend's data processing agreement also includes the Standard Contractual Clauses. For people in Ukraine the transfer is also needed to perform the contract: having the model read your messages is the service. OpenWeather and the OpenStreetMap Foundation operate in the United Kingdom, covered by the European Commission's adequacy decision. You can ask us for a copy of the Standard Contractual Clauses — contacts in section 1.

3. Location

Saved-place reminders ("when I get home")

"Near a supermarket, ATM, fuel station…"

Other sensors

4. Family

A family shares reminders, not location.

Your family sees

Your family does not see

A reminder tied to a place (or to a Wi-Fi network, a Bluetooth device or an NFC tag) that a family member set for you: the author does not see whether or how often it fired, nor your reaction to it. Honestly, what remains: if you mark it done, the author is told, unless you switched that off in your family settings ("When I mark a reminder done"); a one-off reminder disappears from their list once it has fired. You can delete or pause such a reminder — the author learns only that.

Rules

Sharing by link — not only with family

You can give out a link to your timetable or a reminder. Whoever opens it sees its text — as it is in your account right now — and can take a copy of their own. The link page does not show who shared it. The link works until you stop it; copies already taken stay with the people who took them. You are shown only how many times it was viewed and copied. We keep who took a copy only so that nobody gets two — that is never shown to you.

5. The language model and voice

6. Prescriptions and medical documents

Brain Buffer is not a medical app and does not process medical data. We don't read prescriptions, doctor's orders or other medical documents from photos.

Brain Buffer is not intended to be a medical device and does not give medical advice. If a reminder you set differs from your doctor's prescription or the medicine leaflet, the prescription and the leaflet are right.

7. Why a reminder might not arrive

Brain Buffer is an assistant, not a supervisor. We work to make reminders arrive on time, but we can't guarantee it: they travel through your phone, browser, Telegram and notification delivery services. A reminder can be late or not arrive when:

For anything your health, safety, money or deadlines depend on, keep a second way: an alarm, a person nearby, a written schedule.

8. The current period: beta testing and detailed records

This section describes what happens right now, while beta testing is running. When it ends we'll remove this section and delete what it collected.

To find and fix bugs quickly we need the text of real messages. But it is collected from a few people only, and kept in one place:

How long: each encrypted record lives no longer than 14 days, and a phrase in the not-understood list 14 days from the last time it came up. A daily job deletes them, not a person.

Until 3 October 2026 the rules were weaker: phrase digests and reaction texts arrived in the developer's Telegram. Automatic deletion can't reach there, so the developer deletes those messages by hand.

If you are not a tester, your messages never reach these records. A tester can stop testing at any time: no new records are made, and the existing ones can be deleted on request before the window ends.

9. After release: diagnostics and testing

The one-off "Report a problem" already works — it is described in section 2. The rest of this section is in development: it's described here so you can see where this is going, not to promise that it already works.

10. Who else receives data

We pass data to the services Brain Buffer runs on:

ServiceWhat it receivesWhyWhere
Fly.ioall traffic to the server, technical logshostingSweden (Stockholm)
Supabaseeverything we storedatabaseEU
Cloudflaretraffic to brainbuffer.me and telegramaireminder.com; letters you write to our addresswebsite delivery and protection, mail forwardingglobal network
Anthropicmessage text, document photos, context for the model (place names, family names)language modelUSA
Googlenotification text (Firebase); Google sign-in; the text of reminders the app writes into your Calendar if you enabled syncnotifications, sign-in, calendarUSA / global
Telegrammessages to the bot and its replies; Stars paymentsbot, paymentsper Telegram's own rules
Resendemail address and email textsign-in, invitation and email-change emailsUSA
OpenStreetMap: Overpass (FOSSGIS)coordinates for place search — only where we hold no copy of the data (currently outside Ukraine)placesGermany (EU)
OpenStreetMap: map tiles (the OSM Foundation)your IP address and the map tiles you viewthe mapUnited Kingdom; delivered by a global network
OpenStreetMap: Nominatim (OSMF) and OSRM (FOSSGIS)your city's name — to work out the time zone and the weather; the name of the city you are heading to — for a "N km before the city" reminder (once, when you set it); for a "N minutes before I arrive" reminder, the starting point and the destinationcity, "N km before a city", travel timeUnited Kingdom, Germany
OpenWeathercity nameweather remindersUnited Kingdom
Your browser's push service (Google, Mozilla, Apple)an encrypted notificationweb notifications—
jsDelivryour IP address when a page loadsthe map library in the web appglobal network
accounts.google.com, telegram.orgyour IP address and browser details when the sign-in page loadsthe "Sign in with Google" button, Telegram sign-inUSA / global

This is the list as it stands today, and it can change: a service may get more expensive, become unreliable, or stop fitting, and we will replace it. The current list is always here, on this page. If a replacement materially changes where your data goes — to another country, say — we tell you in advance, as with any other change to the terms (section 17). The only change we make without notice is one that sends data to the same place or closer — from someone else's server to our own, for instance.

There are no ads and no third-party analytics trackers now, either on the website or in the app. If an ad network is ever added, it will appear in this list before it receives any data (section 11).

Maps, place search, routes and time-zone boundaries rely on OpenStreetMap data: © OpenStreetMap contributors, licensed under the ODbL, https://www.openstreetmap.org/copyright. The time-zone boundaries come from the timezone-boundary-builder dataset via the timezonefinder library; our server works out a time zone from coordinates by itself, without asking any other service.

The developer has access to the server and the database. While investigating a hard bug he may use development tools that display data from the database — in which case the service those tools run on sees that data too.

11. Ads

There are no ads in Brain Buffer now. If we add them, it will only be through an update to these rules, announced in advance (section 17).

12. Security

What we do

What's not there yet

What you can already do

13. Data and storage

Available now: choose how long photos are kept (don't keep, 30, 90, 365 days, or forever; 365 days by default); download a copy of all your data; delete an individual reminder, note or place; delete the account with all its data.

In development — a "Data and storage" screen in the app and on the website:

If you delete your history, your family members keep their own copies of the messages you sent to the family chat.

What deleting the account does not remove

If you created the family, it passes to the member who has been in it longest.

14. Your rights

You can:

How we confirm a request is yours. A request sent from the app, website or bot where you're already signed in counts as yours. We'll ask you to confirm deleting an account once more. You download a copy of your data yourself; if you ask for it by letter, we first make sure the letter is from the account's owner. We don't ask for copies of documents. Our reply doesn't reveal whether an account exists for an address.

15. Children

The service is for people aged 13 and over. If you are younger than 16, you may use it with the permission of a parent or guardian. That rule comes from the Terms of Use.

We don't ask for your age and we don't verify it — we have no way to confirm it, and we won't collect documents or anything else about you in order to try. So it is a rule, not a check: Brain Buffer is not aimed at children, we don't make it attractive to them, and we don't work out how old you are from what you write.

An adult can add a child to their family and set reminders for them. There are no "parent" and "child" roles in the service: every family member has the same rights, and a child sees and can do the same as everyone else.

16. Data from Google

You can use Brain Buffer with a Google account in two ways. Both are optional.

Where it goes: our database and hosting, to provide these features. Imported events are not sent to the language model. We do not sell data from Google, do not use it for advertising, and do not use it to train AI models — ours or anyone else's.

Brain Buffer's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

How to stop: disconnect the calendar in the app's settings — this also removes Brain Buffer's access at Google (reminders already made from events stay until you delete them); or remove the access at https://myaccount.google.com/permissions; deleting your account deletes the Google id, the email and the reminders made from events.

17. Changes to these rules