Privacy Policy

This policy applies to everyone who signs in to the platform: event hosts, venue operators, cohosts, and guests. It covers information collected through the site, event flows, RSVPs, ID and age verification, and voluntary health screenings uploaded as part of specific event eligibility checks.

• Account data — email, display name, and authentication metadata provided by you or your identity provider.
• Event data — events you create, RSVP to, or attend; compliance documents you upload as a host.
• Age verification — proof-of-age evidence you upload, stored in a private bucket accessible only to reviewers.
• Sensitive information — sexual health screening results — where an event requires it, you may voluntarily upload a recent STI/STD test result. This is classified as sensitive information under the Privacy Act and is treated to a higher standard of protection than ordinary personal information.

Some events on the platform have an operator-set health-screening requirement. In those cases, guests are asked to upload a recent test result so a reviewer can confirm the result is current before granting event access. Uploading a screening is voluntary and gated by explicit consent at upload time; if you do not consent, you cannot RSVP to events that require it, but no other feature is affected.

Purpose (APP 3, APP 6): screenings are used solely to confirm eligibility for events that require them. They are not used for advertising, profiling, research, training AI models, or any secondary purpose.

Storage (APP 11.1): screening files are stored in a private storage bucket that is not publicly accessible. Files are transmitted over TLS and stored encrypted at rest by the underlying storage provider. Access is enforced at the database and object-storage layer: only the uploading user and the platform's designated reviewer/admin role can read a given file. Ordinary staff, other guests, event hosts, and unauthenticated visitors cannot access screening files.

Retention (APP 11.2): screenings carry a fixed 90-day validity window from the test date. Once a screening's validity window ends, it is automatically purged by a daily background job: the underlying file is deleted from private storage and the database record is removed. A minimal audit log (screening id, user id, test date, validity date, purge reason, purge timestamp) is retained to demonstrate compliance with this deletion; the audit log does not contain the health result itself and is readable only by the admin role. Pending screenings older than 90 days and rejected screenings older than 30 days from review are purged on the same schedule.

Disclosure (APP 6): we do not sell, rent, share, or otherwise disclose health information to third parties. The only exceptions are (a) as required by Australian law (e.g. a lawful court order or regulator request) and (b) to the underlying storage and database infrastructure provider that hosts the platform, which processes data on our behalf under contractual confidentiality obligations and does not use it for its own purposes.

Under APP 12 and APP 13 you have the right to request access to the personal information we hold about you, and to correct information that is inaccurate, out of date, incomplete, or misleading. You can:

• View and download your own uploaded screenings, ID verifications, event compliance documents, and account details from your account area at any time.
• Delete a pending screening yourself before it has been reviewed.
• Request full deletion of your account and associated data by emailing support@princesspink90.com or via the channels listed in the site footer. We will action deletion requests within a reasonable time subject to any overriding legal retention obligations (e.g. financial records required by law).

Access to sensitive tables and storage buckets is enforced by row-level security policies at the database layer — not just in the application code — so that a bug in the frontend cannot expose data across users. Health screening files sit in a private storage bucket with per-user path scoping; only the uploading user and the admin/reviewer role can read a given file. Administrator actions on screenings (approvals, rejections) are attributed to the reviewing account.

Despite these controls, no system is perfectly secure. If we become aware of an eligible data breach involving your personal or sensitive information, we will notify you and the Office of the Australian Information Commissioner (OAIC) as required by the Notifiable Data Breaches scheme.

We understand the sensitive nature of adult theatre events. We act with total discretion and never share your participation status, RSVPs, ticket history, or membership tier with public-facing social media or third-party advertisers. We do not sell, rent, or trade your personal information to third parties for marketing purposes.

We use a small number of first-party cookies and browser storage entries that are strictly necessary to keep you signed in and to remember settings such as your age-gate acknowledgement. We do not use these for cross-site advertising. Any analytics we run is aggregated and does not attempt to identify individual users beyond the account you are signed into.

To make a privacy request — access, correction, deletion — or to raise a concern about how your data has been handled, contact the platform operator through the channels listed in the site footer. If you are not satisfied with our response, you have the right to lodge a complaint with the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

We may update this policy from time to time. Material changes to how health data is handled will be surfaced in-app before they take effect. The "Last updated" date at the top of this page reflects the most recent change.