Account and profile data
Email address, display name, profile photo URL, authentication provider, Firebase UID, login tokens, and account settings.
Briko AI
Privacy Policy
This Privacy Policy explains how Briko AI collects, uses, stores, shares, protects, and deletes personal data when you use the Briko AI mobile application, website, account-deletion pages, and related support services.
1. Scope And Developer Identity
Briko AI is operated by Sahar Yafe, Israel ("Briko AI", "we", "us"). This policy applies to the app identified on Google Play as Briko AI with package name com.xfrdaily.app. It also applies to users who install internal, closed, open, or production testing builds.
You can contact us about privacy, data access, correction, portability, objection, account deletion, or support at xfrdaily@gmail.com. We aim to respond to verified privacy requests within 30 days unless applicable law requires a different period.
2. Data We Collect
Workspace and productivity content
Tasks, notes, reminders, subtasks, schedules, app preferences, AI chat history, saved memories, generated task plans, and user-selected attachments.
Voice, speech, camera, and selected files
Microphone audio when you use voice features, camera images or library files you choose, and document content you intentionally import for task extraction, transcription, attachments, or PDF sharing.
Purchase and subscription data
Google Play product identifiers, purchase tokens, subscription status, entitlement level, RevenueCat app user ID, and transaction timestamps. We do not receive or store full card numbers or bank details.
Device, app, security, and notification data
Firebase installation ID, Firebase Cloud Messaging token, device integrity/App Check verdicts, app version, operating system, language, notification scheduling information, rewarded-ad view counters, ad interaction signals, and SDK diagnostics. Ad providers may infer approximate location from IP address.
Diagnostics and support data
Error scopes, warning codes, app state needed to investigate bugs, and any screenshots, logs, or messages you voluntarily send to support.
We do not collect precise location, contacts, SMS, call logs, health data, installed-app inventory, advertising ID for ads, or biometric data.
3. Why We Use Data
- To create accounts, authenticate users, and sync your workspace across devices.
- To create, edit, organize, remind, and notify you about tasks.
- To run AI features you choose to use, including task extraction, transcription, summaries, and productivity suggestions.
- To process subscriptions, verify purchase status, restore purchases, and unlock paid features.
- To send push notifications and time-sensitive reminders you configure.
- To show optional rewarded ads, verify completed ad views, prevent reward abuse, and grant the related credits or call-reminder bonus.
- To protect the app from abuse, quota bypassing, fraud, unauthorized calls to backend services, and payment misuse.
- To provide support, diagnose issues, improve reliability, and comply with legal obligations.
We do not sell personal data, use personal data for third-party advertising, build advertising profiles, or share data with data brokers.
4. Permissions And Prominent Disclosures
| Permission or capability | When used | Purpose |
|---|---|---|
| Microphone | Only after you start voice input or transcription | Convert speech to text and power voice AI features |
| Camera and photos/files | Only when you choose to scan or attach content | Extract tasks from images/files, attach content, or generate/share task artifacts |
| Notifications, exact alarms, foreground services, full-screen intent | Only for reminders and call-style reminder flows you configure | Deliver scheduled reminders reliably, including urgent heads-up/call reminder experiences |
| App Check / Play Integrity | Automatically for protected backend calls | Confirm app integrity and reduce abuse |
Sensitive permissions are requested through Android runtime permission dialogs where available. The app also provides contextual in-app explanations before requesting access for sensitive features.
5. Third-Party Processors And SDKs
We use service providers only as needed to operate the app. They receive the data required for the feature you use.
| Provider | Purpose | Data involved |
|---|---|---|
| Google Firebase Authentication | Account login and session management | Email, display name, provider, authentication tokens, IP-related security logs |
| Google Firebase Cloud Firestore / Storage | Cloud sync and optional attachments | Tasks, notes, reminders, settings, chat records, selected files |
| Firebase Cloud Messaging and Expo/notification tooling | Push notifications and reminders | FCM token, device/app notification metadata |
| Google Sign-In | Optional Google login | Google account profile, email, ID token |
| Google Play Billing | Subscriptions and in-app purchase checkout | Product ID, purchase token, purchase status; payment details stay with Google Play |
| RevenueCat | Subscription entitlement, purchase restoration, paywall metadata | App user ID, purchase tokens, product identifiers, subscription status, transaction metadata |
| Google AdMob / Google Mobile Ads SDK | Optional rewarded ads, ad delivery, ad measurement, SDK diagnostics, and fraud prevention | IP address, ad views/taps, product interactions, diagnostics, and device/account identifiers handled by the SDK. Android advertising ID collection is blocked in the app manifest. |
| Google Gemini API | AI generation and multimodal features | Prompts, task context, and selected images/files when you invoke those features |
| Groq APIs | AI chat, tool use, and Whisper transcription | Text prompts, task/chat context, and temporary audio for transcription when used |
| Google Play Integrity / Firebase App Check | Security and abuse prevention | Integrity verdicts and related device/app attestation metadata |
AI providers process your prompts and content only when you invoke AI features. We do not authorize providers to train general models on your personal content where enterprise or opt-out controls are available to us.
6. Google Play Data Safety Summary
Your Google Play Data Safety form should match the app's real behavior across all active tracks. Based on the current app, Briko AI collects data for app functionality, account management, payments, security, analytics/diagnostics, and support. Data is transmitted over HTTPS and account deletion is supported in-app and through a web request page.
- Collected data categories: account identifiers, email/display name, user-generated content, app activity, diagnostics, device identifiers, purchase history, rewarded-ad interactions, approximate location inferred from IP address by ad/security providers, photos/files selected by the user, and audio when voice features are used.
- Sharing: data is shared with service providers listed above to provide app features. Google Mobile Ads may collect and share ad-related data for advertising, analytics, and fraud prevention. We do not sell personal data.
- Optional collection: microphone, camera/photos/files, and AI content are collected only when you use those features.
- Required collection: account/session data, app security data, subscription entitlement data, and workspace sync data are needed for account-based app functionality.
7. Security
- Data is transmitted using modern encryption such as HTTPS/TLS.
- Firebase and provider storage use encryption at rest where supported by the provider.
- Authentication tokens are stored using platform secure storage when available.
- App Check, Play Integrity, rate limits, and server-side checks help prevent unauthorized backend use.
- We restrict internal access to personal data to what is needed for support, security, and operation.
8. Retention And Deletion
- Account data: kept until you delete your account or request deletion.
- Tasks, notes, reminders, settings, and attachments: kept until you delete them or delete your account.
- AI chat history and saved memories: kept in your account until deleted by you, deleted by account deletion, or purged under app retention rules.
- Voice audio: used transiently for the session or transcription and not intentionally stored as an audio file after processing, unless you explicitly save or share a recording through a future feature.
- Purchase records: retained as long as needed to verify subscriptions, restore purchases, resolve disputes, and meet accounting/legal requirements.
- Security and diagnostics: retained only as long as needed for security, abuse prevention, troubleshooting, and legal compliance.
- Provider backups: deleted data may remain in encrypted provider backups for a limited rolling backup period, typically up to 90 days.
You can delete your account in the app from Settings > Privacy > Delete account permanently, or by using our account deletion page. Account deletion removes account-linked app data unless retention is required for security, fraud prevention, payment disputes, taxes, legal obligations, or enforcement of our terms.
9. International Transfers
Briko AI is operated from Israel and uses providers that may process data in the United States, the European Economic Area, Israel, and other locations where they operate infrastructure. Where required, we rely on contractual protections such as Standard Contractual Clauses and provider security measures.
10. Your Rights
Depending on your location, including under GDPR/UK GDPR, Israel privacy law, and certain US state privacy laws, you may have rights to access, correct, delete, export, restrict, or object to processing of personal data. You may also withdraw optional permissions through your device settings.
To exercise rights, email xfrdaily@gmail.com. We may ask you to verify your identity before acting on a request.
11. Children
Briko AI is not directed to children under 16 and is not intended for use by children without appropriate parental or guardian consent where required by law. If you believe a child provided personal data without appropriate consent, contact us and we will take reasonable steps to delete it.
12. Changes
We may update this policy as the app, providers, or legal requirements change. Material changes will be reflected by updating the "Last updated" date and, where appropriate, by in-app notice or store listing updates.