Privacy Policy
Last updated:
This document is being finalized. Legal operator details and some operational data-handling facts still need confirmation. The contact below is available for product and privacy requests.
1.In short
- We don’t sell your data, show no ads and use no advertising trackers. The app’s update component keeps a random installation ID; see Cookies and storage.
- Our servers process your text and screenshots without saving the originals. Before sending to third-party AI service providers, Brolivo shows who receives them and asks your permission. Local previews and provider retention are explained below.
- Without an account we use a random device ID for daily limits and, if you buy in the app, to link your store subscription. With sign-in and purchase restoration, access can move to your account.
- With an account we keep your e-mail address and your plan. You can delete the account at any time; without one, Delete my data in the app’s Settings deletes an app install’s data.
- Answers are only suggestions: you decide what to send.
The details follow. This policy covers the Brolivo website, app and service.
2.Who is responsible for your data
The controller of your personal data is the operator of Brolivo:
- Operator: [operator details pending]
- Address: [operator details pending]
- NIP (Polish tax number): [operator details pending]
- E-mail: brolivo@darebay.com
Write to the e-mail address above about anything in this policy, including requests about your personal data.
3.What we process, why, on what basis and for how long
In the table, “contract” means Art. 6(1)(b) GDPR (we need the data to give you what you ask for), “legitimate interest” means Art. 6(1)(f) GDPR and “legal obligation” means Art. 6(1)(c) GDPR.
The periods below describe configured cleanup thresholds or operator policy targets. Scheduled cleanup, log deletion and backup deletion have not yet been verified for the current test service. These periods are not confirmed automatic deletion deadlines for that service. Contact brolivo@darebay.com for current information or a data request.
| Data | Why | Legal basis | How long we keep it |
|---|---|---|---|
| What you type into the tools: her message, the context, your draft, names or interests you enter in the free tools | To write the answer you asked for | Contract; for other people’s words, legitimate interest (see People in your chats) | We don’t persist raw inputs on our servers; they are processed in memory for the request. Recent text inputs and results are kept locally in the browser tab until it closes, or in app memory for the current session. They are not synced as cloud history |
| Chat screenshots | To analyze the conversation | Contract and your explicit permission before transfer to AI providers; for other people’s data, legitimate interest (see People in your chats) | Our servers process screenshots during the request without saving them. The app tries to remove temporary upload files when they are no longer needed and during later cleanup. Failed cleanup can leave temporary copies on the device. A small preview may remain in local session history until the conversation is deleted or evicted, the web page leaves or reloads, or the app process ends. Your original image remains on your device |
| Answers written for you | To show them to you | Contract | We don’t persist answers on our servers except in a report or public card (rows below). Recent answers and their text inputs remain in the browser tab until it closes, or in app memory for the current session |
| A report of an answer: the reported suggestion without contact details, your reason, the language, the device ID and account ID | Safety review and fixing bad answers | Legitimate interest | 180 days |
| A report of a card: the card’s link, your reason, the language, the device ID and account ID | Handling notices about public content | Legal obligation (Digital Services Act) and legitimate interest | 180 days |
| A public card you create on the website: a selected reply, your draft or its improved version, a quiz score or a situation-page choice; any displayed score, previous score, tone, label and short explanation; the device and account that made it; when someone else first opened it. Chat screenshots are not included | To show the card to the people you share it with | Contract | 7 days if nobody else opens it; otherwise up to 365 days from creation. On the website you can remove a card from its Share window while that window is available. Otherwise send its link to brolivo@darebay.com to request removal. Delete my data in the app and account deletion remove their cards too; a card someone reported stays hidden, without the link to you, while its reports are kept. Copies already saved by browsers, messengers or other services can remain |
| A share picture in the app: the result you chose, as a card shows it, which the app sends back to our server only to have the picture drawn | Letting you send your move as a picture | Contract | Not stored: drawn and sent back to the app at once; it has no link and no page |
| Account: e-mail address, language, sign-up date, the version of the Terms you accepted and your 18+ confirmation, the campaign code of your first visit, a block flag if we had to block the account | The account, sign-in and proof that you accepted the Terms | Contract; legitimate interest for the campaign code and the block flag | Until you delete the account |
| Sign-in codes (only as a hash), failed attempts and the hashed network address | Secure sign-in | Contract and legitimate interest (security) | 24 hours |
| Sessions: a hash of the session token, the device, times of use | Keeping you signed in | Contract | Until you sign out, or 30 days after your last visit |
| Device record: a random device ID, the platform (web, iOS, Android), when you confirmed you are 18+, the version of the texts you accepted, the separate AI permission version and time of acceptance, a trust level, a block flag, the campaign code of your first visit, first and last visit | Free daily limits, the 18+ gate, recording and checking AI permission, preventing abuse | Legitimate interest | 400 days after your last visit, or until Delete my data in the app |
| Daily usage counts per device and account | Free limits and Pro fair use | Contract and legitimate interest | 35 days |
| Your IP address, only as a hash with a key that changes every day | Rate limits and security | Legitimate interest | 2 days |
| Server logs: time, the address of the page or request without parameters, response status, browser type or the app’s platform, version and build number, referring site, your IP address shortened or as a daily hash (never your texts or e-mail address) | Security and fixing errors | Legitimate interest | Policy target: 14 days. Actual retention in the current test service has not yet been confirmed |
| App update checks: when the app starts, it asks Expo’s update service whether a newer version of its code is available. The request carries your IP address, the platform, identifiers of the installed app code (its runtime version and update IDs) and its update channel, the IDs of updates that recently failed to start, a random installation ID that the update component creates on the device (not linked to your device ID or account), values Expo’s service asked the app to send back (for example to keep it in the same group during a staged rollout) and the technical details the phone adds to any request: on iPhone its system version, the app’s build number and language. After the update component fails to start the installed app code (it then starts the version built into the app), and on iPhone also after a crash from the start until 10 seconds after the first screen appears, the app keeps a short technical description of that error on the phone until the next check, which sends it once. The request is not meant to carry your texts, screenshots, e-mail address or account data; in rare cases an error description can include a fragment of what the app was handling, such as a file name | Keeping the app’s code up to date between store releases and going back to a working version when an update fails to start. Expo also uses these checks for its own service statistics, as a separate controller (see Who helps us) | Legitimate interest | These requests do not reach our servers. Expo keeps them as set in its terms; no exact period is published. The installation ID stays in the app’s storage until you delete the app |
| Subscription: plan, status, period, currency, store, device or account ID, Stripe customer and subscription IDs, RevenueCat purchase and transaction identifiers and dates; payment notification IDs | Providing Pro | Contract | Account-linked records until account deletion; guest records until the device has been inactive for 400 days or Delete my data in the app; notification IDs 90 days |
| Payment records required by tax law (no card details) | Accounting and tax | Legal obligation | As long as tax law requires, in Poland usually 5 years from the end of the year |
| Messages you send us | Support, complaints, requests about your rights | Contract, legal obligation, legitimate interest | Up to 2 years after the matter is closed |
| Cost records of answer processing: the tool, the technical route of the answer, tokens, cost and how it was determined, time, language, type of error (no content, no device or account) | Budget control and reliability | Legitimate interest | 400 days |
| Quality records of answers: the tool, the time and duration, the interface and reply languages, the instruction version, the technical route of the answer and why it was chosen, the strategy, the test group, the outcome or type of error, the cost, the number of attempts and drafted options, which option was recommended, the numbers of conversation lines and images, whether background was added, the goal, automatic quality numbers about the suggested texts (such as length or how many end with a question), the kind of request (new, more, retry or continuation) and links between the answers of one conversation. Pseudonymous: no content, no device or account | Measuring and improving answer quality, including tests of variants | Legitimate interest | 400 days; links between the answers of one conversation 8 days |
| Your rating of an answer: thumbs up or down, a reason chosen from a list, that you marked an option as sent, which option it was with its tone, type and place in the list, and when (no text, no device or account) | Measuring and improving answer quality | Legitimate interest | 400 days |
| Anonymous daily totals by language, campaign, tool, public page and broad visit source (such as Google search or an unknown source), including page views, tool starts, useful results, copied replies, app openings and store subscriptions, trials, payments and refunds with their estimated amounts by store, plan and currency, and per instruction version, technical route and test group: copied and shared suggestions by tone, type and position, follow-up requests, averages of the quality numbers, and counts of help-line answers and refusals by reason. These totals contain no device or account IDs, conversation text, screenshots, search terms or referrer URLs. The visit source is classified in this browser tab without storing the referrer | Decisions about the product, public figures, paying partners for the people they bring | Not personal data | No time limit |
Our legitimate interests are: keeping the free service available and secure, keeping the app’s code up to date between store releases, preventing abuse, helping you with your own conversations, handling reports, measuring and improving answer quality, including tests of variants, and knowing which campaigns bring people to Brolivo. The operator must document how these interests are balanced against your rights and those of the people in your chats before this policy is finalized. You can object to this processing or ask for the available information at brolivo@darebay.com.
You don’t have to give us any data. Without the text of a request we cannot answer it, and without an e-mail address you cannot have an account. You can purchase in the app without an account.
The backup policy target is removal of deleted database data from backups within 35 days. We have not yet confirmed that the current test service enforces that schedule; contact brolivo@darebay.com for information about a specific deletion request.
In the app, RevenueCat verifies purchases using store receipts, purchase history, subscription status, technical app and device information, and random device or account identifiers. We do not send RevenueCat your chats, screenshots, e-mail address or advertising identifiers. When you sign in and restore purchases, we associate verified access with your account; signing out does not give the next account access to that subscription.
4.How we prepare your answers
To prepare your answer, we send your submitted conversation or chosen import excerpt, draft, note and selected screenshots to third-party AI service providers. The permission screen names the services reachable under the current configuration: Kie AI, Anthropic, or both. Screenshots include visible names, photos and other image content. We do not send your account or device ID with the AI request.
We do not train AI models on your content. This describes Brolivo’s own use; it is not a promise about every provider. Kie’s terms permit content use for operating and improving its services. Its website privacy policy does not establish API chat training terms.
Kie’s service guide lists 2 months for text/metadata logs and 14 days for generated media. These are not confirmed deletion deadlines for uploaded screenshots, chat contents or upstream copies. We cannot confirm the complete retention or training terms of Kie’s downstream services.
For direct Anthropic API requests, Anthropic’s standard retention policy states deletion within 30 days, with contractual, feature-specific, safety and legal exceptions. Flagged inputs/outputs may remain for 2 years and safety classifications for 7 years. These terms do not cover requests sent through Kie AI.
AI permission is separate from your 18+ confirmation. You can decline before sending or withdraw it in Settings. We then require permission again before another AI request; an already submitted request cannot be recalled. A change to the disclosed recipients or notice requires renewed permission. Provider deletion requests can be sent to brolivo@darebay.com; deleting local history does not erase provider records.
Before sending text, we filter recognizable e-mail addresses, phone numbers, links and @handles. This cannot remove every personal detail, and it does not redact screenshot pixels. Our server also checks texts for signs of a crisis or of a person under 18, so it can show help contacts or stop instead of writing tips.
Our instructions and safety checks limit harmful or privacy-invasive answers. They do not guarantee that an answer or a public card contains no personal information.
Suggested replies and optional conversation details are generated from the material you submit. Recent results follow the local-history rules in the data table; our servers do not keep private conversation history or build a profile of your contacts.
We make no decisions about you by automated means that have legal or similarly significant effects (Art. 22 GDPR). Answers can be wrong or unsuitable, so read them before you send anything.
5.People in your chats
What you send often contains another person’s messages, name or photo, usually of the person you are talking to. We receive these data only from you, as part of your request, and use them only to write your answer. Our legal basis is legitimate interest (Art. 6(1)(f) GDPR): your interest in getting help with your own conversation. We limit what reaches us so that this interest does not override the other person’s rights:
- our servers do not save raw conversations or screenshots; local history, previews, reports and public cards have the separate rules in the data table;
- screenshots are sent in full for analysis, including any visible names and photos; we may resize images or split them into parts without removing their content;
- recognizable contact details are filtered from text before transfer, without a guarantee of full anonymization;
- we use safety instructions and checks, and do not build a cloud profile of your contacts.
Chats can reveal sensitive information, such as health, sex life or beliefs. Send only the material needed for your question and that you are entitled to share. Your AI permission does not give consent on another person’s behalf. Remove unnecessary identifying or sensitive details before sending.
We do not collect a contact list to identify or notify the people in your chats. This public policy explains the processing to them too. If you think your data reached us through someone else’s request, write to brolivo@darebay.com; we will assess the request and the information and deletion duties that apply.
6.Who helps us
We share data with the providers needed to run Brolivo. The AI permission screen identifies which of the following third-party AI service providers can receive the current request, including a fallback:
| Recipient | What for | Where |
|---|---|---|
| Kie AI | When named in the permission screen: processing text and screenshots using its model services and upstream infrastructure. Its published website terms name NEXUSAI SERVICES LLC and INNOLEAP AI LLC | The published contact address is in the USA; the complete downstream processing locations are not confirmed |
| Anthropic | When named in the permission screen: direct API processing of text and screenshots | USA and other processing locations described in Anthropic’s terms |
| Hosting provider (details awaiting confirmation) | Servers and database hosting | The current hosting entity, processing locations and applicable processing agreement still need confirmation |
| RevenueCat, Inc. | Store purchase verification and subscription status, as our processor under its Data Processing Addendum | USA |
| Apple / Google | App Store and Google Play payments and store accounts under their own privacy policies, as separate controllers | As stated in the store account’s privacy policy |
| Resend | Sending sign-in codes by e-mail, as our processor | USA |
| Expo (650 Industries, Inc.) | App updates: the update check described in the data table and the download of new app code, as our processor under its terms; for its own service statistics from these checks and downloads (for example how many installations run each update and how many download one), as a separate controller under its privacy policy. We still need to confirm both roles. The check is not meant to carry texts, screenshots or account data | USA |
| Stripe, with its Link service | Payments, as a separate controller under its own privacy policy (for example to prevent fraud). Where the checkout says “Sold through Link”, Stripe also resells Pro to you as the merchant of record | Ireland, USA |
Where a provider acts as our processor, it is bound by the applicable processing agreement. The AI section distinguishes our handling from published provider terms and their limits. Authorities and courts receive data when the law requires it. We don’t sell data and have no advertising partners.
Resend applies when e-mail sign-in is enabled; Stripe applies when website checkout is available. The table describes supported services, not confirmation that every service is active. We still need to confirm the current hosting details, support-mail handling and applicable processing agreements before finalizing this policy.
7.Transfers outside the EEA
The third-party AI service providers named above may process data outside the EEA, including the USA. The permission screen reflects the services reachable for your request. A model’s name alone does not establish who operates every upstream service. We have not confirmed Kie AI’s complete downstream locations or transfer safeguards; request the available information at brolivo@darebay.com.
RevenueCat processes subscription information in the USA; its Data Processing Addendum includes Standard Contractual Clauses for restricted international transfers. Expo processes app update checks in the USA; its terms provide the EU standard contractual clauses for its processing as a processor. We still need to confirm that they cover these requests. Apple and Google describe their own processing and transfers in their store privacy policies.
8.Cookies and storage on your device
We use no advertising or analytics cookies and no advertising trackers. The website loads no third-party trackers at all and keeps only these items on your device:
| Name | Type | What for | How long |
|---|---|---|---|
_ | Cookie that scripts cannot read | Keeps you signed in; set only when you sign in | Until you sign out, or 30 days after your last visit |
brolivo. | Local storage | A random device ID for the free daily limits | Until you clear the site’s data |
brolivo. | Local storage | Your answer to the 18+ question | Until you clear the site’s data |
brolivo. | Local storage | Your pending or completed withdrawal of AI permission; blocks further AI sends and is not an acceptance receipt | Until you explicitly grant AI permission again or clear the site’s data |
brolivo. | Local storage | Notes that this device ID is registered with us | Until you clear the site’s data |
brolivo. | Local storage | You closed the hint about a page in your language | Until you clear the site’s data |
brolivo. | Local storage | The language you chose | Until you clear the site’s data |
brolivo. | Local storage | The campaign code of the link you came by | Until you clear the site’s data |
brolivo. | Session storage | Your recent text inputs and results in this tab, never screenshots | Until you close the tab |
brolivo. | Session storage | Unsent text, background, goal and any explicit reply-style choice, per page; never screenshots | Until you close the tab |
brolivo. | Session storage | A counter identifying the current chat in this tab so it survives a reload; no conversation text | Until you close the tab |
brolivo. | Session storage | A reference to the result shown in your current chat, so an explicit return from Account or payment can reopen it; no conversation text or screenshots | Until you close the tab |
brolivo. | Session storage | The page a payment started from, to bring you back to it afterwards | Until you close the tab |
brolivo. | Local storage | Your calibration choices, writing preference and completed UTC practice dates; never conversations or screenshots | Until you clear the site’s data |
Recent conversation cards can include a small screenshot preview held only in page memory on the web, or process memory in the app. It disappears when you reload or close the browser tab, close the app process or delete the conversation. Full screenshots and previews are not kept in saved device history or on our servers; the app tries to remove temporary image files when they are no longer needed. Cleanup failures may leave temporary copies on the device. The app keeps recent text inputs and results in memory for its current session; sending it to the background may keep that session open. This is not cloud account history.
The app also stores your calibration choices, writing preference, completed UTC practice dates and whether you have seen the first Pro offer on this device. Both the website and app keep a local AI-permission withdrawal marker that prevents further sends even if the server is temporarily unavailable. It records whether withdrawal is pending or completed and remains until you expressly grant permission again or clear the site’s or app’s stored data. The permission receipt itself is stored on our server. These are local settings, not training data. Imported chats are parsed locally: participant labels help you choose whose messages are yours, and only the selected messages, their roles and available timestamps are sent for analysis. The server does not save the imported file or transcript. The app can keep a temporary archive copy while you choose or switch between chats. It tries to remove temporary copies when they are no longer needed and during later cleanup, but no deletion deadline is guaranteed. Your original file remains under your control.
Stripe’s payment page sets its own cookies under Stripe’s policy. You can delete all of the above at any time in your browser’s settings (site data); you then get a new device ID.
The app stores a random installation identifier and sign-in credentials in protected device storage. On iOS, Keychain data can survive deleting and reinstalling the app. Deleting the app or clearing local history therefore does not itself erase the server-side device record, reports, usage records or purchase association. Delete my data in the app’s Settings (Your data on this phone) does: see Your rights. The app’s update component (Expo’s expo-updates) keeps in the app’s storage its own random installation ID, the values Expo’s update service asked it to send back, the app updates it has downloaded, the description of a failed start until the next update check carries it, and a log of its own update events, which never leaves the phone: each start removes its entries older than a day. They are not linked to your device ID or account. Deleting the app removes them (a backup of the phone can bring the ID back); Delete my data does not.
9.Your rights
Under the GDPR you have the right to:
- access your data and get a copy of it;
- have inaccurate data corrected;
- have your data erased: you can delete your account yourself on the account page or in the app’s Settings and, without an account, delete an app install’s data in the app’s Settings (Delete my data);
- restrict the processing;
- data portability, for the data you gave us;
- object at any time to processing based on our legitimate interest, including the campaign code;
- withdraw AI permission in Settings at any time, without affecting the lawfulness of earlier processing or automatically deleting a provider’s existing records.
Write to brolivo@darebay.com. We answer within one month; for complex requests we can extend this by two more months and will tell you why. We may ask you to confirm that it is you, for example with a code sent to your e-mail address. Without an account we usually cannot tell which data are yours, because we don’t know who uses a device ID.
You can complain to the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl, or to the data protection authority of the EU country where you live or work.
Deleting an account, or an app install’s data with Delete my data, removes its subscription association and requests deletion of that customer’s RevenueCat record. RevenueCat processes deletion asynchronously. Store purchase records remain subject to Apple’s or Google’s policies and legal retention duties. Deleting the app, an account or an install’s data does not cancel store billing: cancel it in the App Store or Google Play; Restore purchases can bring an active subscription back.
Delete my data in the app (Settings → Your data on this phone) deletes at once, without an account: the install’s 18+ confirmation and AI permission receipt, the campaign code of its first visit, its usage counters, its store purchase association, any public cards linked to it (their pages stop opening; copies others saved can remain; the app itself makes none) and its link in its own reports and in sessions; the app then forgets its local data and starts as a new install with a new device ID. Kept: reports without that link for their retention period, a card someone reported, hidden and without that link, while its reports are kept, AI call and answer-quality records, which hold no device ID, totals without IDs, backups until their retention ends, and the app update component’s installation ID, which stays on the phone until you delete the app (a phone backup can bring it back), with Expo’s records of update checks for as long as Expo keeps them. If we have blocked an install, its data is deleted on request to brolivo@darebay.com. Deleting an account in the app also deletes that install’s data. On the website, clear the site’s data in your browser for the local data. Deleting an account on the website does not delete the browser’s own device record, its usage counters or its link in reports. You may request access to your data, or deletion of a website guest’s server records, without creating an account: write to brolivo@darebay.com. We may need limited information to locate the relevant device or purchase record and verify your authority. Never send a password, sign-in code, session token or full private conversation. The retention rules and any applicable legal exceptions remain relevant.
10.Users in Ukraine
If you are in Ukraine, you also have the rights given by the Law of Ukraine No. 2297-VI “On Personal Data Protection”, including the right to:
- know the sources of your data, the purposes of processing, where the data are and who processes them;
- get access to your data and learn who receives them;
- object to the processing and withdraw your consent;
- demand that we change or delete your data;
- be protected from unlawful processing and from accidental loss or destruction of your data;
- complain to the Ukrainian Parliament Commissioner for Human Rights or go to court.
Write to brolivo@darebay.com; we answer within 30 calendar days.
11.Adults only
Brolivo is only for people aged 18 or over. If you tell a tool that you are under 18, the automatic check removes the 18+ confirmation from your device record; it does not delete an account. Stop using the service if you are under 18. You can delete your account in account settings. For help removing an underage person’s account or data, contact brolivo@darebay.com; the operator handles that request individually.
12.Security
Data travel encrypted (HTTPS). Sign-in codes and session tokens are stored only as hashes, and IP addresses only as hashes with a key that changes daily. Logs never contain your texts, screenshots or e-mail address. Only the people who run Brolivo have access to the servers, as far as their work needs it. If a data breach puts your rights at risk, we will tell you and the supervisory authority as the law requires.
13.Changes to this policy
When we change this policy, we publish the new version here with a new date (this version: October 13, 2026). If a change is material, we tell account holders by e-mail before it takes effect. The operator arranges these notices individually before the change takes effect.
14.Contact
Questions about this policy or your data: brolivo@darebay.com.
Also read: Terms of Use