The things people ask before trusting a new analytics product with their traffic. If yours isn't here, email support@evarist.ai.
An email address. We send a one-time sign-in link, so there is no password to set, and no credit-card step anywhere in the product. (Evarist is free during the beta. Add it from the Claude connector directory and sign in.)
Your email address, the version of our terms you accepted and when, your chat conversations, the facts you ask Evarist to remember and those it suggests, the settings and connections you create, and a record of your activity in the product. We never ask for your name. Connection tokens for your AI are stored only as hashes.
Read your analytics, and set up what you measure: tag events, set conversion goals, declare a visitor property. Adding a website, its domains and your teammates all live in the app instead. Changes go through tools marked as writes, so assistants that honour that marking ask you to approve them first; new tagged events are previewed before they are saved. What it can and can't do is spelled out in the docs.
Separately, after the first crawl that finds something to tag, it also creates a small number of event tags on its own, without asking, but only ones it has verified will work. It does this once: click tags right after that crawl, page tags once your site has enough traffic to check them against. Once each of those has happened, later crawls and refreshes only suggest tags, they never add them. They're labeled "Evarist added this on its own" under Tagged events, and you can remove any of them; goals are never created this way. More in Track what matters.
Touch your website: no code, no content, no deploys. Spend money, because Evarist has no billing system. Delete your analytics. Or reach any account but yours: every analytics query you or an AI runs on your behalf runs under a database account created for you that can only read your sites, enforced by the database, not by the AI's good behavior. Details in how Evarist handles your data.
No. Evarist doesn't train models on your data, and Anthropic, the one AI provider we use server-side, doesn't train on API traffic. Your own AI client (claude.ai, ChatGPT…) processes your questions under your agreement with that provider, not ours.
What a query can reach is decided by which account authenticated, not by what the prompt says. A malicious instruction can't widen access. More in the AI layer.
No. It's about 14 KB compressed. It loads asynchronously after your page and never blocks rendering. If it ever fails to load, it fails silently; your site is unaffected.
Behavior: pages, referrers, scroll depth, time on page, the events and conversions you tag. Identifiers are random first-party cookies: no third-party cookies, no fingerprinting. Visitor IP addresses are masked before they are stored in our analytics data. Apart from the optional email capture below, it doesn't read what people type: no form contents, no keystrokes. On a Shopify store, our checkout pixel also records the search terms visitors submit in the store's search, and drops any term that holds an email address or a phone number before sending it, except a term made only of digits, which it keeps as a likely product code.
(One optional email-capture feature connects form signups to visits. It's off by default: we switch it on for your site when you ask, it captures nothing without the visitor's consent, and captured email addresses are deleted after 12 months. How it works.)
Yes. By default the snippet sets its cookies as soon as it loads, so fire it from your consent tool once the visitor agrees. And if your compliance posture requires no identifying cookie before consent, switch on consent mode: visitors are still counted from their first page, but identifiers stay in per-tab session storage, with no identifying cookie, until your banner signals consent. On Shopify, the Evarist app embed checks the store's Customer Privacy signal before loading the tracker; a store whose theme doesn't provide that signal gets the tracker at page load.
Open Settings, Overview in the app. It says whether events are arriving and when the last one did. A real visit shows up within about five seconds.
You remain the controller of your visitors' data; Evarist processes it on your instructions under a DPA that is part of the terms. The security page has a section written for your DPO, and all documents are public.
Remove the snippet. The tracker stops immediately; nothing keeps running. Cookies it set expire on their own (the session 30 minutes after the last page or after 4 hours at most, the visitor 13 months after the last visit).
On AWS (us-east-1), on the analytics infrastructure Evarist shares with Wisepops. Sub-processors are listed publicly.
Identifiable visitor data: 25 months, then deleted or anonymised; after that we keep daily totals, which hold no visitor identifier. Captured email addresses: 12 months. An analysis's result: as long as its site, while the data behind it (its steps, queries and their results, and what your team did with its recommended actions) goes 25 months after the period it covers. Account data: for the life of your account.
Out: ask your AI; every query result is yours to keep. Deleted: deleting your account removes your sites and configuration immediately. Already-collected visitor events aren't deleted with it; they follow the 25-month retention, unless you ask us to delete them, which we do in our live systems within 30 days of your request; archived copies go at the end of the 25-month retention.
You, the teammates you invite, and for a Shopify store, the staff Shopify lets open Evarist. The Wisepops engineers who run the service can access it to operate and support it, and can open a chat conversation or an analysis for the reasons our security page lists, each opening recorded. Isolation between customers is enforced by the database itself. See tenant isolation.
The team behind Wisepops, the onsite-engagement platform 1,500+ brands rely on. Evarist is founded by Ben Cahen, Wisepops' founder: same team, same infrastructure discipline, new product.
Beta means the product evolves weekly, not that your data is at risk. The isolation, encryption and legal terms on the security page are already in place, and Evarist is live with real companies in ecommerce, media and education.
support@evarist.ai. No form, a direct conversation with the team.