Privacy

Last updated: 2026-10-29

This page describes the current CheersOida app and this website. CheersOida records venue visits and walking routes, supports check-ins, and lets accepted friends follow shared activity. Questions or data requests: cheers@cheersoida.app.

What we collect and why

Account and profile

Your email and sign-in credentials are used for authentication and password recovery. Your username, optional display name, profile photo, and language preference support your profile and friend connections. Other signed-in users can find basic profile details through username search. Your account email is not displayed to other users.

Routes, venue stops, and live position

When you start a session with location permission, the app records timestamped coordinates and GPS accuracy on your phone. Updates can continue with the screen off while the session is active. Android requests timed updates about every 15 seconds; actual timing depends on the operating system and reception. Tap Stop to end session tracking.

Route points are stored locally and uploaded for session finalisation. A latest point can also be sent during active group features. The app uses known venue data to detect stops and records visits, arrival/departure times, and a simplified route. There is no fixed promise of one point per second or a specific route-point spacing.

New sessions share your latest position with accepted friends by default. A sharing switch in the live screen turns this off for that session; it starts on again for the next new session. The shared record contains one replaceable point, its GPS timestamp, and accuracy—not a playback of the whole live route. It is marked stale after one minute and hidden from friends after five minutes without an update.

Switching sharing off or finishing removes the shared point when the server is reachable. If you stop offline, no new live positions are sent and the last point expires from friend access within five minutes. Expiry is an access limit, not a promise of immediate physical deletion. Active group members can also receive latest positions for group features; the friend-sharing switch controls the separate friend snapshot.

Check-ins and social activity

Check-ins can include drink details, a timestamp, an optional location or venue, a town label, a note, and a photo. The app also stores favorites, custom catalog entries, friend connections and requests, group participation, Cheers, messages, and notifications. These provide the activity feed, personal Atlas, and social features. Check-in location is separate from the live-sharing switch.

Photos and image links

Uploaded check-in photos and profile images currently use public image URLs. Anyone who has an image link can view it, even without an accepted friendship. Friend access checks on activity records do not make the underlying image URL private. Removing a photo through the cleanup flow removes its stored image, but cannot recall copies saved elsewhere.

Notifications and diagnostics

If you allow notifications, an Expo push token is stored to deliver activity, friend-request, Cheers, and reply alerts. Notification content may include part of an activity or message. You can turn alerts off in your device settings; an existing delivery token may remain registered after alerts are disabled.

The app keeps a bounded local diagnostic history for notification, location, sync, and map troubleshooting. It may contain account or activity identifiers, timestamps, errors, and location details. Diagnostic exports you choose to share with support can therefore contain personal information. No advertising or third-party behavioral analytics SDK is added by CheersOida.

Who can see what

  • Full raw track: restricted to its owner through the app's data access rules. Latest points used for group features and friend sharing are separate disclosures described above.
  • Latest shared position: you and accepted friends while the session is active, sharing is enabled, and the point is recent enough. Group features can share latest positions with active group participants.
  • Finished route and activity: accepted friends can access shared finished-session details; active-session and group content follow their session/group permissions.
  • Check-ins, notes, Cheers, and messages: shown to the owner and authorized friends/group participants according to the activity's permissions. An included location can reveal where a visit happened.
  • Basic profile: discoverable by other signed-in users; image URLs are public to anyone with the link.
  • Email and private account settings: not displayed in the social feed or username search.

Storage and service providers

The app uses Supabase for accounts, database records, and uploaded images. The project is hosted in eu-west-2 (London, United Kingdom). Device caches, local route data, queued changes, and diagnostics are stored on your phone. Service logs and backups are managed by the relevant provider; this page does not promise a fixed log-retention period or immediate erasure of backups.

Expo provides push delivery and app-update infrastructure; mobile notification delivery also involves Apple or Google. OpenFreeMap serves map tiles, so tile requests expose the requested map area and network information such as your IP address to that service. Venue lookup uses OpenStreetMap data through a server-side Overpass query. Town labels use your device's location/geocoding service. Opening an external directions link sends you to the mapping service you choose.

Provider information: Supabase privacy, Expo privacy, and OpenFreeMap privacy.

Clearing activity or deleting an account

Profile → Settings → Delete all my data clears sessions, check-ins, route history, check-in photos, and the Cheers/messages attached to your content. Your account, profile and avatar, friends, notifications, saved favorites, and custom catalog entries remain.

Delete account also removes your account, profile, friendships, and owned uploaded images. Both operations need a connection. Cleanup is retryable and can remain pending if a network or storage request fails; it is complete only when the app confirms completion. Shared live-location access is revoked as cleanup begins on the server. Deleted activity is not recreated from an older pending queue.

If you cannot sign in, contact cheers@cheersoida.app from the email used for your account. We may need to verify ownership before acting. You can also use that address for requests about access, correction, or deletion of your personal information.

Age requirement

The current app asks you to confirm during setup that you meet the legal drinking age in your country. It does not ask for a date of birth. The service is not intended for children; contact support if you believe a child has created an account.

This website and support

This static website is hosted on GitHub Pages. It has no account system, advertising pixels, analytics script, tracking cookies, or third-party font requests. GitHub receives technical requests needed to serve the site; see the GitHub privacy statement. External links are handled by their destination services.

Emailing support shares the message and return address with the developer. GitHub issues are public, so use email for account details, location information, or diagnostic logs.

Changes to this page

Updates are published on this page with a new date. Please check this page for the current explanation of how your data is used.

Contact

CheersOida support: cheers@cheersoida.app.