Privacy
Effective November 14, 2026 · Independent event-goers. One-to-one connections.Tually is for adults 18 and older. We collect account email and authentication information through Firebase, the profile details you provide (name, age, optional gender, bio and photo), event participation and visibility choices, connections, one-to-one chat messages, reports and blocks, passport photos/videos, calendar plans and invitations, and redacted supporting documents only when you request approval to offer an extra ticket to a guest. Apple and RevenueCat process subscription and purchase-status information; Tually receives membership status and purchase identifiers, not your full payment-card number. Infrastructure providers may process IP addresses and technical service logs to operate and secure the service.
We use this information to run accounts, find people who opted into the same event and connection mode, apply optional gender and age filters, deliver one-to-one chats, show passport albums and the friends feed according to your sharing choices, operate subscriptions and investigate abuse. Tually does not create group chats or organize mass meetups. A friends feed shows shared updates; it is not a group conversation.
Location access is optional. If you choose Use my location, your phone obtains your position and uses its location service to identify a city. Tually sends the city, rather than your coordinates, to its discovery service. You can enter a city instead. Your location is not displayed as a person-dot on the map. For live music and sports discovery, our server sends your chosen city, event category, and any artist/event keywords or date filters you enter to the Ticketmaster Discovery API. It does not send your precise coordinates, account email, profile, private calendar, conversations or passport media to Ticketmaster. Ticketmaster supplies public event information and may process the server request under its own policies. Opening an official event link takes you to the external website, where its own privacy policy applies. City lights on the home map represent city navigation, not live people.
Searching for events does not publish your attendance. In updated app versions, joining an event’s people pool is visible by default; only Explorer can explicitly choose invisible browsing. Previously saved private plans are not automatically published. When your event profile is visible, your profile, optional gender, connection mode and self-reported event status become visible to eligible people browsing that event. Passport albums stay private until their owner chooses to share. All passport memories and attendance are self-reported; ordinary use does not require ticket uploads or organizer codes. Offering an extra ticket is free after host approval. Looking for a ticket requires Premium; Explorer includes Premium features. Extra-ticket hosts must receive private approval before publishing an extra-ticket offer. Moderators must review admission for the specific event; lounge, parking and upgrade-only passes do not qualify as admission evidence. Approval is not verification of ticket validity, identity, entry or transferability. Ticket proof files are kept separate and never appear in albums. Only accepted friends can appear in the Premium friends feed, and sharing upcoming plans with friends requires a separate choice. Premium members can look for an extra ticket and browse approved extra-ticket hosts without marking themselves attending, but must choose a visible event profile to browse. Free and Premium require a visible event-pool profile to view people; saving a private plan alone does not grant browsing access. Only Explorer permits private browsing. Choosing Browse privately hides any existing profile card for that event and does not create an attendance record. Your personal in-app calendar is private. Premium and Explorer members may invite one accepted friend to one event, sharing the inviter name and event details, not their entire calendar. The recipient must accept before the event is added privately; accepting does not turn on event visibility or buy a ticket. No device-calendar permission is needed. Other people may save information you choose to share, and we cannot retract copies they independently make.
We use Google Firebase for authentication, databases, file storage and server operations; Apple for App Store payments; RevenueCat for subscription validation; and Ticketmaster for public music and sports event listings. We do not sell personal information or use advertising trackers in this app. Data may be processed in the United States and other locations used by these providers.
Account, event, chat and album data are retained while needed to provide the service or until account deletion. Guest-host supporting files are private to their owner and authorized moderators and are scheduled for deletion after 30 days. Host approval expires when the supporting record is removed; a new approval is required to offer an extra ticket again. Legacy ticket-proof files follow the same deletion schedule. Requesting account deletion hides event cards and disables access, then removes the profile, event memberships, passport media, connections, calendar invitations and associated conversations and requests RevenueCat customer deletion. Cleanup retries automatically if a provider is temporarily unavailable. A minimal deletion record remains for seven days to prevent old sessions from accessing data. Safety reports may remain with the deleted account's identifiers removed. Provider logs, backups and transaction records may remain under provider retention policies or legal obligations. Apple subscription cancellation is separate.
You may edit your profile, change visibility and sharing, block/report users, deny location/photo access, and request deletion in the app. For access, correction or other privacy requests, email tuallyfounder@gmail.com. Parents or guardians who believe a child provided information can use the same contact. We will update this page when our practices change; material new uses may require notice or consent.
Explorer friend calendars: both friends must have an active Explorer membership and be accepted friends. A request alone never grants access. The calendar owner must explicitly approve before the requester can view their complete recorded attending-event calendar, including events hidden from public pools. Pending invitations, messages and passport media are excluded. If either membership expires or a friendship is removed or blocked, viewing is denied. Either friend can stop sharing in My calendar. Upgrading does not automatically approve a pending request. Friend codes may be shared voluntarily in matched chats; Friends Feed and Contacts are free on every membership after event-day meetup confirmation.
When an event ends, it leaves upcoming discovery; the underlying event metadata may remain to label calendar history and passport memories. Your saved passport media is not removed merely because an event ended. Public event-provider refreshes do not inspect or publish private calendars, conversations or passport media.
Friend invitations and conversations: you can create a short friend code and share an invitation link voluntarily. Invitation pages show the code, not a public personal profile. A recipient must sign in and send or accept a friend request; a code alone never grants friendship, calendar access or album access. Accepted friends appear as contacts with their profile photo and name. We store per-conversation read times to show unread-message indicators to the account owner. Unmatching closes messaging for both people; it does not delete records needed for safety, retention or legal obligations.\n\nEvent-day meetup confirmation: check-in is optional. When you choose it, precise foreground location and accuracy are sent to Firebase to compare the two matched people. Coordinates are never shown to other users and are scheduled for deletion after 24 hours. There is no background location collection. Both people must check in nearby on the event day and confirm the other person's short-lived code before a new friendship is created. Codes expire after ten minutes, attempts are limited, and a shared link alone cannot create friendship. This records a mutually confirmed meetup, not identity verification. Existing accepted friendships remain available. Friends Feed and Contacts are free; chat extensions require both people to have active Premium or Explorer. Full calendar sharing still requires both to have Explorer and the calendar owner's explicit approval.
Friends dashboard: confirmed friends on every plan can view shared photos, likes and comments. Premium and Explorer members can post photos, like and comment. Sharing is optional and posts are limited to confirmed friends; removed or blocked connections lose access. You can delete your own photo posts, report content, and block users. Camera access is requested for optional photo capture and in-person meetup QR scanning. QR scans do not save camera images. Photos you choose to post are uploaded for your friends to view.