Local review draft

Privacy notice

Not published or approved. The operator identity, address, effective date, privacy contact, cross-border transfer details, and jurisdiction-specific disclosures require owner and legal review.

Data Floabit handles

• Account and authentication details, including email and service session data.
• Content the user chooses to capture, save, record, import, or discuss, plus generated results and notes.
• Usage, storage, operation, billing status, and limited diagnostic records needed to run and protect the service.
• Payment status and provider identifiers needed to reconcile a subscription. Floabit does not need card details in its own application database.

How data is used

Floabit uses this data to provide requested features, keep saved work synchronized, enforce usage and storage limits, recover interrupted work, administer subscriptions, prevent duplicate trial use, protect accounts, and respond to deletion requests.

Service providers under review

The current architecture uses OpenAI for inference. Google Gemini is used for selected YouTube video understanding. Supabase provides hosted authentication and database services, Render hosts the private service, Resend supports account and newsletter mail, and Paddle is the planned payment provider. Final purposes, locations, contractual disclosures, and retention terms require release review.

Retention and deletion boundaries

Account deletion removes active Floabit account content after required subscription cancellation is confirmed. Minimal pseudonymous deletion, billing ownership, transaction, subscription, event-replay, and trial-deduplication records may remain to prevent replay or incorrect account restoration. The trial claim is a keyed hash of the normalized verified email with a 365-day logical lifetime; physical cleanup runs periodically. An unfinished checkout temporarily reserves the same hash until its payment outcome is resolved; completion or cancellation clears that reservation. Payment replay records do not yet have an automatic cutoff.

Offline copies on other devices, exported files, provider-held mail, payment-provider records, and backups are outside immediate in-app erasure. The final published notice must state applicable provider and backup retention precisely.

User choices

Capture requires an explicit translation, summary, or explanation choice. Voice recording starts explicitly; Android keyboard recording additionally requires system enablement. Optional automatic Reader and feed summaries run after the user enables them. Users can keep saved material, export supported data, or request account deletion from the app. Final request and appeal channels require owner review.