1. Introduction
TWOZERO ("we", "us", "our") respects your privacy. This Privacy Policy explains how we collect, use, and protect your personal information when you use our Service.
TWOZERO is a creative layer for TouchDesigner providing AI-assisted creative production tools, cloud components, and a library of ready-made TouchDesigner components. The Service includes the TWOZERO plugin for TouchDesigner with its MCP server and ZOPs (Zero Operators), TWOZERO APP (web-based content generation at app.twozero.ai), TWOZERO HUB (storage for your components: HUB Local on your disk and HUB Cloud in the cloud) and TWOZERO Rudiments (a library of components we publish, such as ZERROR). The plugin and MCP are free. Generations and other paid AI operations are paid from a single credit balance.
Controller: The controller of your personal data is SETUP DESIGN DMCC, a Free Zone Company registered in the Dubai Multi Commodities Centre (license No. DMCC-864530), DMCC Business Centre, Level No 1, Jewellery & Gemplex 3, Unit No: 2525, Dubai, United Arab Emirates, which operates TWOZERO.
2. Information We Collect
2.1 Account Information
- Email address
- Username and the avatar you add, which are public, and the cover image you add
- A password, stored as a hash, if you set one on an older account. Sign-in normally uses a one-time code we email you
- An access key that the plugin and APP use to keep you signed in
- The version of our Terms and Privacy Policy you accepted, and when
2.2 Payment Information
- Card payments are processed by Lemon Squeezy, which acts as merchant of record. We do not see or store your card details
- For card payments and subscriptions we store order, customer and subscription identifiers, billing email, amount, status, and renewal and end dates. Lemon Squeezy also tells us your billing country
- USDT payments: you send USDT on Ethereum or Base from a wallet you connect, and sign a message with that wallet to show the payment is yours. We store the sending wallet address, the transaction hash, the amount and the status, and we check the transaction through Alchemy. Blockchain records are public and permanent, and we cannot erase them
2.3 Usage Data
- A ledger of every change to your credit balance: top-ups, bonuses, included credits, spending and refunds
- APP and ZOPs: creation history (generation type, settings, outputs, cost)
- MCP: we do not receive or store the content of your MCP sessions. Plugin usage counts are described in Section 2.6
- HUB Cloud: the people you share components with, public links you create, and the files you send to other users or receive from them, with any message attached
- APP: the projects you share, the people you share them with, their access level (view or add works), and whether they accepted
- Rudiments: the rudiments you add to your HUB Cloud and when, and the rudiments you download while signed in (in server logs, Section 2.7)
- Sign-in records: when you request a sign-in code, the IP address and browser it came from
- When you were last active on the site and in the plugin
- Device and browser information (for APP and web access)
- Product analytics, if you accept it in the cookie banner: the pages you visit and the actions you take, with the account and payment details listed for PostHog in Section 6
2.4 Communications
- Support tickets and emails
- Feedback you provide
- The emails we send you: sign-in codes, invites, notices about your account, and emails about getting started and about the product
- For emails about getting started and about the product: whether you open them and which links you click (see Section 3.1)
- Invites: if you invite someone, we store their email address, who invited them and how many times we sent the invite
- Messages you send to other users through the Service, with their attachments
2.5 Content Data
TWOZERO APP (Private Workspace):
- Prompts and inputs you submit for generation
- Reference images, audio or video you upload
- Outputs stored in your private workspace
ZOPs in TouchDesigner:
- Image, video, audio, digital human and 3D ZOPs send their prompts and inputs (images, audio or video) to our servers. We store them and the outputs in your creation history, like APP generations
- Text operations in the plugin go from your machine straight to OpenRouter with a key we create for your account. We see how much that key spends, not your prompts or outputs
TWOZERO APP (Public Feed):
- Work our team publishes on the curated feed, with its prompt and its author's username and avatar. This includes work users submitted before August 2026
- Your likes on feed posts
TWOZERO MCP:
- We do not store, log, or review the content of your prompts or generated outputs
- All MCP outputs (patches, code, components) are generated and delivered to your local environment
TWOZERO HUB Cloud:
- The components you upload, with their versions, previews and descriptions
- Your repositories and their sharing settings. People who manage a repository or component you have access to (its owner and anyone with full access) see your username and email address
TWOZERO Rudiments:
- A copy of each rudiment you add to your HUB Cloud, with a note of where it came from
- A total download count for each rudiment, which is not linked to you
- Nothing about what you do with a rudiment afterwards: it runs inside your own TouchDesigner and sends us no telemetry
2.6 Plugin Telemetry
While it runs, the TouchDesigner plugin regularly sends us usage counts, usually every few minutes. We keep one record per installation per day. The record holds a key derived from your TouchDesigner installation and stored as a one-way hash, the TouchDesigner and plugin versions, and your operating system. It also holds counts: the number of characters your AI agent and the plugin exchange over MCP (the number only, never the text), tool calls, errors, and the peak number of running instances. We do not link these counts to your account, and we do not store your IP address with them.
2.7 Server Logs
Our servers keep technical logs for a short period, currently about 7 days. They include IP addresses, account IDs, the pages and API paths requested, and the email addresses our messages go to. We use them to keep the Service running and to investigate problems and abuse.
3. How We Use Your Information
We use your data to:
- Provide and improve our Service
- Process payments and manage credits
- Send service-related notifications
- Email you about getting started with your account and about the product (see Section 3.1)
- Respond to support requests
- Prevent fraud and abuse
- Enforce our Terms of Service and Acceptable Use Policy
- Handle copyright notices and counter-notifications
- Curate the public feed
- Understand how the plugin is used, from telemetry counts
- Comply with legal obligations
3.1 Emails About Getting Started and the Product
If you had not paid for anything when the series started, we may send you up to three emails about getting started and about the product: how credits work, what to try first, what a paid plan gives you. We skip an email when it no longer fits, for example after you buy a plan or make a generation. Replies go to hello@twozero.ai.
Our legal basis for these emails is our legitimate interest in helping new users get started and in telling them about paid features.
These emails contain a small image that tells us when an email is opened. Their links go through a tracking address first, so we see which link you click. We keep opens and clicks next to the record of the email we sent. To see which emails help and which to fix, we pick some of the people who would get these emails at random, and they do not get them. We then compare whether people in each group buy credits or a plan in the following weeks.
With the author's consent, these emails can show work from the public feed, signed with the author's username.
You can object to these emails at any time. Each of them has an Unsubscribe link, and many mail apps also show an Unsubscribe button next to the sender. One click stops the emails. You do not need to sign in.
Unsubscribing does not stop the emails the Service needs to work, such as sign-in codes and notices about your account or payments.
3.2 Legal Bases
Where data protection law requires a legal basis, we rely on the following:
- Running your account, providing the Service, answering support requests, taking payments and sending the emails the Service needs: performance of our contract with you
- Product analytics (PostHog): your consent in the cookie banner, which you can withdraw at any time
- Emails about getting started and the product: our legitimate interest in helping new users get started and in telling them about paid features (Section 3.1)
- Plugin telemetry, cookie-free site statistics (Plausible), server logs, security, fraud prevention, content safety filters and enforcing our Terms and Acceptable Use Policy: our legitimate interest in running, protecting and improving the Service
- Sending an invite you ask us to send and keeping the invitee's address: our legitimate interest in letting you invite people to the Service
- Handling copyright notices and counter-notifications, including telling a user about a takedown and passing a counter-notification to the person who sent the notice: our legitimate interest in resolving copyright disputes and keeping the Service lawful
- Keeping payment records and other records the law requires, and answering lawful requests from authorities: our legal obligations
- Publishing your work on the feed or showing it in our emails: your consent, which you can withdraw at any time by asking us to remove the work
4. Privacy Model by Service Component
TWOZERO handles data differently depending on which component you use:
4.1 TWOZERO APP and ZOPs (Private Workspace)
| Aspect | How We Handle It |
|---|---|
| Visibility | Only you can access your private content |
| Monitoring | We do NOT actively monitor private content |
| Storage | Encrypted and stored securely on our servers |
| Sharing | Never published without your consent |
| Retention | Until you delete it or delete your account |
Your private creations remain private. We do not review your private workspace content or show it to other users. Automated safety filters check prompts at creation (Section 5.1). To run the Service, we send your content only to the service providers in Section 6 that store it and run generations for us. Otherwise we look at or disclose your private content only:
- When required by law
- To investigate reported abuse linked to your account
- When you allow us to publish it
- When you share a project: the people you share it with see its works and your username
4.2 TWOZERO APP (Curated Public Feed)
| Aspect | How We Handle It |
|---|---|
| Visibility | Visible to everyone |
| Monitoring | Our team selects and publishes everything on the feed |
| Storage | Stored as public content |
| Sharing | Displayed on curated public feed |
| Retention | Until you request removal or we remove it |
The public feed is curated by our team. Users cannot currently submit content to it. Work that users submitted before August 2026 stays on the feed until its author asks us to remove it or we remove it (Section 5.2).
4.3 TWOZERO MCP
| Aspect | How We Handle It |
|---|---|
| Prompts to your agent | Not stored, not reviewed, not logged |
| Generated outputs | Delivered to your local environment, not stored by us |
| Usage counts | Daily plugin telemetry counts (Section 2.6), not linked to your account |
| Your AI agent | Your agent (such as Claude Code) runs under your own account with its provider. That provider's privacy policy applies to your prompts |
MCP is privacy-minimal by design. MCP itself is free, and the prompts you give your agent do not reach our servers. Your prompts, generated patches and code remain between you and the provider of your AI agent.
ZOPs are different, including ZOPs your agent starts through MCP. Image, video, audio, digital human and 3D ZOPs send their prompt and inputs to our servers to run a generation, and we handle them like APP generations (Section 4.1). Text operations go straight to OpenRouter (Section 6).
4.4 TWOZERO Rudiments
When you add a rudiment to your HUB Cloud, this runs on our servers under your account, so we see which rudiments you add and when. When you download a rudiment while signed in, our server logs record the download with your account (Section 2.7), and for a PRO rudiment we check your subscription. Free rudiments can also be downloaded without an account. Each rudiment has a total download counter that is not linked to you. Once a rudiment is in your own TouchDesigner project, it runs locally and sends us no telemetry. We do not see what you build with it, or whether you open it at all.
4.5 What We See vs. What We Don't
| Data Type | APP Private | Public Feed | MCP | Rudiments |
|---|---|---|---|---|
| Prompts | Not reviewed | Shown with the post | Not stored | N/A |
| Outputs | Not reviewed | Selected by our team | Not stored | Local only |
| Billing data | Stored | Stored | None for MCP itself | Subscription check |
| Username | Shown only to people you share a project with | Shown with the post | Not sent to us | Not shown to others |
ZOP generations, including ZOPs your agent starts through MCP, are handled and billed like APP Private.
5. Content Moderation and Safety
5.1 APP and ZOP Private Content Processing
For content in your TWOZERO APP Private Workspace and your ZOP generations:
- We apply content safety filters at creation in TWOZERO APP and in ZOPs that run on our servers
- Automated systems may block certain prohibited prompts
- We do not perform post-creation review of private content
- We do not use your private content to train models
5.2 Public Feed
The curated public feed operates as follows:
- Our team selects and publishes everything on the feed
- Users cannot currently submit content to the feed
- We may remove any post. If we remove content you uploaded or submitted, we tell you why and how to appeal (Acceptable Use Policy, Section 8.3)
5.3 MCP Processing
For TWOZERO MCP requests:
- We do not store or review prompt content
- We do not store or review generated outputs (code, patches)
- Your prompts are processed by the provider of your AI agent under its privacy policy
5.4 Data Retention for Safety
We may retain records of:
- Prompts and outputs flagged for policy violations
- Account actions taken for Terms violations
- Decisions to remove posts or restrict accounts, and appeals sent to us
- Information necessary to comply with legal requests
6. Data Sharing
We share your information only with:
| Recipient | Purpose | Data Shared |
|---|---|---|
| Lemon Squeezy (merchant of record for card payments) | Card payments and subscriptions | Email, account ID, order and subscription data |
| Alchemy, and the public Ethereum and Base blockchains | Checking USDT payments | Your sending wallet address and the transaction, which are public on the blockchain |
| Heroku | Hosting, database and server logs (Papertrail) | Encrypted account, usage and content data; server logs (Section 2.7) |
| Cloudflare (R2 storage and CDN) | Storing and delivering files | Files you upload, generation outputs and thumbnails, avatars; visitor IP addresses at the CDN |
| Backblaze B2 | Backup copies of stored files | Copies of the files in our storage |
| Resend | Email delivery | Your email address, the emails we send you, and their delivery, opens and clicks |
| Wavespeed, and the third-party models it routes to (generations in APP and ZOPs) | Image, video, audio, digital human and 3D generation | Your prompts and any images, audio, video or other material you upload for a generation. Uploaded material may contain personal data, including images and voices of people |
| OpenRouter, and the models it routes to | AI features in APP and in the plugin, such as prompt writing and text generation | Your prompts and the images you send with them. From APP they pass through our servers. From the plugin they go to OpenRouter directly. The key the plugin uses carries your account ID |
| The provider of your AI agent (MCP) | Your own account with that provider | Nothing from us: your agent works with TouchDesigner through the plugin on your machine. ZOPs that the agent runs are handled as described in Sections 4.3 and 6 |
| PostHog (EU) | Product analytics | Pages you visit and actions you take, such as generations and the model used. Where you click and scroll on our pages. Your IP address and the approximate location derived from it, and your device, operating system and browser. Your username and account creation date, never your email address. Your credit balance and whether you have stopped spending credits. Your payments: amount, bonus, method, billing country, order ID or transaction hash, and your total payments to date. Your plan, billing period and subscription status. When you request a sign-in code, sign in or create an account, with your email domain and whether you used the plugin or the website. When you come back after a week or more away, and when we last saw you. All of this is linked to your account only after you accept analytics in the cookie banner. If you reject or do not answer, your browser sends nothing, and the events our servers record are counted anonymously, without your account ID, username or email domain (Section 13) |
| Plausible | Aggregate site statistics without cookies | Page address, referrer, and your IP address and browser details. Plausible uses them to work out your country, browser, operating system and device type, and to count unique visitors. It does not store your IP address and does not identify you |
| Google (Google Workspace) | Our email inboxes (hello@, dmca@ and abuse@twozero.ai) | Emails you send us, including replies to our emails, support requests, copyright notices and abuse reports, and our replies |
| People you share with or send messages to | Project shares, HUB Cloud shares and public links, and messages you send through the Service | The works, components and messages you share, with their attachments, and your username and avatar. Anyone with a public link you create can see what it links to. A public link to a HUB Cloud component also shows the username and avatar of whoever uploaded each version. In HUB Cloud, people who manage a repository or component you have access to also see your email address (Section 2.5) |
| Visitors to our public pages | The curated public feed (Section 4.2) | Work our team publishes, with its prompt and its author's username and avatar |
| People who send us a copyright notice | Counter-notifications you send (Copyright & IP Policy, Section 5) | Your counter-notification, including your name, address and telephone number |
| Users whose content is the subject of a copyright notice | Telling them about the takedown (Copyright & IP Policy, Section 3) | A copy of the notice, with the sender's contact details removed |
| Legal authorities | When required by law | As legally required |
We do NOT:
- Sell your personal data
- Share data for third-party marketing
- Use your private creations for training purposes
- Expose your private workspace to other users
7. Data Security
We implement appropriate technical and organizational measures:
- Encryption in transit (TLS) and at rest
- Access controls and authentication
- Separation of private and public content storage
- Regular security assessments
- Incident response procedures
7.1 Private Content Security
- Private workspace content is encrypted
- Access restricted to your authenticated sessions
- Not accessible to other users or our staff (except as noted)
7.2 Public Content Security
- Published content is stored separately from private content
8. Your Rights
Depending on your location, you may have rights to:
- Access your personal data
- Correct inaccurate data
- Delete your data (subject to legal retention requirements)
- Export your data
- Restrict how we process your data
- Object to processing based on our legitimate interest (Section 3.2), including emails about getting started and the product (Section 3.1)
- Withdraw consent
- Request removal of published content
You need an email address to create an account and sign in, because we send sign-in codes to it. To buy a plan or credits, you give payment details to Lemon Squeezy, or send USDT from your wallet (Section 2.2). Without this information we cannot provide those parts of the Service. We do not make decisions about you by automated means that have legal or similarly significant effects on you. Automated filters may block a prompt (Section 5.1). If you think a filter blocked a prompt by mistake, tell us.
To exercise these rights, contact hello@twozero.ai. You can also complain to the data protection authority where you live or work.
8.1 Deleting Your Content
Private Content: You can delete private content at any time through your dashboard.
Published Content: You can request removal of published content. We will process removal requests within 7 days.
Account Deletion: To delete your account, email hello@twozero.ai from the address on your account. We will then:
- Delete your private content in TWOZERO APP and HUB Cloud within 30 days, subject to routine backup retention
- Remove your published content from the feed
- Retain only data required by law
9. Data Retention
| Data Type | Retention Period |
|---|---|
| Account information | Until account deletion + 30 days |
| Email records (sent, opened, clicked, unsubscribed) | Until account deletion + 30 days |
| APP and ZOP private creation history | Until you delete it or delete your account |
| APP published content | Until you request removal or we remove it |
| HUB Cloud components, repositories and shares; rudiments you add to your HUB; messages you send and their attachments; your likes on feed posts | Until you delete them or your account is deleted, plus 30 days |
| Product analytics (PostHog) | Until you withdraw consent and ask us to delete it, or until account deletion + 30 days |
| Sign-in records | Until account deletion + 30 days. For a sign-in code that never led to an account, 30 days |
| Invites you send | Until the person accepts the invite, or 12 months after the last invite we sent, or earlier if you or the person you invited asks us to delete them |
| Server logs | About 7 days |
| Payment records and credit ledger | As required by law (typically 7 years) |
| Safety-related records | As necessary for enforcement and legal compliance |
10. International Transfers
We are based in the United Arab Emirates. Our service providers process data in the United States, the European Union and other countries. Where data protection law requires it, we rely on the European Commission's standard contractual clauses or the provider's equivalent safeguards. To get a copy, email hello@twozero.ai.
11. Children's Privacy
Our Service is not intended for users under 18. We do not knowingly collect data from minors. If you believe we have obtained personal information from a minor, please contact us immediately.
12. Third-Party Services
We use third-party services for:
- Payment processing and checking blockchain payments
- Generations and other AI features
- Hosting, file storage, delivery and backups
- Email delivery and our email inboxes
- Analytics
These providers have their own privacy policies. We select providers with appropriate data protection standards.
13. Cookies and Tracking
We use essential cookies to keep you signed in, or signed out, across twozero.ai and app.twozero.ai and to remember your cookie choice.
We also use product analytics (PostHog, hosted in the EU) to understand how the Service is used. What we send to PostHog is listed in Section 6. We ask about it once, in the cookie banner, and that one answer covers all analytics about you: in your browser and on our servers, for example when a checkout opens or a payment goes through. When you are signed in, the answer is also saved to your account, so it applies where there is no browser to ask, such as payment notifications and the TouchDesigner plugin.
If you accept, analytics events are linked to your account ID. If you reject or do not answer, browser analytics stays off, and the events our servers record are counted anonymously: a random ID for each event, without your account ID, email address, username or IP address, and no profile is built. We never send your email address to analytics. Aggregate, cookie-free analytics (Plausible) runs on all our pages and does not identify you.
You can change your answer at any time in your account settings or on the Cookie Policy page.
We count opens and clicks in our emails about getting started and about the product separately, as described in Section 3.1. The cookie banner does not cover them. The Unsubscribe link in those emails stops them.
We do not use tracking cookies for advertising purposes and we do not sell your data. The full list of what we set, and a way to change your choice at any time, is in our Cookie Policy.
14. Changes to This Policy
We may update this Policy. If a change is material, we email you at least 30 days before it applies. That email is a notice: we do not treat your continued use as acceptance, and where a change needs your consent, we ask for it. If you do not agree with a change, you can close your account or cancel your subscription before it applies, and we refund the unused value of your Purchased Credits.
15. Contact
For privacy inquiries:
TWOZERO
Email: hello@twozero.ai
Website: https://twozero.ai
Controller: SETUP DESIGN DMCC, Free Zone Company (DMCC), license No. DMCC-864530
DMCC Business Centre, Level No 1, Jewellery & Gemplex 3, Unit No: 2525
Dubai, United Arab Emirates
Data Protection Contact: hello@twozero.ai