What you type into the early access form
Your work email, company, role, number of production databases, and primary database engine — all of which the form requires — plus an optional note. Nothing else on this site asks you for anything. We mark those fields as required because we cannot assess an application without them; nothing obliges you to apply.
How you reached us
The campaign parameters in the link you followed (utm_source, utm_medium, utm_campaign, utm_term, utm_content), the address of the page that referred you, and the path you first landed on. This is read from the URL in your own browser. It is attached both to your application, so we know which channel it came from, and to the analytics described next.
What the analytics records
One entry for each page you open, and a short list of named events: that the application form scrolled into view, that it was submitted, that the submission succeeded or failed, that a call to action or an outbound link was clicked, and that a research article was opened and read to the end. Azure Application Insights adds the technical fields it collects by default, including your IP address and your browser and device type. A failed submission records the reason it failed, never what you typed.
What we deliberately do not collect
No cookies. Nothing written to your browser storage. No advertising or social pixels, no third-party trackers, no session recording, no fingerprinting, and no fonts or scripts pulled from another company’s servers. This is why the site has never shown you a cookie banner: nothing is stored on your device to ask you about. The analytics also runs without the identifiers that would let us recognize a returning visitor, which costs us the ability to count people rather than page loads — a trade we made on purpose.