Legal

Privacy Policy

Last updated: October 11, 2026

Operator: TCG CALENDAR Marketing Management

Trade Licence No.: 1624328

Licensing Jurisdiction: DET

Registered Address: Belgravia 3 Ellington, JVC, Dubai, UAE

This Privacy Policy explains how TCG Calendar UAE handles information across the TCG Calendar website and the TCG Calendar mobile app for iOS and Android. We operate with UAE privacy requirements as the primary compliance baseline and also describe rights and disclosures commonly required by app stores and international privacy laws.

Who We Are

TCG Calendar UAE provides a public calendar for trading card game events in the United Arab Emirates, plus public organizer, vendor, and venue pages. For privacy questions, contact TCG Calendar UAE through the public support or partner channels available on the site.

UAE Privacy Baseline

We treat UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data as the primary privacy baseline for our service. We aim to process personal data fairly, transparently, for clear purposes, and with appropriate security controls. Where consent is required, we ask for it or provide a clear choice. Where processing is necessary to operate the service, respond to a request, maintain security, comply with law, or protect legitimate interests, we limit the data used to what is reasonably needed for that purpose.

Website Information

The website may collect information submitted through public forms, advertising or sponsor inquiries, partner login flows, newsletter signups, invite flows, organizer or vendor profile workflows, event submission or management workflows, and related support messages. This may include names, business contact details, public profile information, event details, venue details, uploaded content, account login information for website-only partner/admin workflows, and technical logs needed to operate and secure the website.

The website also uses necessary cookies or browser storage for login sessions, security, form behavior, and remembering privacy choices. Optional website analytics are not enabled unless the visitor accepts analytics cookies.

Business Terms Acceptance Records

When a member of a business's team accepts the TCG Calendar Business Terms, whether on an invite, when claiming a profile, or when opening the business dashboard, we store a server-side acceptance record in Supabase. This record may include the business ID, the business name and its tags (such as Store, Vendor, Organizer or Service) at acceptance time, user or account ID, user email where available, accepted terms type and version, last-updated date, exact terms URL or document slug shown to the user, exact checkbox text shown to the user, acceptance timestamp in UTC, IP address, user agent, browser/device/app version metadata where available, and the source flow such as invite, profile claim, business dashboard, profile edit, event application, event creation, or event edit.

We use these records to prove legal acceptance, manage business access, enforce the current Business Terms, protect platform integrity, resolve disputes, and comply with legal, audit, and security obligations. Records cannot be edited or deleted once stored. Records of earlier acceptances of the Vendor Account Terms and Organizer Account Terms, which the Business Terms replace, are kept on the same basis.

Business Memberships

When a business buys a membership, payment goes through Stripe, our payment provider. The card details go to Stripe and never reach our servers. We keep the business's Stripe customer and subscription IDs, the order (branches, TCGs, prices, dates), the payment status, and a record of who accepted the membership terms, when, from which IP address and browser. Stripe processes the payment under its own privacy policy.

Mobile App Information

The mobile app is an end-user app for public event discovery. It does not provide admin dashboards, organizer dashboards, vendor dashboards, profile claiming, event editing, moderation, imports, or partner management workflows. The app may load public event, organizer, vendor, sponsor, and venue information from our public data sources.

When a user chooses app features, the app may interact with device capabilities such as sharing, opening external links, requesting notification permission, or adding a public event to the device calendar. Where the user chooses the related feature and grants the device permission, the app may also use the camera to scan event check-in QR codes, add images the user saves (such as their Collector Card) to the device photo library, and, where location-verified check-in is available, read the device's current location once during a check-in attempt. Camera frames are processed on the device to read the QR code and are not stored or uploaded; the photo library permission is add-only and the app does not read, browse, or upload the user's existing photos; location is requested in the foreground only at the moment of check-in, is used to confirm presence at the event venue, and is not collected in the background or used to build a movement history.

We do not use these features to collect contacts or payment data. Device advertising identifiers are used only for consent-based app-install ads measurement, as described in the Mobile App Install Ads Measurement section below. The end-user profile feature currently uses generated avatars and does not collect uploaded profile photos or videos.

Mobile End-User Accounts

If the mobile app offers end-user accounts, account features are separate from website-only admin, vendor, and organizer workflows. End users may create or access an account using Supabase Auth with an email verification code, password setup, Sign in with Apple, or Google Sign-In. SMS or WhatsApp-based login may be added later only if the app clearly presents that option.

Account data may include email address, authentication identifiers, provider identifiers from Apple or Google, account creation and login timestamps, session tokens, display name, handle, generated avatar seed, friend code, profile visibility and discoverability settings, notification preferences, newsletter preferences, followed events, followed vendors, followed organizers, followed releases and release sets, friend requests, friendship records, blocked-player records, in-app notification records, RSVP records, selected event days, optional arrival times, event check-in records, badge and quest progress records, badge collection and showcase arrangement, share page activation state, account deletion requests, and similar account-linked product actions. Passwords are handled by Supabase Auth and are not visible to TCG Calendar in plain text.

The app does not import a user's device contacts to find friends. Friend search uses display names and handles stored inside TCG Calendar. Handles may change over time, but account identifiers are used internally so existing friendships are not based only on the current handle text.

Before creating an end-user account or continuing with Apple or Google, the app may require the user to accept the current Terms of Use and Privacy Policy. We may store an account acceptance record including acceptance timestamp, accepted document version, accepted document URLs, signup or sign-in provider, account ID, app version, and related technical metadata needed to prove consent and operate the account.

The app stores authentication sessions on the device using secure native storage where available, so users can stay signed in. Users can sign out from the app. The mobile app provides an in-app account deletion flow from Profile, and users who cannot access the app may use the public Account Deletion page. Deletion requests may remove or anonymize the end-user account and account-linked personal data, subject to records we must keep for security, fraud prevention, legal compliance, dispute resolution, or platform integrity.

Mobile Social Features, RSVPs, and Blocking

Signed-in mobile users may create a display name and handle, receive a generated avatar, search for other players by name or handle, send and respond to friend requests, maintain a friends list, block players, follow events, vendors, and organizers, and set RSVP choices for events.

Depending on the feature and user settings, a user's display name, handle, generated avatar, friendship state, and relevant RSVP summary may be visible to other signed-in users, such as friends reviewing plans for an upcoming event or a user receiving a friend request. Blocked players should not be able to find the blocking user through friend search or send new friend requests while the block is active.

The app may create in-app notifications and, where the user grants device permission and keeps the relevant setting enabled, push notifications for friend requests, accepted friend requests, followed-event reminders, followed-event updates, vendor updates, organizer updates, and TCG Calendar product updates. Notification settings can be changed in the app, and device-level notification permissions can be changed in iOS or Android settings.

Event Check-Ins, Badges, and Collections

Where event check-in is available, a signed-in user may check in at a participating event, for example by scanning a check-in QR code shown at the venue. A check-in creates a record that includes the account identifier, the event, and the check-in time. Camera access is used only to read the QR code on the device; camera frames are not stored or uploaded, and only the scanned check-in code is sent to our servers to validate the check-in.

Where location-verified check-in is available and the user grants the device location permission, the app reads the device's current location once, in the foreground, at the moment of the check-in attempt, and uses it to confirm the user is at or near the event venue. We store the check-in result linked to the event. We do not collect background location, and we do not use check-in locations to build a movement profile or for advertising. Location permission can be declined or revoked at any time in iOS or Android settings; without it, location-verified check-ins are unavailable but the rest of the app continues to work.

The app may award badges, trophies, and quest progress derived from account-linked activity such as check-ins, follows, friendships, and collection milestones. Badge and quest records are stored with the account. A user's badge collection and chosen showcase may be visible to other users where the user uses social features, such as the public share page described below. Badges and trophies are product features with no monetary value.

Public Collector Card and Share Page

A signed-in user can generate a Collector Card image and share it. The first time a user chooses Share or Save for their card, we activate a public profile page for that user at a tcgcalendar.ae/p/ web address based on their handle. The public page and the card image may show the user's display name, handle, generated avatar, badge, event, and friend counts, showcased badges, friend code, and a link or QR code pointing to the public page. Anyone with the link can view the public page without signing in, and, like any public web page, it may be indexed by search engines or shared onward by people the user shares it with.

Sharing is off until the user's first explicit share, and merely previewing the card does not publish anything. After the first share, the user can turn the public page off and back on at any time from the Share profile card switch in the app settings; turning it off takes the public page offline. Card images the user saves or shares are copies under the user's control, and taking the page offline does not retract images the user already sent to other people or apps.

Ask Holo (AI Assistant)

Where the mobile app offers it, Ask Holo is an optional AI assistant that answers questions about trading card game events, tournaments, product releases, and businesses in the UAE. Holo is available only to signed-in users aged 13 or older, and only after the user reads Holo's notice and taps Agree before their first question. The notice explains that Holo uses AI from Anthropic and OpenAI, what is sent to them, that its answers can be wrong, and how to withdraw; this section describes the rest. Nothing is sent to Anthropic or OpenAI before the user agrees, and our servers check the user's agreement before every question.

What Holo processes.When a user asks Holo a question, we process the question the user types or says, the page of the app they are on, and the earlier questions and answers in the same chat. Holo keeps on the account the trading card games the user tells it they like and, while personal answers are on, the games, topics, and emirates their questions are about, stored as short labels and never as the user's words. With personal answers on, Holo can also read what the user follows and the tournaments they marked as going, the same way the app shows them to the user; friends going reach Holo as a number, never as names. We also measure how Holo is used, without the words of questions or answers, as described in the Analytics section.

Voice questions. When a user asks by voice, the app records only after the user taps the microphone and grants microphone permission, until the user taps Stop or Send. The recording is sent to our servers and to OpenAI to be turned into text. We do not store voice recordings, and the app deletes the recording from the phone once it has been sent.

How answers are written.Holo writes its answers with Claude, an AI model from Anthropic. The question and the information described above are sent to Anthropic to write the answer, and the model runs in the United States. Under Anthropic's commercial terms, Anthropic does not use this data to train its models; it may keep it for up to 30 days, or for up to 2 years if its automated safety systems flag the conversation. When Anthropic can't answer, and for users who agreed to Holo's earlier notice, which named only OpenAI, OpenAI's models write the answer instead, under OpenAI's API terms: OpenAI does not use this data to train its models and may keep it for up to 30 days to detect abuse. With each question we also send the AI provider a code made from the user's account ID by a one-way hash, never the ID itself, a name or contact details, so its abuse checks can tell one account's questions apart from another's. To keep Holo safe for everyone, including younger players, each question and each answer is also checked by OpenAI's moderation service under the same terms, and our servers check every answer before it is shown, for example to take out contact details that did not come from a business's own listing. Holo answers from TCG Calendar's own published listings and does not browse the web. AI answers can be wrong or out of date, so users should check important details, such as dates, prices, and entry fees, on the listing or with the organizer. Holo does not make decisions about users that have legal or similarly significant effects.

Directions.When a user asks Holo how to get to an event, tournament, or store, Holo shows the venue's address with a Directions button that opens a maps app chosen by the user (on iPhone, Apple Maps, Google Maps, or Waze; on Android, the system's choice). Holo does not read the device's location. The venue is passed to the maps app, whose own privacy policy then applies. A default maps app, if the user picks one, is kept on the phone only.

Why we use this information.To answer the user's questions; to keep the chat and Holo's memory on the account across devices; to keep Holo safe and prevent abuse; and to improve Holo, including by our team reading chats, reported answers and questions Holo could not answer to find and fix wrong or poor answers. If an account is used to misuse Holo, our team can stop that account from using Holo; the user can contact us to ask for a review. We do not use Holo chats for advertising or tracking, and we do not sell them.

The agreement record.When a user agrees to Holo's notice or withdraws their agreement, we keep a record of it: the account, the notice version and its exact words, the time, the links to the Terms of Use and this Privacy Policy, the sign-in session's IP address and user agent, and the app's device details (platform, app version, device model, locale, and time zone). We keep this record to prove the user's choice, for as long as the account exists.

How long we keep it.Holo chats are kept for 30 days after each question, then deleted automatically. To prevent abuse and to find and fix wrong answers, our team keeps every chat for those 30 days even when the user deletes it in the app: deleting removes it from the user's phone and account straight away, and our copy goes when the 30 days are up. What Holo noticed from questions is kept for up to 120 days, and is deleted straight away when the user turns personal answers off. The games a user chose are kept until they delete them or their account; with personal answers off, they are kept only on the phone. When a user reports an answer or rates it with a thumbs up or down, the answer, the question before it, the reason chosen, and anything the user wrote are kept for 180 days for our team; what a user writes in a report goes to our team only, never to Holo. To keep Holo's daily question limit and spot misuse, we record when each account asks a question or a voice question, never what it asks, with short labels for any safety check that stepped in on the answer (never the words), and keep that record for 90 days. If our team stops an account from using Holo, we keep that decision and its reason until it is lifted or the account is deleted; our staff activity log also keeps when an account was blocked or unblocked, and by which staff member. When Holo turns a question away or cannot answer it (for example, a question that is too long or can't be read, a question over a limit or while Holo is under maintenance, or an answer that fails), we keep the question as sent, the reason, the time, and the account for 30 days, so our team can find and fix the problem and spot misuse. Like the chat, this record stays for its 30 days when a user deletes their chat or their Holo data. Before a user agrees to Holo's notice, we keep only the length of such a question, never its words. Deleting the account deletes all of it at once.

Your controls.In the app, under Settings, What Holo knows, a user can see and remove what Holo noticed and the games they chose, turn personal answers off, delete their chat, delete all Holo data, and withdraw their agreement. Withdrawing stops Holo and deletes the chat, the games, and what Holo noticed from the phone and the account; Holo asks for agreement again before the next question. Our team's 30-day copy of the chat, and of questions Holo turned away or could not answer, stays until its 30 days are up, as described above. Any answer can be reported from under the answer. Deleting the account deletes all Holo data, including our team's copy, and the agreement record.

Newsletter Signups

Newsletter signup is optional on both the website and mobile app. If you enter your email address and tick the newsletter consent checkbox, we send your email address, signup source, referrer where available, and the time of the request to beehiiv so it can add you to the TCG Calendar UAE mailing list, send event updates, manage delivery, prevent duplicate subscriptions, and provide unsubscribe tools.

Newsletter subscriptions are managed by beehiiv and are subject to beehiiv's Terms of Use and Privacy Policy. We reference those beehiiv policy URLs when recording newsletter consent proof.

To prove consent for API-created newsletter subscriptions, we store a server-side consent record in Supabase. This record may include your email address, normalized email address, signup source, consent accepted flag, consent text version (newsletter-consent-2026-05-13), consent text, privacy policy version (2026-10-11), privacy policy URL, beehiiv Terms of Use URL, beehiiv Privacy Policy URL, timestamp, request IP address, user agent, and beehiiv subscription status or response metadata.

Newsletter emails are marketing or community update communications. You can unsubscribe from newsletter emails using the unsubscribe link in any newsletter message. Unsubscribing from the newsletter does not remove public event, organizer, vendor, venue, or website account records that are processed for other purposes.

Website Analytics, Mobile Analytics, and Sponsor Reporting

With consent, the website may use PostHog Cloud EU, Vercel Analytics, Vercel Speed Insights, Google Analytics, Google Tag Manager, or similar analytics providers to understand how the site is used, measure page performance, improve public event discovery, and measure sponsored placement performance. Website analytics may include page views, paths visited, referrer or campaign source, browser and device information, approximate region derived from network data, timestamps, performance metrics, and safe interaction events for non-sensitive buttons or controls. When you are signed in, these analytics events are linked to your account identifier so we can understand product usage across your sessions, improve features, and measure sponsored placement performance. Anonymous browsing stays anonymous until you sign in, at which point PostHog merges the earlier anonymous activity into the identified account profile. We configure website PostHog without session replay and without automatic click or form autocapture.

We may also use Google Search Console to understand how Google Search discovers and indexes TCG Calendar. Search Console provides aggregate search performance, crawl, indexing, and technical SEO reports. It does not give us direct access to individual users' Google Search accounts, private search history, or personal Google profile data.

The mobile app may use PostHog Cloud EU or a similar analytics provider to understand how the app is used and improve the product. Mobile analytics may include screen views, app lifecycle events, public event list views, public event detail views, save and unsave actions, share actions, add-to-calendar actions, RSVP status updates, source-link clicks, public organizer/vendor/venue profile views, notification permission request results, and safe interaction events for non-sensitive buttons or controls. When a user is signed in, these events are linked to the account identifier to understand product usage, improve features, and measure sponsored placement performance. Browsing before sign-in stays anonymous until the user signs in, at which point PostHog merges the earlier anonymous activity into the identified account profile.

For Ask Holo, the same analytics record how Holo is used, linked to the account identifier: opening and closing Holo and the time spent, the page a question was asked from and how it was asked (typed, by voice, or by tapping a suggested question), the games, topics, and places a question is about as short labels, the filters and short search words Holo used to look up listings (such as a set, store, or event name), the events, tournaments, sets, products, and businesses Holo recommended or named, the cards opened, the outcome, how long the answer took and what it cost, ratings and reports, and the steps of a voice question. Our servers send the part they see to PostHog after each answer. Holo's analytics never include the words of a question or an answer, or voice recordings. We use them to understand and improve Holo and to report to businesses, in aggregate, how often Holo recommends them.

The mobile app also collects anonymous performance and reliability metrics through Expo's EAS Observe service, such as app startup and screen loading times, time-to-interactive measurements, screen route names, app version, device model, and operating system version. These metrics are aggregate, are not linked to a user's identity, are not used for advertising or cross-company tracking, and are processed by Expo on our behalf solely to monitor and improve app performance and reliability.

The website and mobile app may also track sponsored placement performance, including sponsored placement renders, viewable impressions, promotion clicks, CTA clicks, sponsored public event views, sponsored public vendor views, campaign identifiers, sponsor slugs, placement names, creative identifiers, public entity slugs, placement position, city, game/category, entry type, and source screen. In addition, we keep server-side sponsored-placement measurement records that capture these placement impressions, clicks, and conversions for billing integrity and to verify that sponsored placements were delivered as agreed. These records are retained as described in the Retention section. Sponsor reporting shared with sponsors, vendors, organizers, or partners is aggregate and non-identifying.

Website and mobile analytics do not include raw search query text or the words of Holo questions and answers, names, email addresses, phone numbers, passwords, payment data, precise GPS coordinates, contacts, push notification tokens, or session replay. Product analytics and performance monitoring do not use IDFA, the Android Advertising ID, GAID, or AdMob identifiers. Analytics events linked to a signed-in account are used to understand and improve the product and to measure sponsored placement performance, not for cross-company advertising tracking. Device advertising identifiers are used only for app-install ads measurement as described in the next section, and on iOS only after the user allows tracking through the AppTrackingTransparency prompt.

Mobile App Install Ads Measurement (Meta)

We may run advertising campaigns on Meta platforms such as Facebook and Instagram to promote the TCG Calendar mobile app. To measure whether those campaigns lead to app installs, the mobile app includes the Meta (Facebook) SDK. The SDK may send Meta app-install and app-launch events together with technical metadata such as app version, device model, operating system version, and network information, and, where permitted, the device advertising identifier (IDFA on iOS, Google Advertising ID on Android). We do not share in-app activity such as searches, viewed events, RSVPs, follows, friends, or account details with Meta.

On iOS, the app shows the AppTrackingTransparency prompt before any Meta event is sent. If the user does not allow tracking, the advertising identifier is not used and Meta measurement falls back to Apple's SKAdNetwork framework, which reports installs to Meta in an aggregate, privacy-preserving way that does not identify the user or device. On iOS this choice can be changed at any time in iOS Settings under Privacy & Security, Tracking. On Android, the advertising identifier can be reset or deleted in device settings under Privacy, Ads.

Meta processes this measurement data under its own Privacy Policy. We receive campaign performance reports from Meta in aggregate form.

How We Use Information

We use information to operate the public calendar, publish and maintain event listings, manage website-only partner/admin workflows, respond to inquiries, send requested updates, prevent abuse, maintain reliability and security, measure aggregate product usage, understand sponsor placement performance, and comply with legal obligations.

Service Providers and Sharing

We may use service providers for hosting, databases, authentication, storage, transactional email, newsletter delivery, analytics, crash or reliability diagnostics, app distribution, and other operational services. These providers process information only as needed to provide their services to us. beehiiv is used for newsletter subscription management and email delivery. Expo (Expo Application Services) is used for mobile app build distribution, app updates, and anonymous app performance monitoring. Supabase is used for database, storage, authentication, and account sessions. Apple and Google may process login-related information when a user chooses Sign in with Apple or Google Sign-In. Expo may process device push tokens and delivery metadata when push notifications are enabled. PostHog may process mobile analytics events where configured. Google may also provide Search Console, Google Analytics, Google Tag Manager, Firebase, or Google Cloud services where configured. Meta Platforms processes app-install and app-launch events for advertising measurement as described in the Mobile App Install Ads Measurement section, subject to the user's tracking choices. Anthropic processes Ask Holo questions and the information described in the Ask Holo section to write answers, and OpenAI processes them to check them for safety, to turn voice questions into text and, when Anthropic can't answer, to write answers, as our service providers, and Vercel hosts the servers that run Ask Holo. We may share aggregate, non-identifying usage statistics with sponsors, vendors, organizers, or partners. We do not sell personal data. Stripe processes business membership payments as described in the Business Memberships section.

App Store and Google Play Disclosures

For Apple App Store privacy labels, optional newsletter signup means the app may collect Contact Info, specifically Email Address, when the user chooses to provide it. The email address is linked to the user and used for Developer's Advertising or Marketing through direct newsletter communications. We do not use the newsletter email address for cross-company tracking.

For Google Play Data Safety, optional newsletter signup should be disclosed as Personal info, specifically Email address, collected for app communications, marketing communications, and account/subscription management for the newsletter. The email address is shared with beehiiv as a service provider for newsletter processing and delivery.

For Apple App Store privacy labels, anonymous app performance monitoring means the app may collect Diagnostics, specifically Performance Data. This data is not linked to the user's identity and is not used for tracking. For Google Play Data Safety, the same monitoring should be disclosed as App info and performance, specifically Diagnostics, collected for analytics and app functionality and processed by Expo as a service provider on our behalf.

For Apple App Store privacy labels, app-install ads measurement means the app may collect Identifiers, specifically Device ID (the advertising identifier), and this data may be used to track the user when the user grants AppTrackingTransparency permission. This is disclosed under Data Used to Track You as Device ID. For Google Play Data Safety, the same measurement should be disclosed as Device or other IDs (the advertising ID), collected and shared with Meta for advertising or marketing purposes.

If mobile accounts are enabled, App Store and Google Play disclosures should also cover account creation and account management data, including email address, name or display name, user identifiers such as handles and account IDs, device or push identifiers, profile information, authentication provider data, friend requests, friendship and blocked-player records, in-app notification records, and account-linked app activity such as follows, saved events, RSVP records, newsletter preferences, notification preferences, and account deletion requests, as applicable to the shipped feature set. Account-linked app activity also includes event check-in records and badge or quest progress where those features are shipped. The current end-user profile feature does not collect device contacts or uploaded profile photos.

Camera access for QR check-in scanning and add-only photo library access for saving the Collector Card do not add collected data types by themselves: camera frames are processed on the device and not stored, and the app writes images the user saves without reading the photo library. Where location-verified check-in is shipped and the user grants permission, App Store privacy labels should disclose Location, specifically Precise Location, linked to the user and used for App Functionality, not for tracking. For Google Play Data Safety, the same feature should be disclosed as Location collected for app functionality, not shared with third parties for advertising.

Where Ask Holo is shipped, App Store privacy labels should disclose User Content, specifically Other User Content (questions, reports, and ratings) and Audio Data (voice questions), linked to the user and used for App Functionality and Product Personalization, not for tracking. Google Play Data Safety should disclose Messages, specifically Other in-app messages (questions, reports, and ratings), and Audio, specifically Voice or sound recordings, collected for app functionality and personalization and shared with Anthropic and OpenAI as service providers. Holo's answers can be reported from inside the app.

International Transfers

We are focused on the UAE market, but our service providers may process information in the UAE, the European Union, the United States, or other locations where they operate. When information is transferred internationally, we use appropriate contractual, technical, and organizational safeguards for the service involved.

Ask Holo questions are processed by Anthropic and OpenAI, and voice recordings by OpenAI, in the United States. Holo's notice names both and links to this policy, and we ask for the user's explicit agreement before their first question. The user can withdraw it at any time in Settings, What Holo knows.

Retention

We keep information only for as long as reasonably needed for the purposes described in this policy, including operating the service, maintaining records, resolving disputes, enforcing terms, security, and legal compliance. Public event, organizer, vendor, venue, and sponsor records may remain visible while they are relevant to the public calendar or archived for operational history.

Ask Holo chats are kept for 30 days, what Holo noticed for up to 120 days, reported and rated answers for 180 days, and Holo usage records for 90 days, as described in the Ask Holo section. Holo agreement records are kept for as long as the account exists.

Your Choices and Rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about how your personal data is processed. UAE users may also raise privacy concerns through the applicable UAE data protection channels. To make a request to us, use the public support or partner contact channels available on the site.

Website visitors can accept or reject optional analytics cookies in the cookie banner and can change that choice later through . Device-level permissions, such as calendar, notification, camera, photo library, or location permissions, can be managed through iOS or Android system settings. On iOS, users decide at the AppTrackingTransparency prompt whether the app may use the advertising identifier for ads measurement and can change that choice in iOS Settings under Privacy & Security, Tracking. On Android, users can reset or delete the advertising identifier in device settings under Privacy, Ads.

Mobile users can edit their display name and handle in the app, manage notification settings, unfollow events, vendors, or organizers, remove friends, manage blocked players, arrange or clear their badge showcase, turn their public share page off or on from the Share profile card switch after their first share, sign out, or request account deletion from Profile and App settings. Account deletion removes or anonymizes account-linked records, including check-in, badge, and share page records, subject to the retention limits described in this policy.

Mobile users can see, change, and delete what Holo knows about them, turn personal answers off, delete their Holo chat or all Holo data, and withdraw their agreement to Holo's notice from Settings, What Holo knows.

Children

TCG Calendar is intended for general public event discovery and business/public community listings. It is not directed to children, and we do not knowingly collect personal data from children through the mobile app. Ask Holo is for users aged 13 or older, who confirm their age when they agree to Holo's notice; users under 18 should use Holo with the involvement of a parent or guardian, as the Terms of Use describe. If we learn that a user under 13 has used Holo, we delete their Holo data.

Changes

We may update this Privacy Policy as the website, mobile app, analytics configuration, sponsor reporting, app store requirements, or legal requirements change. The latest version will be posted on this page with the updated date above.