When email login is enabled, Supabase verifies your email using a one-time code and manages your session on this device. Vibe receives a verified provider identifier and email. During the restricted owner review, platform sign-in still controls access to the Site. Vibe stores that identifier, account creation time, saved creation recipes including their text, subscription status, Stripe customer references and webhook processing identifiers. Typing stays on your device. Generating a preview or paid creation sends its words and settings to the server. Preview requests are not saved as creation records. Preview abuse prevention stores a salted network hash with a daily expiry; expired rate-limit records are removed on later preview requests. We do not store raw IP addresses in that table.
Your browser may store style preferences, a personal random seed and motion preference on your device. Exported PNG, SVG and JSON recipe files are downloaded to your device. Recipe files include the words and design settings you export; share them only when you intend to share that information.
When enabled, Stripe hosts payment and billing-management pages. Vibe does not receive or store your full card details. Sites hosts the service and database. Supabase provides email verification and session management when configured. Its delivery provider sends sign-in emails. The managed auth client stores a session on your device so you stay signed in; signing out removes local access. This preview has no advertising pixels or external behavioural analytics. In-browser interaction events are not a persistent analytics service.
You can sign out, change motion preferences and cancel subscription renewal from Account. A verified support route for access, deletion, correction and billing queries is required before the paid launch. Some billing and ownership records may need retention for legal and anti-duplication purposes; the final policy must explain those periods and grounds.