Data Processing Agreement
Version 0.4, effective 21 September 2026, made under Terms of Use and Privacy Policy v0.6. Two questions are deliberately left open and are not decided here, expressly or by implication: the role we play for an individual's own project (Privacy Policy, Section 1), and the basis on which we process a depicted person's data for our own safety review and investigations (Privacy Policy, Section 3). The clauses that turn on those answers say so and apply provisionally until they are settled.
This Data Processing Agreement ("DPA") is between Tensordata Global Private Limited, Bengaluru, Karnataka, India ("TakeOK", "we") and the customer identified in the account that accepts it ("you"). It applies only to processing for which we in fact act as your processor, or as sub-processor to you where you are yourself a processor for your client. It forms part of the Terms of Use and prevails over them on the processing of personal data. Capitalised terms not defined here have the meaning given in the Terms of Use. In this DPA, "data fiduciary", "data processor", "data principal", "personal data" and "personal-data breach" are used as defined in the Digital Personal Data Protection Act, 2023, as contractual terms describing the parties' arrangement; each statutory obligation referred to applies only from its commencement and to the extent it applies to the party concerned.
1. Scope and roles
1.1 This DPA covers "Customer Personal Data": personal data contained in Input you supply and in Output generated from it, where you or your client determine the purpose and means of the processing. It does not cover personal data we process for our own purposes as data fiduciary — your account and member information, billing, the security of the Service, abuse investigation, grievance handling and legal compliance — which the Privacy Policy governs.
1.2 Whether content an individual makes for themselves on their own account is Customer Personal Data under this DPA, or is processed by us as data fiduciary, is to be settled by counsel and then stated consistently in the Terms of Use, the Privacy Policy and this DPA before any of them is published. This DPA creates no interim rule for that case.
1.3 Where you are a processor for your client, you warrant that your client has authorised you to appoint us as sub-processor on these terms, that your instructions to us reflect your client's instructions to you, and that you will pass through to your client the information this DPA gives you.
2. Instructions
2.1 We process Customer Personal Data only on your documented instructions. Your instructions are: the Terms of Use, this DPA, the operations you request through the Service or its API, and the settings you choose. Any other instruction must be in writing to privacy@tensordata.com and is subject to our confirming it is technically feasible and lawful.
2.2 We tell you if, in our opinion, an instruction violates a law that applies to us, and we may suspend the instruction until it is resolved.
2.3 We may process Customer Personal Data outside your instructions where a law that applies to us requires it. Where the law allows, we tell you before we do.
2.4 Processing we carry out on Customer Personal Data for our own purposes — safety screening, investigation of suspected violations of the Terms, and grievance handling — is outside your instructions and is described in the Privacy Policy, Sections 1 and 3. The basis on which we process a depicted person's data for those purposes where consent is absent is to be settled by counsel. Nothing in this DPA resolves it; until it is settled, the release you obtain under the Terms, Section 3.4(b), is the consent relied on.
2.5 No reuse. We do not use Customer Personal Data, or any Output, to train, fine-tune, evaluate or benchmark any machine-learning model, and we do not reuse it for any purpose unrelated to your account. Customer-requested inference — the operations you ask for — and the safety screening the Privacy Policy describes remain permitted. Our models run on our own platform: no training, fine-tuning, evaluation or dataset-export pipeline exists on it, and there is no setting by which one could be turned on. We impose the same prohibition on every sub-processor that processes Customer Personal Data.
3. Your obligations
3.1 You are responsible for the lawfulness of the Customer Personal Data you supply and of your instructions, including: holding a lawful basis for each processing purpose; giving data principals the notice the law requires; obtaining the consents the Terms require, in particular the release from every living person whose face, voice or likeness is used; and not supplying the personal data of a person under 18.
3.2 You keep a record of the consents and releases you hold and produce them to us within 48 hours of a request, so that we can answer a data principal or an authority.
3.3 You are responsible for the security of your own account and credentials, and for what members of your workspaces, teams and projects do.
4. Sub-processors
4.1 The sub-processors that process Customer Personal Data on our behalf are those the provider register at https://takeok.tensordata.com/legal/privacy marks as sub-processors, with the function each performs; the register also lists providers that receive personal data for their own purposes, such as the payment gateway, which are not sub-processors under this DPA. You authorise the listed sub-processors for the functions stated. Our generation, speech and vision models run on our own platform, operated by us, and are not sub-processors. Each sub-processor is bound by its published service terms today; written terms carrying the obligations of Sections 2.5, 5, 6 and 8 are being put in place with each. Any affiliate of ours that processes Customer Personal Data is listed and bound the same way.
4.2 We give you at least 15 days' notice by email or in the Service before adding or replacing a sub-processor that will process Customer Personal Data. You may object in writing within that period on reasonable data-protection grounds. While an objection is unresolved the proposed sub-processor receives no Customer Personal Data of yours. If we cannot resolve the objection within 30 days, you may give notice to close the affected workspace; the closure takes effect 30 days after your notice, the export tools remain available until then, the ordinary deletion periods in Section 8.3 run from the day it takes effect, and we refund unused paid credits.
4.3 We remain responsible to you for our sub-processors' performance of this DPA.
5. Security
5.1 We maintain the technical and organisational measures described in the Privacy Policy, Section 6, and in Annex 2, and update them as risks and practices change without lowering the overall level of protection.
5.2 We restrict access to Customer Personal Data to personnel who need it to perform this DPA, bind them to confidentiality, and log access.
5.3 Content is private to your account and the workspaces, teams and projects you place it in, and to the people the Privacy Policy, Section 4.3, names.
6. Personal-data breaches and security incidents
6.1 Alert. We alert you without undue delay after becoming aware of a personal-data breach or security incident affecting Customer Personal Data, and in any case within 2 hours of awareness — a service commitment of ours, not a statutory processor deadline — with what we then know, an incident contact who can be reached around the clock, and the steps you should take to preserve evidence on your side. We do not wait for the investigation to finish. We supplement the alert with rolling updates as facts emerge, and within 24 hours give what is then known of the breach's nature, the data and data principals concerned, the likely consequences and the measures taken or proposed — early enough for a fiduciary's own 72-hour submission to be prepared — and we assist with any earlier deadline that applies to you.
6.2 Who reports. The statutory notifications of affected data principals and, once operative, of the Data Protection Board under the Digital Personal Data Protection Rules — without delay, with further information to the Board within 72 hours — are made by the data fiduciary for the Customer Personal Data concerned: you, where you are the fiduciary; your client, where you are its processor and we are your sub-processor, in which case you pass our alert and every update to your client without delay and route its questions to us. We assist the fiduciary with the facts and, where it authorises us in writing, make a notification on its behalf. Our own duties are unaffected: we report cyber-security incidents to CERT-In within the time its directions require, currently six hours of noticing or being notified, and we report as data fiduciary for the data we hold in that capacity.
6.3 Sub-processors are required to notify us of a breach affecting Customer Personal Data quickly enough for us to meet Section 6.1; our own written incident-response policy is being completed, and until it is, the Section 6.1 alert runs from the moment we become aware, by whatever route.
7. Assistance with data principals' rights and with authorities
7.1 Requests and complaints that reach us. Where a data principal contacts us about Customer Personal Data with a routine request — access, correction, erasure, withdrawal of consent — we tell you within 2 business days and forward the details to you securely, unless the law requires us to act ourselves. Where a complaint reaching us is urgent — content that shows a person in an intimate manner, impersonates them, or otherwise falls within the time-bound categories of the Information Technology Rules, or a security matter — we act on our own obligations within the periods the Terms of Use, Section 5, state, and tell you at once through the incident contact; referral to you never delays our action.
7.2 We assist you, by the tools in the Service and on request, in answering requests for access, correction, erasure and withdrawal of consent, and in the exercise of a nominee's rights, within the time the law gives you. Assistance beyond what the Service provides is charged at the rate we quote in advance, with an estimate given in advance and agreed before the work starts, except that assistance made necessary by our own breach of this DPA or of the Terms is free; a dispute about a fee never delays assistance that a legal deadline requires.
7.3 We assist you with any assessment, audit or inquiry an authority requires of you concerning Customer Personal Data, to the extent it relates to our processing.
7.4 If an authority or court demands Customer Personal Data from us, we tell you before disclosing unless the law forbids it, disclose only what the demand requires, and record what was disclosed.
8. Retention, export and deletion
8.1 We keep Customer Personal Data for the periods the Privacy Policy, Section 5, states, and no longer, subject to the restricted legal retention that Section describes.
8.2 Export. You may export your content at any time while your account is open; an export request on its own triggers no deletion. Before an ordinary closure — one you plan, or one we give notice of under the Terms, Section 12.2 — the export tools remain available until the closure takes effect.
8.3 Deletion on closure. From the day of closure, Customer Personal Data is removed from active use and deleted within the periods the Privacy Policy states, with no export window added after that day.
8.4 Erasure and withdrawal. A request for erasure, a withdrawal of consent, or a withdrawal of a person's likeness or voice under the Terms, Section 3.6, is acted on at once: the data leaves active use immediately and is deleted within the shorter periods the Privacy Policy states for it, with no export delay.
8.5 Restricted copies. Where the law requires us to keep a record for longer, the categories and their expiry are those the Privacy Policy, Section 5, lists; such copies are restricted, used for no other purpose, and erased when the period ends.
8.6 Confirmation. On request we confirm deletion in writing, stating any copy that remains in a backup or under restricted legal retention and when it expires. Sub-processors delete within the periods the register states, and we confirm that too.
9. Audit
9.1 Once in any twelve-month period, and additionally after a personal-data breach affecting your Customer Personal Data or where a binding regulatory deadline of yours requires it, you may verify our compliance with this DPA by: reviewing the documentation we make available (no independent certification or third-party assessment is held today; the register will say when one is); putting written questions we answer within 15 business days, or sooner where a legal deadline requires; and, where those are insufficient to meet a legal requirement, an audit by an independent auditor bound by confidentiality, on 30 days' notice — or such shorter notice as an incident or a regulatory deadline requires — during business hours, without access to other customers' data, at your cost unless it reveals a material breach. Where a sub-processor's premises cannot be visited, we obtain and provide its audit reports or equivalent evidence, subject to its confidentiality and security restrictions.
10. Cross-border processing
10.1 Sub-processors may process Customer Personal Data outside India, as the register states. Today one path does: we back up our platform's control-plane database — job records including prompt text and any voice-clone transcript, never media files, voice samples or outputs — to a storage vendor in the Netherlands, encrypted with AES-256 before it leaves India with the key held in India, and kept 30 days. All inference and all media storage take place in Bengaluru, India. We are moving that backup to a disaster-recovery site of our own in India; when the move is complete this section and the register will say that all data stays in India. Today, under Rule 7 of the 2011 Rules, sensitive personal data leaves India only with the data principal's consent or where the transfer is necessary to perform the contract with them, and only to a recipient bound to the same level of protection; you are responsible for the consent, and we for the recipient's contractual commitment. From commencement of the Digital Personal Data Protection Act, 2023, transfers are also subject to any restriction the Central Government notifies, and we will tell you of any that affects the Service.
11. Liability and term
11.1 Liability under this DPA is subject to the Terms of Use, Section 11, including the separate cap for confidentiality and data-security claims.
11.2 This DPA applies from acceptance until we have deleted all Customer Personal Data under Section 8. Sections 7.4, 8 and 9 survive as long as any copy exists.
11.3 If a term of this DPA conflicts with the Terms of Use on the processing of personal data, this DPA prevails.
Annex 1 — Processing details
| Item | Detail |
|---|---|
| Subject matter | Generation and editing of synthetic video, image, audio and text from customer-supplied inputs |
| Nature | Hosting, storage, transmission to sub-processors, analysis, transformation by machine-learning models, display, deletion |
| Purpose | The operations the customer requests through the Service |
| Categories of data principals | People depicted in customer-supplied images, video and audio; speakers whose voices are cloned; people named in scripts; the customer's clients |
| Customer Personal Data — supplied | Facial images and video; voice recordings; names and other identifiers in scripts, briefs and prompts; product and brand material containing personal data |
| Customer Personal Data — derived by the Service | Generated media depicting the above; cloned-voice clips and any voice profile or embedding a speech model derives; extracted frames, thumbnails and contact sheets; transcripts and word timings; analyses and descriptions produced from uploads; render parameters that reference the above |
| Not Customer Personal Data (our own purposes, Privacy Policy) | The customer's members' account, membership, billing, usage and security data; grievance and investigation records |
| Sensitive data | Facial images, voice recordings and voice profiles, treated as sensitive whether or not the law classifies them so |
| Duration | Life of the account and the periods in Privacy Policy, Section 5 |
| Sub-processors | Those the provider register at https://takeok.tensordata.com/legal/privacy marks as such |
Annex 2 — Security measures
Implemented controls, stated as they stand on 21 September 2026 from our own systems and platform:
| Control | Measure |
|---|---|
| Access management | Named accounts, role-based access, least privilege, review on leaving; production access logged and reviewed |
| Tenant isolation | Content scoped to account and shared space at the application layer; every media route checks ownership; no cross-account listing |
| Encryption in transit | TLS on every connection you reach; traffic inside our private cluster network is not separately encrypted |
| Encryption at rest and keys | Secrets and credentials encrypted with keys held by us; our offsite database backups encrypted before leaving India; media, prompts and database records are NOT encrypted at rest on our platform storage today, and this row will be updated when they are |
| Deletion | One purge routine erases media, posters and derived files at the end of whichever period applies under Privacy Policy Section 5 — the Trash period for ordinary deletion, the shorter periods for voice data, at once from active use on erasure or withdrawal — and a restricted copy is kept only for an identified legal purpose and period and erased when it ends; the platform deletes media inputs 30 days after upload and outputs 90 days after completion; the console's deletion does not yet reach those copies sooner, and job records including prompt text are kept until the purge being built is in place |
| Backup and recovery | Backups expiring within 90 days; restore tested quarterly; data restored after its deletion is deleted again within 7 days |
| Logging | Security and access logs kept within India, with retention being lengthened to the 180 days the CERT-In directions require; one year for the records the Digital Personal Data Protection Rules cover once they commence |
| Incident handling | The alert in Section 6.1, CERT-In reporting within six hours, post-incident review; our written incident-response policy is being completed |
| Safety screening | Automated screening of prompts and uploads before an operation starts; outputs may be reviewed; human review of flagged content |
| Sub-processors | Due diligence before engagement, written terms carrying this DPA's obligations, the register kept current |
| Personnel | Confidentiality obligations and periodic training |