BuildHop legal
Privacy Policy
BuildHop respects privacy and keeps optional analytics behind consent. This policy explains what we collect, why we use it, and the choices available to you.
Last updated: May 18, 2026
Who we are
BuildHop is a startup discovery platform where visitors browse launches and founders submit products for review, discovery, leaderboards, and related founder tools. References to BuildHop, we, us, or our mean the BuildHop service available at buildhop.io and related BuildHop pages, emails, and product experiences.
You can contact us about privacy at hello@buildhop.io.
Information we collect
- Account information, such as your email address, authentication identifiers, profile role, and sign-in/session details.
- Founder submission information, such as product names, URLs, descriptions, logos, categories, maker links, social profile links, review status, and edits you submit.
- Discovery activity, such as views, hops, skips, votes, dwell time, feedback, launch search activity, referral details, and related anti-abuse signals.
- Payment information for paid boosts or paid features, processed by Stripe. BuildHop does not store full card numbers.
- Communications, such as support messages, transactional emails, launch notifications, and founder feedback alerts.
- Device and technical information, such as IP address, browser type, user agent, approximate location derived from network data, logs, cookie identifiers, and diagnostics.
How we use information
- Provide, secure, maintain, and improve BuildHop.
- Authenticate accounts and keep signed-in founders connected to their workspace.
- Review, publish, rank, moderate, and display founder-submitted launches.
- Operate the discovery feed, vote system, leaderboards, feedback, distribution tools, and anti-spam protections.
- Send service emails, launch updates, feedback alerts, and support responses.
- Process payments, invoices, refunds, fraud checks, and related paid-feature administration.
- Measure product performance and understand usage. Before analytics consent, and after analytics rejection, BuildHop limits PostHog to cookieless pageview and pageleave events without optional browser persistence, autocaptured interactions, user profiles, session replay, surveys, heatmaps, or product tours. Optional analytics cookies or browser storage are used only after you accept analytics.
- Comply with legal obligations and enforce our Terms of Service.
Legal bases for EEA and UK users
- Contract: to provide BuildHop accounts, submissions, dashboards, paid features, and requested services.
- Legitimate interests: to secure the service, prevent abuse, maintain basic operational logs, improve non-invasive product functionality, and communicate about requested service activity.
- Consent: for optional analytics cookies or similar storage where required, and for communications or browser permissions that require consent.
- Legal obligation: when we need to retain or disclose information for tax, accounting, compliance, or lawful requests.
Cookies and similar technologies
BuildHop uses strictly necessary cookies and similar storage for sign-in, security, load/session continuity, privacy choices, and the discovery feed. These include Supabase authentication cookies for signed-in users and a BuildHop discovery session cookie used to keep the no-signup feed, votes, skips, ranking signals, and abuse prevention working.
Optional analytics cookies or browser storage are used only after you accept analytics. Until you accept analytics, and after you reject analytics, BuildHop keeps PostHog in cookieless mode with page-only analytics and without optional analytics cookies or browser persistence. You can reopen Cookie settings from the footer.
Service providers
We use service providers to run BuildHop, including Vercel for hosting and infrastructure, Supabase for authentication, database, and storage, PostHog for analytics when enabled, Stripe for payments, Resend for email delivery, and web push providers for browser notifications when you enable them.
These providers process information for us under their own security and privacy terms. Some information may be processed outside your country, including in the United States.
International transfers
BuildHop is operated from the United States and uses globally available infrastructure providers. If you access BuildHop from outside the United States, your information may be transferred to, stored in, or processed in countries that may have different data protection laws than your country.
Where required, we rely on appropriate safeguards such as contractual protections and provider data processing terms.
Retention
We keep information for as long as needed to provide BuildHop, maintain security, resolve disputes, enforce agreements, comply with legal obligations, and preserve legitimate business records. Founder submissions and public launch pages may remain visible while the launch is approved and live unless removed or hidden under our moderation processes.
You may request deletion of your account or personal information by contacting hello@buildhop.io. Some records may be retained when necessary for security, legal, accounting, or abuse-prevention reasons.
Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal information. You may also withdraw consent where processing is based on consent.
EEA and UK users may complain to their local data protection authority. California and other US state residents may have additional rights under applicable state privacy laws. We do not sell personal information for money.
Children
BuildHop is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information to BuildHop, contact us at hello@buildhop.io.
Changes
We may update this Privacy Policy as BuildHop changes. The updated version will be posted on this page with a new last updated date. Material changes may be communicated through the product or by email when appropriate.