Privacy
If you join the waitlist or sign up through any form on this site, we store the email you enter, which form you used, any note you add, and the page you came from in a signups database hosted on Neon, so we can follow up. If that database cannot be reached, the address stays in your browser and in our server log until it is saved. If you type your email into the waitlist form and leave before joining, we keep it as a draft for 30 days and may email you once with a link to finish; that email has an unsubscribe link. No page on this site shows that list; only the project owner reads it. Do not submit personal data you would not want associated with a product demo.
If you are in the pilot and ask for a sign-in link, the address you type is checked against the pilot list, and only an address on it is sent a link. The link works for 15 minutes.
The Rema CLI keeps its index in a .rema/ folder on your machine. Reading files, searching and capturing sessions send nothing to this site.
Analytics
Without asking, this site counts page views, which landing sections came into view, and clicks on “Copy setup for your agent”, the install line (and for which system), “Ask your AI” (and which one), Book a call, “Read on X” and Install and Docs in the menu, plus whether a waitlist sign-up was saved. Each count records only the page and section, the name of the site that sent you (such as t.co) and any utm tags in the link. It has no cookie, nothing stored in your browser, no identifier, no IP address and nothing you typed, so it is made whether or not you choose “Allow” below. Automated browsers are not counted.
The site also counts, on its own side, each download of the installer and the package: which file, the country the request came from, the site that linked to it, and the kind of program that asked (such as curl). It counts each sign-in step too: a sign-in started, a link sent, an address put on the waitlist, a sign-in refused, a terminal signed in, the daily check that keeps a signed-in terminal on or turns it off, and a waitlisted terminal asking whether it is in yet. A sign-in count carries a keyed hash in place of your address, so one person counts once, and a refused address keeps none. None of these counts store an IP address, a user agent or an email address, and the installer and the CLI send nothing extra for them.
This site can use PostHog, hosted in the US, to see which pages confuse people. It is off until you choose “Allow”; declining is the default, and nothing is loaded from PostHog before you answer. If your browser sends Do Not Track or Global Privacy Control, we never ask and it stays off.
With your consent it records only these events: a landing page view, how far down the landing you scrolled (which sections came into view), clicks on “Ask for access”, whether a waitlist signup succeeded or failed, copying the setup instruction or the install command, blog post views, the start and outcome of a terminal sign-in (signed in, waitlisted, link sent or failed), and whether an “Add an app” request succeeded or failed. No email address is ever sent: not as an event, not as a property. Page addresses are sent without their query strings. There are no ads and no advertising identifiers, and it is not used to follow you to other sites.
On the public pages it may also record a session replay, with every form field masked, email fields included. There is no replay on the pilot sign-in, the terminal sign-in or the pilot dashboard. The dashboard sends nothing except that one “Add an app” outcome. The Rema CLI and its hook send nothing to PostHog at all.
Posts from X on the blog
Some blog posts start with the post as it appears on X. To show it, your browser loads X's embed script from platform.twitter.com, with X's do-not-track option on, which tells X not to use the visit to personalise what it shows you; X's own privacy policy covers what it receives. If your browser sends Do Not Track or Global Privacy Control, if you declined analytics above, or if the script is blocked, nothing is loaded from X and you see a copy of the same post served from this site instead.
Questions: support@askrema.com.