tcktd - PRIVACY POLICY

Last updated: July 22, 2026

Summary
Categories of Information
Information We Collect
How We Use Information
How Information Is Shared
Security
International Data Transfers
Cookies, Local Storage, And Device Storage
Account Visibility And Social Features
Data Retention
Your Rights and Choices
Children
Changes To This Policy
Contact

Summary

This policy explains what personal information tcktd collects, how we use it, and your choices. tcktd is operated by Andrew Raymond Kelly, doing business as tcktd. We process personal information as described here to provide and improve the service. Where applicable law requires consent or another legal basis, we obtain or rely on that basis as required.

Categories of Information

The table below summarizes the main categories of personal information we process, typical sources, and primary purposes. Details appear in the sections that follow.

Identifiers and account data (email, username, profile details) — you provide at signup or in settings; used for account access, support, and security.
User content (event logs, photos, comments, likes, messages) — you provide; used to operate social and logging features.
Social and interaction data (follows, blocks, reports) — generated by your use; used for social features and safety.
Device, network, and diagnostics (app version, crash logs, performance data, IP address and user agent on web) — collected automatically or via configured SDKs; used for reliability, security, and improvement.
Location — device location when you grant permission; used for nearby event features. Rounded coordinates may be sent to SeatGeek for nearby suggestions.
Affiliate and ticket-link activity — generated when you tap ticket links; used to measure referrals and attribute qualifying purchases.
Support communications — you provide when contacting us; used to respond and maintain records.

Information We Collect

Account data (email, username, and profile details you provide).
Content you create or share in the app (event logs, photos, comments, likes, and messages).
Social and interaction data (follows, blocks, reports, and related activity).
Device, network, and diagnostics data needed for security, reliability, and support (for example: device identifiers, app version, crash logs, and performance metrics). Sentry (crash and performance diagnostics) and PostHog (product analytics) are used only when enabled in the build you are using (for example, when the corresponding configuration keys are set in a production release). We do not currently offer an in-app opt-out for PostHog when it is enabled.
Guest and web visitors: If you browse without signing in (for example, as a guest on the feed or search, or when visiting our website), we and our hosting providers may process standard web request data such as IP address, user agent, and pages requested to deliver the service and maintain security.
Location data only when you grant permission and only for in-app location features. On your device we may use precise location (for example, via when-in-use permission) for nearby event detection. When we query SeatGeek for nearby event suggestions, we send rounded coordinates (about 3 decimal places, roughly 100m precision), not your full-precision coordinates.
Ticket link activity: If you tap a SeatGeek ticket link in the app, we record a click identifier, the event you viewed, and related metadata (for example event title, venue, and source screen) so we can measure referrals and, when applicable, attribute ticket purchases through our affiliate partner. This does not include your payment card or SeatGeek account credentials.
Google Sign-In (authentication): If you choose Google to sign in or create an account, Google provides authentication tokens and basic profile information (such as email and name) according to the permissions shown on Google's consent screen. This is separate from optional Gmail import below.
Optional email import (Gmail): If you separately start the optional ticket-email import flow, we request Gmail read-only access and run a narrow app-defined search limited to allowlisted ticket vendors and optional date bounds. Matching messages are parsed on-device to suggest events for your log. You can disconnect or revoke access anytime in your Google account settings.
Optional screenshot import: If you use the screenshot import flow, images you choose are used to detect event text (including on-device processing where supported) so you can add events faster.
Support communications (for example, when you email us).

Gmail import data handling: Raw email bodies used for parsing are processed in memory on your device and are not written to our app database, our servers, analytics, or logs.

No generative AI for Gmail parsing: We do not send your Gmail message content to LLM or generative-AI services for event extraction.

We do not collect biometric templates or biometric identifiers. Device biometrics (Face ID / Touch ID) are handled by your device OS for local unlock checks.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. Affiliate attribution for ticket links (Impact.com) is used to measure qualifying referrals and commissions, not to sell your personal information.

How We Use Information

To provide account access and core app features.
To display and manage your content and social interactions.
To operate, maintain, troubleshoot, and improve the service (including analytics and crash diagnostics when enabled).
To protect accounts, prevent abuse, detect fraud, and maintain service security.
To communicate with you about the service, updates, and support requests.
To comply with legal obligations and enforce our terms and policies.
To measure ticket referral activity when you choose to open SeatGeek links from the app (including affiliate attribution through Impact.com).

We share information as needed to operate the service, at your direction, or when required or permitted by law.

With other users and the public: Depending on your settings and actions, certain profile and content information may be visible to other users (for example, posts, comments, likes, and your profile details). Please consider what you share.

With service providers and subprocessors: We use vendors to host, store, deliver, secure, and measure the service. Providers may include:

Supabase (authentication, database, and file storage)
Vercel (web hosting and related edge services for tcktd.live)
Resend and related email delivery providers (transactional email such as sign-up verification and password reset)
Apple Sign In (authentication, when you choose that sign-in method)
Google (Sign-In for account authentication when you choose that method; and Gmail OAuth only if you separately start the optional ticket-email import — governed by Google's policies and the scopes shown on the consent screen)
SeatGeek (event discovery, nearby event suggestions including approximate location query parameters when you use nearby features, and ticket purchase pages when you tap Buy Tickets links)
Impact.com (affiliate tracking — records referral click identifiers when you tap ticket purchase links so we can measure and attribute qualifying purchases; governed by Impact.com's policies)
Expo Notifications and platform push services (APNs/FCM) for notifications you opt into
Sentry (crash and performance diagnostics, when enabled in your build)
PostHog (product analytics, when enabled in your build)
Google ML Kit (on-device text recognition used for optional screenshot import on supported platforms)
Axiom (server-side operational logs via our backend, when enabled in production)

Event metadata sources: The app may request public event, venue, schedule, or weather information from third-party APIs (for example ESPN, Open-Meteo, or OpenStreetMap-based services). These requests generally do not include your account email or profile; they may include event or location parameters needed to return results.

For legal and safety reasons: We may access, preserve, and disclose information if we believe it is reasonably necessary to comply with law, enforce our terms, protect the rights, property, and safety of users or the public, or prevent fraud or abuse.

Affiliate referrals: tcktd may earn a referral fee when you purchase tickets through SeatGeek links opened from the app. When you tap such a link, we and our affiliate partner (Impact.com) may receive a click identifier and related event metadata as described above.

Business transfers: If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction.

Security

We use safeguards intended to protect information, including encryption in transit (such as HTTPS/TLS) between the app and our servers where applicable. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

Where the app offers encryption for direct message text, content is encrypted when both conversation participants have compatible keys available. To help you read messages on multiple devices, your private messaging key may be stored on our servers in encrypted form and recovered when you sign in on a new device — this is not zero-knowledge end-to-end encryption against the service operator. If compatible keys are unavailable or encryption fails, a message may be sent without message-level encryption while still using transport encryption (HTTPS/TLS). If you lose access to your device or keys before recovery completes, some previously encrypted message content may not be recoverable.

International Data Transfers

The service is operated from the United States. Personal information may be processed and stored in the U.S. or in other regions where our subprocessors operate. If you access the app from outside the U.S., you understand your information may be transferred to and processed in the U.S.

Cookies, Local Storage, And Device Storage

On mobile platforms we rely on the operating system and secure storage mechanisms for session data and preferences where appropriate. On the web, we may use browser technologies such as local or session storage for sign-in state, preferences, and core functionality. For optional encrypted direct messages on the web, related cryptographic material may be stored in the browser using additional protection as described in the app.

You may use privacy settings (for example, a private account) that limit how your profile and certain content appear to other users in feeds, search, and related in-app surfaces. Blocking, follows, and related social controls are designed to limit visibility and interactions, but effects may not be immediate in every surface (for example, cached content or existing conversation state).

Uploaded images and public URLs: Profile pictures, banner images, and event photos you upload are stored in file storage that is publicly readable if someone has the direct URL, even if your account is private or an event is limited to friends. In-app visibility settings control how content appears in feeds and profiles; they do not make the underlying image URL secret. URLs are not meant to be easily guessable, but they may be shared, cached, embedded, or accessed by anyone who obtains the link. Do not upload images you consider confidential.

Data Retention

We keep personal information only as long as necessary for the purposes in this policy, to provide the service, for legal compliance, dispute resolution, and enforcement.

Account deletion: You may delete your account from Settings. When you confirm deletion, we begin removing your account and associated personal information from active systems. Primary deletion is typically completed within 30 days, though some data may take longer to purge from backups, logs, or systems used for security, abuse prevention, or legal compliance. Even after deletion, copies may persist for a limited period in backups or where we have a legitimate need to retain them.

Your Rights and Choices

You can request access, correction, or deletion of your personal information by contacting us at support@tcktd.live. You can also manage certain information in-app (for example, profile details, content you post, and account deletion).

California and U.S. state privacy rights: If you are a resident of California or another U.S. state with a comprehensive privacy law, you may have additional rights, which may include the right to know what personal information we collect, the right to delete, the right to correct inaccurate information, and the right to appeal certain decisions. We do not sell personal information and do not share it for cross-context behavioral advertising as defined under applicable state laws. To exercise rights, email support@tcktd.live with enough information for us to verify your request. We will respond within the time required by applicable law. If we deny a request, you may have the right to appeal by replying to our response.

Push notifications: You can disable push notifications in your device or in-app settings.

Location: You can revoke location permission in your device settings; nearby features will stop using device location.

Google connections: You can revoke Google Sign-In or Gmail access in your Google account settings at any time.

Children

The service is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13 without verifiable parental consent, we will take steps to delete that information promptly. If you believe a child under 13 has provided us personal information, contact us at support@tcktd.live.

Changes To This Policy

We may update this policy from time to time. Material changes will be reflected by updating the date above. If required by applicable law or platform policy, we may provide additional notice or request renewed acceptance for material updates (for example, at sign-in or in the app).

Contact

Questions about this policy: support@tcktd.live.

Operator: Andrew Raymond Kelly, doing business as tcktd (United States).