Privacy Policy — draft for legal review

This is a draft, not a legal compliance certification. Operator legal name, address, privacy contact, retention periods and applicable regional rights must be completed before public account launch.

What Launchpad stores

Guest opportunities, favorites, goals, tasks, roadmap progress and preferences stay in your browser storage. Anyone using the same browser profile can access those guest records. Launchpad does not silently upload them when you sign in.

Configured account workspaces store your email/authentication identity with Supabase and your profile, career records, preferences, feedback and optional AI history in the project's database. Owner-only access requires the deployed Row Level Security policies. Passwords are processed by Supabase; Launchpad does not manually store them. The official SDK stores session tokens in browser localStorage, separate from guest records.

Hosting and security logs

GitHub Pages or Cloudflare Pages, Supabase and configured providers may process IP addresses and network/security metadata as part of hosting and abuse prevention. The operator must finalize provider agreements, retention periods and rights handling before public account launch.

Optional AI processing

AI runs only through the configured server function. Your question is sent to OpenAI; saved profile, goals, progress or prior exchanges are included only when you select those options. Saving exchange history is off by default. OpenAI requests set store:false, but provider processing and any operational retention remain subject to the provider's terms and account configuration. Never send identity documents, passwords, health details or other sensitive information.

Jobs and reminders

Job data is retrieved from Remotive through a shared backend cache. Search filtering happens in your browser. When email reminders are enabled by you and the operator deploys a scheduler, your confirmed account email and reminder text may be sent to the configured email provider (Resend in the supplied implementation). Browser-only reminders do not execute when the app is closed.

Age-appropriate use

Accounts and AI are intended for people aged 16 and older. The profile uses a broad self-declared age range and does not request an exact birth date. People under 16 may use the local guest organizer without creating an account or sending career context to AI. The operator must review applicable child privacy requirements before public launch; this is not formal age verification.

Choices, export and deletion

You can export the active workspace, separately import guest records after confirmation, delete saved AI history, and request account deletion after password reauthentication. Account deletion removes owned career records; minimal billing identifiers, accepted contract versions and required financial records may remain under a legally approved retention schedule. Active subscriptions must first be canceled and confirmed by the provider. Guest data is deliberately retained. Browser storage can be removed through your browser settings after making a JSON backup. Hosted backups and provider logs may have separate retention obligations, which the operator must document.

Security and remaining operational decisions

RLS, server authentication, input validation, bounded AI usage and restricted redirects are included in the code. These controls require correct deployment and live testing. The operator must finalize vendor agreements, support/contact details, backup retention, incident handling, legal bases and jurisdiction-specific rights before charging customers. No advertising trackers are included. Optional first-party pricing-view counts require explicit consent and can be withdrawn and deleted in Billing. Paddle checkout may process security/fraud metadata under its applicable privacy terms.

Commercial processing, GDPR and Brazilian LGPD — draft

Paddle Billing, when configured, receives your verified email, a customer/account identifier and transaction context to manage purchases, renewals, invoices and its merchant-of-record obligations. Launchpad stores provider IDs, subscription state, contract consent versions, token usage and estimated costs, never card numbers. Early-access email consent is optional and can be withdrawn separately.

The operator must establish and document appropriate legal bases: necessary account/service processing for requested services; explicit optional consent for early-access messages and pricing analytics; legal obligations for required financial retention; and any legitimate-interest security processing after the appropriate assessment. These are draft purposes, not a finding of compliance with GDPR or LGPD.

Publish the controller identity and privacy contact, processor list/DPAs, international transfer safeguards and data locations, exact retention periods, rights-request verification and response procedure before launch. Subject to applicable law, users may request access, correction, portability, deletion, restriction, objection, consent withdrawal and information about shared data; explain relevant supervisory-authority complaint routes and financial-record exceptions. Confirm region-specific requirements with qualified counsel.

Paid contracting is restricted to adults. Broad age bands are self-attested, not identity-verified; any guardian involvement needs a reviewed procedure before use. No exact birth date or identity document is requested by this application.