Privacy Policy

When you use TRACE, we collect: • Account data: email address, username, display name, profile photo, and the profile country you select for “From” • Trip data: cities visited or planned, travel dates, photos, captions, and categories you choose to add • Social and communication data: follows and requests, messages, comments, likes, reports, saved trips, and saved places • Selected city data: the city and country you manually choose for “Now in”; TRACE does not use that feature to collect precise GPS coordinates or background location • Crash diagnostics, only when Sentry is configured for the build: error type, exception value, code stack, app version, platform, release, and environment. For Dart-origin Sentry events, TRACE removes the Sentry user, request, message, breadcrumb, transaction, culprit, tag, server-name, extra, and context fields. Exception values and stack traces remain for diagnosis. Native iOS and Android crash diagnostics do not pass through the Dart event sanitizer and may include native context and tag fields supplied by the Sentry native SDK PostHog product analytics is disabled in the current operational configuration. If it is enabled later under reviewed controls, it is limited to a bounded set of product interaction events with app version, platform, environment, and aggregate action context.

“From” is the profile country you select as your origin. “Now in” is a separate, optional city that you select manually and can change or clear. TRACE does not infer either value from continuous device location and does not track “Now in” in the background. The selected “Now in” city follows the same Everyone, Followers only, or Only me audience as your trips.

We use your data to: • Provide and improve the TRACE service • Show your trips and profile to other users (based on your privacy settings) • Send you notifications you have opted into • Detect and prevent abuse, spam, and policy violations • Diagnose crashes and, only when enabled under reviewed controls, understand aggregate product usage

Core account and trip data is stored on Supabase; processor data may be stored separately by the services listed below. TRACE uses Supabase row-level access controls for user-facing data. Authentication is handled by Supabase, and TRACE does not store plaintext passwords in its application data. We use HTTPS for data in transit.

TRACE uses the following third-party services, which may process data for the stated purpose: • Supabase — database, authentication, Edge Functions, and file storage • GeoNames — canonical city data and search aliases (CC BY 4.0 attribution) • Mapbox — interactive map rendering • Google Places — place discovery and place details • OneSignal — push notifications when permission is granted and authenticated device registration succeeds • Sentry — crash reporting when configured; Dart-origin crash events are filtered as described above, while native iOS and Android crash diagnostics are handled separately by Sentry’s native SDK • PostHog — product interaction analytics code is present but operationally disabled until the native payload boundary and other processing controls are verified Each provider publishes its own privacy information. TRACE reviews the applicable processing terms and controls before enabling optional processing. We do not share personally identifiable information with advertisers or data brokers.

You can set the audience for trips to Everyone, Followers only, or Only me. This same audience controls the selected “Now in” city. Shared trip and profile links do not override audience, blocking, moderation, deactivation, or deletion controls. Your complete saved-places list is visible only to you. People who follow you may see that you saved a specific place when they browse that place; blocked accounts are excluded from that network-saves view.

We will never sell, rent, or trade your personal data to any third party for commercial purposes. Your data is used solely to operate and improve TRACE.

You have the right to: • Access the data we hold about you • Request correction of inaccurate data • Request deletion of your account and applicable processor records • Restrict, object to or opt out of optional product analytics • Export a portable copy of your account data The in-app export is a ZIP of JSON files. Uploaded media files are not bundled, although published media references are included in trip data. To exercise these rights or ask about processor records, contact us at support@shareontrace.com.

For privacy-related questions or requests, including questions about processor records, please reach out at: support@shareontrace.com

We process your personal data based on: • Your consent — for example, when you create an account, share trips, or voluntarily enable your location • Our legitimate interests — such as improving the app, ensuring platform security, and preventing abuse You can withdraw your consent at any time by deleting your account or contacting us.

Account content follows TRACE’s account-deletion process. Crash diagnostics and any enabled product analytics follow their configured processor settings and may have a separate retention period. PostHog product analytics remains disabled until its region, retention, deletion handling, and processing terms are verified. Contact support@shareontrace.com to request the current retention details or deletion of applicable processor records. Legal or regulatory obligations may require limited records to be retained.

TRACE is operated and controlled by: Matteo Fietta support@shareontrace.com This entity is responsible for the processing of your personal data under applicable data protection law.

Under the General Data Protection Regulation (GDPR), you have the right to: • Access the personal data we hold about you • Request correction of inaccurate or incomplete data • Request deletion of your data (“right to be forgotten”) • Restrict or object to certain types of processing • Request a portable copy of your data To exercise any of these rights, contact us at support@shareontrace.com. We will respond within 30 days.