Privacy and local data
How PlayLaunch handles browser-local project data and the separate advertising surface
Core workspace data
Projects, checklists, evidence, and preferences are processed in browser storage. PlayLaunch does not send project content to an advertising provider, does not use it for ad targeting, and cannot recover browser-local records for the user.
Advertising data
Approved advertising slots exist only on public guide pages. The AdSense account, public publisher ID, root seller record, site ownership, and required onboarding steps are verified, but Google site review is pending. The current configuration therefore serves only first-party PlayLaunch house messages and sends no advertising request to Google.
Choices
Users can disable contextual and house messages through Advertising choices. Global Privacy Control is honored as a signal that personalization must remain blocked. Rejecting advertising does not restrict the diagnostic workspace.
Hosting and external services
GitHub Pages processes technical hosting requests under its own policies. Opening a public support issue, official store link, sponsor, or affiliate link sends a request to that external service. Paid links are labelled and marked as sponsored.
Retention and deletion
Browser-local project data remains until the user deletes the selected project or clears site data. Advertising preferences remain in the browser until changed or site data is cleared. PlayLaunch currently has no advertising-profile server or account-data advertising store to delete.
Contact and limitations
Privacy and deletion requests currently use the public support route described on the Contact page. Users must not post personal data, credentials, or private project files in a public issue. This notice is not legal advice or a compliance certification.