We do not train on your data.
NIUA does not use customer inputs (uploaded images, prompts, reference media) or outputs (generated meshes, animations, textures, audio) to train, fine-tune, or evaluate any AI model, proprietary or third-party. This applies to every account and every generation, including free usage. NIUA has no plan tiers. There are no exceptions, no opt-outs to enable, no enterprise upgrade required.
Some platforms in this space include language in their terms permitting training on non-Enterprise customer data. We do not operate that way, for anyone.
We make no claim on derivative works of our outputs. Use them however you want, including to train your own models. That is your right as the IP owner of the asset you generated. (Two upstream model licenses restrict training on specific outputs, speech and dialogue audio and part decomposition: see the Terms §5 and §6 carve-outs and the Model Licenses page.)
1. Introduction
NIUA ("we", "our", "us") is operated by Frank Yin at ohao.tech. This Privacy Policy explains how we collect, use, and protect your information when you use NIUA at ohao.tech/niua.
2. GDPR Compliance & Data Minimization
NIUA is operated in compliance with the European Union's General Data Protection Regulation (GDPR). The protections, rights, and disclosures described in this policy apply to all users globally. We do not run a two-tier privacy regime where EU users get different treatment than the rest of the world.
We practice data minimization. We collect only the data strictly necessary to operate the service. We do not gather information about you for marketing, profiling, behavioural advertising, third-party data brokers, or any other purpose disconnected from delivering the service you signed up for.
Specifically: basic account information (your verified email address from Google, GitHub or an email link, and a profile picture only if you upload one), payment data (handled by Stripe; we never see your card number), and the content you choose to upload for gate checks and generation jobs (which we store privately in your account so the service can function). The only other data we collect is the operational records and first-party product analytics described in §3.
3. Information We Collect
Account information: When you sign in with Google or GitHub, we keep only your verified email address. The provider may send us your name and profile picture, but we do not store them. If you sign in with an email link, we receive only your email address. We do not receive or store your password. A profile picture exists only if you upload one.
Payment information: When you top up your wallet, payment is handled by Stripe. We store the resulting wallet balance and a Stripe customer ID; we do not see, store, or process your card number, CVV, or full payment details directly.
Uploaded content: Files you upload to be checked by the gate, and the prompts, images, video clips and reference media you submit to the legacy generation add-on, including voice reference clips you upload for voice cloning. Stored privately in your account so the service can check them or produce outputs from them.
Contracts: Custom contracts you create are stored in your account.
Gate checks and receipts: A check records which file you checked (its storage key, hash, type and size), the contract, the result with any failures and measurements, the API key used, and the time. When a file passes, NIUA signs a receipt, and you can attach signed simulation reports (with their replays) to it. A receipt is public: anyone with its id can read it at ohao.tech/niua/receipts/<id> or through the API. It shows the file's hash, the contract, the result, the measurements the check took, when it was issued, and any signed simulation reports you attached to it (simulation only, no hardware tested). It never contains the file itself, its name or storage key, or who you are. There is no public list of receipts. Checks run without an account (the playground and the sample checks) are checked in memory and not kept. Gate checks run on NIUA's own servers (Railway and Cloudflare R2) and are never sent to a GPU provider.
Operational metadata: Job status, processing time, model used, error logs, and a trace of each API and MCP call (tool, client app, session, status, timing). For each sign-in session we also store the IP address and browser user agent, for security; they are deleted with your account. We use this to run the service and to show you your own agent's history, not to profile you. NIUA staff can feature a trace on a public showcase.
API keys and MCP connections: API keys you create are stored in your account. When you connect an MCP client, our MCP server keeps the sign-in session, the grant and a refresh token for up to 365 days, renewed each time the client refreshes, and issues access tokens that carry your email address.
Product analytics (first-party, cookieless): We record first-party usage events (page views and a few key actions: signing up, requesting early access, starting a generation, primary button clicks) to understand how the product is used and make it better. Analytics uses no cookies and no third-party trackers: we store a first-party random id in your browser's local storage and a per-tab session id in session storage. Each event records the page path, the referring page, any utm campaign tags and, when you are signed in, your account id. Events go only to our own servers. The data is never sold, never used for advertising, and never used to build a cross-site profile of you. We also derive a coarse country from your IP address for aggregate geographic insight; the country is stored and the raw IP address is immediately discarded.
Cookies: The only cookies we set are the ones that keep you signed in: a 30-day httpOnly session cookie on ohao.tech, a 10-minute cookie that guards the Google or GitHub sign-in step, and sign-in cookies for MCP connections.
4. How We Use Your Information
- To run gate checks on the files you submit and sign receipts for the ones that pass
- To run the legacy generation jobs you submit and return the resulting assets
- To authenticate your account and manage your sessions
- To bill your wallet for the generations you run, including auto-recharge if you turn it on
- To communicate service updates or respond to support requests
- To monitor uptime, error rates, and system performance
We do not use your inputs or outputs to train, fine-tune, or evaluate AI models. See the headline clause above.
5. Data Storage & Retention
Your data is stored using industry-standard cloud services (Railway PostgreSQL for account and job data, Cloudflare R2 for file storage). All data is transmitted over HTTPS.
Uploaded inputs and generated outputs stay in your account until you delete them. There is no automatic expiry. Deleting an asset removes its file and job record. Check records and public receipts for that file stay until you delete your account. To have a single receipt withdrawn sooner, write to privacy@ohao.tech.
6. Third-Party Services
We use the following third-party services to operate NIUA. Each receives only the data its role needs; none receive your generated content for training or marketing purposes.
- Resend: transactional email delivery (e.g. magic-link sign-in)
- Cloudflare: hosting, file storage (R2), and the proxy in front of our API (it tells us your country, which we use to keep outputs of the retired part decomposition feature unavailable in the EU, UK and South Korea)
- Railway: database and API hosting
- Modal: GPU compute for the legacy generation add-on (3D mesh, rigging, motion, music, speech, voice design, dialogue and sound effects, including voice reference clips you upload)
- Groq: the language model behind the LLM helpers (prompt polish and the workbench assistant); the text you send them goes to it
- Stripe: payment processing and wallet top-ups (PCI-DSS compliant; we do not handle card data directly)
- Google / GitHub: OAuth sign-in providers
- Discord: feedback you send through the app, with your account email, and operator alerts reach a private Discord channel
- unpkg: the API docs page loads its viewer from unpkg.com, which sees your IP address
7. Data Sharing
We do not sell, trade, or otherwise transfer your personal information to third parties. Your inputs and generated outputs are private to your account unless you share them (a public receipt, or a share link you create) and are not shared with other users, used in marketing materials, or fed into model training pipelines, ours or anyone else's.
8. Your Rights
Under GDPR, and applied to all users regardless of jurisdiction, you have the right to:
- Access: download all data we hold on you, including generated assets and operational metadata
- Rectification: correct inaccurate account information
- Erasure ("right to be forgotten"): delete your account and we remove, in one step, your profile and wallet, checks with their public receipts and simulation reports, contracts, generation jobs, the projects you own (with their members and invite links), your membership in other people's projects, playground chat sessions, agent runs, custom voices, early access requests, pending uploads, API keys, webhooks, traces, sign-in sessions and unused sign-in links. Right after, we delete the files you uploaded (for gate checks or for generation, including voice reference clips), every generated output file, thumbnails and your profile picture. Work other members did in a project you owned, or built on your files, stays in their own accounts. We keep only: your email on a list of addresses that already received starter credits (so they cannot be claimed twice); a record that the account id was deleted (so a sign-in token that has not expired yet cannot bring the account back); analytics events, with the account id removed; and, on jobs other members ran in a project you paid for, the id of the wallet that paid, which then points at nothing. Two things are not removed automatically: a file another account still uses (one they imported through a share link you made, or one they built on, made a voice from or checked in a shared project) stays while they keep it, and MCP sign-in sessions held by our MCP server can no longer reach the deleted account but are stored until they expire. Cached replies to retried API requests are deleted on their own within about a day. Write to privacy@ohao.tech to have any of these removed sooner.
- Portability: export your data in a standard, machine-readable format
- Objection: opt out of any non-essential processing (we don't run any, but the right is yours)
- Commercial use: use your generated outputs commercially, including to train your own models, with no attribution required
To exercise any of these rights, contact privacy@ohao.tech. We respond within 30 days as required by GDPR.
9. Changes to This Policy
We may update this policy from time to time. Changes will be posted on this page with an updated revision date.
10. Contact
For questions about this privacy policy, contact Frank Yin at privacy@ohao.tech.