Privacy note
X PROJECTS ApS (CVR 41736720), c/o Christensen Kjærulff, AIH, Østbanegade 123, 2100 København Ø, Denmark, operates People On Pedals and is the data controller for this intent-validation campaign. General questions, privacy, access, correction, deletion or consent-withdrawal requests can be sent to christian@peopleonpedals.com.
What the forms record
A public YES is click-only. It records an anonymous interest signal: a hashed browser visitor identifier or, for signed former backers, a hashed non-guessable backer token, plus source/UTM attribution and timestamps. Colour is stored only if you tap a colourway. A public YES does not collect region or motor. POP SUV interest is not part of a public YES; further involvement is only through Build POP with us. Signed former-backer yeses, public anonymous yeses and optional email-update subscribers are stored and counted separately and are never merged.
Optional “KEEP ME POSTED” email is collected only after a YES, only if you ask for it, and is confirmed by a separate email. It does not change whether your YES already counted.
The Build POP with us form records a short first touch: name, email, country, a short note, the selected path, and only the few path fields needed now (relevant area; company, market and service capability; or investor type, optional organization, optional range and acknowledgement), plus source and allowed UTM attribution, required contact acknowledgement, any separate optional marketing request, server timestamps, verification-token hash and delivery/verification status. It does not infer or retain your IP location, accept attachments, or collect accreditation, identity or financial documents.
Why
For a YES: to measure genuine interest in POP without holding that signal hostage to email. For optional updates: to send a confirmation message and later tell you if POP goes live. For Build POP with us: to verify and respond to an expression of interest that you requested; it is not recruitment, an appointment, or an investment offer. Optional marketing is not required for a YES or for a response. This remains intent validation, not a preorder; nothing is due today.
Analytics
Cloudflare estimates the request country at the edge before the browser can create an analytics identifier. The browser receives only a coarse rule: opt_in, notice_opt_out or unknown. We do not store or send the estimated country or US state to Mixpanel.
In the EEA, UK, Switzerland and Canada, and whenever location is unknown or not yet reviewed, analytics are off unless you choose “Accept analytics.” In the United States and Brazil, the current rule permits the same limited analytics after clear notice, with an immediate “Opt out” control. Global Privacy Control is honored everywhere and keeps analytics off. “Privacy choices” in the footer lets you change the setting anytime. This deliberately conservative operating matrix is reviewed quarterly and does not claim that every visitor or use case is governed by identical law.
When permitted, the site sends deliberately limited event funnels through our Cloudflare Worker to Mixpanel’s EU-hosted project (a processor, not first-party storage): page visits, analytics choice, YES placements, signed versus public anonymous yeses, optional post-YES preferences, optional email steps, sharing, SUV interest, colour view/interaction/selection and the selected involvement pathway. It includes a random pseudonymous browser ID plus first- and last-touch campaign attribution. It never sends your email, name, country, company, website, verification token, full referrer URL, precise location, fingerprint, session recording, investment range, free text or other submitted answers. We do not sell or share analytics data for targeted advertising, use it for advertising profiles, or load Mixpanel’s browser script.
Cookies and browser storage
We set no cookies. The site uses first-party localStorage records. pop.analyticsConsent.v1 remembers an accept/reject choice, its source and time for up to 365 days; this preference record remains after rejection so the site can remember it. pop.analyticsId.v1 holds one random UUID for up to 180 days from the most recent permitted analytics activity. pop.analyticsAttribution.v1 holds allowed first/last UTM fields for up to 180 days from that activity. pop.yesVisitor.v1 holds a random UUID, with an explicit 180-day expiry, used only to recognise a repeat public YES in that browser. Expired analytics and visitor records are removed on the next visit. Opting out or withdrawing immediately deletes the analytics UUID and attribution record.
Processors
Cloudflare serves the site, stores encrypted commitment and involvement records in D1 and proxies permitted analytics events. AgentMail sends verification and acknowledgement messages and delivers verified involvement notifications to the published POP inbox. Mixpanel processes only permitted, pseudonymous analytics in its EU data residency environment. These processors receive only the limited data needed for their role.
Retention and rights
Signed former-backer YES records (hashed non-guessable backer identity) and public anonymous YES records (hashed browser visitor identity) are retained for up to 12 months for campaign validation. Pending optional-email confirmation records are deleted automatically no later than 7 days after the request if they are not confirmed. Confirmed optional-email subscribers are retained until you unsubscribe or the address is no longer needed. Unverified Build POP introductions are deleted automatically no later than 7 days after submission. Verified Build POP introductions are retained for up to 12 months from the most recent submission, unless an active documented relationship creates a new purpose; they are then deleted or archived outside this intake register. You may request access, correction, deletion or withdrawal at the address above. Every future marketing email will provide an unsubscribe route before marketing sends begin.
Security
Optional update emails and complete involvement payloads are encrypted before storage. Verification tokens and YES identity keys are stored only as hashes. Interest-email deduplication uses a separate keyed hash, and records are unique per email and pathway. Involvement records remain separate from YES signals and cannot affect signed-backer or public-anonymous totals.
Last updated 2 September 2026. Privacy-regime review due by 30 November 2026.