1. Scope
This Policy explains the information processed when visitors use public pages and when buyers, creators or administrators use authenticated PayBikini services.
2. Information collected
We process registration and profile details, accepted policies, payment and wallet records, support communications and security records. Creator verification includes ID front and back images and a live verification video, restricted to authorized administration.
3. Content and communications
The service processes uploads, protected previews, custom-request briefs and deliveries, support tickets, permitted attachments, reports, reviews and notifications. Support and dispute records may contain information voluntarily supplied by members.
4. Technical and security records
Security records may include session data, event type, timestamps, pseudonymized IP-derived values, administrative decisions and error references. These records support authentication, abuse prevention, troubleshooting and accountability.
5. How information is used
Information is used to provide accounts and protected access, verify creators, process manual payments, administer store credit, deliver content, operate support and disputes, prevent fraud, enforce platform rules, maintain records and protect users and the service.
6. Storage and access controls
Original photos, verification evidence, attachments and application logs are kept outside the public document root. MariaDB records are held on the configured database server. Authenticated permissions protect access.
7. Sharing
Buyer email and identity are not displayed to creators. Creator legal identity, private contact and location details, birth date and KYC files are not displayed to buyers. Information may be disclosed to hosting or infrastructure providers acting to operate the service, to professional advisers under confidentiality, or when required to respond to valid legal process, prevent harm or protect rights.
8. Blockchain information
Public blockchains operate independently. Wallet addresses, amounts and transaction IDs submitted or observed during payment verification may remain publicly visible and cannot be deleted or changed by PayBikini.
9. Retention
Records are retained when needed for purchases, security, accounting or disputes. KYC evidence is deleted only by an explicit administrator action after reviewing retention needs. A review reminder does not delete files automatically.
10. Member choices
Members can correct profile data and use a support ticket to request access, correction or deletion. Optional contact fields can be cleared; required verification and profile fields must remain valid. Transaction or dispute records may require retention.
11. Security
Protection includes password hashing, CSRF checks, role permissions, private storage and file validation. No system removes every risk; protect credentials, check wallet details and report suspicious activity through support.
12. Policy updates
Updates are published with a revised effective version. Continued use after an update or explicit acceptance, where requested, means the revised Policy applies from that date.
