Fizzip
Log in

Draft

DRAFT for legal review. This text describes how Fizzip works today but has not been reviewed by a lawyer and is not final. It may change before launch and must not be relied on as legal advice.

Privacy and Cookie Policy

What Fizzip collects, why, who it is shared with, how long it is kept and how to use your rights.

Draft of October 2026

Who we are and what this covers

Fizzip connects Seekers with High-Value Professionals for paid 15-minute meetings, and lets Connectors earn a referral bounty for bringing professionals onto the platform. This policy explains what personal data Fizzip handles for those three kinds of users and for visitors to the site.

Data controller: [legal entity name and registered address to be confirmed]. Privacy contact: [privacy contact email to be confirmed].

Account and sign-in data (Amazon Cognito)

Sign-in is run by Amazon Cognito. When you create an account we store your name, email and a password (held by Cognito as a salted hash, never visible to us). You can add optional details: company, phone number and LinkedIn profile URL, which we use to confirm you are a real professional and to improve matching.

If you continue with Google, Microsoft or LinkedIn, that provider shares your name, email and profile identifier with Cognito. We do not receive your provider password and we do not post on your behalf.

We also keep your role (Seeker, High-Value Professional, Connector or admin), your onboarding progress and your notification preferences.

When you agree to these Terms of Service and this Privacy Policy and confirm that you are 18 or older and live in the United States, we keep a record of when you agreed and which version of each document you agreed to.

Identity verification (Stripe Identity)

High-Value Professionals may be asked to verify their identity before they can be paid. Verification is run by Stripe Identity: the government ID and selfie you submit go to Stripe, which tells us only whether the check passed and, where needed, limited details such as the verified name. Fizzip does not store the ID images.

Payments and payouts (Stripe and Stripe Connect)

Seekers pay by card through Stripe. Card number, expiry and security code go straight to Stripe and never reach Fizzip servers. We keep the billing name, email, billing address you enter, the amount, status and Stripe identifiers of each payment, plus any Fizzip credit balance and its history.

High-Value Professionals and Connectors who want to be paid set up a Stripe Connect account. Stripe collects the bank, tax and identity details needed to pay you and is responsible for them under its own terms. We keep your Connect account identifier, whether payouts are enabled, and the record of each payout, bounty and credit.

Payment, credit and audit records are append-only financial records, and we keep them for the period required for accounting, tax and dispute handling.

Video meetings (Daily)

Meetings run on Daily. We create a private room for each booking and give each participant a short-lived token. Daily processes the audio and video stream while you are in the room. Fizzip does not record meetings: recording is switched off for every room.

We keep the meeting session record: booking, room identifier, join and leave times and whether each side showed up. These drive the no-show guarantee, the 15-minute timer and payout.

A Seeker stays anonymous to the professional until the professional joins the meeting. At that moment the Seeker name and LinkedIn link are revealed to that professional for the booking.

Calendar sync (Google and Microsoft)

If you connect a Google or Microsoft calendar, we ask for permission to read your free and busy times so we only offer slots you are available for, and to add accepted meetings to your calendar. We store the connection tokens needed to do that and the availability you set in Fizzip. You can disconnect at any time from your account settings, which stops further access.

Notifications and email

We send transactional email through Amazon SES (for example meeting requests, reminders, receipts, referral and payout notices) and in-app notifications in real time. Email categories can be turned off in settings or from the unsubscribe link in each email. Some messages that keep your money and account safe cannot be fully disabled.

Referral and recruitment attribution

When you open a link that carries a referral code (?ref=...), we use the code to credit the Connector who invited you. The code is kept in the sign-up link itself and in your browser for the current visit. If you accept functional cookies it is also kept for 30 days in a first-party cookie and in local storage, so the credit survives if you sign up later. The code is linked to your account only if the account is new, and it never changes afterwards.

Recruitment requests let a Connector invite a specific professional. If you claim such a request we link your account to it, and we may check that the LinkedIn profile you give matches the person the Connector named. A Connector sees the people they referred only as first name and initial, plus the status of their bounty.

Cookies and similar technologies

Fizzip uses first-party cookies only. We do not use advertising or cross-site tracking cookies. You choose between two settings in the banner, and you can change your choice at any time with Cookie settings or Your Privacy Choices in the footer.

We honor the Global Privacy Control (GPC) signal. If your browser sends it, functional cookies stay off even if you accepted them earlier.

  • Necessary (always on): the sign-in session cookie (access_token), your selected role view, the reminder cookie that limits how often a verification reminder shows, and the cookie that remembers your cookie choice (180 days). Without them the site cannot work or stay secure.
  • Functional (only if you accept): a referral cookie (fizzip_referral_code, 30 days, SameSite=Lax) and a matching local-storage entry that remember the referral code you arrived with. Declining keeps the code only in the sign-up link and for the current tab.
  • Session storage: during sign-up the current tab keeps the referral code and recruitment request you arrived with so email confirmation and first login can finish the job. It is cleared when you close the tab or when the code is used.

Who we share data with

We share data only with the providers needed to run the service: Amazon Web Services (hosting, Cognito, SES, databases), Stripe (payments, Connect and Identity), Daily (video), Google and Microsoft (calendar, sign-in) and LinkedIn (sign-in). Each acts under its own terms and, where required, a data-processing agreement. We do not sell personal data.

The people you meet see only what the product needs them to see: a professional sees a Seeker only after the meeting begins; a Seeker sees the professional public profile and price.

How long we keep data

Account data is kept while your account is open. Financial, payout and audit records are kept for [retention period to be confirmed with counsel, typically 7 years] to meet accounting and tax duties. Referral cookies last 30 days. Meeting room data is kept for the booking record. When you close your account we delete or anonymise personal data that we are not required to keep.

Your rights and choices

Depending on where you live, you can ask to access, correct, export or delete your personal data, object to or restrict some uses, and withdraw consent you gave (for example functional cookies) without affecting what happened before. You can also complain to your data protection authority.

To use these rights write to [privacy contact email to be confirmed]. We may need to confirm who you are first, and some financial records cannot be deleted while a legal duty to keep them applies.

Security, children and changes

Data is encrypted in transit and at rest in our AWS infrastructure, and access is limited by role. Fizzip is for adults and is not directed at anyone under 18. [International transfer mechanism to be confirmed with counsel.]

If we change this policy in a material way we will tell you in the app or by email before the change applies.