This page explains the privacy architecture and handling principles behind OshiZone’s application and creator workspace.
The simplest rule: OshiZone will never ask you to send an ID through email, text, or direct message.
At signup we collect your OshiZone username, a protected password hash, email, stage name and public OnlyFans, Instagram and X/Twitter handles, plus your adulthood confirmation and policy acceptance records. Identity verification adds your verified legal name, date of birth, issuing country, result and provider reference. Accepted clients also have manager assignments, contract and booking records, communications and, when connected, content and work records.
We use this information to confirm identity and adult eligibility, review applications, enter and administer agreements, provide requested management services, maintain account security, document consent, and meet legal and compliance obligations.
New applicants can continue to identity verification without first confirming email ownership. Your email remains marked unverified until confirmed separately. Postmark delivers requested verification codes and receives the destination address and message. Identity approval does not prove ownership of your email address. Older accounts may retain their existing email-confirmation step.
In the new onboarding flow, you provide your ID and selfie directly to Didit for document, liveness and face-comparison checks. OshiZone stores the necessary identity fields and verification reference, not copies of Didit images, biometric templates or full result payloads. Authorized reviewers inspect evidence in Didit. Legacy identity files remain under their existing restricted storage and retention controls. Never send identity files by email, text or direct message.
New clients arrange OnlyFans and social-account access through Bitwarden with their manager on the onboarding call. Public signup collects handles, not those account passwords. You keep control of your accounts and your Bitwarden master password. Bitwarden account and sharing arrangements are explained before access is granted. Existing clients using the older BookOS encrypted credential flow retain that arrangement until a separate migration is agreed.
Identity records are intended only for authorized verification and compliance workflows. Access decisions, status changes, and important record actions should be attributable through an audit history. A verified badge is private to the creator workspace and does not expose legal identity.
Images and videos submitted to the content library are security-scanned before storage, encrypted outside the public web directory, and available only to you and authorized OshiZone staff. Each upload records whether it is intended for a post or vault, any instructions you provide, and your confirmation that you own it or have documented permission from every identifiable adult.
Necessary identity and relationship records are maintained while we represent you. Ending the relationship triggers a retention review, not an assumption that every record must be stored forever or immediately erased. Rejected and abandoned applications, contracts and Didit evidence need their own retention periods and any applicable legal holds. The final schedule and Didit settings must be confirmed before this onboarding process launches publicly.
If your application does not proceed, joining the future-opportunities email list is optional. We store your email, opt-in time and any withdrawal. You can unsubscribe from your application page. Joining the list is not required for review or access to your records.
You may ask to access, correct, or delete eligible information; withdraw optional consent; or close your account. Some records may need to be retained for fraud prevention, disputes, contracts, or legal obligations. OshiZone will explain any exception that applies.
Contact privacy@oshizone.com. Do not include identity documents in your message.