Privacy

Fellow Future stores member profiles, organization records, opportunity participation, and an append-only evidence trail aligned with the FF Impact Protocol in Supabase Postgres. Authorization is enforced with row-level security under four access levels — public, member, restricted, confidential. Restricted and confidential documents stay with the owning organization. This notice will be replaced when counsel ratifies the public policy. The public policy is at fellowfuture.com/privacy-policy.

How the platform is measured

Every page reports one anonymous pageview to a first-party collector run by the Sarnian Group: the path, the referrer and any campaign tag, plus a visitor hash derived from the network address and browser and a salt that changes daily. No cookie is set and no identifier is stored, so a visit cannot be joined to a person or to another day. Do Not Track and Global Privacy Control switch it off.

Recognising an organisation, if you agree

The public landing page can additionally run LeadLens, a visitor-identification script operated by the Sarnian Group on Fellow Future's behalf. It sets one first-party cookie (a random identifier, kept for a year) and looks up the organisation behind a network address in a business-contact database. It does not identify an individual unless that individual gives their details in a form, and it never runs inside the members area. Nothing runs until you agree in the notice shown on the landing page; declining is remembered for as long as agreeing would be, and Do Not Track or Global Privacy Control suppresses the notice entirely. To withdraw consent, use "Cookie choices" at the foot of the landing page; declining there deletes the cookie straight away. The lawful basis is consent (GDPR art. 6(1)(a)). Data is held in Supabase Postgres in the United States; requests to access, correct or erase it go to the address on the public privacy policy.