1. Scope
This Privacy Policy explains how DateCompass handles information when you use the DateCompass mobile application, beta services, support channels, and related test features. The beta may use local-only features and selected staging cloud services depending on the build configuration.
2. Privacy-first product design
- Many core functions—including the activity catalog, saved content, planning tools, checklists, curated Date Coach guidance, local preferences, and certain reminders—can operate on the device.
- DateCompass does not currently request background location permission.
- Local notification reminders are scheduled on the device.
- Analytics consent is designed to default off unless the user affirmatively enables it.
- Date Coach free text is not intended to be stored in notification history or sent to billing providers.
3. Information DateCompass may process
Information stored locally
Saved activities, Favorites, Bucket List items, My Dates, planner information, checklist state, custom lists, reminder preferences, notification history, recent planning areas, and other app preferences may be stored on your device.
Account and cloud information
If accounts are enabled, DateCompass may process authentication identifiers and account metadata, private user state selected for cloud backup or synchronization, consent metadata, and limited operational records necessary to provide cloud-enabled features.
Beta feedback and diagnostics
When you submit beta feedback, DateCompass may attach privacy-safe diagnostics such as app version, build number, current screen or route, device class, operating-system version, and activity context where relevant. Feedback is not intended to include passwords, billing credentials, exact location, Date Coach free text, authentication tokens, or unrelated personal content.
Location
DateCompass may request foreground location after a contextual explanation. Depending on platform permissions, the app may receive approximate or precise device location while you use that feature. Manual planning-area entry remains available.
Notifications
DateCompass may request permission to send local notifications after you use reminder-related features. Reminder settings and notification metadata may be stored locally on the device.
Billing
If billing is enabled in a future staging or production build, DateCompass may use a configured billing service to interpret store entitlements. Apple or Google processes payment credentials; DateCompass should not receive full payment-card details.
4. External providers
Depending on build configuration, DateCompass may rely on third-party services for authentication, cloud storage, crash reporting, weather, maps/routes, billing, app distribution, or support.
- Firebase services may be used for authentication, private synchronization, account deletion, beta feedback, callable functions, and staging diagnostics.
- Open-Meteo may be used for weather information when live weather is enabled.
- Mapbox may be used for directions or mapping when configured.
- RevenueCat or another billing adapter may be used for subscription entitlement handling when billing is enabled.
- Google Play and Apple may process distribution, purchases, crash information, and platform permissions under their own policies.
5. How information is used
- Provide requested discovery, planning, saving, reminder, and location-assisted features.
- Synchronize private data when a user chooses account-enabled cloud features.
- Respond to support requests and beta feedback.
- Maintain security, prevent abuse, enforce quotas, and diagnose failures.
- Improve DateCompass using consent-aware analytics or crash information when enabled.
6. Sharing and sale of information
DateCompass does not intend to sell personal information. Information may be disclosed to service providers only as necessary to operate configured features, comply with law, protect users or the service, or support a legitimate business transaction subject to applicable law. DateCompass does not use planning content for third-party advertising in the current beta design.
7. Retention
Local information generally remains on the device until you delete it, clear app data, uninstall the app, or use an available reset or delete function. Cloud information, when accounts are enabled, is retained as necessary to provide the service, maintain security, resolve disputes, or meet legal obligations, subject to the account and data deletion process.
8. Data deletion and controls
You may edit or delete many locally stored preferences and planning records within the app. If accounts are enabled, use the in-app account deletion flow when available or contact northstarapp.support@gmail.com for assistance. See the Data Deletion Policy for more information.
9. Minimum age
The invitation-only beta is intended for adults age 18 and older. Do not use the beta if you are under 18.
10. Security
DateCompass uses reasonable safeguards appropriate to a beta application, including access controls, validation, privacy-filtered logging, and security testing. No system can guarantee absolute security, and beta software may contain defects.
11. Your rights
Privacy rights vary by jurisdiction. If applicable law gives you rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, contact DateCompass Support.
12. Changes
DateCompass may update this Privacy Policy as the beta changes. Material updates may be communicated through the app, beta communications, or this hosted page.
13. Contact
Privacy questions: northstarapp.support@gmail.com