Legal
Privacy policy
Roleborn ("we", "us") operates roleborn.com. This page describes how the Phase 0 static marketing site handles information. We do not operate a product application or customer account database yet.
What we collect
- Founding deposits: when you place a deposit, payment and billing details are collected and processed by Stripe. Roleborn does not receive or store your full card number. Stripe may share your email and payment status with us for fulfillment of the founding-member list.
- Waitlist email: if you join the waitlist, we store your email address, a signup timestamp, and an optional source string (which form you used). Purpose: send build updates about Roleborn only. No drip marketing campaign. Delete on request by emailing [email protected].
- Email you send us: if you contact [email protected], we receive the content of that message.
- Analytics: Plausible Analytics runs cookieless aggregate pageview stats when configured. No personal profiles, no cross-site ads.
- Ads measurement (optional): Meta Pixel loads only if you accept the consent bar. Details in Meta Pixel (ads measurement).
- Technical logs: Cloudflare may process standard request logs (IP, user agent, path) for security and reliability. We do not run a heavy marketing tag manager on this site.
What we do not do (Phase 0)
- No Roleborn product user accounts
- No sale of personal data
- No inventing of customer lists for marketing claims
- No Meta Pixel load, and no Meta _fbp / _fbc cookies from this site, unless you accept the consent bar
Meta Pixel (ads measurement)
On the production site, we may use Meta Pixel for ads measurement and conversion tracking (including PageView). It complements server-side conversion APIs. The browser pixel is omitted from local and preview builds. On production it runs only after you accept the consent bar.
- If you accept on production, the site loads Meta's fbevents.js script, initializes pixel ID 2045578009373934, and sends a PageView event.
- Meta may set first-party cookies named _fbp and _fbc (and related storage) to measure ads and attribute visits. Those cookies are not set if you decline or ignore the bar without accepting.
- If you decline, we do not load the pixel script and we do not fire browser PageView through Meta on this site.
- Your choice is stored in this browser under the localStorage key rb-meta-pixel-consent (values: granted or denied).
Meta's own policy: Meta Privacy Policy
To withdraw consent: clear site data for roleborn.com in your browser, reload the site, and choose Decline on the consent bar. You can also email the contact address below and we will note your request. Clearing site data removes the stored choice so the bar appears again.
Processors
- Plausible Analytics - Cookieless aggregate traffic analytics. No personal data, no cross-site tracking.
- Meta Pixel - Optional ads measurement and conversion tracking. Loads only after you accept the consent bar. May set _fbp and _fbc cookies. See Meta Pixel section below.
- Stripe - Payment processing for founding-member deposits. Roleborn does not store card numbers.
- Cloudflare - Hosting and CDN for the static site and Pages Functions.
- Waitlist store (Cloudflare KV) - Email, signup timestamp, and optional source string for the marketing waitlist. Deleted on request via the contact email.
Their privacy policies govern data they process on their platforms.
Retention
Founding-member contact details needed to honor deposits and conversion offers are retained until you request deletion (subject to legal and accounting needs) or we complete / cancel the founding program with refunds as applicable. Waitlist entries expire automatically after about 400 days and can be deleted sooner on request. Meta Pixel browser cookies follow Meta's retention when you have accepted; declining prevents those cookies from this site.
Contact
Privacy questions: [email protected]
This is a short Phase 0 policy for a static site, Stripe-hosted checkout, a waitlist store, cookieless analytics, and optional consent-gated Meta Pixel. It will be revised when a product application, accounts, or additional processors launch.