Privacy-friendly by default
AnotherLaunch records aggregate page, badge, widget, outbound-click, and release-reaction activity so product owners can understand whether their releases are reaching people and how those updates are received. We do not create advertising profiles, fingerprint visitors, or sell personal information.
Account information
Founder accounts require a name, email address, and securely hashed password. Password-reset and team-invitation links are stored as one-way token hashes, expire automatically, and can be revoked or used only as described in the email. Products added by their signed-in owners are public when saved; nominated products require approval and domain verification before they can be claimed. Founder portfolio details, selected public projects, and an uploaded profile photo become public only when the founder explicitly publishes the portfolio. Authentication, reaction, and API abuse controls may retain keyed, non-reversible network identifiers for a limited period.
Product update subscriptions
When you follow a product, AnotherLaunch stores your email address, signup source, consent time, subscription status, and one-way hashes of private management tokens. Product owners see aggregate active-subscriber counts, not subscriber addresses. Active followers receive confirmation and newly published release or roadmap emails. Every update email includes a private link to unsubscribe or resume the subscription.
Release reactions
AnotherLaunch shows aggregate like and dislike totals. When you are signed in, your choice is remembered with your account. Otherwise, a first-party, session-only cookie remembers your choice until the browser session ends. The stored keyed identifier is different for each release and cannot be used to connect your activity across releases. Reaction records do not contain IP addresses, user-agent strings, or fingerprinting data.
Public visit analytics
We use our cookie-free website analytics collector on public home, discovery, category, product, founder, recap, claim-library, pricing, and legal pages. It records page paths and titles, campaign tags, external referrer hosts, broad browser, operating-system and device details, approximate location supplied by our network provider, visible-page engagement time, and the text of buttons visitors click. It stores no raw IP address and retains raw events for up to 90 days. It is not loaded on accounts, dashboards, administration, reports, share kits, invitations, referral links, subscription management, embeds, media, APIs, or other tokenized pages.
Browser Do Not Track and Global Privacy Control signals disable the public collector. A signed browser-exclusion link can also set a first-party preference cookie for up to 400 days; on that browser profile it suppresses the public collector and AnotherLaunch's first-party page and outbound-click analytics.
Website analytics for account owners
Signed-in account owners can add multiple domains and activate analytics only after proving control of each domain. The installed, cookie-free collector records page paths and titles, external referrer hosts, campaign labels, broad browser, operating-system and device families, approximate location supplied by our network provider, visible-page engagement time, and the text of buttons visitors click. It honors browser Do Not Track and Global Privacy Control signals. Owners can exclude their browser on the verified website with a first-party preference lasting up to 400 days, or exclude their current public IP address for 400 days, and can re-enable either exclusion from their private report. IP exclusions are stored only as site-specific keyed hashes; the raw address is not stored. AnotherLaunch otherwise uses a keyed identifier that rotates daily only for aggregate daily visitor counts. Raw website-analytics events are removed after 90 days. Deleting an analytics domain deletes its collected events, exclusions, and usage records.
Embeds and analytics
The changelog widget does not set third-party tracking cookies. It reports aggregate views and the referring host when available. Badge and outbound clicks are counted without building a visitor history.
Share links and founder referrals
Release, nomination, and founder-invitation links record aggregate visits and completed actions such as product follows, registrations, claims, and qualified referrals. Attribution is kept in the first-party session for up to 30 days. Growth events do not store IP addresses, user-agent strings, or persistent visitor identifiers. Referral participants see aggregate counts, not a referred founder's private email address.
Service providers
Payment details are handled by Stripe when billing is configured. AnotherLaunch stores subscription identifiers and status, not card numbers. Brevo processes recipient addresses and transactional message content to deliver account recovery, team invitations, subscription confirmations, and product updates. Pending message content is stored in a protected outbox and erased after successful delivery.
Contact and deletion
Account owners can request correction or deletion of private account data. Public releases may be retained as unavailable records when needed for moderation and link integrity.
Last updated September 16, 2026.