AlphaR

Privacy policy

Last updated 19 October 2026

This policy explains what personal data AlphaR collects, why, who it is shared with, how long it is kept, and the rights you have. It covers the AlphaR members' platform at platform.alpharealised.com: sign-in, onboarding, the member app, event pages for invited guests, and the AlphaR team's console. [TBC: whether this policy also covers the alpharealised.com website]

Questions or requests: write to support@alpharealised.com.

1. Who we are

AlphaR is run by Refayce Ltd, 51 New Road, Porthcawl, CF36 5DH, United Kingdom (company number [TBC: company number]). Refayce Ltd is the controller of the personal data described in this policy: we decide why and how it is used.

We are a UK company, so the UK GDPR and the Data Protection Act 2018 apply. Where we offer membership to people in the European Union, the EU GDPR applies too. Our UK regulator is the Information Commissioner's Office (ICO). [TBC: ICO registration number] [TBC: EU representative under Article 27 EU GDPR, if appointed]

This policy is about:

  • members, including Portfolio Heads and colleagues invited on a team plan;
  • people we have invited who have not joined yet;
  • non-members who register for an event through a guest link;
  • AlphaR team members who use the console.

2. What we collect

What you give us

  • Account and sign-in. Your name, email address and password. Your password is stored by our sign-in provider in hashed form; we cannot read it. If you use Continue with Google, Google confirms your email address to us.
  • Membership. Your plan, seat, the account you belong to, your membership status, and invitations you send or receive.
  • Profile. Photo, role, company, company website, headline, bio, location, LinkedIn and website links, experience, expertise, what you can help with, what you are looking for, and whether you are open to introductions.
  • Company. Your employer, your role there and when you started; your company's region, ARR band and sales motion. For Portfolio Heads, the portfolio's name, website, description and logo.
  • Benchmarks. Your company's quarterly metrics (such as net and gross revenue retention, gross margin, CAC payback, win rate and pipeline coverage). These describe your company, not you personally, and stay with the company if you leave it.
  • My Alpha. What you write in your cycles (mandate, beliefs, next moves, reviews), your check-back dates, and who you share it with.
  • Events. Your registrations, waitlist places, check-ins, survey answers, and any host or speaker role. If you subscribe to your private calendar feed, a secret link that identifies you.
  • Peer Circles. Which circles you are in, hot-seat sessions, and session notes posted to a circle.
  • Introductions. Who you asked to meet, your note, and the outcome; and requests other members make to meet you.
  • Library. Lessons you start and complete, items you save, questions you ask in Ask, and contributions you add to your profile.
  • Simulator. Your application for access, and, if you take part, your participation, scores, feedback, reports and Decision Quality Score.
  • Settings and messages. Your email notification choices, email address changes, and anything you send us through the contact form.
  • Event guests. If you register for an event as a guest, your name, email address and company.

What we get from others

  • LinkedIn, through Limadata. Only if you paste your LinkedIn address: we look up your public LinkedIn profile to pre-fill your directory card and copy your profile photo into our storage. You can edit or remove anything before and after it appears.
  • Whoever invited you. Your name, email address and, for company and portfolio invitations, your company.
  • The AlphaR team. Your approval, circle placement, event check-in and how your introductions were handled.
  • The Simulator provider. Your results, as described above.

What is recorded automatically

  • Activity record. A log of what you do on the platform, such as completing a lesson, registering for or attending an event, requesting an introduction or submitting benchmarks. It powers your activity on your profile and the AlphaR team's view of how members use AlphaR.
  • Analytics and session replay. See section 6.
  • Error reports and server logs. When something breaks, an error report (see Sentry in section 5). Our hosting provider logs requests, including IP addresses.

3. How we use it, and why we're allowed to

Running your membership

Legal basis: Contract

Your account and sign-in, the directory, introductions, events, Peer Circles, the library, My Alpha, benchmarks and the Simulator, and the service emails that go with them.

Benchmark cohorts

Legal basis: Contract

Your company's submissions are pooled with other firms' so members see cohort statistics. Only the people listed in section 4 see your company's own figures.

Pre-filling your profile from LinkedIn

Legal basis: At your request (contract) [TBC: confirm lawful basis]

Only when you paste your LinkedIn address.

AI features in the library

Legal basis: Contract

Answering what you ask in Ask, and drafting a contribution card from a page you link.

Understanding how AlphaR is used

Legal basis: Legitimate interests [TBC: confirm lawful basis and consent position for analytics and session replay]

Product analytics and session replay, to see which features members use and where they get stuck, and to fix problems.

Keeping the platform secure and working

Legal basis: Legitimate interests

Error monitoring, rate limits, and checking who may see what.

Event guests

Legal basis: Legitimate interests

Confirming your place, sending reminders and the follow-up survey for the event you registered for, and inviting you to join AlphaR afterwards.

Legal and accounting duties

Legal basis: Legal obligation

Keeping records we are required to keep and answering lawful requests.

We don't make decisions about you by automated means that have legal or similarly significant effects. Introductions are made by a person on the AlphaR team; suggestions such as “People you should meet” are matched on what you are looking for and your segment, and you decide what to do with them.

4. Who can see your information on AlphaR

  • Other members see your directory card: name, photo, role, company, location, headline, bio, expertise, what you can help with, what you are looking for, your links and whether you are open to introductions. Only active members are listed: while your membership is paused, or after it ends, you are hidden from the directory.
  • Event attendees see who else is going once they have a place.
  • Your Peer Circle sees its members and the notes posted to it.
  • My Alpha is private by default. You can share it, read-only, with members you name, and stop sharing at any time. The AlphaR team sees only counts and dates (your stage, chosen lever, check-back date), never what you wrote.
  • Benchmarks. Your company's own submissions are visible to you, to colleagues at the same company on AlphaR, and to your Portfolio Head if your company is in a portfolio. Everyone else, the AlphaR team included, sees only cohort statistics: a cohort is shown only once at least ten other firms are in it, its outer percentiles only from twenty, and firm counts are rounded down to the nearest ten. You are never compared against your own company.
  • Portfolio Heads see the people at their portfolio companies (name, title, photo and membership status), pending invitations, and those companies' benchmark submissions. They have no view of an individual member's activity.
  • The AlphaR team uses the console to approve members, route introductions, run events and circles, and support members. It can see member records (including email addresses), profiles, membership details, your activity record, introduction requests, event rosters, Simulator progress and reports, and the My Alpha counts above. It cannot see a company's benchmark figures.
  • Profile photos are stored as public files: anyone who has the exact link to a photo can open it.

5. Service providers (sub-processors)

These companies process personal data for us, under contract and only on our instructions. [TBC: confirm a data processing agreement is in place with each]

  • Supabase

    What it does

    Database, sign-in and file storage.

    Personal data it receives

    Everything described in section 2 that we store: your account, profile, company details, benchmark submissions, My Alpha, events, circles, introductions, activity record and profile photo. Your password is held here in hashed form.

    Where

    EU (Stockholm, Sweden).

  • Vercel

    What it does

    Hosts the platform and runs its server code; cookieless visit statistics (Vercel Web Analytics).

    Personal data it receives

    Every request passes through it, so it handles all the data above in transit, plus your IP address, browser and the pages you visit. Web Analytics receives page addresses (with any private links removed), referrer, country, device and browser.

    Where

    Server code runs in the EU (Stockholm, Sweden); content is delivered through Vercel's global network. [TBC: Vercel's processing locations and transfer safeguards]

  • Resend

    What it does

    Sends the platform's emails.

    Personal data it receives

    Your name and email address and the content of each email: invitations, sign-in and email-change links, event confirmations and reminders, introductions, Peer Circle notices, and My Alpha check-backs (which repeat the next move you wrote).

    Where

    [TBC: Resend hosting region]

  • Google (Gemini API)

    What it does

    AI answers in the library's Ask, drafting contribution cards, and indexing library content for search.

    Personal data it receives

    The question you type into Ask, and the text of a web page you link when adding a contribution. Library content. Not your name, email or account details.

    Where

    [TBC: Gemini API processing region, and confirmation that inputs are not used to train models]

  • Limadata

    What it does

    Looks up a public LinkedIn profile to pre-fill your directory card.

    Personal data it receives

    The LinkedIn profile address you paste during onboarding or when editing your profile. It returns your public profile: name, headline, about, current role and company, experience, skills, location and photo. The AlphaR team also uses it to look up a portfolio company's public LinkedIn page.

    Where

    [TBC: Limadata hosting region]

  • PostHog

    What it does

    Product analytics and session replay in the signed-in app.

    Personal data it receives

    Your member ID (not your name or email), your seat type, account ID, company region, ARR band and sales motion, and whether you are AlphaR staff. The pages you view, what you click, your browser and device, and recordings of your sessions (see section 6). Feature events such as completing a lesson or registering for an event.

    Where

    EU (PostHog EU Cloud).

  • Sentry

    What it does

    Error monitoring.

    Personal data it receives

    Error messages, stack traces, the page path, browser and device type, and timing data. Configured not to send who you are, cookies, headers, form contents or query strings.

    Where

    [TBC: Sentry data region (EU if the project's DSN host is ingest.de.sentry.io)]

  • Zoom

    What it does

    Creates meeting links for online events and Peer Circle sessions.

    Personal data it receives

    The event title, start time and duration. No member data is sent when the meeting is created. When you join a Zoom call, Zoom processes your data under its own terms.

    Where

    [TBC: Zoom account data region]

  • Sanity

    What it does

    Manages library content (courses, lessons, resources).

    Personal data it receives

    Library content, and the name, role and photo of course hosts, which the AlphaR team adds. No member account data.

    Where

    [TBC: Sanity project hosting region]

  • Simulator provider (NewReLLM)

    What it does

    Runs the GTM Simulator (currently open by application only).

    Personal data it receives

    When you launch a simulation: your name, email address and member ID. It sends back your participation status, scores, feedback and reports.

    Where

    [TBC: legal entity operating the Simulator, and its hosting region]

  • The Motion Bridge

    What it does

    [TBC: role (development partner / Simulator team) and legal entity]

    Personal data it receives

    Simulator applications: your name, email address, company, role and member ID.

    Where

    [TBC: location]

Google sign-in. If you choose Continue with Google, Google handles that sign-in under its own privacy policy.

Embedded videos. Some library lessons play videos from YouTube (through its privacy-enhanced youtube-nocookie.com player) or Vimeo. When you play one, that provider receives your IP address and may set its own cookies.

Payments. [TBC: payment provider, once online billing is live]

6. Cookies, device storage and analytics

We use cookies and browser storage only for the purposes below. We do not use advertising or cross-site tracking cookies.

  • sb-…-auth-token

    Type

    Cookie (may be split into .0, .1)

    Purpose

    Keeps you signed in. Strictly necessary.

    How long

    Up to 400 days, or until you sign out.

  • sb-…-auth-token-code-verifier

    Type

    Cookie

    Purpose

    Completes Google sign-in and password reset securely. Strictly necessary.

    How long

    Until the sign-in or reset completes.

  • sidebar_state

    Type

    Cookie

    Purpose

    Remembers whether you left the sidebar open or collapsed.

    How long

    7 days.

  • onboarding-draft-v2:<member id>

    Type

    Local storage

    Purpose

    Saves your onboarding answers on this device so you can pick up where you left off.

    How long

    Removed when you finish onboarding.

  • alphar:library-ask:v1

    Type

    Session storage

    Purpose

    Keeps your library Ask conversation while the tab is open.

    How long

    Until you close the tab.

  • my-alpha:draft:…

    Type

    Session storage

    Purpose

    Keeps unsaved My Alpha text if the page reloads.

    How long

    Until you save or close the tab.

Analytics

Vercel Web Analytics counts visits on every page, including sign-in, without cookies or storing anything on your device. Private links (invite, guest, calendar and sign-in links) are removed from page addresses before they are sent.

PostHog runs only once you are signed in to the member app or the console, and only on the live site. It keeps its identifiers in your browser's memory, so it writes no cookies or browser storage, and it knows you by your member ID, never your name or email. It records the pages you view and what you click, and records sessions so we can replay how a screen was used:

  • everything you type is hidden in recordings, on every screen;
  • all text on screen is hidden too, including names and image descriptions, except on three screens that show no member data: the library (but not its Ask tab), the FAQ and the events list;
  • the “Add to calendar” menu is never recorded, so your private calendar link stays out of analytics;
  • AlphaR team sessions are flagged so they can be left out.

[TBC: how members can object to or opt out of analytics and session replay]

7. How long we keep it

  • Your account and profile are kept while you are a member. If your membership ends, your record is kept so you can come back. [TBC: retention period for former members' data before deletion]
  • When you ask us to delete your account, we delete your profile, photo, employment history, activity record, My Alpha, event registrations and survey answers, circle memberships, introductions, contributions, saved items, Simulator reports, notification choices and your sign-in account. Where a record belongs to someone else and only mentions you (for example, as the person who checked a guest in), we remove the link to you and keep the record. Session notes you posted to a circle stay with the circle without your name. Your company's benchmark submissions stay with the company, because they describe the company, not you.
  • Event guests: 90 days after the event ends, a guest's name, email address and company are replaced with an anonymous placeholder, unless the guest has since been invited to join.
  • Analytics and session recordings: [TBC: PostHog retention period, and deletion of a member's analytics data on erasure]
  • Error reports and server logs: [TBC: Sentry and Vercel log retention periods]
  • Emails: [TBC: Resend email log retention period]
  • Backups: [TBC: database backup retention period]

8. International transfers

Our database is in the EU (Stockholm, Sweden) and our server code runs there too. Some of the providers in section 5 are based in, or may access data from, other countries, including the United States. When personal data leaves the UK or the EEA, we rely on an adequacy decision (such as the UK–US data bridge or the EU–US Data Privacy Framework, where the provider is certified) or on standard contractual safeguards: the UK International Data Transfer Agreement or Addendum, and the EU Standard Contractual Clauses. [TBC: confirm the transfer mechanism for each provider]

9. Security

  • All traffic is encrypted in transit (HTTPS only).
  • Passwords are stored hashed by our sign-in provider; we cannot read them.
  • Your company's benchmark figures are stored encrypted (AES-256). The key is held only by the platform's servers, never in the database, so someone browsing the database sees no figures.
  • Database access rules limit each member to the data they are allowed to see, and the console is limited to the AlphaR team.
  • Private links (invitations, guest pages, calendar feeds, email changes) use unguessable tokens, and are removed from page addresses before analytics are sent.
  • Error reports are configured to leave out who you are and what you typed.

10. Your rights

You have the right to:

  • Access the personal data we hold about you and get a copy.
  • Correct it. You can edit your profile and company details yourself, and change your name, email and password in Settings.
  • Delete it. Email us and we will erase your account and personal data as described in section 7.
  • Take it with you (portability). There is no self-serve export yet: email us and we will send your data in a commonly used format.
  • Object to processing based on legitimate interests, including analytics, and ask us to restrict processing while a concern is looked at.
  • Withdraw consent at any time, where we rely on it.

You can also turn off optional email types under Notifications in Settings, and turn off Open to intros on your profile.

To use any of these rights, email support@alpharealised.com. We may need to confirm it's you, and we will reply within one month.

If you are unhappy with how we handle your data, please tell us first. You can also complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint or on 0303 123 1113. If you are in the EU, you can complain to the data protection authority where you live or work.

11. Changes to this policy

When we change this policy, we will update it here and change the date at the top. [TBC: how members are told about significant changes]

12. Contact us

Refayce Ltd, 51 New Road, Porthcawl, CF36 5DH, United Kingdom.
Email: support@alpharealised.com