TOASTLAUNCH PRIVACY

Privacy, plainly.

Effective November 13, 2026

Account and content

We use Supabase Auth for Google and email code sign-in. We receive your email, account identifier and, when provided, display name. Your maker name, launches, images and comments are public. Your email is never publicly listed. Administrators can remove launches that break our rules.

Google sign-in data

If you sign in with Google, we receive only your basic profile: your name, email address and profile picture URL, through the standard “openid”, “email” and “profile” permissions. We do not request or access your Gmail, contacts, Drive, calendar or any other Google data.

We use this information only to create and secure your ToastLaunch account, sign you in, show your name on your launches and comments, and send emails about your account and launches. We do not sell it, use it for advertising, or share it with anyone except the service providers that run ToastLaunch (Supabase for accounts and Brevo for email). ToastLaunch’s use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect ToastLaunch from your Google account at any time in your Google Account’s security settings, and delete your ToastLaunch account and all its data from your dashboard.

Launch measurement

We record product page views and outbound Visit clicks with a product identifier, event type, time and a daily visitor hash. We do not store raw IP addresses in our application database. An IP address is processed briefly to produce a secret salted hash that changes each UTC day. Changing the browser user agent does not create another unique visitor. Visitors sharing an IP address are counted together. This estimates unique daily visitors without maintaining an identity across days. Obvious bots are ignored. Counts can include repeat visits and may be affected by blocking or automation.

We use separate IP-only and normalized-email hashes for short-lived abuse prevention limits. The user agent is used to ignore obvious bots, not to identify unique visitors or set rate-limit keys.

Drafts, reports and follow intents

Saved drafts belong to your account. Public maker profiles show the information you choose to publish. Following a maker stores a relationship between accounts and emails you when that maker launches. Launch reports are private unless you enable a public link and select the metrics to share. Disable sharing to revoke that public view. Moderators can review reports and feedback; admin decisions are retained in an audit log to operate the service.

Newsletter and optional diagnostics

When you create an account, we subscribe your account email to the weekly winners newsletter and turn on launch notifications (comments on your launches, your launch going live, launches you follow). You can turn each one off in your email settings or with the unsubscribe link in every email. If you sign up for the newsletter without an account, we store your normalized email, subscription status and hashes of confirmation and unsubscribe tokens, and you confirm your address before receiving anything. Unsubscribing before you create an account is respected afterwards.

Outside Europe and the UK, Google Analytics 4 sets cookies and receives the pages you view, how you arrived, your approximate location and device, and named actions such as starting a launch or upvoting, never what you type. If your device is set to a European time zone, Google Analytics never loads. Anyone can turn analytics off (or on) with the link in the footer. Sentry receives restricted error diagnostics without request data, cookies or account identifiers. These providers may process network information to deliver their service.

Deleting your data

You can delete any of your launches from your dashboard. You can also delete your whole account there: this permanently removes your launches, votes, comments, maker profile, follows, saved launches, drafts, orders, uploaded images and any newsletter subscription for your email. Our payment provider keeps its own payment records as the law requires.

Cookies and providers

Essential authentication cookies keep you signed in. Google Analytics cookies are set only outside Europe and the UK, and never if you turn analytics off in the footer. We do not use advertising cookies. Supabase stores account and platform data. Our hosting provider and Supabase may process network logs, including IP addresses, under their own policies. Google processes sign-in when you choose that option.

Checkout and transactional email

Dodo Payments handles checkout and payment details. ToastLaunch stores order and booking details and the provider references needed to reconcile them. Brevo processes recipient addresses to deliver transactional email. The application email log stores a recipient hash and delivery status.

Website verification

We fetch the website you submit to check for a ToastLaunch badge. A current verification controls the Visit link’s relationship attributes. Visitors follow external links at their own discretion.

Retention and your choices

Account information and content are retained while needed to operate the service. Launch events are retained to support cumulative launch measurement and future reporting. Expired rate-limit records are removed by our daily maintenance job. You can request access, correction, deletion or account removal by emailing privacy@toastlaunch.com. Deleting an account removes its launches and associated events and comments from our application database; provider backups may persist under provider retention schedules.

Updates

Changes will be published here with a revised effective date.