Legal

Data Processing Agreement

Effective 19 November 2026

Template noticeThis document is a template prepared for FanMiind and must be reviewed by a qualified lawyer before launch.

Parties and purpose

This Data Processing Agreement (the "DPA") forms part of the agreement between FanMiind ("FanMiind"), operated from the Gold Coast, Queensland, Australia, and the customer that uses the FanMiind platform (the "Customer"). That agreement consists of our Terms of Use, our App Terms and any order form (together, the "Agreement"). FanMiind and the Customer are each a "Party".

The Customer is a creator, agency or business that uses FanMiind to manage creator accounts and talk with fans on platforms such as OnlyFans, Fanvue and Fansly. To provide the services, FanMiind processes personal data about the Customer's fans and other people on the Customer's behalf. This DPA sets out the terms of that processing.

This DPA applies automatically when the Customer accepts the Agreement. If this DPA conflicts with the Agreement, this DPA applies to the processing of Customer Personal Data. If this DPA conflicts with the Standard Contractual Clauses, the Standard Contractual Clauses apply.

1. Definitions

Words not defined in this DPA have the meaning given in the Agreement. In this DPA:

  • "Data Protection Laws" means all privacy and data protection laws that apply to the processing of Customer Personal Data under the Agreement. These include, where they apply, the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles, the EU General Data Protection Regulation 2016/679 (the "EU GDPR"), the EU GDPR as it forms part of UK law (the "UK GDPR"), the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended by the California Privacy Rights Act (the "CCPA").
  • "Customer Personal Data" means personal data that FanMiind processes on behalf of the Customer in providing the Services, as described in Annex 1.
  • "Services" means the FanMiind platform, apps and AI chatter (Mia), and related support, as described in the Agreement.
  • "Controller", "Processor", "Data Subject", "Personal Data", "Processing", "Personal Data Breach" and "Supervisory Authority" have the meanings given in the GDPR, and include equivalent terms under other Data Protection Laws (such as "business" and "service provider" under the CCPA).
  • "Sub-processor" means any third party that FanMiind engages to process Customer Personal Data.
  • "Standard Contractual Clauses" or "SCCs" means the standard contractual clauses approved by the European Commission in Implementing Decision (EU) 2021/914, as amended or replaced.
  • "UK Addendum" means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner.
  • "Connected Platform" means a third party platform or messaging channel that the Customer connects to the Services, such as OnlyFans, Fanvue, Fansly, Telegram, Instagram, TikTok or X.

2. Roles and scope

  1. For Customer Personal Data, the Customer is the Controller and FanMiind is the Processor. Where the Customer is itself a processor for a creator, FanMiind is the Customer's Sub-processor, and the Customer confirms that the creator has authorized this.
  2. Under the CCPA, the Customer is a "business" and FanMiind is a "service provider". FanMiind will not sell or share Customer Personal Data, will not keep, use or disclose it for any purpose other than providing the Services or as the CCPA otherwise permits, will not use it outside the direct business relationship with the Customer, and will not combine it with personal data it receives from other sources except as the CCPA permits. FanMiind will tell the Customer if it can no longer meet its duties under the CCPA.
  3. FanMiind is a Controller of the account, billing and usage data of the Customer's own Users, as described in our Privacy Policy. This DPA does not apply to that data.
  4. The subject matter, duration, nature and purpose of the processing, and the types of personal data and categories of Data Subjects, are set out in Annex 1.

3. Processing on instructions

  1. FanMiind will process Customer Personal Data only on the Customer's documented instructions, unless the law requires otherwise. In that case, FanMiind will tell the Customer of the legal requirement before processing, unless the law forbids this.
  2. The Customer's complete instructions are this DPA, the Agreement, and the Customer's configuration and use of the Services. This includes the rules, guardrails, prices and settings the Customer writes for Mia, the content it places in the vault, and the actions its team members take. Any further instruction must be in writing and agreed by both Parties.
  3. FanMiind will tell the Customer at once if, in its opinion, an instruction breaks a Data Protection Law. FanMiind may then suspend the processing concerned until the Customer confirms or changes the instruction.
  4. FanMiind may create aggregated and de-identified data from the use of the Services, to operate, secure and improve the Services, provided that this data cannot identify the Customer, any creator or any Data Subject, and that FanMiind does not try to re-identify it.

4. Customer obligations

The Customer confirms and agrees that:

  1. it has a lawful basis under Data Protection Laws for the processing of Customer Personal Data, including any processing of message content that may reveal special categories of data, and that it has given each Data Subject every notice the law requires, including any notice about the use of AI to reply to messages where the law or the Connected Platform requires one;
  2. its instructions comply with Data Protection Laws and with the terms of each Connected Platform;
  3. it has the right to connect each creator account to the Services, and to give FanMiind access to the data in it;
  4. it will use the Services only for adult creators and adult fans, and it will not knowingly provide personal data of any person under 18; and
  5. it is responsible for the accuracy and quality of Customer Personal Data, and for the access it grants to its own team members.

5. FanMiind personnel

  1. FanMiind will make sure that every person it authorizes to process Customer Personal Data is bound by a duty of confidentiality, whether by contract or by law.
  2. FanMiind will limit access to Customer Personal Data to the personnel who need it to provide, support or secure the Services, and will train them on their data protection duties.
  3. FanMiind staff will access the content of Customer messages only where needed to give support the Customer has asked for, to investigate a security incident or abuse, to stop any processing that involves a minor, or to comply with the law.

6. Sub-processors

  1. The Customer gives FanMiind general authorization to engage Sub-processors. The Sub-processors in use on the effective date are listed by category in Annex 3, and the Customer approves them.
  2. FanMiind will give the Customer at least 14 days' notice before it adds or replaces a Sub-processor, by email or by a notice in the Services. The Customer may object on reasonable data protection grounds within that period. If it does, the Parties will discuss the objection in good faith. If they cannot resolve it, the Customer may end the affected Services, and FanMiind will refund any fees paid in advance for the period after the end date.
  3. FanMiind will enter into a written contract with each Sub-processor that imposes data protection duties no less protective than those in this DPA, to the extent they apply to the service the Sub-processor provides.
  4. FanMiind remains responsible to the Customer for the performance of each Sub-processor's duties.

7. Data subject rights

  1. The Services include features the Customer can use to access, correct, export and delete Customer Personal Data, such as fan profiles, notes and conversation history.
  2. Taking into account the nature of the processing, FanMiind will help the Customer, by appropriate technical and organizational measures and as far as possible, to respond to requests from Data Subjects who exercise their rights under Data Protection Laws.
  3. If FanMiind receives a request directly from a Data Subject about Customer Personal Data, it will pass the request to the Customer without undue delay and will not respond itself, other than to direct the Data Subject to the Customer, unless the Customer authorizes it or the law requires it.
  4. FanMiind will also give the Customer reasonable help with data protection impact assessments and prior consultations with Supervisory Authorities, to the extent they relate to the Services and the Customer does not otherwise have the information.

8. Security and data breaches

  1. FanMiind will implement and maintain appropriate technical and organizational measures to protect Customer Personal Data, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks to Data Subjects. These measures include those described in Annex 2. FanMiind may update them, provided that the overall level of protection does not fall.
  2. The Customer is responsible for the security settings it controls, including the team members it invites, the roles and permissions it grants, the protection of its own login details and devices, and its use of the pause controls for Mia.
  3. If FanMiind becomes aware of a Personal Data Breach that affects Customer Personal Data, it will notify the Customer without undue delay, and in any event within 48 hours. The notice will describe, as far as then known, the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed. FanMiind will update the Customer as more information becomes available.
  4. FanMiind will take reasonable steps to contain and investigate the breach and to reduce its effects, and will give the Customer reasonable help to meet its own notification duties, including under the Australian Notifiable Data Breaches scheme and Articles 33 and 34 of the GDPR.
  5. A notice of a breach is not an admission of fault or liability by FanMiind.

9. International transfers

  1. The Customer agrees that FanMiind and its Sub-processors may process Customer Personal Data outside the country where it was collected, including in Australia, the United States, the European Union, the United Kingdom, Singapore and other countries where Sub-processors operate, subject to this section.
  2. Where Customer Personal Data subject to the EU GDPR is transferred to a country that has not received an adequacy decision, the SCCs apply and are incorporated by reference. Module Two (controller to processor) applies where the Customer is a controller, and Module Three (processor to processor) applies where the Customer is a processor. For the SCCs: the optional docking clause in Clause 7 applies; Clause 9(a) option 2 applies, with the notice period in section 6 of this DPA; the optional wording in Clause 11 does not apply; Clauses 17 and 18 are governed by the law of, and disputes heard in the courts of, Ireland; and Annexes I and II of the SCCs are completed with the information in Annexes 1 and 2 of this DPA.
  3. Where Customer Personal Data subject to the UK GDPR is transferred, the UK Addendum applies, completed with the information in this DPA. Where data subject to Swiss law is transferred, the SCCs apply with the changes the Swiss Federal Data Protection and Information Commissioner requires.
  4. Where Customer Personal Data subject to the Australian Privacy Act is disclosed to a recipient outside Australia, FanMiind will take reasonable steps to make sure the recipient does not breach the Australian Privacy Principles in relation to it, as required by APP 8.
  5. FanMiind will make sure that each Sub-processor that receives Customer Personal Data in a third country is bound by an appropriate transfer mechanism.

10. AI processing

  1. The Services use AI models to draft and send replies, suggest prices, tag vault content, translate messages and write fan notes. To do this, FanMiind sends the relevant parts of Customer Personal Data and the Customer's rules to AI model providers listed in Annex 3, only as needed to produce each output.
  2. FanMiind will engage AI model providers only on terms that do not permit them to use Customer Personal Data to train or improve their general models, and that limit how long they may keep it.
  3. FanMiind will not use Customer Personal Data to train AI models that are made available to other customers.
  4. The Customer can review the output of Mia, see every message Mia sends in the Activity Log, and pause Mia per account, per fan or per chat at any time. The Customer remains the Controller of all such output.

11. Deletion or return of data

  1. During the term of the Agreement, the Customer can export and delete Customer Personal Data through the Services.
  2. When the Agreement ends, or when the Customer disconnects a creator account, FanMiind will delete the related Customer Personal Data within 30 days, unless the Customer asks in writing within that period for a copy in a common machine-readable format, in which case FanMiind will provide it and then delete the data.
  3. Deleted data may remain in encrypted backups for up to 35 more days, until those backups are overwritten in the normal cycle. FanMiind will keep such data protected and will not actively process it.
  4. FanMiind may keep Customer Personal Data where the law requires it, and will then protect it and process it only for the purpose the law requires.
  5. On request, FanMiind will confirm the deletion in writing.

12. Audits and information

  1. FanMiind will make available to the Customer the information reasonably needed to show compliance with this DPA and with Article 28 of the GDPR. This may include summaries of its security policies, its Sub-processor list, and any third party audit reports or certifications it holds.
  2. If that information is not enough to show compliance, or if a Supervisory Authority requires it, the Customer may carry out an audit, or have an independent auditor bound by confidentiality carry one out, no more than once in any 12 months, unless a Personal Data Breach has occurred.
  3. The Customer must give at least 30 days' written notice of an audit and agree its scope, timing and duration with FanMiind in advance. Audits must take place during business hours, must not unreasonably disrupt FanMiind's operations, and must not give access to the data of other customers. The Customer bears its own costs of the audit.
  4. Audits of Sub-processors are carried out through the audit reports and information those Sub-processors make available.

13. Liability

Each Party's liability under or in connection with this DPA is subject to the limits and exclusions in the Agreement, to the extent the Data Protection Laws allow. Nothing in this DPA limits the rights of Data Subjects under the SCCs or Data Protection Laws.

14. General terms

  1. Term. This DPA applies for as long as FanMiind processes Customer Personal Data, and ends when that processing ends.
  2. Changes. FanMiind may update this DPA to reflect changes in Data Protection Laws, Sub-processors or the Services, with notice to the Customer. An update may not lower the overall level of protection for Customer Personal Data.
  3. Severability. If any part of this DPA is found invalid or unenforceable, the rest remains in force, and the invalid part is replaced by a valid term that is as close as possible to the Parties' intent.
  4. Governing law. Except as the SCCs require otherwise, this DPA is governed by the laws of Queensland, Australia, and the courts of Queensland have non-exclusive jurisdiction.
  5. Contact. Questions about this DPA can be sent to privacy@fanmiind.com or legal@fanmiind.com. A countersigned copy of this DPA is available on request.

Annex 1: Processing details

Data exporter (controller)The Customer, as identified in its FanMiind account. Contact: the account owner's email address.
Data importer (processor)FanMiind, Gold Coast, Queensland, Australia. Contact: privacy@fanmiind.com.
Subject matterProviding the FanMiind CRM, AI chatter and related apps for the creator accounts the Customer connects.
Categories of Data SubjectsFans and subscribers of the Customer's creators; other people who message the creator accounts on Connected Platforms; the creators themselves; and the Customer's team members, to the extent their activity on creator accounts is recorded.
Categories of personal dataFan usernames, identifiers and display names; profile details a fan shares on the Connected Platform; subscription status, dates and renewal data; spend, purchase, tip and PPV history; message content, including text, voice notes, images and video sent or received; vault content metadata and records of which content each fan has; notes, tags and summaries written by the Customer, its team or Mia; inferred preferences, interests and buying signals; language and time zone; online status and activity timestamps; tracking link and campaign attribution; creator account data, including earnings and statistics.
Special categoriesThe Customer does not intend to submit special category data. However, message content on adult platforms may reveal information about a person's sex life or sexual orientation. FanMiind protects all message content with the measures in Annex 2 and processes it only to provide the Services.
Frequency of transferContinuous, for as long as a creator account is connected.
Nature of processingCollection through Connected Platform sessions, storage, organization, structuring, analysis, AI generation of replies, prices, notes, tags and translations, transmission of messages and content to fans, display to the Customer's team, retrieval, export and deletion.
Purpose of processingTo provide, secure and support the Services under the Agreement, as instructed by the Customer.
Duration of processingThe term of the Agreement, plus the deletion periods in section 11.
RetentionAs set by the Customer during the term; deletion within 30 days after disconnection or termination, and from backups within a further 35 days.
Sub-processor transfersAs listed in Annex 3, for the purposes and durations described there.
Competent supervisory authorityFor the SCCs, the authority determined under Clause 13 of the SCCs. For Australia, the Office of the Australian Information Commissioner.

Annex 2: Technical and organizational measures

FanMiind maintains the following measures, which it may improve over time.

1. Governance

  • A named person in FanMiind's management is responsible for information security and data protection.
  • Written security policies, reviewed at least once a year and after any significant incident.
  • Risk assessment before new features or providers that affect Customer Personal Data are introduced.

2. Access control

  • Access granted on the principle of least privilege and need to know, and removed promptly when no longer needed.
  • Multi-factor authentication for all FanMiind staff access to production systems and administrative consoles.
  • Role-based permissions in the Services, so each Customer team member sees only the accounts and data the account owner allows.
  • Passwordless team access, so team members never receive the creator's platform password.
  • No storage of OnlyFans passwords. Access to creator accounts uses secure sessions that the Customer controls and can end at any time.

3. Encryption

  • Encryption of all data in transit with TLS 1.2 or higher.
  • Encryption of stored data at rest, including backups, with industry-standard algorithms.
  • Session tokens and secrets stored encrypted and kept separate from general data.

4. Physical security

  • Data is hosted with providers whose data centers use controlled entry, surveillance, environmental controls and redundant power, and that hold recognized security certifications.
  • FanMiind does not keep Customer Personal Data on paper or on unencrypted local devices.

5. Separation

  • Logical separation of each Customer's data, so one Customer cannot access another Customer's data.
  • Separate environments for development, testing and production. Production Customer Personal Data is not used in testing.

6. Logging and monitoring

  • An Activity Log, available to the Customer, that records every action by every team member and by Mia, including each message sent.
  • Logging of administrative access to production systems, with logs protected against tampering.
  • Monitoring and alerting for unusual activity, failed logins and service errors.

7. AI controls

  • Guardrails the Customer writes in plain words, applied to every reply Mia drafts.
  • A check on every reply before it is sent, for leaks of personal data, breaches of the Customer's rules and lines that must not be crossed.
  • An automatic stop on any sign that a fan may be under 18.
  • Pause controls per account, per fan and per chat.
  • Only the minimum data needed for each request is sent to AI model providers.

8. Incident response

  • A documented plan to detect, contain, investigate and recover from security incidents, with defined roles.
  • Notice to Customers in line with section 8 of this DPA.
  • A review after each significant incident, with corrective actions recorded.

9. Availability and resilience

  • Hosting on a distributed network with protection against denial of service attacks.
  • Regular encrypted backups, with restores tested at least twice a year.
  • Capacity monitoring and planning.

10. Secure development and maintenance

  • Code review before changes reach production.
  • Dependency and vulnerability scanning, and timely security patches.
  • Periodic security testing of the Services.

11. Personnel

  • Confidentiality duties for all staff and contractors.
  • Security and privacy training at onboarding and at least once a year.
  • Prompt removal of access when a person leaves or changes role.

12. Supplier management

  • Security and privacy review of Sub-processors before engagement.
  • Written data protection terms with each Sub-processor, in line with section 6.

Annex 3: Sub-processors

FanMiind uses Sub-processors in the following categories. The name, location and transfer mechanism of each current provider are available to Customers on request at privacy@fanmiind.com, and changes are notified under section 6.

CategoryProviderPurposeData processed
Hosting, network and edgeCloudflare, Inc.Hosting of the website and Services, content delivery, security and protection against attacks, edge storage and computeAll categories in Annex 1
Database and file storageCloud database and storage providerStoring account, CRM, message and vault metadata in encrypted formAll categories in Annex 1
AI model providersLarge language model and translation providersGenerating replies, drafts, price suggestions, notes, tags and translationsThe message, fan profile and rule data needed for each request
Email deliveryTransactional email providerSending alerts and service emails to the Customer's teamTeam member names and email addresses; alert content, which may name a fan
Mobile pushApple Push Notification service and Firebase Cloud MessagingDelivering push alerts to the mobile appDevice tokens; alert content, which may name a fan or show a message preview
Error and performance monitoringMonitoring providerDetecting and fixing errors in the ServicesTechnical logs, which may include identifiers
Customer supportSupport desk providerHandling support requests the Customer sendsAny Customer Personal Data the Customer includes in a request

The payment processor handles the Customer's own billing data as an independent controller or as FanMiind's processor. It does not process Customer Personal Data and is therefore not listed here. See our Privacy Policy.

Book a demo

See it run on your accounts.

A 20 minute walkthrough with someone who has run chat teams. We reply within one business day.

Our team will not bite.