Legal
Privacy
A plain-language summary of the data used by the WrapOS catalogue and account features. This draft still needs the operator and retention details completed before public launch.
Last updated 13 October 2026
Account and garage data
If you create an account, WrapOS processes your name, email address, password hash or Google account identifier, verification state, and sign-in sessions. Account and garage records are stored in Cloudflare D1. When signed in, your selected Tesla and saved catalogue wraps are attached to your account; while signed out, browser-only selections and favorites are stored in localStorage on that device. Google sign-in is available only when configured.
Account emails
Resend is used to deliver email verification and password-reset links. These messages contain single-use authentication links. Never forward them to anyone else.
Purchases and downloads
After a payment is verified by Stripe, WrapOS stores the purchased wrap, amount, payment identifiers, status, and date in D1 so access can be checked and the file downloaded again. Stripe processes payment details; WrapOS does not store your card number. Purchased artwork is served from private Cloudflare storage, while free catalogue files are available for download. Checkout is not open until its production setup and tests are complete.
Uploads and custom creation
Uploading personal images, creating wraps with AI, and business workspaces are not part of this soft-launch release.
Analytics
WrapOS maintains aggregate download counts by catalogue wrap. Detailed production analytics are not connected. Raw passwords, payment details, and private account information should never be placed in analytics events.
Before public launch
The operator identity, contact route, lawful basis, retention periods, subprocessors, regional rights, and account deletion process still require legal review and production configuration. This page is a product draft, not a substitute for that review.