Privacy
This notice covers reapr.dev and the Reapr Cloud waitlist. The rpr command-line tool has its own notice: see
Telemetry.
The website
reapr.dev sets no cookies and uses no local storage. Fonts and images are served from reapr.dev itself. Two third-party scripts can load, both from Cloudflare: the Web Analytics script, only when your browser does not ask for privacy (see below), and the Turnstile spam check, only on pages with the waitlist form.
The site is hosted on Cloudflare Workers. Like any web host, Cloudflare receives the IP address and request details of each visit in order to deliver the page, under Cloudflare’s privacy policy.
What the site measures
Two things, both without cookies, and neither tied to a person.
Page views, with Cloudflare Web Analytics. It counts views in aggregate: the page, the referrer, the
browser and device type, the country, and page-load timings. It sets no cookies and keeps no state in your
browser. Script: static.cloudflareinsights.com, reporting to cloudflareinsights.com.
Five product events, sent through reapr.dev itself. The page posts them to /api/event on reapr.dev. The
site’s Worker drops anything not on this list, then forwards the event to PostHog (US cloud):
| Event | Properties | When |
|---|---|---|
install_copied |
command: install or run |
You copy the install or run command. |
cta_clicked |
cta (which button), page (the path) |
You click a main call-to-action button. |
guide_viewed |
slug (which guide) |
You open a guide. |
skill_install_copied |
which (which command or text) |
You copy an install command or the agent prompt on /skill. |
waitlist_submitted |
interests (the boxes you ticked) |
You join the waitlist. Never your email. |
Each event gets a new random id, so events cannot be linked to each other or to you. PostHog is told not to create a person profile and not to look up a location. PostHog receives the event from Cloudflare’s servers, not from your browser, so it never sees your IP address. The Worker stores nothing about the event.
How to opt out. Turn on Global Privacy Control or Do Not Track in your browser. With either one set, pages
load no analytics script and send no events, and the Worker discards events and does not report waitlist
sign-ups. A content blocker that blocks static.cloudflareinsights.com and /api/event has the same effect.
The Reapr Cloud waitlist
When you join the waitlist on /cloud, Reapr stores:
- your email address,
- the interests you ticked,
- the time you signed up, and the time of your last change if you sign up again (UTC),
- a keyed hash of your IP address.
Why: to email you when Reapr Cloud opens, and to learn which features matter most. The IP hash exists only to limit how many sign-ups one address can send per minute, against spam. It is an HMAC-SHA-256 with a secret key, so it cannot be turned back into your IP address without that key. Your IP address itself is never stored.
Spam check: the waitlist form, and only the form, uses Cloudflare Turnstile. It runs in your browser when the form loads and gives the form a one-time token, which reapr.dev checks with Cloudflare when you submit. Turnstile sets no cookies for this. What Cloudflare processes is described in its Turnstile Privacy Addendum. Turnstile needs JavaScript, so the form cannot be sent without it.
If you sign up again with the same email, the interests you tick are added to the ones you ticked before, and the time of the change is stored next to the first sign-up time.
What we do not do: sell, share or rent the list, send it to a mailing service, or use it for anything other than Reapr Cloud announcements.
Where: in Cloudflare Workers KV, on Reapr’s Cloudflare account.
How long: until the list is no longer needed for Reapr Cloud announcements, or until you ask to be removed, whichever comes first. Rate-limit counters are kept by Cloudflare’s rate limiting for one minute and are not stored with your entry.
How to ask for access or deletion
There is no email address for Reapr. To see or delete your waitlist entry, open a private report on GitHub with the email address you signed up with. Only the maintainers can read it. For questions about this notice, use GitHub Discussions.
Changes
Changes to this notice are published on this page, with the date below.