Privacy Policy — BAYBO
Last updated: August 18, 2026 Effective: from publication on this page
This Privacy Policy describes how the BAYBO mobile app (Android and iOS) and the https://baybo.app website collect, use, store, share, and protect user information. It applies to all users in Brazil and abroad. By using the service, you agree to the terms described here.
The service complies with the Brazilian General Data Protection Law (Law No. 13,709/2018 — LGPD).
1. Who is the controller
BAYBO is operated by:
- Legal entity: TORPHI CONTISE TRATAMENTO DE DADOS LTDA
- Brazilian tax ID (CNPJ): 05.526.201/0001-40
- Address: Alameda dos Guatás, 468, Apt 102, Planalto Paulista, São Paulo/SP, ZIP 04053-041, Brazil
- Legal representative: Marco Pisani (managing partner)
- Privacy contact e-mail: marco@baybo.app
TORPHI CONTISE TRATAMENTO DE DADOS LTDA acts as the data controller under art. 5, VI, of the LGPD.
2. Data we collect
2.1. Data you provide directly
| Category | Data | When we collect it |
|---|---|---|
| Identification | Full name, profile photo, e-mail address | When you create an account (e-mail/password) or sign in with Google |
| Credentials | Password (stored as a hash) | When you create an account or change the password by e-mail |
| Content | Messages sent through the support chat | When you open the help chat |
| Content | Questions, messages, and answers from the Baybo Assistant | When you use the Baybo Assistant |
| Content | .xlsx spreadsheets you choose to send to create or update a strategy | When you use the optional spreadsheet analysis feature |
| Settings | App preferences (language, theme, filters) | While using the app |
| Content | The screenshot you choose to update a manual account's balance | When you use the optional "update balance by photo" feature |
2.2. Data collected automatically
| Category | Data | Source |
|---|---|---|
| Identifiers | Internal user ID, anonymous device/app ID | Internal + Firebase/Google Analytics + PostHog + session replay when enabled |
| App usage | Screens visited, interaction events, session time | Firebase/Google Analytics and PostHog |
| Service usage | Days you used the app, date and time of last use, platform and app version, and a record of each login (password, Google, or Apple) | BAYBO backend |
| Diagnostics | Error logs, stack traces, breadcrumbs, device model, OS and app version | Sentry |
| Notifications | FCM push token (Android and iOS) | Firebase Cloud Messaging / react-native-firebase |
| Network | IP address, approximate country derived from IP | API server, Firebase/Google Analytics, PostHog, and session replay when enabled |
| AI usage | Credit balance, model used, tokens, estimated cost, and timestamp of the call | BAYBO backend |
| AI credit purchases | Product purchased, store, purchase identifier/token/status, credits granted, and confirmation timestamp | Google Play/App Store + BAYBO backend |
We do not collect:
- Precise location (GPS).
- Contacts, camera, microphone, calendar.
- Advertising identifier (IDFA on iOS, AAID on Android).
- Health data, or identifiable biometrics (biometric authentication uses the OS API — your fingerprint or Face ID never leaves your device).
- Payment data, credit card, or bank account. For in-app purchases, the store processes the payment; BAYBO receives only the identifiers and statuses needed to validate the purchase, deliver AI credits, and prevent duplicate delivery.
About photos: the app does not scan or store your gallery. In the optional "update balance by photo" feature, you choose a specific screenshot (your bank app's balance screen), which is sent for reading by artificial intelligence and discarded afterwards — it is not kept on our servers. See §2.1, §4, and §6.
2.3. User financial data
When you register investments, positions, or goals in the app, that data is stored on our backend and associated with your user ID. It is not shared with third parties for commercial purposes nor used for marketing. It is used solely to generate the KPIs, charts, reports, and explanations the app shows you.
When you use the Baybo Assistant, the backend may send the AI provider only your question and the excerpts of your own financial data needed to answer it (for example: equity, deposits, profit, return, comparisons with CDI/dollar/Bitcoin, accounts, and relevant movements). The assistant is optional, requires in-app acceptance, does not execute orders, does not recommend investments, and does not change data.
When you use AI spreadsheet analysis, the original .xlsx file is stored on BAYBO's backend for strategy history, review, and republishing. In free-form AI mode, the backend converts the spreadsheet into a textual/canonical representation and sends OpenAI the content needed to interpret the spreadsheet and generate extraction, reconciliation, and calculation-plan artifacts. In BAYBO Template mode, parsing is deterministic on the backend and does not call an AI provider.
When you buy AI credits inside the app, payment is processed by the operating system's store. BAYBO records the purchased product, purchase identifier/token/status, and delivered credits to validate the receipt, unlock the digital benefit, provide support, and prevent the same purchase from granting credits more than once.
3. How we use the data
| Purpose | Legal basis (LGPD) |
|---|---|
| Authenticate you in the app | Performance of a contract (art. 7, V) |
| Display your investments, KPIs, and charts | Performance of a contract (art. 7, V) |
| Send push notifications you enabled | Consent (art. 7, I) |
| Answer questions through the Baybo Assistant about your own numbers | Consent (art. 7, I) |
| Analyze spreadsheets you send to create or update a strategy | Performance of a contract (art. 7, V) and, for free-form AI mode, consent (art. 7, I) |
| Read the balance from a screenshot you send (optional "update balance by photo") | Consent (art. 7, I) |
| Validate AI credit purchases, deliver the credits, and prevent duplicates or fraud | Performance of a contract (art. 7, V) and legitimate interest (art. 7, IX) |
| Diagnose crashes and improve stability | Legitimate interest (art. 7, IX) |
| Understand which screens and features are most used | Legitimate interest (art. 7, IX) |
| Answer questions via the support chat | Performance of a contract (art. 7, V) |
| Comply with legal obligations | Compliance with a legal obligation (art. 7, II) |
We do not use your data to build advertising profiles, sell to third parties, or train machine-learning models outside the service. We also do not authorize the use of your questions, answers, spreadsheets, or financial data sent through the Baybo Assistant or AI Spreadsheet feature to train AI models.
4. Who we share with
We share only what is strictly necessary with data processors (subprocessors), all under contractual protection clauses:
| Service | What we use it for | Data sent |
|---|---|---|
| Google Sign-In (Google LLC) | Authentication | Name, e-mail, profile photo |
| Sign in with Apple (Apple Inc.) | Authentication on iOS | Apple account identifier and e-mail (real or the Hide My Email relay address, if you choose it), plus your name on first sign-in |
| Google Play Billing / Google Play Developer API (Google LLC) | Process Android in-app purchases and validate/consume AI credit purchases | Product purchased, purchase token, purchase status, and order metadata needed for validation, delivery, support, and fraud prevention |
| Firebase/Google Analytics (Google LLC) | App usage analytics | Anonymous ID/app instance ID, screens, events, device model |
| Firebase Cloud Messaging (Google LLC) | Notifications on Android and iOS | FCM push token, notification payload |
| Apple App Store / StoreKit (Apple Inc.) | Process iOS in-app purchases and validate AI credit purchases when iOS IAP is active | Product purchased, transaction/receipt identifier, purchase status, and metadata needed for validation, delivery, support, and fraud prevention |
| Apple Push Notification Service | Final notification delivery on iOS via FCM/APNs | Notification payload |
| PostHog (PostHog Inc.) | App usage analytics (funnels, retention) and AI credit subscription events sent from our server | Internal user ID, screens, interaction events, device model; and, from the server, product purchased, store, credits delivered, and subscription status |
| Microsoft Clarity (Microsoft Corporation) | Session replay | Replay anonymous ID, current screen, device model, screen recordings when enabled |
| Sentry (Functional Software, Inc.) | Error monitoring | Stack trace, breadcrumbs, device model, app version |
| Anthropic (Anthropic PBC) | Baybo Assistant and reading balances from screenshots via vision AI | In the Baybo Assistant: your question, conversation history sent during the session, and excerpts of your financial data needed to answer. In balance-by-photo: the screenshot you send (may contain your name and the displayed balance). Data is sent only to process the answer/reading, not used to train models by default in the commercial API, and not sold by us. |
| OpenAI (OpenAI, L.L.C.) | Spreadsheet analysis in free-form AI mode | Textual/canonical representation of the .xlsx spreadsheet, answers you provide during the analysis, intermediate artifacts needed to interpret the spreadsheet (extraction, reconciliation, and calculation plan), model used, and usage/token metadata. Data is sent only to process the analysis, not used to train models by default in the commercial API, and not sold by us. |
The support chat is Baybo's own: the messages you exchange with us are stored on our servers (they do not go through a chat vendor) and are included in "download my data".
Provider policies: Google (https://policies.google.com/privacy), Apple (https://www.apple.com/legal/privacy/), Firebase (https://firebase.google.com/support/privacy), Microsoft Clarity (https://privacy.microsoft.com/privacystatement), PostHog (https://posthog.com/privacy), Sentry (https://sentry.io/privacy/), Anthropic (https://www.anthropic.com/legal/privacy), OpenAI (https://openai.com/enterprise-privacy/).
We do not sell your data. We do not share it with advertisers, brokerages, financial institutions, or any third party outside this list, except when required by court order or to protect the rights, safety, and integrity of the service.
5. International transfer
Some subprocessors (Google, Apple, Microsoft, PostHog, Sentry, Anthropic, OpenAI) process data on servers outside Brazil, mainly in the United States and the European Union. Transfers rely on art. 33 of the LGPD (standard contractual clauses or a country with an adequate level of protection, as applicable).
6. How long we keep it
| Category | Retention period |
|---|---|
| Account data (name, e-mail, ID) | While the account exists; up to 30 days after a deletion request |
| Financial data you registered | While the account exists; up to 30 days after a deletion request |
| Error logs (Sentry) | 90 days |
| Usage events (Firebase/Google Analytics) | 12 months |
| Usage and subscription events (PostHog) | Per the vendor's plan: 1 year on the free plan and up to 7 years on paid plans; deleted within 30 days of an account deletion request |
| Session replay recordings (Microsoft Clarity, when enabled) | 30 days; favorites and provider-selected samples may be retained for up to 9 months |
| Support chat messages | 24 months |
| Baybo Assistant messages | Not stored as permanent history on the backend; they remain in the app during the conversation and transit through the AI provider to process the answer |
| AI Spreadsheet files and artifacts | While the account/analysis exists; analyses that failed or were replaced can be deleted by you; up to 30 days after an account deletion request |
| Data sent to OpenAI in free-form AI mode | Temporary retention by the provider according to API policy; by default, up to 30 days for abuse monitoring, unless legal obligations or different contractual settings apply |
| AI credit/usage records | While the account exists; up to 30 days after a deletion request |
| AI credit purchase history and delivery ledger | While the account exists; up to 30 days after a deletion request, except where retention is needed for support, fraud prevention, chargebacks, or legal obligations |
| Screenshot sent for balance reading | Not stored by us — it only transits for the reading and is discarded; temporary retention at the provider (Anthropic) per its policy |
| Backend access logs | 6 months (minimum required by art. 15 of the Brazilian Civil Rights Framework for the Internet) |
| Backups | Up to 30 days after the original data is deleted |
After these periods, data is irreversibly deleted or anonymized.
7. Security
We apply reasonable technical and organizational measures to protect your data:
- HTTPS/TLS on all traffic between app, site, and backend.
- Authentication tokens stored in the Keychain (iOS) and Keystore/EncryptedSharedPreferences (Android) via expo-secure-store.
- Passwords: there are three authentication paths — e-mail/password, Google Sign-In, and Sign in with Apple. When you create an account or change the password by e-mail, the password is stored only as a hash (never in plain text); reset is done via a single-use link sent to your e-mail.
- Backend access restricted by API keys and JWT authentication.
- Databases with access restricted by IP/credential.
- Security updates applied regularly to dependencies.
No system is 100% secure. In case of an incident affecting your data, you will be notified as required by art. 48 of the LGPD.
8. Your rights (LGPD art. 18)
At any time, you may request, free of charge:
- Confirmation that we process your data.
- Access to the data we hold about you.
- Correction of incomplete, inaccurate, or outdated data.
- Anonymization, blocking, or deletion of unnecessary data or data processed in non-compliance with the LGPD.
- Portability of the data to another service provider.
- Deletion of data processed based on consent.
- Information about whom we share your data with.
- Withdrawal of consent, where applicable.
How to exercise: e-mail marco@baybo.app. We respond within 15 business days.
Delete your account
You can delete your account at any time at https://baybo.app/delete-account. You must be signed in to confirm. The operation removes your profile, all registered investments, connected integrations, preferences, and support messages. Removal occurs within 30 days and backups are purged within 60 days. If you prefer, send a request by e-mail to marco@baybo.app.
9. Children and adolescents
BAYBO is not directed at people under 18. We do not knowingly collect data from minors. If you are a legal guardian and identify that your underage child created an account without authorization, contact the e-mail above so we can remove the data.
10. Cookies and similar technologies (website)
The https://baybo.app website uses essential cookies (keep you signed in and remember preferences). When session replay is enabled on the web, the provider may use local storage/technical cookies to link the session recording. You can disable cookies in your browser — without the essential ones, login won't work. The mobile app does not use cookies: it stores a session token in the OS secure storage.
11. Identifiers and tracking (iOS — App Tracking Transparency)
The app does not track you across third-party apps and websites. We do not use Apple's IDFA. For that reason the app does not show the App Tracking Transparency prompt. Internal usage analytics use an anonymous identifier/app instance ID, not linked to advertising identifiers.
12. Changes to this policy
We may update this policy to reflect changes in the service, the law, or subprocessors. The "Last updated" date at the top will change. Relevant changes will be notified via push and/or an in-app banner at least 7 days in advance.
13. Governing law and venue
This policy is governed by the laws of the Federative Republic of Brazil. The courts of São Paulo/SP are elected to settle any disputes, without prejudice to any other venue privileged by law.
14. Contact
Questions, requests about your data, or reports:
E-mail: marco@baybo.app Controller: TORPHI CONTISE TRATAMENTO DE DADOS LTDA — CNPJ 05.526.201/0001-40 Legal representative: Marco Pisani (managing partner)