Data controller: BrokeDaddy
Contact (privacy & data requests): thecoolbotcompany@gmail.com
Mailing address (optional): Not published here; available on request to the contact email for legitimate legal or data-protection inquiries.
Before you use the App
Host this document at a public URL and add that URL to your app store listings and, where you add it, in App settings. If your legal entity or contact details differ from what is shown below, update the controller name and address sections accordingly.
1. Who is responsible for your data?
2. What data we process
Account and identity
Email and authentication if you use email/password or Sign in with Google, Facebook, or X (Twitter). OAuth is handled by Supabase and the identity provider; we may receive name, email, and a provider user ID as the provider allows.
User ID and session tokens on your device to keep you signed in.
Financial and App content you enter
Profile and budget data: e.g. currency, income, budget/reset preferences, AI “hostility” options.
Spending and transaction data you log: amounts, categories, notes, dates, and roast text or metadata we store.
Onboarding data you provide.
This is user-entered; we do not pull live bank data in the current App and we do not collect card numbers or bank account numbers as part of the App.
Analytics (PostHog)
Product analytics: e.g. sign-up/sign-in, settings, expense logged, dashboard views, ad surfaces, and similar events.
Expense events may include category, amount (number), mode, currency, and budget flags.
When you are signed in, we may use your user ID and, where sent, email in identify for analytics.
Advertising (Google Mobile Ads)
Device, advertising, and related identifiers and technical data used to show, deliver, and measure ads, per your device and account settings and Google’s practices.
Notifications (optional)
If you enable reminders, the OS / Expo / Apple or Google may process device tokens for delivery.
AI / roasts
We may send amount, category, note, language, and related fields to Supabase Edge Functions (or similar) and, where used, a model provider, only to return text in the App. Sandbox flows may send limited input in sandbox/rate-limited mode.
Technical data
IP, device type, OS, app version; device or other IDs (including for ads and analytics); we do not use the App to collect precise location in the current version.
Web
Local storage / cookies as needed for auth and the web build.
3. How we use your data
Including: account management; app functionality; personalization (e.g. roasts and insights from what you log); analytics; advertising (AdMob and partners); security, fraud, and legal compliance. We do not sell your data for money in the common sense; ads and analytics may still involve sharing with partners as described by Google and your analytics provider.
5. Legal bases (EEA, UK, CH, etc.)
Contract; legitimate interests (product, security, limited analytics); consent where required (e.g. some cookies, ads in some cases); legal obligation where applicable.
6. International transfers
Supabase, PostHog, Google, and others may process data in the U.S. and other countries, using appropriate safeguards (e.g. SCCs or Data Privacy Framework where applicable) as described by those providers.
7. Retention
Data is kept while your account is active and for backup / legal periods after, unless law requires longer. Analytics and logs follow each provider’s retention. Contact thecoolbotcompany@gmail.com for more detail.
8. Your rights
Subject to your location: access, correction, deletion, portability, restriction, objection, and complaint to a regulator. You can change much of your data in the App. Account and data deletion: use your in-App data-deletion request link (if you add one) or email thecoolbotcompany@gmail.com with “Account and data deletion” and your registered email. For U.S. state ad opt-outs, use Google and device ad / tracking settings. EEA/UK/CH users: contact the email above.
9. Children
Not directed at children under 16 (or the age in your country). We do not knowingly collect data from children; contact us to delete if you believe we have.
10. Security
HTTPS in transit and reasonable safeguards. No system is 100% secure; use a strong password and keep your device safe.
11. Changes
We will update this page and the Effective date; we will add in-app or email notice for material changes where required by law.
12. Contact
If you have any questions or requests about this Privacy Policy or your data, contact us at: