DRAFT — inventory must be verified in the production build. Updated To be confirmed: effective date.
PPLONLY uses browser and device storage to support requested features. The web implementation uses an HTTP-only session cookie (ppl_session) for authentication and browser session storage for booking, gift and creator-application drafts. The native app uses secure device storage for its session token. Server-side preferences, messages and bookings are separate from cookies.
| Storage purpose | Choice and effect | Publication requirement |
|---|---|---|
| Authentication/security | Signing out invalidates the session; disabling required cookies can prevent sign-in | Confirm actual cookie attributes, expiry and domain |
| In-progress drafts | Discard the draft or clear session storage; private browser settings may limit recovery | Confirm each key, scope and expiry against code |
| Calendar/sharing | Initiated through the relevant device feature | Explain what booking details leave PPLONLY |
| Optional analytics/advertising, if introduced | Separate controls and consent where required | Inventory SDK/provider before enabling; do not load nonessential tracking before the required choice |
The draft baseline excludes advertising trackers; this is not a completed production tracking audit. Third-party hosted payment or onboarding pages may use storage under the provider's own notice. Do not describe that as first-party PPLONLY storage.
The published cookie register must contain each actual name/provider, purpose, duration and essential/optional classification: To be confirmed: cookie register. Consent controls must offer a meaningful refusal and later withdrawal for optional processing. Where applicable, recognized browser opt-out signals must be honored. Clearing a cookie does not delete an account or erase server records. Privacy questions: cayla@pplonly.com.