How visitor data and your account are protected — 5 questions.
Iteratist does not use third-party cookies. Visitor identification is handled via localStorage in the visitor's browser — a more privacy-friendly approach than cookies that also avoids the Intelligent Tracking Prevention (ITP) restrictions applied to cookies in Safari and other browsers.
Iteratist collects only the data necessary to run experiments:
Iteratist does not collect names, email addresses, IP addresses, device fingerprints, or any other personally identifiable information.
Iteratist is designed with privacy in mind. The platform does not collect personally identifiable information and does not use third-party cookies. The anonymous visitor ID stored in localStorage is a random string with no connection to a person's identity. Because no personal data is collected, the GDPR consent requirements that apply to advertising cookies or personal data processing do not apply to Iteratist's core tracking. However, you should consult your own legal counsel regarding your specific obligations as a data controller for your website.
Yes. All data is transmitted over HTTPS. Account passwords are hashed using industry-standard algorithms before storage — we never store plain-text passwords. Session tokens are cryptographically random and expire automatically. Your experiment data is logically isolated from other users' data and is never shared or made visible to other accounts.
Visitors who use an ad blocker or block JavaScript will automatically be excluded from experiments — they'll see your default page. Visitors who clear their browser's localStorage will lose their assignment and receive a fresh random ID. Since Iteratist collects no personally identifiable information and uses no third-party cookies, most standard opt-out frameworks (such as cookie consent banners) do not apply to Iteratist's tracking.
Set up in minutes — no developer or credit card required.
Get started free