How this site uses your data
AmpLabs.ai Inc operates amplabs.ai. This page explains how we use visitor data and the records of our former waitlist.
Visits and your privacy choices
Vercel hosts this site and receives technical request information, including your IP address and browser details. Hosting, form storage and security checks work independently of your optional tracking choices.
Your default depends on where you visit from. Vercel tells the site which country a request comes from. The site uses only whether that country is in the European Economic Area, the United Kingdom or Switzerland, and does not store it. If we cannot tell, we treat the visit as coming from one of these places.
In the European Economic Area, the United Kingdom and Switzerland, optional analytics and advertising measurement stay off until you turn them on in Privacy choices. Elsewhere, both are on by default and a notice bar at the bottom of the page tells you so. You can turn either off in Privacy choices, which you can open from that bar or the site footer. If your browser sends a Global Privacy Control signal, both stay off unless you turn them on.
When analytics is off, PostHog still counts pageviews and clicks on “Sign up” links without cookies or identifiers stored in your browser. Each of these events includes the sanitized page address, the domain of the site that referred you (not its full address), campaign parameters on that page, whether its link had an ad click identifier (not the identifier itself), and browser and device details. PostHog’s servers count visits with a hash of information such as your IP address and browser, using a secret that changes daily. Nothing else is collected in this mode, and Google services do not load.
When analytics is on, PostHog uses cookies and browser storage to recognize your browser across visits. It also records clicks and form submissions (not what you type), heatmap and scroll data, when you leave a page, page-performance measurements and session recordings. A session recording shows what the page displayed and how you moved, scrolled and clicked. Form fields are blocked from recordings, typed values are masked, other form text is masked, and email-like text is replaced. Google Analytics, when enabled, measures pageviews and clicks on “Sign up” links.
Advertising measurement lets Google Ads count clicks on “Sign up” links that follow an ad click, when enabled. Ad personalization and Google Signals are not enabled.
With analytics on, the campaign source, medium, name and keyword of the first page you visit, the domain of the site that referred you, whether its link had an ad click identifier, and how many pages you view are kept for the rest of that browser tab’s session so that a sign-up click can be credited to the campaign. With analytics off, these values are recorded only on the pageview. With analytics on, PostHog also counts how many visits this browser has made, kept with its other analytics storage for 180 days, so that a visit can be shown as new or returning.
Our team receives a short Slack notice from PostHog each time someone clicks a main button on the site, such as “Sign up”. It says which button and page, how the visit arrived (ad, tagged link, search engine, referring site, or direct, with any campaign, ad group and keyword), the page the visit started on, the approximate city, region and country, the local time there, and the browser, operating system, device type, screen size and language. With analytics on, it also says whether this browser visited before and how many times, with links to the session recording and to that browser’s earlier events in PostHog. About ten minutes after a visit with such a click, form activity or a signup ends, a second notice summarizes it: the pages viewed in order, the time on the site, the labels of buttons and links clicked (with analytics on), and whether a signup happened. These notices do not include your IP address, name, email or anything you type.
These services can receive browser and device details, page and referring addresses, and campaign parameters. Google can also receive the ad click identifier in the page address; PostHog receives only whether one was present, and only the domain of the referring site. A sign-up click event contains only the name of the button. This site does not identify visitors to analytics. PostHog requests go to its United States cloud at us.i.posthog.com.
Admin and unsubscribe pages do not load these optional trackers. Automated browsers, such as crawlers and testing tools, do not load them either. Other public URLs and referrers are sanitized to remove non-attribution query parameters and fragments.
Sign-up and the former waitlist
“Sign up” links on this site open AmpLabs sign-up in the AmpLabs app (hub.amplabs.ai). This site does not receive what you enter there.
This site and the AmpLabs app send analytics to the same PostHog project. With analytics on, a link from this site to the app also carries this browser’s random PostHog visitor ID, so that our analytics can connect your visit here with your visit to the app. If you then create an account or sign in, the app links that visitor ID to your account in PostHog. With analytics off, links to the app carry no ID.
Until 21 October 2026, this site had a waitlist for beta access. The waitlist is closed, and its old address now opens AmpLabs sign-up. We keep the stored waitlist records as described below.
The waitlist form asked for your email address and, optionally, your name, company and whether you are interested in testing, simulation or both. If you left the company blank and your email address was on a company or institution domain, we recorded that domain as your company. We keep signup details, dates and access status in a private Vercel Blob store to manage related communications.
- Vercel BotID
- BotID checked browser security information before a signup was saved. A blocked or unavailable check prevented the signup and its notifications.
- Resend (email delivery)
- Our configured mailer attempted a confirmation after saving your signup. Resend received your email address and the message, including your first name and company if you gave them, and an unsubscribe link containing your email address and a signed token.
- Team notification webhook
- The configured webhook received signup details, including your email, any name, company and interest you gave (or the company domain taken from your email), signup time and any use-case text, for team follow-up. If analytics was on when you signed up, the notice also included the campaign source, medium, name and keyword that brought you to the site, whether you arrived from an ad click, your landing page, how many pages you viewed and a link to your PostHog session recording. This information goes only into the team notification; it is not added to the stored signup record.
- AmpLabs app (hub.amplabs.ai)
- If we invited you, you received an account-setup link. The app used invitation and email information to verify your access.
Eligible blocked submissions were kept in a separate private review list to find people blocked by mistake. This includes bounded name, email, company and interest fields, time and rejection reason; it did not create a signup or send notifications. The review interface shows the last seven days.
Playground and parameter downloads
Parameter access is delivered by email. A single-use link confirms access to that inbox and signs you into the AmpLabs app to view, edit or download the selected parameters. Clerk handles this passwordless sign-in and receives your email address and account/session information. We record the request and email-link verification. Older download-only links can also record file access and create a browser download session for seven days. Model-update emails are a separate choice.
A live run in the playground sends the settings you chose to the AmpLabs playground service. Before the first live run of a visit, Cloudflare Turnstile checks your browser; Cloudflare receives your IP address and browser details for this check. Your browser counts live runs in local storage to decide when to suggest logging in; the count is not sent to us.
“Download parameters” asks for your email address and, optionally, your organization and role. We save them, the cell and the time in a private Vercel Blob store as a record of the download, and our team receives a short notice with these details. Analytics, when on, receives only the cell, the role category and whether you ticked the box, never your email or organization.
One box is optional. “Email me new free cell models and parameter sets” lets us send you such news. We store its state with the time and the text you saw. In the European Economic Area, the United Kingdom, Switzerland and Canada, or when we cannot tell your country, the box starts unticked; elsewhere it starts ticked. You decide before you submit. Every such email has an unsubscribe link.
“See inside the cell” asks for your email address and emails a single-use sign-in link. The link saves the run in your AmpLabs account and opens the simulation tool with the public playground settings you selected. “Continue in AmpLabs” opens the simulation tool in the AmpLabs app with those settings, which may require sign-in. “Try it with your own data” opens AmpLabs sign-up, then the parameterization tool. It does not carry your playground settings and does not send any files.
Talk to an engineer
The “Talk to an engineer” form asks for your email address and, optionally, your name, organization and what you want to model or which cell and data you have. We save them with the time in the same private Vercel Blob store, and our team receives a short notice with these details and your message so that we can reply by email. Vercel BotID checks the browser first. The optional box works as described for parameter downloads above; your request never depends on it. Analytics, when on, receives only whether you ticked the box and whether the request was sent.
Your data and contact
We keep the former waitlist records and the information from the forms on this site to manage related communications. Opting out marks your record as not interested; it does not delete the stored record.
For privacy questions or to request access to or deletion of your data, contact info@amplabs.ai.