BePresent Android Privacy Policy

1. Information We Collect

The app collects information you provide directly, information generated through app use, and information required to support login, analytics, syncing, subscriptions, and social accountability features.

Category	Examples	Why it is collected
Account and profile information	Name, display name, and in some flows email or username associated with login or analytics profiles.	To create and manage your account, personalize the app, support authentication, and measure product usage.
Identifiers	Auth0 subject identifier, internal user ID, friend code, Mixpanel identity, and a generated device ID.	To authenticate users, link synced records, support social features, and associate subscription state with a device or account.
App activity and usage information	Per-app screen time, open counts, foreground events, session history, goals, streaks, XP, coins, and focus statistics.	To provide dashboard metrics, app intentions, focus features, progress tracking, syncing, and accountability features.
Installed-app metadata	Installed app package names and app names selected or detected for app intentions, blocking, and usage reporting.	To let you choose apps, display app labels, and sync selected or measured app data to backend services.
Accountability partner information	Partner contact name and phone number, plus messages triggered when a partner is added or when goals are broken.	To support accountability features and send SMS notifications through Twilio.
Subscription and purchase information	Stripe customer ID, Stripe subscription ID, subscription status, price ID, current billing period end, and device-linked subscription records.	To create subscriptions, process subscription state, and unlock paid features.
Technical and analytics information	App version, locale, acquisition source, age bracket, event history, and last active timestamps.	To monitor usage, understand product performance, and improve the app.

Payment card details are typically collected by Stripe during checkout. Based on the current Android and backend code reviewed for this page, the BePresent app stores subscription-related identifiers and status, not raw card numbers in this codebase.

2. Android Permissions and Device Access

BePresent requests several Android permissions to deliver focus and blocking features. Important permissions include:

Usage access (`PACKAGE_USAGE_STATS`): used to read app usage events and calculate screen time, open counts, and foreground activity.
Query all packages (`QUERY_ALL_PACKAGES`): used to identify installed apps so you can select apps for intentions or blocking, and so app names can be synced alongside package names.
Notifications: used to send reminders and session-related notices.
Foreground service, exact alarm, wake lock, boot completed, battery optimization, and overlay-related permissions: used to keep monitoring, alarms, and blocking features working reliably.
Internet access: used to sync with backend services and communicate with third-party providers.

3. How We Use Information

Provide app intentions, blocking sessions, scheduled sessions, streaks, rewards, dashboards, and social accountability features.
Authenticate users and connect app data across devices or sessions.
Sync local data to backend services so progress and account-linked features can persist.
Measure app usage, feature adoption, and product performance through analytics.
Create and maintain subscriptions and link subscription state to your account or device.
Send accountability-partner SMS notifications when those features are used.
Maintain app security, reliability, debugging, and fraud-prevention workflows.

Auth0 for login Convex for backend and sync Mixpanel for analytics Stripe for subscriptions Twilio for SMS

4. How We Share Information

We share information with service providers only as needed to operate the app and its features. Current providers indicated by the code reviewed include:

Auth0: for authentication and account identity.
Convex: for backend data storage, syncing, and application logic.
Mixpanel: for product analytics and user profile/event tracking.
Stripe: for subscription creation, billing workflows, and subscription lifecycle events.
Twilio: for accountability-partner SMS notifications.

We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer such as a merger, acquisition, financing, or asset sale.

5. Data Retention

We retain information for as long as reasonably necessary to operate the app, maintain your account, provide subscriptions and social features, comply with legal obligations, resolve disputes, and enforce agreements. Retention periods can vary depending on the data type, whether you maintain an account or subscription, and operational or legal needs.

6. Your Choices and Rights

You can stop providing certain information by not using optional features such as account login, subscriptions, or accountability partners.
You can revoke Android permissions through your device settings, although some features may stop working properly.
You can request access, correction, or deletion inquiries by contacting us using the information below. We will review requests in line with applicable law and operational constraints.

7. Children’s Privacy

The app is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information, contact us so we can review and address the issue.

8. Security

We use reasonable administrative, technical, and organizational measures designed to protect information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

9. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we may update the effective date above and provide additional notice where appropriate.