Privacy policy
How information is handled when you use Launch Check.
Who we are
This sample policy describes how [Legal business name], the operator of Launch Check, handles personal information. Replace these placeholders with your registered name, [Postal address], and [Privacy email]. Effective date: [Date].
This is a starting point for customization, not a statement of a deployed business’s actual practices.
Information we collect
Account information may include your name, email address, profile image, and authentication details. Workspace information may include memberships, invitations, settings, and content you create or upload.
Subscription records may include your plan, billing contact, payment status, and payment-provider identifiers. Payment card details are handled by the payment provider. Describe any device information, logs, support messages, feedback, and usage events your deployment actually collects.
How information is used
Information is used to provide accounts and workspaces, process subscriptions, respond to support, maintain security, and send service communications. Describe additional uses only if you actually perform them.
Where required, identify the lawful basis for each purpose: for example, performing a contract, meeting legal obligations, legitimate interests with those interests explained, or consent that can be withdrawn.
Service providers and sharing
List the providers your deployment actually uses, what each receives, and why. The starter can use Supabase for accounts and databases, Stripe for payments, Resend for email, and Vercel for hosting. Optional integrations require additional disclosures when enabled.
Explain how workspace administrators and teammates access shared information. Identify public content and describe any disclosures required by law or associated with a business transfer.
AI and optional integrations
If AI is enabled, explain which prompts and conversation context reach each provider, how responses are stored, and the provider’s retention and training practices. Only submit information you are authorized to share.
If analytics or advertising are enabled, describe the actual data collected and available choices. This sample does not obtain consent to optional tracking.
Cookies and browser storage
The application uses authentication cookies and may retain workspace and display preferences. Add an inventory describing the purposes and lifetimes of cookies and browser storage in your deployment.
Where required, obtain consent before setting optional cookies and explain how people can change their choices.
Retention, security, and transfers
Specify retention periods or concrete criteria for account content, logs, billing records, and backups. Explain what happens after account or workspace deletion and which records must be retained.
Describe actual security practices without promising absolute security. Identify processing locations and applicable international-transfer safeguards, including how to obtain further information.
Your choices and rights
You can manage available profile and workspace settings in the application. Depending on applicable law, you may have rights to access, correct, delete, export, restrict, or object to processing, and withdraw consent where processing relies on it.
Send requests to [Privacy email]. State verification procedures, response timelines, and the relevant supervisory authority or complaint route. Add applicable regional rights and how to exercise them.
Children, changes, and contact
Specify your intended audience, applicable minimum age, and process for handling information collected from children. Choose these terms for your product and markets.
Explain how you communicate material policy changes. Contact: [Legal business name], [Postal address], [Privacy email].