How to write a privacy policy for your companion business
A companion business handles information that can expose a person’s relationships, movements and sexual activity. Its privacy policy should explain what is collected from clients and workers, why it is needed, who can access it and when it is removed. The language should remain clear to someone reading on a mobile phone before deciding whether to register.
A model such as CallBoyOne Club that combines registration details, eligibility information and booking guidance needs disclosures that follow the actual journey from sign-up to service delivery. In Australia, the business must comply with applicable federal, state and territory rules, including the Australian Privacy Principles where the Privacy Act 1988 applies. Sydney and Melbourne also operate under different council service rules, so local requirements can affect in-person services.
Define the service and its boundaries
State whether the business covers virtual chat, video calls, companionship, in-person bookings or a combination. Limit registration to adults aged 18 and over, and do not onboard minors. Where services operate across Australia, describe availability without suggesting that every worker or location may legally provide the same offering.
Check licensing, advertising, insurance and screening requirements in each council area where workers operate. Explain whether clients, workers or both must create an account, and whether a professional alias affects bookings. Allow for a mixed market of independent escorts and agency workers by explaining how each arrangement is handled. Use Australian English and familiar labels such as “mobile number”, “suburb” and “account”, then name the legal entity, an Australian contact point and the relevant complaint pathway.
Identify information and collection purposes
List the identity and contact details needed for registration, age and work-eligibility checks, bookings, payments, support and optional marketing preferences. Keep these purposes separate. A Brisbane client requesting a home visit may provide a precise address, but the form should explain whether that address is visible to the assigned companion, coordinators or other workers.
Distinguish public profiles from private records. A worker may use a professional name while verification documents remain confidential. For every data category, state its purpose, source, legal basis and retention period. Collect sensitive health, criminal-check or biographical details only when necessary, and explain any limited retention required for tax, payment, regulatory or safety reasons.
Control access, retention and security
Limit access to staff performing defined tasks such as onboarding, coordination, support, payment or compliance. Use unique accounts, multi-factor authentication and approved password management. Separate identity documents from ordinary chat records, and encrypt sensitive information in transit. Say who can access verification files and what a support worker does not need to see.
Set deletion rules for inactive profiles, expired bookings, recordings and support tickets, and explain how backups are handled. Workers should know whether chats are routinely monitored, while clients should know when a conversation may be reviewed for safety or a substantiated legal complaint. Test shared devices and personal phones; a coordinator’s private spreadsheet can undo otherwise strong server controls. Contractors should also be expected to return or delete client information after an engagement unless a documented legal duty applies.
Give people meaningful control
Provide a way to view and correct details, withdraw marketing consent and request deletion. You may need to verify the requester, and you can explain any lawful reason for retaining a limited record. Let workers choose whether their real name appears publicly and how much professional information is displayed, without burying those choices in an administrative process.
Explain the information required for optional add-ons, such as customised gift services, and keep their booking data separate from unrelated marketing records. In Adelaide, a booking may use a neutral pickup point rather than a home address, but the policy should still cover any location shared directly. Make contact preferences and cancellation settings easy to find.
Explain communication and marketing
Say which channels carry confirmations, reminders, support and promotions. Separate transactional messages from advertising, keep consent records and provide a functional unsubscribe. Apply the Spam Act 2008 by identifying commercial messages, obtaining appropriate consent and honouring objections. Promotional calls should also be checked against the Do Not Call Register.
Record whether staff reply from personal accounts, and explain the retention of call notes, voice messages and photographs. Obtain specific consent before sending intimate material and explain how that permission can be withdrawn. Do not treat a booking as consent for unrelated publicity or profile content. Avoid passing email addresses, booking identifiers or other personal details through referral URLs and advertising pixels.
Audit connected services and keep the policy current
Your disclosures should cover services that receive visitors from your platform. If a footer points to adult entertainment sites, people should reach a destination with its own privacy notice, not a link that quietly carries a customer identifier. Use clean referral links and check the destination’s practices before relying on that relationship.
Review payment processors, booking tools, identity-check providers, analytics scripts, support platforms and cloud storage, recording what each receives and why. Update the policy when a tool or process changes, publish the revision date and follow applicable breach-notification duties. The practical takeaway is to reconcile the document with the booking system, inbox and payment records before publication, then repeat that check whenever a new app, worker or service is added.