Everything on your server
One Node process with SQLite that you run yourself. Visitor data never leaves your network, because it is never sent anywhere.
PRPrivacy & compliance
Test without asking
the legal department.
Most testing tools send your visitors to somebody else’s vendor. abdriven runs entirely on your own server, there is no third party for data to be transferred to.
- Self-hosted, no vendor in between
- No IP addresses, no profiles
- Consent as a technical switch
The difference
Not “privacy-friendly”.
No third party at all.
Other vendors explain how carefully they handle your visitor data. With abdriven that transfer does not exist: the snippet, the analysis and the database all sit on your infrastructure.
Delivered from your own domain
The snippet loads from a subdomain of your website, for example t.your-domain.com. To the browser that is not a third-party request.
No IP addresses
abdriven stores no IP addresses, no names, no e-mail addresses, and links nothing across websites.
Consent that actually takes effect
With data-consent="required" nothing happens before consent: no identifier, no event, no request.
Aggregated results only
Analyses, reports and exports contain totals and rates, no individual visitors, no event log.
A revocation that cleans up
SplitTest.revoke() stops measurement, removes applied changes and clears this website’s local visitor data.
To be precise
What abdriven stores ,
and what it does not.
An A/B test needs exactly one thing to persist: which variation this browser has seen. Otherwise the same visitor sees something different on their next click and the result is worthless.
- Stored: an anonymous identifier created in the browser, the assignment to a variation, and aggregated counters.
- The assignment itself is a salted hash of experiment and identifier, no visitor can be reconstructed from the database.
- Not stored: IP address, plain user agent, form contents, page contents, mouse movements.
- Segments (device, source, new versus returning) are recorded once at first contact, with no identifier alongside.
- Browsers without usable local storage are not enrolled at all.
Inside the company
What IT wants
to hear.
Access, keys and changes are traceable, not because it sounds good, but because an audit asks for it.
- Activity log: who started, paused or reconfigured which experiment, and when.
- Roles per level, agency, client, website, with read-only access for everyone who only needs results.
- API tokens are limited to websites, expire after 30, 90 or 365 days, and are stored only as a SHA-256 hash.
- Shared report links expire, can be revoked individually, and are likewise stored only as a hash.
- Passwords as salted scrypt hashes, sessions as HttpOnly cookies, additionally Secure over HTTPS.
Honestly
What is not there yet today
- Two-factor login and single sign-on do not exist yet. If you need them for sign-off, talk to us first.
- E-mail invitations and password recovery are missing; access is created by an administrator and credentials are passed on through your own secure channel.
- Stored secrets such as webhook signatures sit unencrypted in the database, protect the file accordingly.
- This text is not legal advice. Whether and how you obtain consent is decided by you and your own responsible people.
Coming
Already planned
None of this is built yet. It is here so you know what you can rely on, and what you cannot rely on yet.
Two-factor login and SSO Coming
Login with a TOTP app and single sign-on over SAML for companies with their own identity management.
E-mail invitations Coming
Access through an invitation link instead of handing over a password, including password recovery.
Encrypted secrets Coming
Webhook signatures and other stored keys encrypted in the database.
Retention periods Coming
Configurable deletion periods for raw data per website, cleaned up automatically.
A data processing agreement template Coming
A template for processing on your behalf, in case abdriven is operated for you rather than by you.
FAQ
Privacy & compliance
Do I need cookie consent for A/B tests?
That depends on your setup and your legal assessment. abdriven is built for both routes: with data-consent="required" it stays quiet until your consent manager calls SplitTest.consent(). You can also load the snippet only after consent.
Where is the data?
Wherever you run abdriven. There is no transfer to us, because the software runs on your server and its database lives there.
Can I switch abdriven off in sensitive areas?
Yes. Experiments only run on the page paths you allow. Customer accounts, checkout or internal areas stay out of it as long as you do not target them.
What happens when a visitor withdraws consent?
SplitTest.revoke() stops measurement, undoes applied changes and clears this website’s local data. Anonymous totals already counted remain, because they cannot be attributed to a visitor.
Product
More of the product
Make your next change an informed one
Less guesswork.
More now we know.
One question is a good place to start.