Privacy Policy
Last updated October 30, 2026.
This policy explains what personal data Domino collects, why, who we share it with, how long we keep it, and the rights you have over it.
Who we are
Domino is operated by JPEG SRL, a company registered in Romania at Aleea Teilor bl. 3 sc. B ap. 9, Sfantu Gheorghe, Covasna 520067, with VAT number RO45465669 (“Domino”, “we”, “us”).
For anything in this policy, write to privacy@domino.run.
Who this policy covers
Domino is a platform for community quests, points, and rewards.
- Operators are our customers and their teams. They sign in to Domino Console and build projects: quests, rewards, and the apps their members use. We are the controller of operators’ personal data.
- Members are the people who take part in a customer’s project: they sign in to an app built on Domino, complete quests, and earn rewards. The customer who runs the project decides why and how its members’ data is used, and is the controller of that data. Domino processes it on the customer’s behalf and on its instructions. Questions about a project should go to the customer first; we will help them answer.
- Visitors of this website and the Domino docs, which use analytics cookies only if you agree; see Cookies and analytics.
What we collect
Operators
- Account. Your name, email address, and sign-in details, held by our authentication provider, Clerk, and the organizations you belong to and your role in them.
- Billing. Your plan, invoices, and billing contact. Stripe processes payments; we never see or store full card numbers.
- Projects. What you create: quests, rewards, settings, app source code, uploaded images, and the API keys and secrets you configure, which we store encrypted.
- Playground. When you build with the agent in Console, your project code runs in an isolated sandbox, and your prompts and code are sent to the AI model you choose through OpenRouter.
- Feedback and support. Messages you send us, including feedback sent from the CLI and conversations in the support messenger.
- Usage. How far your organization has got with Domino (such as whether a project has gone live), which we use to improve the product and to know which customers to help. If you agree to analytics cookies, also what you do in Console, as described in Cookies and analytics.
Members
What a project collects depends on how its operator set it up. It can include:
- Email sign-in. Your email address and a one-time code we email you.
- Google, Apple, X, Discord, and Telegram. When you sign in with or link one of these accounts, we receive the account’s ID, and the name, username, profile picture, and email address it shares with us.
- Communities. When a project connects a Discord server or a Telegram group, we check whether you are a member, and on Discord we can assign the roles the operator configured. For quests that count activity there, we record the messages you post and the reactions you add on Discord (with the message text only when the operator asks for it), and the reactions you add in Telegram groups. So that reactions can be credited to a message’s author, we note who wrote each message in a connected Telegram group, never its text, and delete that note after 90 days.
- Wallets. The public address of a wallet you connect and the signature that proves you own it. We read public blockchain data about that address, such as balances, to check quest requirements.
- Quest evidence. Photos, files, and answers you submit for a quest. A photo, a text answer, or a linked post a quest checks can be reviewed automatically by an AI model running on Cloudflare.
- Activity. Your profile, the quests you start and complete, points, rewards, referrals, and leaderboard positions.
- Creator and social accounts. When you link a YouTube channel or a TikTok account, we read the data described in the sections below. When a project tracks posts on X, we read the public posts and profile of your linked X account.
- Provider tokens. When reading an account in the background is part of a quest, we keep the access and refresh tokens the provider gives us, encrypted, until you unlink the account.
Everyone
Our servers see your IP address and browser details with each request. We use them to keep the service running and secure, such as limiting sign-in attempts, and keep them in short-lived logs.
If you write to us in the support messenger on this website, the docs, or Console, we keep your conversation and any contact details you give us, so we can answer you.
YouTube channels
A member can link a YouTube channel to a project so that quests can count the Shorts they publish. Linking uses Google sign-in with the read-only YouTube scope (youtube.readonly) and asks you to pick one channel. With it we read:
- the channel’s ID, title, and profile picture, to show which channel you linked;
- the channel’s uploads, and for each video its title, description, tags, publish date, and duration, to find the Shorts a quest counts;
- each video’s file details (its width, height, and rotation), only to tell whether it is a vertical Short; we do not store them;
- each video’s public view, like, and comment counts, which quests use as goals.
We read your channel only with your own authorization, never post or change anything on it, and never use the data for advertising. The operator of the project you linked it to can see the Shorts and counts that their quests use.
Domino’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Domino uses YouTube API Services: by linking a channel you agree to the YouTube Terms of Service, and Google’s handling of your data is described in the Google Privacy Policy.
You can stop our access at any time: unlink the channel in the project, or revoke Domino’s access in your Google security settings. Unlinking deletes the tokens we kept, and once Google tells us access was revoked we stop reading your channel. We delete the YouTube data we stored within the period the YouTube API Services policies require after you revoke access.
TikTok accounts
A member can link a TikTok account to a project so that quests can count the videos they publish. Linking uses TikTok Login Kit with two scopes:
user.info.basic: your open ID, display name, and avatar, to show which account you linked;video.list: your own videos, with each video’s title, description, duration, dimensions, share link, whether it is marked as AI-generated, and its view, like, comment, and share counts, which quests use as goals.
We read this data only with your own authorization, never post anything to TikTok, and delete the tokens we kept and the TikTok data we read when you unlink the account. You can also revoke Domino’s access in TikTok’s settings.
Why we use it
- To provide Domino under our contract with operators: running their projects, signing members in, checking quests, and granting rewards. This includes the service notices we email operators about their account, billing, and integrations, such as a trial starting, a live app going offline, or an integration that keeps failing. They go to your account email address whether or not you agree to analytics cookies.
- To bill and meet our tax and accounting duties (legal obligation).
- To secure the service, prevent abuse and fraud, and fix problems (legitimate interests).
- To improve Domino and to get in touch with operators about how they use it, through the milestones our servers record and our customer records (legitimate interests).
- Where you agreed (consent): analytics cookies and Console session recordings, and reading an account you link and authorize us to read. You can withdraw consent at any time, in Cookie settings or by unlinking the account.
We do not sell personal data.
Who we share it with
We use these service providers to run Domino. Each processes data only on our instructions.
- Rackforest (Hungary): the servers that run our database and backend.
- Cloudflare: network delivery, app hosting, file storage (including quest evidence), sign-in email delivery, and the AI model that reviews quest evidence.
- Clerk: operator sign-in.
- Stripe: payments and invoices.
- PostHog (EU): product analytics, Console session recordings, and error reports from your browser, which run only if you agree; the usage milestones our servers record; and sending operators’ service notices about their account, billing, and integrations, for which we give it your account email address.
- Featurebase: the support messenger and its conversations.
- Twenty: our customer records for operators’ organizations.
- E2B and OpenRouter: Playground sandboxes and access to AI models.
- GitHub: storing and building the source code of hosted apps.
- Linear: feedback sent from the CLI.
- dRPC, PublicNode, and the public Cosmos Hub and Osmosis endpoints: reading public blockchain data about connected wallets.
- An X data provider: reading public X posts for projects that track them.
We also exchange data with the services you sign in with or link (Google and YouTube, Apple, X, Discord, Telegram, and TikTok) as described above, and we share a member’s data with the operator of the project they take part in. We disclose data to authorities when the law requires it.
International transfers
Our database and backend run in the European Union. Some of the providers above are based in, or reach data from, the United States and other countries outside the European Economic Area. Where they do, we rely on an adequacy decision, such as the EU–US Data Privacy Framework for certified companies, or on the European Commission’s Standard Contractual Clauses.
How long we keep it
- Operator accounts and projects: while the account is open. When a customer deletes a project, it can be restored for 30 days; after that its data, including its members’ data and evidence, is deleted.
- Quest evidence: deleted 90 days after it is reviewed, unless the project’s operator sets another period.
- Linked-account tokens: until you unlink the account.
- Console session recordings: 30 days.
- Billing records: as long as Romanian tax and accounting law requires.
- Sign-in codes, sessions, and rate-limit records: until they expire.
- Logs and backups: for a limited time, then deleted.
Security
Data is encrypted on its way between your device and Domino, and between Domino and its service providers. Provider tokens and the secrets operators configure are encrypted at rest with keys held separately from the data. Access to production systems is limited to the staff who need it.
Your rights
Under the GDPR you have the right to access your personal data, to have it corrected or erased, to restrict or object to how we process it, to receive it in a portable format, and to withdraw consent at any time. To use any of these rights, write to privacy@domino.run. If you are a member of a customer’s project, you can also ask the customer, who controls that data.
You can complain to a data protection authority. Ours is the Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP), and you can also complain in the EU country where you live or work.
Children
Domino is not meant for children under 16. If you believe a child has given us personal data, write to us and we will delete it.
Changes
We will update this policy when what we do changes, and change the date at the top. If a change matters, we will tell operators by email before it takes effect.
Contact
JPEG SRL
Aleea Teilor bl. 3 sc. B ap. 9
Sfantu Gheorghe, Covasna 520067
Romania