A little clarity on privacy.

This notice covers the CueFounder community pilot at cuefounder.ai and founders.cuefounder.ai.

When you request an invite

We store your name, verified email address, company or idea description, stage, support needs, support offers, acceptance of the community commitments, LinkedIn URL, company domain and verification evidence, founder photo, profile draft, application time, and review status. We use this information to review membership requests and contact you about joining. Submitting a request does not subscribe you to a marketing newsletter.

Email sign-in and your member page

We use Better Auth to manage account records and sessions. Resend delivers one-use sign-in links from signin@cuefounder.ai. Links expire after 10 minutes; token hashes are stored for verification. Your browser receives a host-only, HttpOnly session cookie on founders.cuefounder.ai. Sessions expire after seven days and can be ended by signing out. Session and rate-limit records may include your connection address and browser information to protect accounts against abuse.

Your private member page shows your application and, after approval, a time-limited Buzz invite. Website sign-in and Buzz identity are separate. Approval and an invite are required to enter the Buzz community.

Where the information lives

The application database and the Buzz community are hosted on CueFounder-operated infrastructure at Hetzner in Helsinki, Finland. Cloudflare provides DNS. Resend processes your email address and sign-in email for delivery. Our hosting providers may process operational information needed to deliver these services.

Company review and profile drafting

We check public DNS records and the company website you provide, and compare company and LinkedIn details across applications to flag cases for human review. A flag is a request for closer inspection, not a finding of fraud. LinkedIn URLs are provided by applicants; we do not bypass LinkedIn sign-in or claim to independently verify their profiles.

With your confirmation, Google Gemini processes your professional application answers and a public company website excerpt to draft a profile. We do not send your portrait or sign-in email for this draft. You can edit the draft or write your own profile, and must confirm its accuracy before submission. Operator decisions and review notes are stored in an audit history. Applicant-facing notes are separate from private operator notes.

Portrait uploads are converted to WebP and metadata is stripped. Application photos and details are accessible only to the applicant and authorized operator accounts.

Community conversations

Membership is invite-only. Messages and profile information are processed by our Buzz server, and members of a conversation can read and copy what is shared there. Operators can access server-stored data for administration, support, and moderation. Do not treat the service as a confidential vault or assume end-to-end encryption.

Your Buzz identity

Buzz uses a cryptographic identity. Keep your private identity key safe in a password manager. We cannot promise to recover an identity if you lose its key. Membership administration and identity recovery are different things.

Cookies, analytics, and abuse prevention

We do not use advertising cookies or third-party analytics. Authentication uses essential session cookies. It temporarily uses a hash of your connection address to limit repeated form submissions; these in-memory entries expire after 15 minutes. Infrastructure logs and server backups may also contain operational information.

Access, corrections, and deletion

You can ask the CueFounder operator who invited you to correct or delete your application or review your community data. You can sign in to update your profile. For a privacy request before you have a community invite, describe the request in your support profile so the operator reviewing applications can see it. We may need to verify the relevant Buzz identity separately. Deleting server data cannot remove copies other members already saved.

Application records remain available for pilot review until an operator removes them. Server backups may retain deleted data until those backups rotate. This notice will be updated if the pilot’s data handling changes.