Privacy policy
Foundset (“Foundset”, “we”, “us”, or “our”) provides a customer discovery and acquisition platform for software founders. This policy explains how we collect, use, store, share and protect personal information when you visit our website, create an account or use our services.
1. Information we collect
Account information
Signing in with an email link collects your email address and the authentication identifiers Supabase issues for your session. Where Google sign-in is available and you choose it, we also receive the basic profile information described in section 2. We store the answers you give during onboarding — your product URL, the problem you describe, who you say pays for it, and what you are hoping to get out of Foundset — against your account.
Product and workspace information
When you use Foundset we process your product website URL, product description, intended customer audience and search queries, and we store the campaigns you create and the conversion-tracking configuration attached to them. A campaign records the public discussion you selected: its title, an excerpt, the author’s public handle and a link to the original.
Discussions you save rather than turn into a campaign are kept in your own browser’s local storage and are never sent to us. Clearing your browser data removes them, and they do not follow you to another device.
Publicly available information
Foundset searches supported public online communities — currently Hacker News, Bluesky and Software Recommendations on Stack Exchange — to identify discussions relevant to your product. Results may contain publicly available usernames, post titles, excerpts, timestamps and links to the original discussions. This information is fetched live for a search and is only stored when you create a campaign from it.
Usage and attribution information
When someone follows one of your tracked links we record the visit: a click identifier, the link it belongs to, the referring page and the time. We do not store the visitor’s IP address or user agent. We store a salted one-way hash of them, which lets us recognise a repeat visit without being able to recover either value.
Conversions are not something Foundset can observe. They exist only when your own application reports one to us, signed with your account’s own secret, carrying the click identifier, whether it was a signup or a payment, and for a payment the amount and currency.
Waitlist relay
If you connect a form provider so that signups can be attributed, we receive the submission and store a salted hash of the subscriber’s email address rather than the address itself. Your form provider remains the system of record for the address.
Managed-service enquiries
If you ask about Foundset Managed we collect the name, email address, company website and goals you submit, and use them to reply and arrange a conversation. We do not add Managed-service enquiries to a marketing mailing list.
2. Google Sign-In
Sign-in links sent to your email address are how you sign in to Foundset today. Google sign-in is built and may be switched on; this section sets out what would happen if you use it, and describes nothing we collect before then.
Where Google sign-in is available, it runs through Supabase Authentication. Choosing “Continue with Google” requests the basic account information needed to identify and authenticate you, which — depending on what Google makes available — may include your name, email address, Google account identifier and profile picture.
That information would be used only to create or identify your Foundset account, maintain your authenticated session and give you access to your workspace. Foundset does not request access to your Gmail messages, Drive files, calendar, contacts or password, does not sell information received through Google, and does not use it for advertising.
3. How we use information
- Create and maintain accounts, and keep private workspaces private.
- Read a submitted product website and run searches of public discussions.
- Show, rank and save customer discovery opportunities.
- Support outreach that you write and approve yourself.
- Record tracked visits and attribute the conversions your application reports.
- Answer support requests and Managed-service enquiries.
- Diagnose errors, prevent abuse and keep the platform secure.
- Meet legal obligations that apply to us.
Where applicable we process personal information on the basis of consent, performance of a contract, legitimate interests or compliance with a legal obligation.
4. Sharing information
We use third-party providers where they are needed to operate Foundset:
- Supabase — authentication and database infrastructure.
- Vercel — application hosting and delivery.
- Google — authentication, only if you choose Google Sign-In.
- Netlify — relays form submissions to us where you have connected that integration.
- Supported public platforms — Hacker News (via the Algolia search API), Bluesky and Stack Exchange, which we query to find public discussions. These are read-only requests; nothing about you is sent to them.
We may also share limited information to respond to lawful requests or to protect the security of the platform. We do not sell personal information. If you authorise an integration to publish a message you have written and approved, that message becomes public on the channel you posted it to.
5. Cookies and tracking
Foundset sets authentication cookies so that your session survives a page load. That is the only purpose for which we set cookies. We run no analytics, advertising or third-party tracking scripts on this website.
Separately, the attribution feature you use on your own site relies on tracked links. A tracked link records a visit and passes a click identifier to your destination page, where your own site’s privacy practices apply. A tracked visit is never treated as proof of a purchase: a conversion exists only when your application reports one.
6. Data storage and security
We use technical and organisational safeguards intended to protect personal information against unauthorised access, disclosure, alteration and loss. These include authenticated access, database-enforced separation between accounts so one account cannot read another’s data, a signing secret unique to each account for conversion reporting, and restrictions that prevent attribution records being deleted casually.
No online service can guarantee absolute security. Information may be processed or stored in countries other than your own through our infrastructure providers, with appropriate safeguards where required.
7. Data retention
We retain account and workspace information for as long as is reasonably necessary to provide Foundset, to meet legitimate operational requirements and to comply with applicable law. Campaigns and attribution records stay associated with your account until the account is closed or retention is no longer justified.
Because attribution is the thing customers rely on Foundset for, deletions of visit and conversion records are recorded in an internal, append-only audit log that keeps a copy of the deleted record and the time it went. That log is not readable from any account and exists so that a missing conversion can always be explained. It means a record you delete is removed from your workspace and from every number we report, while a copy remains in that log for security and integrity purposes.
Technical and security records may be kept for shorter operational periods, or longer where reasonably necessary for fraud prevention, investigations or legal obligations. We may retain information where the law requires it, including after an account is closed.
8. Your privacy rights
Depending on where you are and the law that applies, you may have the right to:
- Request access to the personal information we hold about you.
- Request correction of inaccurate information.
- Request deletion, subject to lawful exceptions.
- Object to certain processing.
- Withdraw consent where processing relies on it.
- Complain to a data protection authority.
Email dollarmoodgroup@gmail.com to make a request. We may need to verify your identity first where the request concerns an account. Closing an account removes its campaigns, links, visits and conversions; because individual attribution records are deliberately protected against deletion, a request to remove one is handled by hand and recorded as described in section 7.
9. Public discussions and other websites
Foundset displays information from publicly accessible discussions. Those discussions stay subject to the original platform’s terms and privacy practices, and we do not control their content, availability or later deletion. If you believe Foundset is displaying personal information that should no longer be processed, contact us and we will review it. Links to external websites are a convenience and do not make us responsible for their privacy practices.
10. Children’s privacy
Foundset is intended for business users and is not directed at children under 18. We do not knowingly solicit personal information from children, and will act if we find we have collected it without a lawful basis.
11. Changes to this policy
We may update this policy as the platform changes or the law requires. The effective date above shows the latest revision, and we will give additional notice of material changes where required.
12. Contact us
Foundset — foundset.vercel.app
dollarmoodgroup@gmail.com
We review privacy enquiries and respond in line with applicable law.