Back to Home
AmsayaAmsaya

Privacy Policy

Effective Date: December 1, 2026 · Version 2.2

1. WHO WE ARE AND WHAT THIS COVERS

Cain, Inc., a Delaware corporation ("Amsaya", "we", "us"), operates Amsaya.ai (the "Platform"). This policy explains what personal information we collect from creators, Studios, agents and visitors, why, who receives it, how long we keep it, and the choices and rights you have. Part 4 is our public Biometric Data Policy.

Read it together with the Creator Terms of Service, Studio Terms of Service and Agent Terms of Service. Those documents control how a dataset may be used. If this policy and a License Schedule differ about how a Studio may use a dataset, the License Schedule and the Terms control.

2. WHERE WE OPERATE

  • 2.1 The Platform is operated from the United States, and your information is stored and processed in the United States. Our content reviewers work in the United States and Ethiopia (6.3).
  • 2.2 Creator and agent accounts are open only to residents of the 50 states, the District of Columbia, and US territories where Stripe Connect can make payouts. We do not accept creators or agents who are residents of Illinois or Washington. We do not knowingly collect personal information from creators or agents outside those places.
  • 2.3 Studios may be located outside the United States, except in China (including Hong Kong and Macau), Cuba, Iran, North Korea, Russia, Venezuela, or any country or region under comprehensive US sanctions. Information about a Studio's staff is processed in the United States.
  • 2.4 We may change the list of places we serve. If your state or territory is removed, Creator Terms 12.4 explains what happens to your existing licenses.

3. INFORMATION WE COLLECT

CategoryExamplesSource
AccountName, email, public alias, role (creator, Studio or agent), and the profile image and ID from your sign-in provider (Google, Microsoft or Discord)You and your sign-in provider
Business detailsStudio or agency name, website, country, billing address, contact person, and the Studio's eligibility confirmationsYou
Marketplace media (creators)Head and full-body photos, including on chroma-key backgrounds; for Tier 3 and voice-only datasets, voice recordings and the voiceprints we create from them to check that they are from one speaker; the live phrase recording you make when you submit a Tier 3 or voice-only dataset; speech-to-text transcripts of Tier 3 and voice-only recordings; dataset titles, tiers and prices; your declaration of whether the voice in a dataset is your natural voice or a performed voice; the options you accept on each License Schedule. We remove location (GPS) and device metadata from files.You
Optional profile attributes (creators)Age range, gender, height and ethnicity, only if you choose to add them. Ethnicity is shown only with your separate consent.You
Identity verification (creators)Name, date of birth, ID type and country, an image of your government ID, and a selfie and liveness check. Stripe Identity collects and holds these. We keep the verification result and status, and authorized reviewers can view the Stripe record to compare your selfie with your first dataset or resolve a dispute.You, through Stripe Identity
Payout and business verification (creators and agents)Information Stripe Connect requires to verify you and pay you, such as legal name, address, date of birth, taxpayer ID and bank details. Stripe holds these; we keep your Stripe account ID, verification status and payout records.You, through Stripe Connect
Studio paymentsCard and billing details, collected and held by Stripe. We see the payment status, amount and the last four digits of the card.Studios and Stripe
Licensing and referral recordsLicenses, Production declarations, License Certificates, referral codes, signup dates, commissions and payoutsOur systems
Records of agreementEach version of the Terms, the biometric consent and each License Schedule you accept, with time, IP address and browserOur systems
Moderation and safetyReview decisions and notes, automated screening results, reports we receive, and an audit log of moderation actions (the log contains no images)Our systems, reviewers and people who report content
Technical and usageIP address, device and browser type, pages visited and actions taken, server logs and security events, and the cookies in Part 8Your device
CommunicationsMessages you send us and notices we send youYou and our systems

4. BIOMETRIC DATA POLICY

  • 4.1 What counts. "Biometric Data" means data generated by technologically measuring or analyzing a person's physical features (for example, face geometry or a voiceprint) to identify them. The selfie, liveness check and ID-to-selfie match that Stripe Identity performs for us are Biometric Data, and so are the voiceprints we create from Tier 3 and voice-only recordings (4.2). Some laws also treat face images and voice recordings from which such data could be extracted as biometric information, so we handle your dataset photos and voice recordings with the same care.
  • 4.2 What we do, and do not do. Stripe Identity matches your selfie to your ID. A trained reviewer then visually compares your verification selfie with your first submitted dataset that contains photos to confirm that the same person appears in both. Each later dataset with photos is compared the same way, visually, with your first approved dataset. A voice-only dataset has no photo, so for it a reviewer listens to the recordings instead. We do not run automated face matching or create face templates from your datasets. For Tier 3 and voice-only datasets, we run voiceprint analysis: our own speaker-verification software, which we run on Google Cloud servers, creates a voiceprint (a mathematical representation of the features of your voice) from each recording in a Tier 3 or voice-only dataset and from the live phrase recording made for that dataset (described below), and compares them with each other, to check that they are all from the same speaker. We do not compare your voice with other datasets or other creators' accounts. The system only flags possible mismatches; a person reviews every flag and decides. Voiceprints are used only for this check, are never given to Studios, and are never used to train any model. Recordings delivered to Studios carry no voiceprint. When you submit a Tier 3 or voice-only dataset you also record, live in your browser, a short phrase we show on screen (the "live phrase recording"). It shows that a real person is recording at that moment, and lets a reviewer hear your voice next to your dataset. Our speaker-verification check compares it with the recordings in that dataset. It is never given to Studios and is not part of your dataset. Our automated screening (Google Cloud Vision SafeSearch and logo detection) checks uploads for explicit content and logos and does not identify anyone.
  • 4.3 Purposes. We use Biometric Data only to verify your identity and age, confirm that you are the person in your datasets, confirm that Tier 3 and voice-only recordings are from one speaker, prevent fraud and impersonation, and meet legal duties. We do not use it for advertising, profiling or any other kind of identification.
  • 4.4 Consent. We collect Biometric Data only after you accept a separate biometric notice and consent screen that tells you what is collected, why, how long it is kept and who receives it. Before your first Tier 3 or voice-only upload, you see and accept a separate voice-biometric consent for voiceprints. Each license of a dataset to a Studio is a separate permission you give by accepting that dataset's License Schedule.
  • 4.5 Who receives it. Stripe (as our identity-verification provider, and under its own privacy policy for its own legal duties), Google Cloud, which hosts the speaker-verification software we run ourselves, and our authorized reviewers. Studios never receive identity-verification data. We do not sell, lease or trade Biometric Data.
  • 4.6 Retention schedule and deletion. We instruct Stripe to permanently delete your verification images and Biometric Data on the earliest of: (a) 45 days after your first dataset review is complete and no fraud or identity dispute is open; (b) 12 months after your last interaction with us; or (c) 45 days after you close your account. We keep only the verification result and status. If a law or a court order requires us to keep data longer, we keep it only for that purpose and delete it when the requirement ends. We delete voiceprints within 45 days after the dataset's review is complete, and keep only the result of the check. We delete the live phrase recording and speech-to-text transcripts when the dataset is approved, rejected, deleted or Withdrawn. We delete an unfinished Tier 3 or voice-only draft, with any photos, 30 days after you start it. Dataset files are kept and deleted as Part 9 describes.
  • 4.7 Security and incidents. We protect Biometric Data with the safeguards in Part 12 and limit access to authorized staff and reviewers under confidentiality duties. We keep a written incident-response plan. If a security incident affects Biometric Data, we will investigate, contain it, and notify affected people and regulators as the law requires.
  • 4.8 Review. We review this Biometric Data Policy and our retention schedule at least once a year.

5. HOW WE USE INFORMATION

  • Operate the marketplace, create and secure your account, and show you its contents.
  • Verify identity, age and residence, and prevent fraud, impersonation, deepfakes and illegal content.
  • Screen uploads with automated tools and have a person review every dataset before approval.
  • Deliver licensed datasets to Studios at your direction, send Production Notices, issue License Certificates, and enforce license terms.
  • Let Studios search listings, including by the optional profile attributes you choose to add.
  • Calculate and pay creator earnings and agent commissions, and issue required tax forms through Stripe.
  • Keep records that prove what you agreed to and when.
  • Understand how the Platform is used so we can fix and improve it, using our own server logs. We do not use third-party analytics or advertising tools.
  • Send service notices, such as review results, payouts and changes to our terms.
  • Develop and improve Amsaya's own AI models and tools, but only from datasets whose creator ticked "Amsaya Model Development" (Creator Terms 5.5).
  • Monitor security, investigate misuse, comply with law and respond to valid legal requests.

We do not use your information for targeted advertising. We do not make decisions about you with legal or similarly significant effects solely by automated means: a person reviews every dataset before approval or rejection.

6. WHO WE SHARE INFORMATION WITH

  • 6.1 Studios, at your direction. When you accept a License Schedule, you instruct us to make that dataset available to Studios on those terms. A licensing Studio receives the dataset files, your public alias, the optional profile attributes you chose to display, and its License Certificate. Studios never receive your legal name, email, address, identity documents, verification data or payout details. Studios are bound by contract to use datasets only as your License Schedule allows, to keep raw files only for the Access Period and then delete them, to protect them, and not to transfer them to countries of concern. We cannot guarantee a Studio's compliance, and a model trained within an AI Training Bundle may retain information about appearance.
  • 6.2 Referring agents. If you signed up through a referral link, that agent sees an anonymous short label for you, your signup date, and the amounts and status of sales and commissions linked to you. They cannot see your name, email, media or identity details.
  • 6.3 Service providers. Companies that help us run the Platform. They may use your information only for that purpose and must protect it: Google Cloud (hosting, storage, image screening, speech-to-text transcription, and hosting the speaker-verification software we run ourselves), Google Workspace (email), Stripe (payments, Stripe Connect payouts and verification, Stripe Identity, and tax forms), your sign-in provider (Google, Microsoft or Discord), and our content reviewers in the United States and Ethiopia. Reviewers see uploads, verification selfies and live phrase recordings only inside our secure tools, under written confidentiality and access-control terms.
  • 6.4 Legal and safety. To comply with law, court orders and valid requests from authorities; to report apparent child sexual abuse material and other legally reportable content, for example to NCMEC and law enforcement; to respond to reports of intimate imagery shared without consent; and to protect the rights, property or safety of Amsaya, our users or the public.
  • 6.5 Business changes. If we are involved in a merger, acquisition, financing or sale of assets, information may transfer to the successor. The successor must honor this policy, existing licenses and License Schedules. We will notify you before your information becomes subject to a materially different policy.
  • 6.6 At your direction. When you ask us to share information, or accept a License Schedule.

7. "SALE" AND YOUR DIRECTION

  • 7.1 We do not sell personal information to data brokers, advertising networks or marketers, and we do not share it for cross-context behavioral advertising. We never sell, lease or trade identity-verification or Biometric Data.
  • 7.2 Studios receive a creator's dataset because the creator directs us to license it, dataset by dataset, on terms the creator accepts. We treat that as a disclosure you direct, not a sale. Because some state laws can treat licensing for value as a "sale", we say so openly: your acceptance of a License Schedule is your consent and instruction for that disclosure. To stop new licensing of a dataset, Withdraw it (Creator Terms 8.1).
  • 7.3 You may ask us for a list of the Studios that received your datasets (Part 10).

8. COOKIES

We use only the cookies the Platform needs to work. We do not use analytics, advertising or other third-party tracking cookies. If we add any in the future, we will update this policy first.

CookiePurposeLasts
Session cookieKeeps you signed in and secures your sessionUp to 30 days
amsaya_intended_roleRemembers whether you chose creator, Studio or agent signupUp to 1 day
amsaya_refRecords the referral link you arrived through so the referral can be credited. First link wins.30 days

Global Privacy Control. We honor GPC and similar browser signals as a request to opt out of any sale or sharing of your personal information, and apply it to the signed-in account. A GPC signal does not cancel a License Schedule you have accepted; to stop new licensing, Withdraw the dataset. We do not respond to "Do Not Track" signals, because there is no common standard for them.

9. HOW LONG WE KEEP INFORMATION

InformationKept until
Identity-verification images and Biometric Data (held by Stripe)Deleted on the earliest of the dates in 4.6. We keep only the result and status.
Voiceprints (Tier 3 and voice-only)Deleted on the dates in 4.6. We keep only the result of the check, and delete that result when the dataset's files are deleted.
Live phrase recording and speech-to-text transcripts (Tier 3 and voice-only)Deleted when the dataset is approved, rejected, deleted or Withdrawn. If a recording session fails or expires before a dataset is submitted, deleted within 48 hours. We keep only the review result.
Verification result and statusWhile your account is open, then 3 years
Rejected files, or files you delete before approvalDeleted when rejected or deleted
Unfinished Tier 3 and voice-only draftsDeleted 30 days after you start the draft if you have not finished the voice steps and submitted it. We remind you 7 days before.
Approved dataset filesAfter you Withdraw the dataset and its last active license ends (or if it never had one), deleted within 90 days. Kept while it is offered to Studios.
Optional profile attributesUntil you remove them or the dataset is deleted
Moderation audit log (no images)7 years
Records of agreement (acceptances, consents, License Schedules, Production declarations)7 years after the license or account ends
Payment, payout and tax recordsAs tax and accounting law requires (Stripe holds tax forms)
Account informationWhile your account is open, and 3 years after it closes
Server and security logs12 months

10. YOUR RIGHTS AND CHOICES

We offer these rights to everyone in the United States, whatever state you live in.

  • Access: ask what information we hold about you, including inferences, and get a copy in a portable format.
  • Correction: ask us to fix inaccurate information.
  • Deletion: ask us to delete your information, subject to the limits below. We will also tell our service providers, and the Studios that received your datasets, about the request.
  • Third parties: ask for a list of the specific Studios and other third parties that received your information.
  • Opt out: of any sale or sharing, of targeted advertising (we do none), and of profiling that has legal or similarly significant effects (we do none).
  • Limit sensitive information: we use sensitive information (identity documents, Biometric Data, financial details and any ethnicity you choose to add) only to provide the service, verify you, prevent fraud and meet legal duties, or to display the attributes you chose.
  • Withdraw consent: withdraw a dataset at any time (Creator Terms 8.1), remove optional attributes, or close your account.
  • No retaliation: we will not treat you differently for using these rights.

How to ask. Use the privacy request form in your account settings or at amsaya.ai/privacy-request, or email info@brotherscain.com. We will verify your identity, usually by confirming control of your account email. You may use an authorized agent with your signed permission; we may ask you to confirm your identity directly. We respond within 45 days, and may extend by another 45 days if we tell you why.

Appeals. If we decline your request, you may appeal by replying within 60 days. We will answer the appeal within 45 days. If we still decline, you may contact your state attorney general.

Limits you should know about. We cannot delete an approved dataset while a license on it is active, because we owe Studios the files they paid for (Creator Terms 8.3). We keep records the law requires, including tax, payment and fraud records, and anything under a legal hold. Withdrawing a dataset or deleting your account does not recall files already delivered to Studios, finished Outputs, or models already trained within a license. Studios must delete raw files when the Access Period ends.

11. STATE-SPECIFIC INFORMATION

  • 11.1 California. In the last 12 months we collected the categories in Part 3. Under the California Consumer Privacy Act those include identifiers; customer records; characteristics of protected classifications (age range, gender and ethnicity, only if you add them); commercial information; biometric information (verification data held by Stripe, and face images and voice recordings in datasets); internet activity; audio and visual information; and professional information. Sensitive personal information we collect: government ID, Biometric Data processed to verify identity, financial account details (held by Stripe), and ethnicity if you add it. We use sensitive personal information only for the purposes California law permits without a right to limit, or to display what you chose. We disclose audio and visual information, face images and voice recordings, your public alias and your chosen attributes to Studios at your direction (Part 7). We have not sold or shared personal information for cross-context behavioral advertising. We keep each category for the periods in Part 9. Sources and purposes are in Parts 3 and 5. Financial incentives: the payment you receive when a Studio licenses your dataset is a commercial license fee for your work, not a payment for your personal information. If California law treats it as a financial incentive, the value of your data is the license fee the Studio pays, and you receive the share described in Creator Terms 10; you may withdraw at any time by Withdrawing your datasets.
  • 11.2 Colorado. Part 4 is our Biometric Data Policy under the Colorado Privacy Act.
  • 11.3 Texas. We capture Biometric Data only after notice and consent, never sell or disclose it except as Part 4 describes, and destroy it within the periods in 4.6.
  • 11.4 Connecticut, Oregon, Minnesota and other states with consumer privacy laws. You have the rights in Part 10, including the right to a list of third parties. To appeal, follow Part 10, then contact your state attorney general if needed.
  • 11.5 Nevada. We do not sell covered information as Nevada law defines it. You may still send an opt-out request to info@brotherscain.com.

12. SECURITY

We use safeguards designed to protect your information, under a written information security program. These include encryption in transit (TLS) and at rest, signed time-limited file links, access controls, logging, and confidentiality agreements for staff and reviewers, hosted on Google Cloud. No system is perfectly secure and we cannot promise absolute security. If a breach affects your information, we will notify you and regulators as the law requires. You are responsible for keeping your sign-in account secure.

13. CHILDREN AND AGE OF MAJORITY

The Platform is only for adults: people who are at least 18 and have reached the age of majority where they live (for example, 19 in Alabama and Nebraska, and 21 in Mississippi and Puerto Rico). We do not knowingly collect information from anyone younger. If we learn we have, we will close the account and delete the information, except that the law may require us to preserve and report certain material. If you believe a minor has used the Platform, contact info@brotherscain.com.

14. CHANGES TO THIS POLICY

We may update this policy. We will post the new version with its date and a summary of changes, and give at least 30 days' notice by email or in-app notification before a material change takes effect, unless the law requires sooner. A change never adds a new permitted use to an existing License Schedule, and we will ask for your consent again where the law requires it, including before using Biometric Data or sensitive information for a new purpose.

15. CONTACT

Cain, Inc., Attn: Privacy, 5874 South Wayland Way, Meridian, Idaho, USA 83642. Email: info@brotherscain.com. Privacy requests: amsaya.ai/privacy-request.