Ce document n'est disponible qu'en anglais.
Data processing agreement
Last updated: October 8, 2026.
This Data Processing Agreement (the "Agreement") forms part of the terms of service between Invisos LLC ("Invisos" or the "Processor") and the customer agency (the "Agency" or the "Controller"). It meets Article 28 of Regulation (EU) 2016/679 (GDPR). It applies from the moment the Agency starts using the service. If this Agreement conflicts with the terms on data protection matters, this Agreement prevails.
1. Parties and roles
- Controller: the Agency, which acts as controller of the data of its creators, fans and team that it enters or manages in Invisos or, where it processes that data on behalf of a creator, as her processor, depending on the actual relationship. In the latter case, the Agency warrants that it has the creator's authorization to engage Invisos as a sub-processor, and references in this Agreement to the "Controller" mean the Agency in that capacity.
- Processor: Invisos LLC, a New Mexico (USA) limited liability company, registration number 0008131742, located at 2105 Vista Oeste St NW, Suite E-1266, Albuquerque, NM 87120, United States. Contact: invisos@proton.me. Where the Agency acts as a creator's processor, Invisos acts as sub-processor.
Invisos is a controller, not a processor, for the Agency's account data, billing, website, contact and security logs, and for processing for its own purposes: the security of the service, handling reports and mandatory reports to authorities or organizations such as NCMEC, and the defence of legal claims. That processing is described separately in the privacy policy.
This Agreement does not make Invisos an agency or a manager of the creators. Each party is responsible for meeting the obligations that this Agreement and the law assign to it.
2. Subject matter
The Processor processes personal data on behalf of the Controller only to provide the Invisos service described in the terms: a CRM for agencies that manage content creators (fans, lists, content vault, mass messages, scheduling, analytics, team and finance) and AI chatting, in which an AI drafts and sends replies to fans from the creator's account, in the style and within the rules, schedules and escalations the Agency defines.
3. Duration
The Agreement lasts for as long as the Agency uses the service and afterwards until deletion or return of the data is complete under clause 10.
4. Nature and purposes of the processing
The processing consists of receiving, storing, organising, consulting, analysing, transmitting and deleting data for these purposes, always in the service of the Agency:
- Hosting the Agency's data and content.
- CRM: managing fans, lists, notes, the content vault, mass messages and scheduling.
- AI-assisted drafting and sending of messages to fans, with the Agency's team able to step into any chat.
- Analytics and finance for the Agency about its own activity.
- Connection with the platforms the Agency links, through an external connection provider, and publishing or scheduling on social networks.
- Connection of third-party AI assistants through MCP, with the permissions the Agency grants.
- Security, backups, technical support and prevention of misuse of the service.
MCP clients. By connecting an MCP client, the Agency authorises the disclosure of the data covered by the permissions granted to the provider it selects. Before connecting it, the Agency must check that provider's terms, role, retention and international safeguards. The retention commitments of our inference providers do not automatically extend to the MCP client. The Agency may revoke access at any time.
5. Data subjects and categories of data
Data subjects: creators managed by the Agency, fans of those creators, and the Agency's staff and collaborators.
Categories of data:
- Identifiers: usernames, aliases, platform account identifiers, and email and contact details of the team.
- Messages and conversations between fans and creators.
- Purchases and transactions: tips, subscriptions, sales and their attribution.
- Content: images, videos, audio and text in the content vault.
- Notes, context and preferences about fans and creators, and derived data such as summaries.
- Team activity data in the dashboard.
Special categories. Conversations and notes may reveal special categories of data under Article 9 GDPR, such as sex life or sexual orientation. The Controller alone is responsible for having a valid Article 6 legal basis and an Article 9 condition, and for minimising the data. Invisos does not ask for this data and does not use it for any other purpose.
6. Processor obligations
The Processor undertakes to:
- Documented instructions. Process the data only on the Controller's documented instructions, which are this Agreement, the terms and the configuration the Agency sets in the service. If it believes an instruction infringes the rules, it will tell the Controller without delay.
- Confidentiality. Ensure that persons authorised to process the data are bound by a duty of confidentiality and have access only to the extent necessary.
- Security measures. Apply technical and organisational measures appropriate to the risk (Article 32 GDPR), including:
- isolation between agencies through row-level security in the database;
- encryption in transit (TLS) and encryption of platform credentials and sessions;
- passwords stored hashed;
- administrative access restricted by VPN;
- technical logs designed not to include the text of chats;
- roles and permissions per creator;
- backups on Hetzner storage and an independent second copy;
- comparison of images and videos against databases of known child sexual abuse material, using hash matching and detection models, with quarantine and restricted-access human review;
- deletion procedures designed to also cover derivatives (summaries, vectors and caches).
- Memory separation. Invisos's AI does not share a fan's memory or history across creators or agencies, and does not use other customers' conversations as examples.
- Assistance. Assist the Controller, taking into account the nature of the processing, in responding to data subjects' requests to exercise their rights, and in meeting obligations on security, breach notification, data protection impact assessments (DPIAs) and prior consultation with the supervisory authority. If a data subject contacts the Processor, it will refer them to the Controller and will not respond on its own unless instructed.
- Personal data breaches. Notify the Controller without undue delay and in any event within 48 hours of becoming aware of any breach of security affecting the Controller's data, with the information available (nature, data and people affected, likely consequences and measures taken or proposed). Notifying the supervisory authority and data subjects is the Controller's responsibility.
- Deletion or return. Comply with clause 10.
- Information and audits. Make available to the Controller the information necessary to demonstrate compliance with this Agreement. Invisos will allow for and contribute to the necessary audits, including inspections, conducted by the Agency or an auditor it appoints. Documentation (description of measures, policies, answers to questionnaires and, where available, third-party reports) will be used first where it is sufficient. Audits will not give access to other customers' data. Confidentiality, notice and organisational conditions will not prevent urgent audits following incidents or requests from an authority. Costs will be reasonable and not dissuasive; Invisos will bear those arising from its own proven breaches.
7. Sub-processors
The Controller gives general authorisation to use the following sub-processors:
- Hetzner Online GmbH (Germany; data centre in Helsinki, Finland, EU): hosting, database and backups.
- Cloudflare, Inc. (United States): network, DNS, security and secondary backup.
- OpenRouter, Inc. (United States): AI model gateway, and the model providers it routes to (for example xAI and other inference providers).
- External OnlyFans connection provider (API): connection with the accounts the Agency links.
- Stripe, Inc. / Stripe Payments Europe, Ltd.: card payments (no access to fan or chat data).
- Proton AG (Switzerland): email.
Invisos will impose on each sub-processor data protection obligations equivalent to those in this Agreement, and remains liable to the Controller for the sub-processor's performance of them.
Changes. Invisos will notify the Agency by email or in the dashboard at least 15 days in advance of any addition or replacement of sub-processors. The Agency may object on reasonable data protection grounds during that period by writing to invisos@proton.me. The parties will seek a solution in good faith; if there is none, the Agency may terminate the affected service without penalty, with a refund of the unused balance and the pro-rata share of fees for the service not provided, as set out in the terms.
8. Artificial intelligence
To draft messages, AI models receive the necessary context of the conversation. Inference routing requires endpoints with no data retention and no training. Invisos does not use the Controller's data to train its own or third-party models. These commitments do not extend to the MCP clients the Agency connects (clause 4).
The AI can make mistakes. The Controller configures the AI, its rules and its supervision, and is responsible for messages sent from its accounts, as set out in the terms.
9. International transfers
Invisos is based in the United States and some sub-processors are too. Data is hosted in the European Union (Helsinki) but may be accessible from, or processed in, countries outside the European Economic Area. Where a transfer requires it, the parties apply the European Commission's standard contractual clauses (Decision (EU) 2021/914) or another valid safeguard under Chapter V GDPR, such as an adequacy decision. For those clauses, the Agency acts as exporter (controller) and Invisos as importer (processor) under the relevant module, and they are incorporated by reference into this Agreement, with the information required in their annexes taken from this Agreement. Invisos requires equivalent safeguards from its sub-processors.
10. Deletion or return on termination
When the service ends, the timeline in the terms applies. During a transition period of up to 30 calendar days, Invisos will give reasonable assistance with exporting the data or switching provider and will maintain continuity and security. Once the transition ends, the Agency will have at least 30 more calendar days to retrieve the data, which Invisos will return in a commonly used format on request. After that, Invisos will delete the Controller's personal data and existing copies, unless the Agency gives a valid instruction otherwise or the law requires them to be kept. Backups are overwritten in a cycle of up to 30 days, and deletion procedures cover derivatives (summaries, vectors and caches). Invisos may keep data it must keep by law (for example billing data) in its capacity as controller.
Exception for child sexual abuse material. No deletion period in this Agreement applies to material reported to the NCMEC CyberTipline or its context. Invisos will block suspected material without destroying evidence that must be preserved, report it when it has actual knowledge of facts subject to mandatory reporting, keep it with its context for one year from the report, or for any longer period required by law, with strictly restricted access, and cooperate with the competent authorities, disclosing to them the information the law requires. These actions are Invisos's own processing to comply with the law, do not require the Agency's instructions and are governed by the acceptable use policy.
11. Controller obligations
The Agency undertakes to:
- Have a valid legal basis for each processing activity and, for special categories, an Article 9 GDPR condition, and to minimise the data it enters.
- Hold current written authorisation from each creator, and ensure that everyone appearing in the content is an adult and has consented.
- Inform creators and fans as the law requires (Articles 13 and 14 GDPR), including transparency about the use of AI towards fans and the public where the law requires it, for example Article 50 of Regulation (EU) 2024/1689. Invisos provides the means to do so, but the obligation is the Agency's.
- Give lawful instructions and ensure that its users, chatters and assistants connected through MCP act within them.
- Comply with the terms of the connected platforms and handle data subject requests addressed to it.
- Notify the authority and data subjects of breaches that require it, and carry out any impact assessments that apply.
12. Liability and governing law
The parties' liability under this Agreement is governed by the limitations and indemnities in the terms of service, to the extent the law allows. This does not limit data subjects' rights or liabilities that the law does not allow to be limited, and the third-party exclusions in the terms do not remove Invisos's liability for its sub-processors under clause 7. The law and courts stated in the terms apply (New Mexico; Bernalillo County), without prejudice to the mandatory rules of the GDPR and to the standard contractual clauses, which are governed as they provide.
13. Contact
To exercise rights under this Agreement, or to report breaches or objections, write to invisos@proton.me. See also the privacy policy.