Last updated: 24 October 2026
Privacy Policy
For people who use Gathr.
Who operates Gathr
Gathr is operated by Tamenang Choh. For privacy questions or requests, contact tamenang@thegathrapp.com. Gathr is intended for people age 16 and older.
Account and profile information
We process your phone number for authentication and friend discovery, your account identifier, and the profile details you provide. We process your date of birth to determine age eligibility. Date-of-birth eligibility information is stored privately rather than as a public profile field. Phone numbers used for sign-in are sent to and stored by Google for spam and abuse prevention across Google services, including Firebase.
Events, messages and media
We process events you create or join, including their addresses or coordinates, invitations, attendance, friendships, messages and other information needed for event and social features. We store photos, videos, audio included in videos, captions, profile images and event images that you upload. We also process reports and related information to investigate safety concerns.
Contacts and invitations
If you grant contacts permission and use contact matching, phone numbers are normalized and hashed for matching, and contact hashes are uploaded. These hashes remain identifiers; they are not anonymous information. Matching does not require uploading your contacts’ names. SMS invitations open your device’s composer so you can review, send or cancel the invitation.
Location
With location permission, we use location for nearby events, maps and event features. Posting an event Story requires a location eligibility check and stores precise posting coordinates. You can manage permission in device settings. Features requiring location will have limited functionality without it.
Usage, notifications and diagnostics
We process installation/device identifiers, push tokens and technical information to operate the app and deliver notifications. Product interactions and crash/diagnostic information are processed to understand usage, debug problems and improve reliability. Product telemetry uses predefined events and categorical parameters; it does not intentionally include names, phone numbers, birth dates, message text, media URLs or precise GPS coordinates. Native Analytics also processes app-instance/vendor identifiers, device and app information, session/activity information and approximate location derived from network information, according to the effective collection settings. Crash reporting can include device/OS information, stack traces, application state and Analytics breadcrumbs. These native flows are separate from the limited custom event parameters.
How information is used
Information is used to authenticate accounts, enforce age eligibility, provide profiles and friend/contact matching, discover and manage events, deliver chats and Stories, send enabled notifications, operate safety tools, respond to requests and maintain and improve Gathr.
Visibility to other users
Profiles and public events are visible to other users according to the app’s current access rules. Private-event access depends on invitations, attendance and authorized membership. Messages and group/event chats are available to authorized participants. Story access depends on event and Story permissions and timing. Hiding an older event from a list does not delete its record or necessarily revoke access to its details or chat.
Service providers
We use Google Firebase Authentication, Firestore, Storage, Cloud Functions, Cloud Messaging, Analytics and Crashlytics for authentication, storage, processing, notifications and telemetry. iOS map features use Apple’s map services. The iOS build prepared for public release uses native Apple MapKit for address and venue autocomplete and selected-result resolution. These searches send the query to Apple; selecting a result saves its address and coordinates with the event in Gathr. Earlier beta builds used Google Places for these searches and sent search/place requests and network information such as IP address to Google. Google may retain those earlier requests to provide and improve its services; Gathr does not claim they were immediately discarded. Switching search providers does not delete saved historical event locations. Providers process data needed to deliver these services, subject to their terms and privacy practices. Learn more in Firebase privacy information and the Google Privacy Policy and Apple Privacy Policy.
Analytics sharing and provider retention
Google Analytics is configured with Google products and services sharing off. Aggregated and de-identified measurement contributes to Google’s modeling and business insights; Google technical support may access Analytics data when needed to provide service. Account-level information may also be used for business recommendations. Current Analytics retention settings are two months for event data and 14 months for user data, with the user-data period resetting on new activity. These controls do not cover most standard aggregated reports and are separate from Gathr’s event/chat/media retention. Google states that Crashlytics keeps crash stack traces, extracted minidump data and associated identifiers for 90 days before starting removal from live and backup systems.
Event and chat retention
Event history and shared chats are retained. An event ending does not automatically delete its event, attendance or chat records. Ordinary map/feed visibility ends after the event grace period, and profile history has a six-calendar-month visibility window. These are display windows, not deletion periods. Authorized event chat can remain available after an event ends while membership permits access.
Story and safety-evidence retention
For normal events, Story posting ends one hour after the event ends, and viewing ends 24 hours after the event ends. Viewing expiry or removal of public Story metadata does not automatically delete protected media, upload receipts or related safety evidence. No routine automatic purge of those retained records is currently configured. Fixed automatic deletion periods have not been selected for retained historical records, moderation evidence or incomplete-upload receipts.
Account deletion
You can request account deletion in Settings. Cleanup proceeds asynchronously and includes the account’s profile records, private birthday/eligibility record, uploaded contact hashes and authentication account. This does not erase every piece of shared history or safety evidence. Shared message history, historical events and report/safety evidence may remain under the applicable access restrictions. A reported profile image or event image may be retained privately with limited public identity attribution for safety investigation; the image-evidence copy does not archive the exact birthday or contact data. Host account deletion and event cancellation do not recursively erase every associated history or media record. Storage objects that are actually deleted can remain recoverable for the configured seven-day soft-delete period; this is separate from retention of objects that have not been deleted.
These support pages
When you visit these pages, Cloudflare, our hosting service, processes connection and request information needed to deliver and protect them. The page code does not include analytics scripts, advertising scripts, forms or account sign-in. Email links open your email application; your email service processes messages that you choose to send.
Your choices and requests
You can manage contacts, location and notification permissions, update available profile details, block/report users and request account deletion. For access, correction or deletion questions—including when you cannot sign in—email tamenang@thegathrapp.com. We may need to verify your identity appropriately. Inquiries and reports are monitored daily with a target initial response within 24 hours; resolution may take longer.
Age eligibility
Gathr is for people age 16 and older. The declared-date-of-birth gate determines eligibility; it is not government-ID verification. If you believe an underage person is using Gathr, contact us.
Changes
When this policy changes, its update date will be revised. This policy takes effect when published by the operator.