DRAFT — not effective. Updated To be confirmed: effective date. Controller/operator: PPLONLY Inc., 452 NE 31st Street, Miami, Florida To be confirmed: postal zip, United States. Privacy requests: cayla@pplonly.com. Applicable representative or privacy officer: To be confirmed: privacy representative if required.
Scope and current state
This notice covers PPLONLY accounts, profiles, booking, messages, live conversations, support and the website/apps. It describes the proposed public service and must be reconciled with the production data inventory before publication. Live Stripe payments and creator Connect are configured, with end-to-end verification still required and public booking access restricted. Separate vendor bank payouts are not activated. Live AI moderation and platform call recording are not active. If these features are introduced, a specific notice will explain the processing before it begins.
Information we handle
| Category | Examples and origin | Purpose |
|---|---|---|
| Account and security | Name, email, protected password representation, session records and verification/recovery events provided by you or generated by the service | Sign-in, account security and communication |
| Creator profile | Bio, authorized image, offerings, pricing, availability and application details submitted by the creator | Discovery, scheduling and creator administration |
| Booking and transaction records | Participants, UTC time/timezone, duration, amount, currency, fees, provider references and payment/refund status | Reserve sessions, reconcile payments and resolve problems |
| Messages and preferences | Booking-thread text, saved profiles, interests, notification choices, early-access signup and draft gifts | Deliver requested communication and personalization |
| Call data | Live audio/video transmitted when you join, room authorization, participant/connection and attendance events | Deliver and secure the live session; determine attendance |
| Support and safety | Reports, voluntarily supplied evidence, case decisions and audit events | Investigate issues, protect users and handle appeals |
| Technical information | Device/network request data and service diagnostics processed by hosting or communication services; exact fields subject to inventory verification | Operate the service, investigate errors and prevent abuse |
Payment details and creator verification information may be collected directly by Stripe. PPLONLY receives the provider references, capability flags, requirements and transaction information needed for its role; it should not receive full payment-card credentials through support messages. Confirm the exact live account model before publication. Do not put card numbers, identity documents or private medical information in messages or booking notes.
Camera and microphone access transmit your live conversation when enabled. Calendar export shares booking details with the calendar service you choose; system sharing sends the selected content to your chosen destination. Revoking device permission affects that feature, not unrelated account functions. A native secure-storage session token is used to keep you signed in.
Who can see information
Creators' approved public profiles and offerings are visible to people browsing the service. Other participants see the information necessary for their booking and the messages you send them. Private account, payout and identity data must not appear on public profiles. Authorized staff may access necessary records for support, security, moderation or legal work. Staff access is subject to purpose restrictions; private messages should not be described as accessible only to participants if staff can investigate them.
Service providers process information for hosting, live communication, email, payments and security. The confirmed provider list, purposes and processing locations are To be confirmed: published provider register. The implementation references Render hosting, LiveKit, Stripe and Resend; their exact contracted entities, enabled production services and locations still require verification. Payment providers may also process data for their own legal obligations under their notices.
We may disclose necessary information to comply with valid legal process, address a serious safety concern, protect rights or complete a lawful business transfer with appropriate safeguards. We do not promise absolute confidentiality against valid legal requirements. Proposed launch commitment: no sale of personal information, cross-context behavioral advertising, or use of private session content for general-purpose model training. Verify SDKs, contracts and actual processing before publishing this commitment.
AI, recordings and sensitive information
There is no platform call recording or live AI conversation monitoring in the current build. Reports and stored messages may be reviewed by authorized staff. Proposed AI moderation would flag specific harmful conduct for review; the data, provider, retention and available choices would be disclosed separately before activation. No emotion scoring, accent scoring, face recognition or inference of protected personal characteristics is authorized by this policy. Optional content use for model training would require a separate, explicit decision and lawful process; agreement to this notice does not grant it.
Do not assume a call is legally privileged or impossible for another participant to capture. Participants are prohibited from unauthorized recording, but PPLONLY cannot guarantee that external devices never capture a conversation.
Purpose and legal basis
Where a lawful-basis framework applies, processing must be mapped to the actual activity: providing a requested account/session, complying with legal duties, proportionate security and abuse prevention, or valid consent for optional features. These are not interchangeable blanket grounds. The launch record must identify the chosen basis, relevant interests and any additional conditions for sensitive data. See To be confirmed: regional privacy supplement for jurisdiction-specific details and complaint authority. Withdrawing consent stops future consent-based processing without changing the lawfulness of earlier processing.
Retention and deletion
We retain records only for documented operational, dispute, security and legal needs. Publish the approved category-specific periods here: To be confirmed: public retention schedule. Longer retention for a valid legal hold must be limited, justified and reviewed. Deletion includes active records, downstream providers and scheduled backup expiry, subject to exceptions explained to you. Account deletion is not the same as erasing every financial/legal record or recalling information already lawfully shared with another participant. No numerical deletion promise is effective until the corresponding workflow and backup limits are verified.
Choices and requests
Use account settings for supported profile/preferences changes and device settings for camera/microphone permissions. Contact cayla@pplonly.com for access, correction, export, deletion, restriction, objection or consent withdrawal requests available under applicable law. We verify requests proportionately and explain denials or exceptions. Authorized-agent processes and statutory response periods depend on applicable law; the internal register controls deadlines. We do not penalize you for exercising protected privacy rights.
Where California privacy law applies, the regional notice must cover applicable access, deletion, correction, opt-out, sensitive-information and non-discrimination rights and recognized preference signals. Where European/UK law applies, identify the appropriate supervisory authority and transfer safeguards. We will not claim a universal right or exemption without checking scope.
International processing and security
Provider processing may take place outside your location. The production register must identify the locations and required transfer mechanisms before launch; no specific mechanism is claimed in this draft. We use proportionate safeguards and access restrictions but cannot guarantee absolute security. Do not describe the service as end-to-end encrypted without an independently verified architecture supporting that claim.
Children, changes and contact
The proposed service is for adults 18 and older. Report suspected underage participation at To be confirmed: safety contact. We will assess and restrict such access and handle the associated data under applicable obligations. The age rule must be implemented before launch. Material notice changes will be clearly communicated, with additional choices or consent where required. Contact cayla@pplonly.com or 452 NE 31st Street, Miami, Florida To be confirmed: postal zip, United States for questions.