Ensenada Discovery EN / PRIVACY
Privacy policy
Ensenada Discovery lets people discover activities and places in Ensenada without creating an account. This policy explains what information is processed when using the app, why it is used, and the choices available to each person.
We do not sell personal data or collect precise device location.
Developer and contact
Ensenada Discovery is published by Eduardo Prieto Apps, the developer responsible for the practices described in this policy. For questions, privacy requests, or to exercise your data choices, email eduardoprietoapps@gmail.com.
Use without an account
Home, Explore, the map, and public details can be used without signing in. Public editorial content is hosted in Supabase. To improve availability during connection problems, the app may temporarily keep a local copy and discard it after seven days.
Account data
Creating an account is optional and requested only for favorites, follows, and synchronized preferences. When signing in with a supported provider, we may receive an internal user identifier, email, name or image when shared, the provider used, and technical information needed to maintain the session. We do not receive or store Google or Apple passwords.
Favorites and preferences
When signed in, your account can store identifiers for favorited activities, followed places and organizers, preferred zones, and categories. Language and theme choices are stored locally. These data synchronize Saved content.
Usage and diagnostics
Operational telemetry is enabled by default and currently has no switch in Settings to disable it. We may process sessions, random installation and session identifiers, screens, content types and internal identifiers, filters, result counts, exploration mode, external actions, favorites, follows, authentication, notifications, app version, platform, language, general device model, operating system, crashes, exceptions, retries, and technical context. Operational telemetry is sent to Supabase and Firebase Crashlytics processes technical error information. When signed in, the server may associate events with an internal account identifier. Properties do not include a name, email, free-form search text, precise location, notification tokens, private URLs, or complete Supabase responses. Offline events are removed after the backend accepts or rejects them and are pruned after a maximum of 35 days or when local limits are reached. We do not use this data for advertising or to track a person across apps or websites.
Notifications
Notifications are optional and depend on system permission. If enabled while signed in, we may store a technical Firebase Cloud Messaging token, platform, and its account relationship to deliver Ensenada Discovery notifications. Followed places, organizers, zones, and categories may be used to select relevant alerts. When notifications are disabled or you sign out, we try to disassociate the token.
Calendar and location
When you choose Add to calendar, the app opens the system interface with the activity details. We do not upload calendar data to our servers. We show editorial locations and coordinates for activities or places, but do not request or collect precise device location.
Support and reports
When contacting support or reporting incorrect information, the app opens your email client with a template. Sending is voluntary and free-form text is processed by your email provider. We do not include it in operational telemetry or Crashlytics.
Providers and shared data
We use Supabase for public content, authentication, accounts, favorites, follows, preferences, operational telemetry, and notification inbox and device registration; Google Firebase for Crashlytics and Cloud Messaging; and Google or Apple when you choose a sign-in provider. We share only the data needed for those functions. We require our providers to protect data to a level equivalent to that described here and review their applicable terms and controls.
Retention and deletion
We retain account data while the account is active. After a deletion request, we delete or disassociate the account and its associated data, normally completing the process within 30 days. Backups and minimum technical logs may remain temporarily through their operational cycles or when needed for security, fraud prevention, or a legal obligation, after which they are deleted or anonymized.
Your choices and withdrawing consent
You can withdraw notification permission in system settings and delete your account under Account → Account settings → Delete account. You may also request access, correction, or deletion by email. Operational telemetry is enabled by default and currently has no in-app opt-out control. Withdrawing permission does not affect processing completed before that change.
Security, transfers, and changes
We use access controls and encrypted connections, although no system is completely infallible. Providers may process information in other countries under their terms and safeguards. This policy may change when the app, providers, or applicable requirements change; we will publish the current date here.
Contact
For privacy questions or data requests, email eduardoprietoapps@gmail.com.