Bolgo privacy policy
Version dated October 27, 2026
Who looks after your data
Bolgo is operated by PMARTINSDEV Tecnologia LTDA, CNPJ 55.279.733/0001-07, with its registered office at Rua Bananeiras, 361, sala 107, caixa postal 658, Manaíra, João Pessoa, PB, 58038-170, Brazil, the controller of your personal data. For any request about it, write to officialbolgo@gmail.com.
What we keep, and what for
Your account. Name, e-mail and the password as a hash (never the password itself). They let you sign in, recover the password and receive confirmation codes. Signing in with Apple or Google gives us the e-mail the provider verified and, the first time, the name.
Your entries. Accounts, cards, entries with amount, date, description and note, budgets, categories and category rules. They are what Bolgo exists to keep: they live in Bolgo's cloud, so you can change phones without losing anything, and your phone keeps only a copy of what the screens show and what has not gone up yet. Nobody on the team reads your entries. Support sees only your profile, your plan and the phone in use, and every action of the team is logged.
Your phone. Its platform (iPhone or Android), the app version, the time zone, and the currency and country its region suggests. They serve the session, your "today" and your currency. We also keep the days the app was opened, only the day and nothing of what you did in it, so we can count how many people use Bolgo and how many come back.
Your subscription. Your Bolgo account identifier and what the store you subscribed in (the App Store or Google Play) reports about each charge, through RevenueCat: the amount, the currency, the country, the plan, the date and whether the subscription renews. Never the card number, which stays with the store. We keep each charge to know how much the company earns; if you delete your account, the charge keeps nothing that says it was yours.
Usage statistics. Which screens you use and how often, with the app's language, country and currency and a random identifier of this install, which is not your account. Never amounts, descriptions, banks, e-mail or names. With the same yes, the app also records the screen (where you tap and where you go) with every text, number and image covered before it leaves the device, with no identifier of your account. In the European Economic Area, the United Kingdom and Switzerland nothing leaves before you allow it; elsewhere it leaves until you turn it off in Settings. There is no geolocation.
PDF statements. When you choose to import a PDF statement, the file is read by an artificial intelligence model from OpenAI, in the United States, only to become entry lines. The whole file goes, with everything it shows: the entries, the amounts, the descriptions, the bank's name and, if they are printed on it, your name and account number. Before the first PDF the app says so and asks for your permission, and only sends it after you tap "Allow and send"; with "Don't send", the PDF does not leave your device. Bolgo sends nothing else of yours with the file: not your e-mail, not what is already in the app. Under OpenAI's terms for those who use its API, the file is used only for this reading, is not used to train models, and may be kept for up to 30 days for OpenAI to check for abuse, before it is deleted. OFX, QFX, QIF and CSV statements are read by Bolgo itself, on our server, and never go through a model.
AI assistants you connect. If you connect an AI assistant to Bolgo, such as Claude, by Anthropic, it reads and changes your data in Bolgo the way you ask it to, after you tap Allow on a page of Bolgo itself. What the assistant reads (accounts, cards, entries, budgets, categories, and the descriptions and notes you wrote) goes to its company, on its servers, and there it follows that company's privacy policy, not this one: the assistant is your choice, not a service Bolgo hires. It never receives your password, and through Bolgo it cannot delete your account, erase all your data or touch your plan. For each connection we keep the assistant's name, how it identified itself to Bolgo (the address of its document, or the registration it made itself, with the addresses it goes back to), what you allowed (to read, or to read and change) and when it was used. You disconnect it whenever you want in Settings, "Where you are signed in", and changing your password or deleting your account disconnects it too.
The website waitlist. When you join the waitlist on the website you give us your email, and with it we keep the language of the page, the version of this policy it showed and the country, which we take from your browser's time zone (never from your IP address), and, when the link that brought you says which campaign it is from (the utm words of the address, such as utm_source=instagram), those words, and, when you came through a Google ad, the id of that click (the gclid of the address), which only says which ad the entry came from. They serve one notice only: that Bolgo is out on iPhone. Before it, we may send you an email to confirm the address is yours; without the confirmation, it leaves the list after 7 days. The email does not become an account, gets no other message and goes to no one. The exception is the Android test: when you ask to test the app through the form on the website, you join this same list with a mark of the request, and we send it the emails of the test: the invitation, right after the confirmation, with the link to join Bolgo's group of testers, a Google Groups group whose members only our team can see and which is how Google Play opens the test to the Google account of whoever joins, and three more during the 14 days of the test, with tips and questions you answer only if you want to. If you'd rather not get the rest, just reply to one of them. The website also counts its own visits, with no cookie and without keeping your IP address: each visit to a page, each tap on Download and each entry to the list adds 1 to a number for the day, with the page and the kind of site the visit came from (or the utm_source word of the link). None of it says who visited. The website uses no cookies and no script from another server without your yes.
WhatsApp, if you want it. After the email, the website also offers WhatsApp, and giving the number is optional. If you give the number and tap the button that says you agree, you get the same notices there: that Bolgo is out and, if you asked for it, the ones of the Android test. We keep the number with your entry on the list, with the day you agreed and the version of this policy the page showed. The messages leave through Ledio, the messaging tool we use, and arrive through WhatsApp, from Meta. To stop getting them, just reply STOP.
The website's cookies. If you accept in the website's cookie notice, it loads Google Tag Manager, Google Analytics, Microsoft Clarity and the Meta Pixel. They serve to understand how the page is used (Clarity records the movements on the page, with what you type hidden) and to measure Bolgo's ads. When you join the list, they only get the news that someone joined, the language of the page, whether the form was the iPhone's or the Android's and the utm words of the link that brought you, never your email or your name. Without your yes, none of them loads. The choice lasts 12 months, and you change it with the "Cookies" link at the bottom of the website.
Who we share with
Only with those who provide a service to Bolgo, and only what the service needs:
- Railway (United States, Virginia): where the API and the database live.
- Resend: sends the e-mails with codes. Receives your e-mail and the code, never your name.
- OpenAI (United States): reads PDF statements, only after your permission in the app.
- RevenueCat: manages the Premium subscription with the store you subscribed in.
- PostHog (servers in the European Union): receives the usage statistics, under the conditions above.
- Microsoft Clarity (United States): receives the app's screen recordings, covered, under the same conditions.
- Sentry (United States): receives crash reports from the app and the API, so we can fix what breaks. A report says where the code failed, the app version and the device model. Before it leaves, it goes through a filter that takes out e-mails, amounts and long numbers, built so it does not carry what you logged or who you are.
- Apple: Sign in with Apple and, on iPhone, the subscription payment.
- Google: Sign in with Google, the subscription payment on Android, the group of testers of the Android test (Google Groups) and, on the website, Google Tag Manager and Google Analytics, only if you accept the cookies.
- Ledio: sends the waitlist's notices on WhatsApp to whoever gave a number. It receives the number, the language of the page and whether you asked for the Android test, never your email.
- Meta, through WhatsApp: delivers those messages.
- Microsoft and Meta: on the website only, and only if you accept the cookies (Microsoft Clarity and the Meta Pixel), on the terms above.
- Expo (United States): delivers the app's updates. The app asks whether there is a new version and downloads its code; the request carries the app version, the phone's system and a random identifier of this installation, never what you logged or who you are.
Outside this list, your data only goes to another company when you send it yourself: an AI assistant you connect, under the conditions above, is that case.
We do not sell data. There are no ads.
Where your data lives
The API and the database are in the United States. For people in Brazil (LGPD) and in the European Economic Area, the United Kingdom and Switzerland (GDPR and UK GDPR) this is an international transfer, covered by the providers' contractual clauses. What your phone keeps stays on it.
For how long
- Your account and your entries: as long as the account exists. When you delete the account you have 7 days to come back by signing in again; after that, everything is erased.
- Ended sessions: 30 days. E-mail codes: 1 day after used or expired. The sync command log: 30 days. The days the app was opened: 400 days, and sooner with the account. The website's visit counts: 400 days.
- Subscription charges: as long as accounting and tax law require, and with nothing that says whose they were once the account is gone.
- The database backups: the daily ones for 6 days and the weekly ones for 27. What was erased leaves them within that time.
- "Erase all data" erases the entries in the cloud and on the phone at once, and the account stays, empty.
- The waitlist: 30 days after the launch notice, or sooner, if you ask to leave. An address that was sent a confirmation and never confirmed: 7 days. The WhatsApp number you gave leaves with your entry.
Your rights
At any time, in the app itself, you can: see and correct what we keep (that is the app); export everything as a spreadsheet or a backup file; erase all data; delete the account; turn usage statistics off. The steps to delete the account, also for whoever no longer has the app, are at bolgo.io/en/delete-account. For whatever the app does not do, write to officialbolgo@gmail.com: we answer within 15 days. You may also complain to the ANPD (Brazil) or to the data protection authority of your country.
Security
Passwords with argon2id, sessions with a 15-minute token and rotating renewal, one active session per person on the phone and another on the computer, each connected AI assistant with its own, everything over HTTPS. On the phone, the code and biometric lock is optional, and the code lives only in the phone's key store (the Keychain, on iPhone). The backup file you export is not encrypted: keep it where only you can reach it.
Age
Bolgo is for people aged 18 or older.
Changes
A new version of this policy has a new date. The app keeps the version you accepted and asks again when it changes in what matters.