Who receives your data: processors and recipients

Live list. Last updated 23 October 2026. Published at mirai.inc/legal/recipients. Page text version 5.3, 22 October 2026.

v5.3 change note: the US-person rule stated plainly; the face-comparison, image-safety and video partner rows; no affiliate named (R17). Added 22 October 2026: the AI vision checks, moderation, voice and Meta Pixel rows.

This is the live list that our Privacy Notice (section 6) and the Likeness Licence (clause 12.4 and Part 3, T4) refer to. Mirai Talent Inc. ("Mirai") is responsible for your data and stores it in the United States. Below is everyone else who receives it, what they get and where they process it.

• Processors act only on our written instructions, under contract.
• Generation engines may not train on your data.
• "Face data" in the tables below means your kit references, face data or both.

The US data rule

The face of a US person never goes to an engine, face check or partner developed or run by a company based in, or controlled from, China (including Hong Kong) or another country of concern. More precisely, US users' face data is processed only by engines that meet the US data rule. An engine meets it when no company or person restricted by the US Justice Department's rule on Americans' sensitive data (28 CFR Part 202) can access the data through it, and it keeps nothing after the job. If any signal says you are in the United States or a US territory, if you tell us at sign-up that you are a US citizen or US permanent resident, or if we are unsure, we treat you as a US user. Which engines serve which users can change; this list always shows the current choice.

1. Hosting, storage and database

2. Generation engines

Decentralised compute (0G). 0G decentralised compute network

• Serves non-US users only, for video generation.
• Not live. It is added here, with its node regions, with 30 days' notice (Terms Schedule D2) before it receives any data.
• Its data terms will cover: no training on your data; deletion after each job; node regions listed here; a transfer basis for each region. No data terms are signed, so no face data goes to it.

3. Face match and moderation

Our video partner

Voice, only if you add it

4. The partner model

None at launch. A partner multimodal model that makes content, checks content and scores competition entries is named here, with its country, before it receives any data (30 days' notice, Terms Schedule D2). For US users, only if it meets the US data rule.

5. Payments and payouts

Payout, tax and wallet-screening providers are added here, with their countries, before any payout runs. Support and appeals are handled by our own team, by email and in the app; no separate support provider receives your data.

6. Analytics, email and support

7. Platform Partners

Other apps that show Mirai content under a Partner Agreement. They get your card, price, rules and licence rows, never your kit.

8. Training recipients

None. Mirai is not training today.

9. Affiliates

None hold your data. If we name a Mirai affiliate by notice (Terms §1.3), it never receives kits, face data or data about US persons.

10. Others who may receive data

Independent controllers we receive data from. Our identity-verification partner runs the Verified Human Check, and a Partner App operator runs the Partner App you use Mirai in, each under its own privacy notice (Privacy Notice 1.4, 3). They send us the check's result, your verification level, a code unique to you and Mirai, and your Partner App username and picture. We send them only what the check or the payment needs. The current list of these named providers is available on request at legal@mirai.inc.

Buyers of licences, the clients named on their licence records, and social platforms you connect (outputs, licence rows, your posts); insurers, advisers and auditors, under confidentiality; a company that takes over running Mirai (Privacy Notice section 12); and police, courts and child-safety bodies, including NCMEC, where the law requires.

How we announce changes

• A new processor or engine: added here, with 30 days' notice in the app, before it receives your data (Terms Schedule D2). Moving a feature between engines already on this list is not a change (Schedule D2A).
• A new Platform Partner: in the United States, named here and in the app 30 days ahead, with a one-tap decline. Outside the United States, it serves you only after your Allow tap.
• Argentina: any new recipient waits for your Allow tap.
• Training: a recipient gets your data only if it was named when you signed or after your Allow tap on a card naming it, and every run is announced 14 days ahead with a one-tap "Not this one".
• Earlier versions of this list are at mirai.inc/legal/versions.

Questions: legal@mirai.inc.