Access only after the scope is agreed
Access to accounts, including OnlyFans, may be needed to carry out agreed tasks. Before work begins, we define the scope of permissions, authorised people and account usage rules. Do not send passwords, authentication codes or document scans through the application form.
If login details are needed for the agreed scope of work, we first agree on a secure way to share and store them, such as an encrypted password manager with access for designated people. We consider the platform's capabilities and terms, two-factor authentication, account recovery, and revoking permissions and changing passwords when the collaboration ends.
Your boundaries must be clear to the team
We describe the permitted scope of content, the publishing approval process and situations requiring an additional decision. This also covers descriptions, promotion, individual offers and audience communication.
Consent to one type of content does not automatically mean consent to every subsequent type. The agreed plan must change if it no longer fits your boundaries. The terms of content use and rights to it must be set out in a separate agreement.
A pseudonym limits disclosure but does not guarantee anonymity
Linked profiles, distinctive features of your surroundings, your voice, tattoos, descriptions or information in files can reveal your identity. Before publishing, it is worth checking more than your face: examine everything around the content and its context.
Once shared, content may be copied or published elsewhere. There is no sound basis for promising to prevent such situations entirely. We can discuss limiting disclosures and how to respond; the availability of specific protection tools depends on the platform.
Payments and exit arrangements are also part of safety
Before signing, check the basis for calculating commission, payment dates, additional costs and access to payment information. Unclear items should be explained in writing. A percentage alone, without stating the amount it is calculated on, does not describe the full cost of collaboration.
The agreement should specify the notice period, final settlement, content handover and removal of access. An exit checklist helps maintain continuity of work and orderly permissions.
How do we handle application data?
We collect the data needed to discuss collaboration. A public profile and additional message are optional. Do not send particularly sensitive data, documents or private photographs.
We store form data in a private, encrypted inbox and send it to the team by email. When notifications are enabled, the full application is also sent by a bot to the configured team chat on Telegram. We periodically delete the encrypted server copy after 90 days; this deletion does not cover copies in email or Telegram. You can contact the controller about your data sooner. Full information about purposes, legal bases for processing and your rights is available in the privacy policy.