Privacy Policy

This policy explains how Mind1 handles data in FilaCerta. For questions or requests about your data, email leo@mind1.tech.

Data we use and why

• Account and sign-in: email address, provider-issued identifier, sign-in dates, and permissions used to create your account, authenticate you, and control access. The sign-in provider may also give the authentication service your name and profile photo.
• Session and security: authentication records, sessions, a second factor when configured, and technical records needed to prevent abuse, investigate failures, and protect the service. The infrastructure may record connection information such as your IP address.
• favorites, alerts, and guest identification are stored in your browser. Clearing this site's local data removes these preferences from that browser.
• Itinerary: Trip dates, parks, chosen attractions and progress are saved on this device and, when signed in, synced to your account for use on other devices. Earlier device-only plans are imported only when you choose to do so. Deleting a plan also syncs its deletion; clearing device data removes only its local copy.
• Comments, when enabled: your display name, comment, attraction, and date may be stored and shown to other users. Avoid including other people's personal information.

Sign-in with Google or Apple

When available, social sign-in is processed by the provider you choose and Supabase Auth. We request only the identity information needed to sign you in. We do not request access to Google email, files, calendars, or contacts. FilaCerta does not receive your Google or Apple account password.

Cookies and local storage

We use necessary cookies to maintain your session and protect sign-in, as well as local storage for the preferences described above. Signing out ends your FilaCerta session, but does not automatically delete your favorites or disconnect your Google or Apple account.

Service providers and processing

We use Supabase for authentication, Railway for the API and database, and Vercel to host and deliver the website. These providers process data needed to operate the service; it may be stored outside Brazil. Data received from Google is used for authentication and account functionality, not for advertising or sale.

Purchases

When purchases are available, Stripe processes website payments; Apple or Google Play processes app payments. RevenueCat validates store purchases. We use your account identifier, product, transaction, payment status and expiry to recognize your pass across devices and handle refunds. The FilaCerta app does not collect card details.

Notifications and maps

App preferences and predictive alerts stay on this device. Remote queue alerts, when enabled, send a notification token, language, selected attractions and limits to the alert service and Expo. An alert expires after 24 hours; inactive installation records expire after 30 days. Maps use ThemeParks.wiki and OpenStreetMap; providers receive your IP and requested map area. The app does not request GPS location, microphone or contacts.

Retention and requests

Request account deletion. The app also offers this option in Profile. Deletion removes the profile, synced itinerary and sessions, and requests removal from the identity provider. Minimal transaction and security records are retained for refunds, fraud prevention and legal obligations. Subscription renewal must be canceled where you purchased. Other devices may still hold local preferences until their data is cleared.

Account data is kept while you use the service. Technical and security records may be retained when needed to protect the system or meet legal obligations. You can request access, correction, or deletion of your data using the contact above. We may verify your identity to protect your account and tell you about any data that must be retained.

You can also revoke FilaCerta's connection in your Google or Apple settings. Revocation prevents new access through that connection, but does not replace a request to delete data already stored in FilaCerta.

Updates

This page will be updated when our data practices change, with the version date shown.