bre — Privacy Policy
Last updated: 10 November 2026
The short version
bre turns a topic you type or speak into a podcast with AI hosts.
- Your episodes are written on our servers, by an AI model. Your topic — and what you say when you talk an idea through with bre — is sent to us and on to Anthropic, who write the script.
- To make the episode you hear, the lines the hosts speak are turned into audio by bre's own voice models, on computers we rent for the purpose.
- The file you attach never leaves your phone; the words in it do. bre opens a text or Markdown file on your device, takes the text out, and sends that text and the file's name with your topic. The file itself, and every other file on your phone, stays where it is.
- A photo works the same way. If you add a photo of a page, notes or a whiteboard, bre reads the words in it on your phone — with Apple's text reader on an iPhone, Google's on Android — and sends only those words and a name such as "Photo · Sep 30". The picture is not sent, and it is deleted from the app as soon as it has been read.
- Your library lives on your phone. Your episodes, notes, highlights and the episodes you save are kept in the app on your device, and signing in does not copy them anywhere. To make an episode, though, our server writes the script and turns it into audio, and keeps them only as long as §5 says. If you turn on bre's memory, our server keeps a short record of what you listened to, asked and highlighted — never your notes or the episodes themselves (§2.6).
- bre's memory is off unless you turn it on. You can see everything it holds, delete any of it, or turn it off, at any time.
- No advertising and no tracking. bre carries no ads and no analytics of our own, and does not follow you across other apps or websites. Two outside services work inside the app: Sentry, which tells us when the app crashes (you can switch it off, §2.4), and RevenueCat, which confirms which plan you have paid for (§4). We do not sell or share your personal information, and we never have. (On Android, the text reader that reads a photo also reports anonymous diagnostics to Google, and only when you add one: §2.4.)
- We do not use your content to train AI models, ours or anyone else's.
- Everything bre says is synthetic, and it is labelled as such — in the audio files themselves, and by bre saying so at the start of every Talk (§3).
- Stories collects no personal information from a child. A parent or guardian runs it on their own account; the child only listens (§9).
The rest of this page is the detail.
1. Who we are
bre is operated by BRE LLC, 701 Market St Ste 110 PMB 1342, Saint Louis, MO 63101, USA.
For anything about this policy or your data, write to support@askbre.app.
If you are in the UK or the EEA, BRE LLC is the controller of the personal data described here.
The EU and the UK
bre is not offered in the European Union or the United Kingdom yet. Before it is, we will appoint a representative in each, as the law requires, and name them here.
2. What bre collects, and why
We have tried to keep this list short by not collecting things. Everything we do collect is below.
2.1 Things kept on your device
These are kept in the app on your phone:
| What | Why it exists |
|---|---|
| The files you attach, as files | bre reads them here; the file itself is never uploaded |
| The photos you add, as pictures | bre reads the words in them here and deletes the picture from the app straight after; the picture is never uploaded |
| Your library: episodes, their scripts and transcripts | So you can play them again. The script is written and the audio made on our servers, which keep their copies only as §5 says; signing in does not copy your library anywhere |
| Notes, highlights and bookmarks | Your own marks on an episode |
| Which episodes you saved, and playback positions | To keep your shorter list and resume where you stopped |
| Settings and preferences | So the app behaves how you set it |
They are stored in the app's own storage on your phone. Deleting the app deletes them. We cannot read them and we cannot recover them for you.
The one exception is bre's memory, only if you turn it on: then the words of a line you highlight or bookmark, the questions you ask the hosts, and how far you got through an episode are also kept on our server so later episodes can build on them (§2.6). Your notes never are.
2.2 Things sent to bre's servers
| What | Why | How long we keep it |
|---|---|---|
| Your topic | To write the episode | Kept only while your episode is being made or waits in line — at most three days — and for up to 30 minutes after, so the app can pick the episode back up if the connection drops; then deleted. Two exceptions: the research cache may keep the words of your topic, with what bre gathered from the public web for it, for up to about 24 hours (§3, §5); and memory, if you turn it on (§2.6) |
| What you say when you talk an idea through with bre, as text | So bre can answer you and plan the episode with you | Not stored: each turn is answered and dropped — unless memory is on, when bre keeps anything you ask it to remember and one line about the episode you planned (§2.6) |
| The country set as your phone's region: two letters, such as "US". It comes from your phone's region setting, not from where you are: bre does not work it out from your location or your network address | To show the right crisis line if you need one. Sent with each Talk turn and with each question you ask during an episode | Used for that one request and not stored. Where bre has a crisis line for your country, the country's name is included in what is sent to Anthropic for that turn |
| The name you asked the hosts to call you, and the interests you picked (if you gave them) | So the hosts can use your name now and then, and pick examples you'll care about. Not sent for Stories episodes | Used for that episode or conversation only. With an episode, kept exactly as long as your topic is (above), then deleted |
| The text of a file you attach or a photo you add, and its name | To write the episode from your own material | Kept exactly as long as your topic is (above), then deleted. Memory never keeps a word of it |
| What bre remembers about you — stored on our server, only if you turn memory on | So each episode builds on the last; read by Anthropic's model when bre writes for you (§2.6) | Each item 12 months after it was last updated, or until you delete it, turn memory off and choose to delete it, or delete your account |
| What you agreed to, and when: the version of these terms, this policy, the AI notice and the memory setting you accepted or withdrew | So we can show what you agreed to, and ask again when the words change | While your account exists |
| The lines your hosts speak | To turn them into audio | See §5 |
| Your account identifier | To know whose plan is being used | While your account exists |
| Whether you are under 18 (yes or no; never your age or birth date) | To apply bre's rules for under-18s: memory stays off, and episodes and Talk follow stricter content rules | While your account exists |
| Your phone's time zone | Your phone's time zone is sent with each request, not stored, to show times where you are and, if we turn on a daily limit, to find your local midnight. | Not stored |
| Your language setting in the app, when it is not English | So the hosts write and speak in your language. Sent with the request | Kept with the usage count for that episode, as long as usage counts are (§5) |
| The children's age band you set for Stories (2-4, 5-7 or 8-10) | So a story suits the child's age. The setting itself stays on your phone | Sent with each Stories episode and kept exactly as long as your topic is (above), then deleted |
| Your plan and its renewal date | To give you the plan you bought. Apple or Google takes the payment; bre never sees a card number. Our billing service, RevenueCat, tells our server which plan is active (§4) | While your account exists |
| What you write to support — in the app, or by email to support@askbre.app — and the email you give us to reply to | To answer you. Software, and sometimes an AI model, reads each message to sort it by topic and urgency. A message from the app is answered by a person. An email may be answered by our AI assistant, which says so in the reply; a question about a refund, a cancellation or a bill gets a fixed automatic reply with the steps for your store. Messages about deleting your account, your privacy, safety, a disputed charge or the press are read by a person. | Messages from the app: while your account exists; when you delete it, the words and your reply-to email are deleted, and we keep only that a message was sent, its reference, its topic and urgency, whether it needed a person, its date and the details that came with it (your plan, your phone's platform and the app version). Emails: kept in our support inbox while we need them to help you; ask us and we will delete them |
| Your email address, if you sign in with email (your password is kept only as a one-way hash) | To sign you in, confirm your address and reset a password | While your account exists |
| Your recovery email: the email address of your account, whichever way you sign in (see Recovery email below this table) | To send the notices our Terms and the law require about your subscription: a confirmation when you subscribe, and a reminder before a free trial ends and before a yearly plan renews; and a short safety note if something typed for Stories suggests a child may be at risk. Never for marketing | While your account exists; replaced each time you sign in, and deleted with your account |
| If you sign in with Apple, a token Apple gives us | So that when you delete your account we can tell Apple to end bre's access, as Apple requires | Deleted with your account |
| Your email address and account identifier, sent to our website (askbre.app) when your account is new | To recognise you if you joined the waitlist there | Until you delete your account, when we ask the website to forget the link |
| How much audio and writing your plan has used | To enforce your plan's allowance and stop runaway charges | While your account exists; kept without anything that identifies you after you delete it |
| The rendered audio | So replaying an episode does not cost you a second time | See §5 |
| A report you file about an episode, and anything you type with it | So a person can review what bre said | While your account exists. When you delete it, what you typed is deleted, and we keep only that a report was filed, its reason, the episode and line it was about, and the date. The one exception: a report about a child's safety or about self-harm can also be emailed to us when you file it, and that email is not deleted when you delete your account |
| That bre showed or said crisis help in Talk | So we can check the safety steps work, and report the number each year where the law asks | Counted only: a number for each month, with no account identifier, no words and no topic |
The file itself is never uploaded. bre opens it on your phone, takes the text out, and sends that text and the file's name — so the hosts can refer to "your notes" — and nothing else. The file and its metadata stay on the device. Be aware of what this does and does not mean: it keeps the document private, not the words in it — the text bre extracts is sent to us and on to the model that writes your episode, exactly like a topic you typed. bre can only read plain text and Markdown files today, and refuses anything it cannot read rather than attaching it.
A photo is read on your phone too, and the picture is never uploaded. When you choose From library under Add files, your phone's own photo picker gives bre only the picture you choose, with no permission prompt. bre reads the words in it on your phone, with Apple's text reader on an iPhone and Google's on Android, and sends only those words and a name such as "Photo · Sep 30" with your topic, the same way as a file's. The picture, and the smaller copy bre makes to read it, are deleted from the app straight after, whether or not any words were found. bre does not send the picture to any server. If that ever changes, this section, the in-app notice and the photo permission wording change first.
Recovery email. bre keeps the email address of your account, whichever way you sign in. That is the verified address Apple or Google shares with bre when you sign in with them (with Apple this can be a private relay address), or the address you signed in with by email. It is also where we send the notices our Terms and the law require about a subscription: a confirmation when you subscribe, and a reminder before a free trial ends and before a yearly plan renews, each with the price, the date and how to cancel. Your recovery email is used for subscription notices and the Stories safety note, and to link your bre account with your askbre.app account if you choose to sign in on the website. We use it for nothing else. Each new sign-in replaces it, and it is deleted with your account. The email is sent through Resend (§4).
Network address. bre's servers see the network (IP) address of each request and use it only to limit abuse, such as repeated sign-in attempts. We do not use it to work out where you are.
Notifications. If you turn on notifications, your phone gives bre a push token, which we pass to Apple's (or Google's) notification service to reach your phone.
2.3 Microphone and speech
bre asks for the microphone only when you tap to dictate a topic or to talk an idea through, or while an episode plays on screen with hands-free switched on, which you turn on yourself. It is not listening at any other time, and it never records in the background.
Hands-free listens for "hey bre" while the episode plays. bre only offers it on a phone that can recognise speech on the device, and uses that on-device recognition for the wake word and for the question you ask after it, so that audio does not leave the phone. It stops when you leave the player or lock the phone.
What happens to your voice is important and we want to be exact about it. bre asks the operating system — Apple's on iOS, Google's on Android — to turn your speech into text. Where your device has an on-device speech model for your language, that happens on the phone and the audio never leaves it. Where it does not, Apple or Google transcribes the audio on their servers, under their privacy policies, not ours. bre receives only the resulting text. We do not store the audio, and we do not receive a copy of it. bre's memory never holds audio.
- Apple's policy: https://www.apple.com/legal/privacy/
- Google's policy: https://policies.google.com/privacy
2.4 Crash reports
bre uses Sentry to find out when the app crashes.
When bre crashes or errors, Sentry receives the error and where in the code it happened, the app version, the device model and operating system version, and a random identifier for the installation — not for you — so that one person hitting the same crash forty times is not counted as forty people. It also records whether a session ended normally or in a crash, which is how we know whether a release is healthy.
With an error, Sentry also receives a short trail of the app's recent activity: each request's method, the shape of its address with the ids taken out, and the status it got back; the screens you moved between, again without ids; and app events such as going to the background. None of it includes your topics, your questions, episode titles or ids, or anything that signs you in.
What it does not receive: your name, your email, your IP address, your topics, your questions, what bre remembers about you, or anything an episode said. We have turned off the setting that would have sent the first three (sendDefaultPii), and performance tracing is off entirely.
bre's server reports its own errors to Sentry too: the error, where in the code it happened, and which kind of request it was — never the request itself, your account identifier, or anything you sent.
Crash reports are not used for advertising, not sold, and not used to build a profile. If you would rather the app sent none at all, there is a switch in Settings, and it stops every kind of report, including crashes in the app's native code. If you turn reports back on, they resume the next time you open the app. One small exception: on the first launch after an update, a single "session started" record can be sent before the app has read your setting.
Photo reading on Android
On Android, the text reader sends Google anonymous diagnostics. To read the words in a photo, the Android app uses Google's ML Kit on the phone. It never sends the picture or the words it reads. Google documents that the library does report, when it runs, the device model and operating system version, how long a read took and an identifier for the installation (not for you). That happens only when you add a photo. Apple's reader on an iPhone is part of iOS and sends nothing.
2.5 Things we do not collect
No advertising identifiers. No analytics or behavioural telemetry of our own (the Android text reader's diagnostics, §2.4, are Google's, and run only when you add a photo). No location from your device (the country in §2.2 is your phone's region setting, not where you are). No contacts. No camera. No access to your photos beyond the one picture you choose (§2.2), and no microphone access beyond §2.3. No cross-app or cross-site tracking of any kind. We do not do behavioural advertising, and bre's memory (§2.6) is not a profile for advertising or anything else: it is a short, visible list you control.
2.6 bre's memory (optional)
Memory policy version 2026-11-03.
bre can remember you between episodes, so a second episode on a subject starts where the first left off instead of from zero. It is off unless you turn it on. The app asks you, in plain words, before it is ever switched on, and you can turn it off at any time in Settings.
What bre remembers, when memory is on:
- the topics you make episodes about, and each episode's title, what it covered, how far you listened, and whether you skipped it or told the app you liked it;
- the depth, length, format and number of hosts you usually choose;
- the questions you ask the hosts during an episode, and the lines you highlight or bookmark;
- things you explicitly ask bre to remember when you talk an idea through ("remember I'm a nurse");
- one short line for each conversation with bre that ends in an episode plan — what you planned, not what was said.
What bre never remembers: audio of your voice; your notes; anything from a Stories episode; the contents of files you attach; passwords, card or account numbers, government identity numbers, email addresses or phone numbers; and sensitive details — about you or anyone else — even if you ask bre to remember them: health, religion or beliefs, sexuality or sex life, racial or ethnic origin, politics, trade union membership, genetic or biometric data, money details, or exactly where you live. bre is built not to keep those: it checks everything before it is written, and if you ask it to remember one of those it tells you it doesn't keep that kind of detail, and keeps nothing. No automatic check is perfect, in every language and every way of saying something, so bre may occasionally miss one. You can see and delete every item in Settings, one at a time or all at once. A topic is not a detail about you: an episode about diabetes or a religion is remembered like any other.
Why: so the hosts skip what you already know, pitch at the depth you have shown, refer back to what you asked last time, and never make you the same episode twice.
How it is used: when bre writes an episode for you or answers you when you talk an idea through, a short note drawn from your memory — at most about 1,500 characters — is sent to Anthropic with your request, marked as information about you rather than as instructions. It is sent nowhere else, used for nothing else, never sold, never used for advertising, and never used to train AI models, ours or Anthropic's. An episode bre writes for you may mention something it remembers, and those lines are voiced like any other (§3). Research that bre does on the web for an episode never includes anything from your memory. People at bre do not read what bre remembers about you: our own tools show how many people use memory and how many items exist, never what they say.
Keeping it small: each item is deleted 12 months after it was last updated, and bre keeps at most 60 episodes, 60 questions, 60 highlighted lines, 30 things you asked it to remember and 20 conversation lines — the oldest go first.
Your controls, all in the app:
- see everything bre remembers, in plain words, under Settings;
- delete any single item, or everything, at once;
- turn memory off: use stops immediately, and you choose whether bre keeps what it has (unused, and still visible and deletable) or deletes it;
- ask for a copy of it, with the rest of your account data (§6);
- deleting your account deletes all of it immediately.
If you are in the UK or the EEA, the lawful basis for memory is your consent, which you can withdraw at any time without affecting what happened before. bre's memory is built not to keep special categories of personal data, and it may occasionally miss one; you can see and delete every item in Settings.
3. Artificial intelligence, stated plainly
bre's hosts are AI, not people. Episodes are generated, so what the hosts say can be wrong, out of date, or confidently incorrect. Check anything that matters. bre is not a source of medical, legal, financial or safety advice, and an episode is not a substitute for a professional.
Three kinds of AI are involved, and they are not the same:
- Writing the episode happens on our servers. Your topic, text extracted from files you attach or photos you add, the name and interests you gave bre (if any), what you say when you talk an idea through, and — only if you turned memory on — a short note of what bre remembers about you (§2.6) are sent to Anthropic, whose model writes the script and the hosts' lines. A message you send to support is also read by Anthropic's model, to sort it and sometimes to draft or send a reply. The same goes for Talk: what you say to bre is turned into text by your phone's speech recognition (§2.3) and sent on to Anthropic, whose model writes bre's reply. A question you ask during an episode sends its words, the episode's topic and your region setting to bre's servers and on to our AI service.
- Speaking the episode happens on our servers too. The written lines are turned into audio by bre's own voice models, which run on computers we rent from Modal (see §4). No outside speech company receives them.
- Researching the episode, for the episodes where bre does it: Anthropic's web search looks things up using searches bre builds from your topic. The part of bre that plans the searches is never given your memory, and a search is refused if it would contain an email address, a phone number, a street address, or more than eight words in a row copied from a file you attached. To make episodes faster, bre keeps what it gathered from the public web for an episode (the searches it ran, the pages it read, and the fact sheet built from them) for up to about 24 hours, in a cache shared by all listeners. It is stored without your account ID, but it can include the words of your topic or of a question you asked (§5).
Your content is not used to train models. Not ours, not our providers'. If that ever changes, we will say so here before it takes effect and not after.
Every episode is labelled as AI. All speech in bre is synthetic. The audio files bre makes carry a machine-readable "AI-generated by bre" mark in their metadata (WAV INFO and MP3 ID3 tags), and a matching header when an episode is downloaded, so other software can tell what the file is. Talk opens every session by saying that bre is an AI. bre's hosts are fictional characters; they do not imitate a named real person, and bre will decline a request to make them do so. The label is there to be kept: do not strip it to pass the audio off as a recording of a real person (the Terms of Service, §6, say the same).
4. Who else processes your data
We use a small number of service providers. They act on our instructions and may not use your data for their own purposes.
| Provider | What they receive, and why | Where | Their terms |
|---|---|---|---|
| Anthropic PBC | To write episodes and answer you: your topic, text extracted from files you attach or photos you add, the name and interests you gave bre, what you say when you talk an idea through, and what bre remembers about you if memory is on. For support: to sort the messages you send, and to write the replies our AI assistant sends to emails. To research an episode, where bre does: the searches built from your topic, which Anthropic runs through its web search. Your phone's region setting (a two-letter country code) picks the right crisis line; for some countries the country's name is also added to what we send to our AI service. | United States | https://www.anthropic.com/legal/privacy |
| Modal Labs, Inc. | The lines your hosts speak, turned into audio by bre's own voice models on Modal's computers. A line can include your name or something bre remembers, if the episode uses it | United States | https://modal.com/legal/privacy-policy |
| Railway Corporation | Hosts bre's server and its database: your account identifier, plan, usage counts, the questions you asked and lines you marked, and — only if you turned memory on — what bre remembers about you (§2.6). Also the server's logs, which carry account identifiers and counts, never your topics, words or memory (we can read them for 30 days; Railway may keep them for up to 90 days) | United States | https://railway.com/legal/privacy |
| Apple | If you choose Sign in with Apple: signing you in, and a stable identifier and your email or a private relay address for us; when you delete your account, our request to end bre's access. Speech audio, only where your device has no on-device model (§2.3). Payment for subscriptions bought on the App Store | Per Apple's policy | https://www.apple.com/legal/privacy/ |
| If you choose Sign in with Google: signing you in, and a stable identifier and your email for us. Speech audio on Android, only where your device has no on-device model (§2.3). Payment for subscriptions bought on Google Play | Per Google's policy | https://policies.google.com/privacy | |
| RevenueCat, Inc. | Your bre account identifier and your App Store or Google Play subscription records, to confirm which plan you have paid for. On an iPhone, RevenueCat's software also sends a device identifier that Apple gives bre's app on that phone (Apple's "identifier for vendor", not the advertising identifier). bre itself never reads it. | United States | https://www.revenuecat.com/privacy |
| Resend | Your email address and the email itself: sign-up and password-reset codes from the app and a notice if someone tries to sign up with an address that already has an account (email accounts only), a confirmation when you subscribe and reminders before a free trial ends or a yearly plan renews, and a short safety note if something typed for Stories suggests a child may be at risk (the confirmation, the reminders and the safety note go to the recovery email of the account, §2.2), an email to us with a report you can file about a child's safety or about self-harm (§2.2), and confirmation and support-reply emails from our website | United States | https://resend.com/legal/privacy-policy |
| Cloudflare, Inc. | Runs our website (askbre.app) and our domain's DNS, and receives your email address and account identifier when your account is linked to the website (§2.2). It also stores the finished episode audio in Cloudflare R2 object storage, played back through signed, expiring links: audio files only, with no name, email or topic attached. It also receives the emails you send to an askbre.app address and passes them to our support system (Cloudflare Email Routing) | Cloudflare's network; the storage location is chosen automatically, not fixed to one country | https://www.cloudflare.com/privacypolicy/ |
| Google (Gmail) | A copy of each email you send to support@ or hello@askbre.app, and the replies a person sends from that inbox, kept in our team's inbox | United States | https://policies.google.com/privacy |
| Google (ML Kit, Android only) | Reads the words in a photo you add, on your phone. Google does not receive the picture or its words; it receives anonymous diagnostics from the library when it runs (device model, operating system version, timings and an installation identifier; §2.4) | Per Google's policy | https://policies.google.com/privacy |
| Functional Software, Inc. (Sentry) | Crash reports from the app and error reports from bre's server (§2.4) | United States | https://sentry.io/privacy/ |
Subscriptions are paid through the App Store or Google Play. Apple and Google take the payment; bre never receives or stores your card details.
News episodes are built from today's headlines and summaries in publishers' public news feeds, each credited by name, never from full articles. When you make a News episode, the app fetches the latest headlines directly from those publishers' public feeds (ScienceDaily, ESPN, the World Health Organization and NASA), so each publisher receives an ordinary request from your phone, and only those headlines and summaries go to bre's server to write the episode.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising — as those terms are used in the California Consumer Privacy Act. We never have.
5. How long we keep things
| Data | Retained |
|---|---|
| Your topic, the text of attached files or photos, the children's age band for a Stories episode, and your name and interests, when you ask for an episode | Kept only while the episode is being made or waits in line — at most three days — and for up to 30 minutes after it ends; then deleted (the research cache, below, is the exception) |
| What you say when you talk an idea through | Not stored: held in the server's working memory while the answer is written, then dropped |
| What bre gathered from the public web for an episode: the searches it ran, the pages it read and the fact sheet built from them, which can include the words of your topic or of a question you asked (§3) | Up to about 24 hours, in a cache shared by all listeners. Not linked to your account. It expires on its own and is not removed early when you delete your account |
| Whether you are under 18 (yes or no) | While your account exists |
| Your phone's time zone | Not stored |
| Your language setting, when it is not English | Kept with the usage count for that episode, as long as usage counts are (see Usage counts and quota records) |
| What bre remembers about you (only if memory is on) | Each item 12 months after it was last updated, or until you delete it (§2.6) |
| What you agreed to, and when | While your account exists |
| Usage counts and quota records | While your account exists; after you delete it, kept without anything that identifies you, because they are also the record of what bre spent |
| Rendered audio in our cache | Kept in a cache shared by everyone, so replaying costs nothing; the least recently played audio is deleted first when the cache is full. The same episode text is one shared file, so we record which accounts have each file. When you delete your account we delete the files only you had, straight after your records are erased (retrying if the storage is unreachable), and keep any file another account also has. Audio made before this went live has no such record, so it is not deleted with your account and leaves the cache as it fills |
| Support messages and reports from the app | While your account exists; when you delete it, the words and your reply-to email are deleted, and we keep only that one was sent, its topic or reason, its date and the details that came with it (for a message, its reference, its urgency, whether it needed a person, your plan, your phone's platform and the app version; for a report, the episode and line it was about). A report about a child's safety or about self-harm can also be emailed to us when you file it, and that email is not deleted when you delete your account |
| Emails to support@askbre.app | Kept in our support inbox while we need them to help you; ask us and we will delete them |
| Your account record, sign-in email and Apple token | Until you delete your account |
| Your recovery email (§2.2) | Until you delete your account; each sign-in replaces it |
| Notices we sent you (the welcome when you subscribe, and the reminders before a trial ends or a yearly plan renews: which one, about which date, when) | Until you delete your account |
| Renewal facts for a subscription (the store, the billing period, the renewal date, the last price charged, whether it renews; no name or email) | Kept with the subscription's record, like its weekly usage, so a purchase restored onto a new account is still reminded; not linked to you once your account is deleted |
| Server logs (account identifiers and counts, never your topics, words or memory) | We can read them for 30 days; Railway, which hosts our server, may keep them for up to 90 days |
When you delete your account, we delete at once your account record, your sign-in details, your recovery email, what you agreed to, everything bre remembers about you, the record of reminders we sent you, and the words of any support message or report you sent from the app, and we ask our website to forget you. What stays has nothing that identifies you:
- usage counts, which are also our record of what bre spent;
- the App Store's or Google Play's billing events for your plan (which plan, what happened, when), with your account identifier removed;
- a one-way fingerprint of your account identifier, so a late message from the store cannot bring the account back;
- that a support message or report was filed, with its topic or reason, its date and the details that came with it (for a message, its reference, its urgency, whether it needed a person, your plan, your phone's platform and the app version; for a report, the episode and line it was about);
- the renewal facts kept with your subscription (see the table above).
Emails you sent to support@askbre.app are not part of your account: they are kept as the table above says, and we delete them if you ask. A report about a child's safety or about self-harm can also be emailed to us when you file it, and that email is not deleted when you delete your account.
What bre gathered from the public web for an episode (§3) is not linked to your account, so it is not removed when you delete the account; it expires on its own within about 24 hours. We delete the audio files only you had, straight after your records are erased. Audio another account also has stays for them; audio made before this went live ages out of the cache as it fills; and our server's logs age out as the table above says. RevenueCat, which confirms subscriptions for us, keeps its own record of your purchases under your old account identifier; write to us and we will ask it to delete that record. If we must keep a record to meet a legal or tax obligation, we keep only that record, and only for as long as the law requires.
6. Your choices and your rights
You can delete your account from inside the app, under Settings. It removes your data as described in §5.
You can see, delete and switch off bre's memory from inside the app at any time (§2.6).
Depending on where you live you may also have the right to ask us to:
- tell you what personal data we hold about you, and give you a copy;
- correct it if it is wrong;
- delete it;
- restrict or object to how we use it;
- receive it in a portable form;
- withdraw a consent you gave us, without affecting what we did before you withdrew it.
bre's server can produce a copy of your account — your plan, what you agreed to and when, and everything bre remembers about you — in a portable (JSON) form. Write to support@askbre.app for it, or for anything else above, and we will answer within one month. We will not charge you, and we will not treat you differently for asking.
If you are in the UK or the EEA, our lawful bases are: performance of a contract (running your account and your plan), consent (the microphone, which you grant and can revoke in your device settings at any time; sending your topics to our AI provider, which the app asks for before it sends anything; and bre's memory, §2.6), and legitimate interests (keeping the service running and preventing abuse of quotas). You have the right to complain to your data protection authority — in the UK, the ICO at https://ico.org.uk.
If you are in California, you have the rights to know, delete, correct and opt out of sale or sharing. We do not sell or share, so there is nothing to opt out of, but the other rights apply and the address above is how to use them.
7. Where your data is processed
bre's servers, and the computers our voice models run on, are in the United States. The finished audio files are kept in Cloudflare R2, which chooses where in its network to store them, so they may sit in other countries too. If you are in the UK or the EEA this means your data may be transferred outside it; where that happens we rely on the UK/EU Standard Contractual Clauses or an equivalent approved mechanism.
8. Security
Your connection to bre is encrypted in transit (TLS); the app refuses to talk to a server over an unencrypted connection. Requests are authenticated, and audio links are individually signed and expire. We keep no provider keys in the app itself — every paid call is made by our server. There is no public storage bucket: audio is served only through a signed, expiring link. Each account can only ever read or delete its own memory.
No system is perfectly secure, and we are not going to pretend otherwise. If you find a vulnerability, please tell us at support@askbre.app and we will work with you.
9. Children
bre is not intended for children under 13 to use on their own, or under the higher minimum age some countries set (Terms §1), and we do not knowingly collect personal data from them. If you believe a child has given us data, write to support@askbre.app and we will delete it.
Stories. Stories makes gentler, shorter episodes for a child to listen to. It is operated by a parent or guardian, on their own account: an adult signs in and opens Stories. The child only listens. In Stories:
- nothing is recorded: no microphone, no Talk, no hands-free listening;
- no questions or words are collected from the child, because there is no way for the child to ask one;
- no memory is kept of what was listened to: nothing from a Stories episode is added to bre's memory (§2.6);
- no personal information is collected from the child. If crash reports are on (a switch in Settings), a crash in Stories sends only the technical details listed in §2.4: the error, the device model and operating system version, the app version, a random identifier for the installation, whether the session ended normally or in a crash, and a short trail of the app's recent activity with the ids taken out, which we use only to keep the app working.
What a parent types to make a Stories episode is handled like any other topic (§2.2); the name and interests from onboarding are not sent for one. In Stories, the age band you pick (for example 5 to 7) is sent with the story request to our AI service so the story fits; no name or interests are sent. bre is not in Apple's Kids Category.
A child in Stories can leave to the rest of bre, where plans that cost money are sold. Use Apple's Ask to Buy or Screen Time to control purchases.
10. Changes to this policy
If we change this policy in a way that materially affects you, we will tell you in the app before the change takes effect, and update the date at the top. Continuing to use bre after that means the new version applies. If we change what bre's memory keeps, how it is used or who receives it, we will ask you again, and memory stays off until you answer.
11. Contact
BRE LLC 701 Market St Ste 110 PMB 1342, Saint Louis, MO 63101, USA Privacy: support@askbre.app Support: support@askbre.app