Privacy Policy

Plain-English summary

Here's the short version. The rest of this page has the detail and the legal framing.

If you played a game and claimed a code, your email or phone number went to the brand that made the game, along with your score and a record of the consent text you saw. We emailed you the code on the brand's behalf. We don't market to you and we don't sell your contact. See If you played a brand's game.
If you're a brand, we collect your account, your workspace and games (including assets we fetched from your site at your request), the contacts your games capture, billing details, and the keys for the tools you connect. The contacts are yours; we process them for you and keep a copy only for deduplication, billing, and your ledger.
We don't sell personal information, and we don't share it with advertisers for cross-context behavioral advertising.
AI helps build games, not process people. Your store's text and images may be sent to our AI providers to write copy and cut out a mascot. Player contacts are never sent to an AI provider, and nothing is used to train models. See AI processing.
You can delete your workspace and data by emailing us — we remove it within 30 days, with narrow exceptions listed below.
Our core infrastructure runs on Google Firebase, payments go through Stripe, and emails go through SendGrid. A full list of service providers is in the subprocessors section.

Who we are

“Arcadette,” “we,” “us,” and “our” refer to VNTOS LLC, the Delaware limited liability company that operates the Arcadette application, the website at arcadette.com, the games we host on play pages and serve inside embeds on brands' sites, and related services (together, the “Service”). For users in the European Economic Area, the United Kingdom, and Switzerland, VNTOS LLC is the data controller for brand account information and for the data we hold about play, billing, and security.

A note on player contacts. When a player claims a reward in a brand's game, the brand decides what to ask for and what consent to show, and the contact goes to the brand. So the brand is the controller of that contact and Arcadette processes it on the brand's behalf as its service provider (processor) — capturing it, sending the code email, and syncing it where the brand chose. For the narrow purposes of billing, detecting duplicates and abuse, and honoring suppressions, we act as an independent controller. The processor terms are in our Terms. Arcadette is a small, independent operation — if you email us, you're likely reaching the founder directly.

If you played a brand's game

You can play any Arcadette game without an account and without giving us anything. Here is exactly what happens if you claim a reward:

What you give. An email address and, if the brand asked for it, a phone number. The game also records your score, the code you unlocked, the consent text shown to you, the time, your IP address, and the page (and any campaign tags in its address) the claim happened on.
Where it goes. To the brand's Arcadette workspace and, in real time, to the marketing tools the brand connected (for example, its Shopify customer list, Klaviyo, Mailchimp, or an SMS platform). What the brand does with it after that is governed by the brand's own privacy policy and the consent you gave.
What we send you. One email with your code, sent on the brand's behalf from an Arcadette address. We don't send marketing, and we don't track opens or clicks in that email.
What we keep. A copy of the contact in the brand's ledger, a hashed version of your address for deduplication, delivery events for that one email (delivered, bounced, reported as spam), and whether the contact synced to the brand’s list. Aggregate play counts per game carry no identity.
Your browser. The game stores your best score and the codes you already claimed in your browser's local storage so you don't see the form twice. A popup on a brand's site remembers when it was last shown so it doesn't nag. Nothing here identifies you to us.
To stop hearing from a brand, use the unsubscribe link or reply STOP to what they send, or contact the brand. If you can't reach them, email support@arcadette.com and we'll add you to that brand's suppression list and help you reach the right party. See also Data in a brand's workspace.

Information we collect

We group the data we handle into the buckets below. Not every person generates data in every bucket — players only ever touch the first two.

Category	Examples	Source
Player contacts	Email address, phone number (if the brand enabled it), score, reward tier and code, consent record (text shown, time, IP address, page URL and campaign parameters), delivery status of the code email, billing outcome, and sync status per destination.	Players, via the brand's game
Play counting	A random anonymous browser identifier is transformed into a workspace-scoped one-way signal and added to aggregate player estimates. A separate daily one-way network signal helps detect implausibly fast automated traffic. Raw IP addresses and browser identifiers are not stored in play analytics, and IP addresses are never treated as people or used to cap genuine replay. The country an address belongs to is looked up on our own servers and counted per day; the address itself is not kept. Country data: IP Geolocation by DB-IP.	Collected automatically from the game
Play activity	Counts per game per day of qualified plays, finished runs, codes shown, claim sheets opened, contacts captured, shares, and filtered automated or duplicate starts. Approximate player counts are held as aggregate statistical sketches, not player profiles.	Collected automatically from the game
Brand account	Email address, Google Sign-In identifier if you use it, display name, workspace name and membership, sign-in codes (stored hashed and expired within minutes).	Brands, Google
Workspace & games	Store URLs you paste and the public text, logos, mascots, product images, and colors we fetch from them at your request; images you upload; game copy, reward tiers and the codes you paste, capture and consent settings, placement settings, and the generated character art.	Brands, and the brand's own website
Destinations	Settings and keys for the tools you connect (Stripe, WooCommerce, Shopify, Klaviyo, Mailchimp, a webhook URL and signing secret), stored encrypted and never shown back; Arcadette API keys you make (kept only as a one-way hash) and the AI tools you approve. For a store that installs Arcadette from Shopify: the store's name, contact email and domain, whether it is a development store, and the store's access token, stored encrypted.	Brands, Shopify
Billing	Stripe customer identifier; the kind of payment method on file with its brand or bank and last four digits (for Link, a masked email); plan, plays this month, credits, invoices, refunds. Full card and bank account numbers never touch our servers. For a workspace billed through Shopify: the Shopify subscription and purchase identifiers and their status; Shopify holds the payment details.	Brands, Stripe
Suppression list	Hashed emails and phone numbers a brand never wants captured (uploaded lists, bounces, spam reports, unsubscribes). The original values are not stored.	Brands, delivery events
Device & usage	Browser and device type, language, approximate IP-derived country, a device identifier cookie for games made before sign-in, and basic event and error logs needed to operate and secure the Service.	Collected automatically

Referrals.If someone sent you to Arcadette (for example, with a link to claim a game made for your business), we record who sent you and which plan you first paid for, so we can credit them. We don't share your contacts or game data with them.

Sensitive data we try to avoid

We don't ask for government IDs, payment-card numbers (Stripe handles those), biometrics, or health data. Don't put sensitive information in game copy or consent text.

How we collect it

Directly from you — when a brand creates an account, pastes a store URL, uploads an image, edits a game, connects a destination, adds a card, or contacts support; and when a player fills in the claim sheet.
From the brand's website — when a brand pastes its store URL, we fetch that site's public pages, images, and product listings to build the game. We only fetch what's public, and only at the brand's request.
Automatically from the game and your device — the game runtime sends anonymous play counts, and our infrastructure logs basic device, usage, and error data for security and reliability.
From third parties — Google returns a basic identifier and email when a brand signs in with Google; SendGrid returns delivery events for code emails; Stripe returns card metadata and invoice status; a connected destination may tell us whether an address is already subscribed there (so we don't bill it).

How we use it

Each of the purposes below corresponds to a legal basis under the EU/UK GDPR. We only process your data where we have a valid basis.

To run the Service — build and serve games, capture the contact a player chose to leave, email the code, sync the contact to the brand's destinations, and show the brand its ledger. Legal basis: performance of our contract with the brand; for players, the brand's consent and our processing on its instructions.
To bill fairly — decide whether a contact is verified and new, count plays against the plan, and produce invoices. Legal basis: performance of contract; legitimate interests.
To build games with AI — send a brand's text and images to our AI providers to draft copy and prepare character art. Legal basis: performance of contract; legitimate interests.
To keep Arcadette honest and safe — detect duplicate, disposable, and abusive claims; honor suppression lists; detect fraud; enforce our Terms; investigate reports. Legal basis: legitimate interests; legal obligations where they apply.
To improve the Service — understand which features are used and diagnose errors, using aggregate play counts and basic product events. Legal basis: legitimate interests; your consent where required.
To communicate with brands — sign-in codes, billing notices (receipts, plan changes, renewal reminders, failed payments, plays running low), the weekly digest of a workspace's numbers, and occasional product announcements you can opt out of at any time. Legal basis: performance of contract; legitimate interests; consent for marketing where required.
To comply with the law — respond to valid legal process, defend claims, and meet regulatory obligations. Legal basis: legal obligation; legitimate interests.

We do not use personal information or your content to train generative AI models, and we do not sell personal information as the term is defined under California and other US state privacy laws.

AI processing

When a brand makes a game, the public text we fetched from its site (or the brand name and description it typed) is sent to Anthropic to draft the game's copy in the brand's voice, and mascot or product images may be sent to fal.ai to remove backgrounds and prepare sprites.

These providers process the data as our service providers to return a result and do not use it to train their models. Under our agreements, data we submit is not retained beyond what is needed to provide and secure the service.
Player contacts are never sent to an AI provider. Nothing a player types in a claim sheet leaves our systems except to the brand's destinations and the code email.
Because AI output can be inaccurate, brands should review generated copy and art before placing a game. See the Terms' AI features section.

We share personal information only in the ways listed here.

Player contacts with the brand — the contact a player leaves goes to the brand that made the game and to the destinations that brand connected. See Where brands send contacts.
Public games with everyone — a game's play page shows the brand's name, art, and copy to anyone with the link, and public games appear in our gallery. Play pages never show contacts or scores of other players.
With our service providers — vendors who host infrastructure, process cards, deliver email, or provide AI features on our behalf, under written contracts that restrict their use of your data. See the subprocessors table.
For legal reasons — to comply with subpoenas, court orders, and other lawful requests; to enforce our Terms; to protect the rights, property, or safety of Arcadette, our users, or the public.
In a business transfer — if Arcadette is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred. The acquirer must honor commitments made in this policy or give you notice and a choice before any materially different use.
With your consent — for any sharing not covered above, we'll ask first.

Service providers (subprocessors)

These vendors process personal data on our behalf. We'll update this list as the stack evolves, and give brands notice before adding a provider that handles player contacts.

Provider	Purpose	What they see
Google — Firebase and Google Cloud (Authentication, Firestore, Cloud Storage, Cloud Functions, App Hosting)	Account auth, database, image storage, backend, hosting	Everything in the table above, at rest in our systems. Privacy
Stripe	Payments (cards, wallets, bank accounts and other methods Stripe offers), plan subscriptions, build coin and play packs, invoices, refunds	Brand name, billing email, payment details (entered directly into Stripe), usage counts, invoice history. Privacy
Shopify	For stores that install Arcadette from Shopify: the app in the Shopify admin, discount codes in the store, and plans and packs billed on the store's Shopify bill	The discount codes we create for winners (named after the game, no contact details), the plan or pack bought, and the amount. Privacy
SendGrid (Twilio)	Delivers code emails to players and transactional email to brands	Recipient email address, the code and brand name in the message, delivery events. Open and click tracking are off. Privacy
Anthropic (Claude API)	Drafts game copy in the brand's voice	Public text from the brand's site and the brand's own descriptions. No player data. Not used for advertising or model training. Privacy
PostHog	Product analytics for this website and the brand dashboard	Which pages a brand visits here and what they do in their dashboard, with a workspace identifier and the domain half of the sign-in email. No player data — PostHog is not loaded on a game, an embed or a play link, so nothing a player does reaches it. No session recording. Not used for advertising or model training. Privacy
fal.ai	Removes backgrounds from mascot and product images	The brand images submitted for processing. No player data. Not used for model training. Privacy

We do not sell personal information to advertisers or third parties, and we do not share it for cross-context behavioral advertising.

Where brands send contacts

Every captured contact is kept in the brand's workspace, where its admins can export it. When a brand connects its own tools, captured contacts are also sent there at the brand's direction. Those recipients are the brand's service providers, not ours; the brand's account and agreements with them govern what happens next. Nothing is sent to a tool until the brand connects it.

Klaviyo, Mailchimp — the contact is added to the list or audience the brand chose, and subscribed only if the person agreed to marketing (email, or SMS where they ticked that box), with when they agreed and the game, prize, and code as profile properties or fields. Mailchimp only receives people who agreed; a brand may have Klaviyo also keep people who didn't, as profiles that are never subscribed.
Webhooks — the contact, what they agreed to, and what they won are posted as JSON to a URL the brand controls, signed so the brand can verify it came from us.
Discount codes in the brand's store — when a brand connects Stripe, WooCommerce, or Shopify, a single-use code is created there for each winner, named after the game. In Stripe the code also carries an internal Arcadette reference for the contact, never their email.
The Arcadette API and AI tools — the brand's own systems, and AI tools a workspace admin approves (for example through our MCP server), can read that workspace's games, results, and contacts, within the permissions the admin gave.
CSV export — workspace admins can download their contacts.

Before syncing, we may ask a connected destination whether an address is already subscribed there, so the brand can see which contacts are new. We keep that answer only as a label on the contact.

Cookies & local storage

We use a handful of cookies and browser-storage keys, all first-party and none for advertising.

Name	Where	Purpose & lifetime
Sign-in session	arcadette.com (Firebase Auth)	Keeps a brand signed in. Until sign-out.
al_device	arcadette.com	Random device identifier so a browser can edit the games it made before signing in and see their contacts. One year.
ph_<key>_posthog	arcadette.com — this website and the brand dashboard only	PostHog product analytics: tells one visit from another so we can see where brands get stuck. Never set on a game, an embed or a play link, so it is never placed on a brand's store or on a player's browser. We honour Do Not Track. One year.
arcadelet:<game>	Browser local storage, on the page where the game runs	Your best score and the codes you already claimed in that game, so it can greet you instead of asking again. Until you clear site data.
arcadelet:seen:<game>	Browser local storage, on the brand's site	When a popup game was last shown, so it respects the brand's frequency cap. Until you clear site data.
arcadette:visitor	Browser local storage, on the page where the game runs	A random identifier for this browser, generated by the game and tied to nothing else about you. It stops one device being counted as a crowd: it caps how many plays a day count from the same browser, filters repeat views of the same game, and lets a brand estimate how many people played without anyone treating an IP address as a person. It travels with each play and is hashed before anything is written down, so what we keep cannot be turned back into it. Until you clear site data.

Brands placing a game on their own site should cover these keys in their own cookie disclosures where local law requires. None of them is used for advertising and none follows you to another site: the game keys are what let it behave as described, and the visitor key is what keeps its counts honest.

Your choices & controls

Players can decline. Playing never requires a contact. Skip the claim sheet and keep playing.
Brands control capture. Turn capture off per game, choose email and/or phone, write the consent text, and set where contacts go.
Suppression list. Brands can upload addresses that should never be treated as new contacts.
Visibility. Each game is unlisted (link only), public (in the gallery), or private. Change it any time; delete a game to stop it everywhere it's placed.
Export your contacts. Workspace admins can download a CSV from Settings → Destinations.
Billing emails (cap reached, failed payment, receipts) and the weekly digest can be reduced from Settings → Notifications; sign-in and legal notices can't be turned off.
Access, correct, or delete your data. Email support@arcadette.com and we'll help. To delete a workspace, email us — we permanently remove its information, games, and contacts from live systems within 30 days. Any copies in routine encrypted backups rotate out within 90 days and can't be restored on request. Narrow exceptions are listed below.

Your regional rights

European Economic Area, United Kingdom, and Switzerland

Under the GDPR and UK GDPR you have the right to access, correct, delete, restrict, and port your personal data, to object to processing based on legitimate interests, and to withdraw consent at any time. You also have the right to lodge a complaint with your local supervisory authority. To exercise any of these rights, email support@arcadette.com. We aim to respond within 30 days and don't charge a fee for most requests.

California (CCPA/CPRA)

California residents have the right to know what personal information we collect and how it's used, request deletion or correction, and opt out of “sharing” for cross-context behavioral advertising (we don't do this, but the right exists). You also have the right not to receive discriminatory treatment for exercising these rights.

Other US states

If your state grants privacy rights similar to the above (access, correction, deletion, portability, opt-out of targeted advertising/sale/profiling), we honor them. Email support@arcadette.com and tell us which state you're writing from.

Data in a brand's workspace

If you left a contact in a brand's game, that brand controls it and we process it on their behalf. Please direct access or deletion requests to the brand; we'll support them in responding, and you can email support@arcadette.com if you need help reaching the right party. If you ask us directly, we'll add you to that brand's suppression list so the contact is never treated as new again, and forward your request to the brand.

Retention & deletion

Active workspaces: we retain a brand's data for as long as its workspace exists so the games keep working and the ledger stays auditable.
Player contacts: kept in the brand's workspace until the brand deletes the workspace or asks us to delete the contact. Deleting a game keeps its contacts in the ledger; deleting the workspace removes them.
Games made before sign-in that are never claimed may be deleted after a period of inactivity.
Deleted workspaces: we remove or anonymize personal data, games, assets, and contacts from live systems as soon as practicable, typically within 30 days. Copies may persist in routine encrypted backups for a limited additional period (up to 90 days) before rotating out.
Copies outside our systems: contacts already synced to a brand's destinations and share cards players sent are outside our control.
Billing records (invoices, usage ledgers) are retained as long as tax and accounting law requires.
Safety & legal holds: we may retain limited information after deletion to comply with legal obligations, resolve disputes, prevent abuse, or enforce our agreements.
Aggregate & de-identified data (for example, play counts per game) that can no longer be linked to anyone may be retained indefinitely.

International data transfers

VNTOS LLC is based in the United States, and our service providers store data primarily in the US. If you use the Service from outside the US, your information is transferred to and processed in the US. Brands outside the US that need standard contractual clauses for player data can email support@arcadette.com.

Security

We protect your data with encryption in transit (TLS) and at rest for our primary databases and image storage, authentication through Firebase with one-time codes rather than passwords, encryption of the API keys brands give us, hashing of addresses used for deduplication and suppression, and access controls that limit who can reach production systems. Card numbers are entered directly into Stripe and never reach us. Still, no system is perfectly secure. If we become aware of a breach affecting your personal information, we'll notify you (and, for player contacts, the brand) and the appropriate regulators as required by law.

Children

Arcadette is not directed to children under 13, and brands may not aim a game or its reward at them. By using the Service, you confirm that you are at least 13 years old. If we learn that we've collected personal information from a child under 13 without parental consent, we'll delete it promptly — email support@arcadette.com to report it.

Changes to this policy

We may update this policy as the Service evolves. For material changes we'll notify brands via in-app banner or email before the change takes effect. The Last updated date at the top always reflects the current version.

Contact us

Privacy questions, requests, and complaints — from brands or players — go to support@arcadette.com. General hello-type messages go to hello@arcadette.com. Arcadette is a small independent operation, so the person who replies is likely the person who built it.