This Privacy Policy explains how Togapa ("Togapa", "we", "us", "our") — a service owned and operated by DJ Graffiti LLC, 2232 S Main St #216, Ann Arbor, MI 48103, USA — collects, uses, shares, and protects information when you use the Togapa service at togapa.com and app.togapa.com (together, the "Service").
The Service is a real-time song-request and voting platform for event hosts. Guests scan a QR code or open a link to request and vote on songs; the event host manages a live queue from a dashboard, with an optional big-screen venue display.
By using the Service you agree to this Policy. If you do not agree, please do not use the Service.
Two kinds of people use Togapa, and our responsibility differs for each:
| Role | Who they are | Our role |
|---|---|---|
| Event Host / Account Holder | An event host, venue or organisation that creates a Togapa account and runs events. | We are the data controller for your account, billing, and login information. |
| Guest | A member of the public who joins an event host's event to request or vote on songs. No account or password is required. | For guest information collected inside an event, the event host who runs that event is the controller, and Togapa acts as a data processor on the event host's behalf. We also act as a controller for the limited technical data needed to run the Service securely. |
What this means in practice: An event host decides what guest information to collect (for example, whether to ask for a name, email, job title, company, or phone number), sets the wording of any consent or terms shown to guests, and controls how that information is used after the event. If you are a guest and want your information corrected or removed, you can contact us, but the event host who ran your event is primarily responsible for it — see Section 9.
When you create and use a Togapa account, we collect:
When you join an event as a guest, the following may be collected — but only the fields the event host has chosen to ask for:
Guest email protection. By design, guest email addresses are never stored on the public song-request record. A database trigger strips them out and stores any email separately in a protected contacts table that only the event's own host can read.
We use third-party analytics and advertising cookies — from Google (Analytics and Ads), Meta (Facebook/Instagram), and LinkedIn — to understand how our sites are used and to measure and target our marketing. Where the law requires it (for example in the EU/UK), these are set only with your consent. See Section 7 for the full list and how to opt out.
We use the information above to:
Togapa does not sell personally identifiable user data, and we will not do so without your express permission. We do not share personally identifiable information with third parties for their own marketing or for monetary or other valuable consideration, except:
We do not exchange your personal information for money. However, our use of advertising cookies (Section 7) shares online identifiers — such as cookie IDs and device/usage data — with Google, Meta, and LinkedIn to measure and target advertising. Under some laws (for example California's CPRA), this may be considered "sharing" or a "sale" of personal information for cross-context behavioural advertising. You can opt out at any time through our cookie settings or the controls in Section 7, and we honour Global Privacy Control (GPC) browser signals where required.
Anonymised or aggregated data that cannot reasonably identify you is not subject to this restriction.
We rely on a small number of trusted providers to run the Service. Each processes only the data needed for its function:
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication, real-time updates, storage | All account, event, request, vote, message, guest-contact, and billing-state data; login credentials (hashed). |
| Netlify | Hosting and content delivery | All application traffic and server logs (incl. IP addresses). |
| Stripe | Payment processing and subscription management | Event host email, payment card/bank details (handled entirely by Stripe — never stored by Togapa), subscription and purchase data. |
| Resend | Transactional & service email delivery | Recipient email address and message content (e.g. one-time login codes, billing and recap emails). |
| Apple — iTunes Search API | Song catalogue search | Search terms and the searching device's IP address. No account data is sent. |
| Apple Music (optional) | Catalogue/preview features, where enabled | Configured via a developer token; no guest identity is sent. |
| Spotify (optional) | Export an event's requests to a Spotify playlist, when an event host connects their account | The event host's Spotify authorisation and the song selection to be added to the playlist. |
| Google — Fonts | Web fonts (Hanken Grotesk, Permanent Marker) | The loading device's IP address and user-agent (standard for any font CDN). |
| Google — Sign-In (optional) | "Continue with Google" login for event hosts | Your Google email and basic profile, only if you choose this login method. |
| Google — Analytics & Ads | Website analytics, advertising, and conversion measurement | Cookie/advertising IDs, device and browser information, IP address, and on-site activity (pages viewed, actions taken). Set only with consent where required. |
| Meta (Facebook/Instagram) | Advertising, retargeting, and conversion measurement | Cookie/advertising IDs (e.g. the Meta Pixel _fbp), device and browser information, IP address, and on-site activity. Set only with consent where required. |
| Advertising, retargeting, and conversion measurement | Cookie/advertising IDs (LinkedIn Insight Tag), device and browser information, IP address, and on-site activity. Set only with consent where required. |
These providers may process data outside your country, including in the United States. Where required, such transfers are covered by appropriate safeguards (for example, the providers' Standard Contractual Clauses and Data Processing Addenda).
We will keep this list current. Material changes to our subprocessors will be reflected in an updated version of this Policy.
You can get your data out of Togapa and use it as you see fit:
Togapa uses cookies and similar technologies in three categories: strictly necessary (always on), analytics, and advertising. Necessary cookies are required for the Service to work. Analytics and advertising cookies are optional and, where the law requires it (for example in the EU/UK), are set only after you consent via our cookie banner — you can change or withdraw your choice at any time through our cookie settings. Everything we set is described below.
| Name / pattern | Type | Purpose | Lifetime |
|---|---|---|---|
sb-…-auth-token (and related …-code-verifier, …-expires-at) | Essential | Keeps an event host securely signed in (authentication tokens). | Session / token refresh |
togapa_gs_{eventId} | Essential | Anonymous guest session for an event, so requests/votes are linked and one-vote-per-song is enforced. HTTP-only. | 24 hours |
spotify_oauth_state | Essential | Security (CSRF protection) during the optional Spotify connection flow. | Short-lived, during connect |
_ga, _ga_*, _gid (Google Analytics) | Analytics | Measures how visitors find and use our sites so we can improve them. | Up to 2 years |
_gcl_au (Google Ads) | Advertising | Measures ad conversions and supports remarketing via Google. | Up to 3 months |
_fbp (Meta / Facebook Pixel) | Advertising | Measures ad performance and lets us show and retarget ads on Facebook and Instagram. | Up to 3 months |
bcookie, lidc, UserMatchHistory, li_* (LinkedIn Insight Tag) | Advertising | Measures ad performance and lets us show and retarget ads on LinkedIn. | Up to 2 years |
| Key / pattern | Purpose |
|---|---|
togapa-admin-theme | Remembers an event host's light/dark theme on the dashboard. |
togapa-theme-{eventId} | Remembers a guest's light/dark theme for an event. |
togapa_guest_{eventId} (legacy) | Older guest-session storage, being phased out in favour of the cookie above. |
| Song-artwork cache | Temporarily caches album-art URLs to speed up search, cleared when the browser tab closes. |
You can change or withdraw your consent at any time through our cookie banner or cookie settings, and you can clear cookies and local storage through your browser settings. You can also opt out directly with the providers — for example via Google Analytics' opt-out browser add-on and the ad-preference settings of Google, Meta, and LinkedIn. Note that blocking essential cookies will prevent sign-in and guest sessions from working.
Depending on where you live (e.g. the EU/UK under GDPR, or California under CCPA/CPRA), you may have the right to:
Event hosts: you can update most data directly in your account, and you can delete your account, which removes your profile and cascades deletion to your events, requests, votes, messages, and guest contacts.
Guests: because the event host who ran your event controls your guest information, the fastest route is usually to ask that event host. You may also contact us at support@iwantoverflow.com and we will help facilitate your request with the relevant event host.
To exercise any right, contact us at support@iwantoverflow.com. We may need to verify your identity first. We will respond within the timeframe required by applicable law (generally within 30 days). You also have the right to complain to your local data protection authority.
We protect data with measures including: encrypted transport (HTTPS), hashed and salted passwords managed by our authentication provider, HTTP-only and Secure cookies, database Row-Level Security so that event hosts can only access their own data, restricted-access guest contact tables, signed and verified payment webhooks, rate-limiting on sensitive actions, and audit logging. No system is perfectly secure, but we work to protect your information and to respond promptly to any incident.
The Service is intended for event hosts and event guests and is not directed at children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided us personal data, contact us and we will delete it. Event hosts are responsible for ensuring their events comply with laws applicable to their audience.
Togapa is operated from the State of Michigan, USA, and uses providers located in various countries, including the United States. If you use the Service from outside those countries, you understand your data may be transferred to and processed there, with the safeguards described in Section 5.
We may update this Policy from time to time. When we make material changes we will update the "Last updated" date and, where appropriate, notify account holders by email or in-app notice. Your continued use of the Service after changes take effect constitutes acceptance.
For privacy questions, data requests, or complaints: