Privacy.

The short version

• A visitor is a random number kept in their own browser, not a name. We never store their IP address.
• Anything the tracking code sends that looks personal is redacted before it reaches our database. An email address becomes a one-way fingerprint so a sale can be matched to a visit, and can never be read back.
• We never record screens, keystrokes, or what anyone types into a form.
• When you connect Google Tag Manager, we use that access once to add one tag, then throw the access away. No refresh token is ever issued, so nothing stays open behind you.
• No data is sold, and none of it goes to an advertising network or a data broker.

Two different people are in this policy

You — the person or business with a Meet Eric account. We decide what we collect about you, so for your own data we are the controller.

Your website visitors — the people whose journeys Eric reads. That is your data about your customers. You decide what happens to it and you are the controller; we only hold and process it for you. If one of your visitors asks you to delete what you hold on them, write to us and we will find and delete their rows.

What the tracking code collects

A small script, served from our domain, on every page it is installed on (on most sites it is a short block of a few lines). Here is everything it sends, and it is a complete list rather than a summary.

How personal data is kept out

The properties you can attach to an event are the one place an email address could reach us, so they are filtered on arrival, not later:

• An email address becomes a one-way fingerprint, salted per business. Two visits by the same person match; nobody, including us, can turn the fingerprint back into the address.
• A card number, password, national identifier, token or anything under a name that suggests one is replaced with [redacted] before the row is written.
• A string that reads like a phone number or a postal address is replaced the same way.

What the tracking code never does

• No session recording, no screen recording, no keystroke capture.
• What it does keep is where on a page people click and how far down they scroll, as positions and counts, never the words or a picture of the screen. That is how Eric sees where visitors get stuck.
• No reading of form fields, and no password field is ever touched.
• No IP address stored. To stop abuse, requests are counted per caller using a scrambled form of the address, and those counts are deleted within 48 hours.
• No following anyone across other websites. The visitor number lives in your site’s own browser storage and cannot be read by any other site, ours included.
• No sharing with advertising networks, data brokers or anyone buying audiences.
• No fingerprinting of devices, and no third-party tracker loaded alongside ours.

Cookies and consent

The tracking code sets no cookies. It keeps the two numbers above in the browser’s own local storage, which is readable only by your site, and a few small flags listed on the cookie notice. On our own app, the cookies we set are the ones that keep you signed in and the short-lived ones that tie an install to the browser that started it. A referral code from someone’s link is held only in the open page and the address of your sign-in links, never stored on your device.

We do not run analytics, advertising pixels or session recording on our own website or app.

Whether your visitors must agree before they are measured is your call: you know which of them the law covers. On a site running OneTrust, Cookiebot or Google Consent Mode, the script waits for a yes to analytics by itself and stores and sends nothing before it. With any other consent tool, either load the script only after consent (anything sent before it loads is queued, so firing it from your consent tool or on a consent trigger in Tag Manager loses nothing), or add consent=required to the script’s address and call ec("consent", "granted") when the visitor agrees, or ec("consent", "denied") if they refuse. Global Privacy Control in the visitor’s browser always stops it.

Google Tag Manager: exactly what the access is used for

The quickest way to get Eric onto a site is through the Tag Manager the site already runs. If you choose it, you sign in with Google and we ask for three permissions and no others.

The whole install, step by step

• We list the Tag Manager accounts and containers your Google account can reach, so we can find yours.
• We read your website’s own pages to see which container it actually loads, and we only touch that one. A container id typed into a browser is never trusted.
• We create a Tag Manager workspace of our own called Meet Eric (installs before 28 October 2026 called it EverConvert). Whatever you have half-finished in your own Tag Manager workspace is left exactly as it was.
• Inside it we add one Custom HTML tag — the Meet Eric script, with your site key already in it — on the All Pages trigger. Nothing else is added, edited or deleted.
• We create a version from that Tag Manager workspace and publish it, because a tag that is not published is not live.
• We then fetch your published container the way a browser would, and check our tag is really being served. That is how the screen can tell you it worked instead of hoping.

What we keep afterwards, and for how long

• Not the access. We ask Google for online access only, so no refresh token is ever issued. The access token lasts about an hour at most, and we delete our copy the moment the install finishes, fails, or the attempt expires.
• We keep the container id we published to, the permissions you granted, and the time — so the screen can tell you what happened and so you can see it later.
• We never read your other tags, your other containers, your Analytics, or anything else the permissions would technically allow. The install writes one tag and reads back the same container.
• Data from these permissions is never sent to a language model, never used to train any model, never used for advertising, and never shared with anyone.

Google API Services User Data Policy

Meet Eric’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Taking it back

You can remove our access at any time at myaccount.google.com/permissions. Because we hold no standing access, there is usually nothing there to remove after an install has finished. Removing access does not remove a tag that is already published — to stop the measurement, delete the Meet Eric tag (called EverConvert on older installs) in Tag Manager and publish, or ask us and we will tell you exactly which tag it is.

Slack

Eric lives in Slack, so connecting it is how you talk to him. When you add him we ask for the permissions that let him do exactly that: read messages that mention him, messages sent to him directly and replies in threads he started; post and reply under the name Eric; create and join the channel he works in and invite you to it; and see the names of the people in your Slack workspace, the workspace’s name and the email address on your own Slack profile. Slack lets an app see other messages in a channel it is in; Eric ignores them.

The email address on your Slack profile is used only to match you to the Eric account you are already signed in to. Connecting Slack does not create an account or sign anyone in. We store your Slack workspace and channel ids, the messages Eric posts, and what you ask him.

What you ask Eric is read by a language model to write his reply. That happens through the Lovable AI Gateway, using models from Google, Anthropic and OpenAI. We have switched off the use of our content for model training in our Lovable account, and the providers are listed below. Nothing from your Google Tag Manager permissions is ever included.

The other tools you connect

You can connect Google Analytics, Search Console, Stripe, HubSpot, Shopify and others so Eric can line up what happened on your site with what happened in your business. Those connections are made through Composio, which holds the tokens; we ask each one for the least it can answer with, and for the analytics and revenue tools that means read access only. You choose each one, and you can disconnect any of them from Connections whenever you like, which revokes the token.

The Shopify app and its checkout pixel

Shopify’s checkout runs on Shopify’s own pages, where the tracking code cannot go, so Eric’s Shopify app adds a checkout pixel instead. It reports three things: a checkout was started, payment details were submitted, and an order was completed, each with the order total, the currency and the order number. It reads the same visitor and session numbers the rest of your site uses, so a sale joins the journey that produced it. It never sends us a shopper’s name, email address, postal address or payment details.

Uninstalling the app in Shopify stops all of it and removes what we hold about that store. The order number is kept so the same order is never counted twice.

Who else touches the data

We add a processor only when it is needed to run the product, and we do not sell, rent or trade data with anybody.

How long things are kept

• Raw website events — the visitor-level rows — are kept for up to 13 months, then deleted. Ask us to delete them sooner and we will.
• Messages sent and received through Eric on WhatsApp, Slack and SMS are kept for up to 12 months. The delivery record behind them — sent, delivered, failed, with no content — is kept for 24 months for billing and disputes.
• An install nobody finished is cleared automatically: the token is dropped and the attempt is marked as never completed.
• Tokens for a one-off install — Google Tag Manager, ClickFunnels — are deleted as soon as the install ends, either way.
• Your account and what Eric has learned about your business stay until you ask us to erase them. Closing your account in Eric retires your business: its channels stop and its history is kept. To have the data erased, ask us (signed in or not, at /livechat): our team deletes personal data within 30 days of your request, and backups age out within 90. An account with other members or with payment history may need a conversation first.

What Eric learns, and what survives deletion

Eric gets better by spotting patterns, so it matters exactly what is kept once the raw data is gone. There are two separate layers and they never mix.

• What Eric knows about your business stays inside your account, is used only for you, and is erased when you ask us to erase your account. We do not train shared models on your raw events, your messages or your customers’ words.
• What Eric knows in general — statistical patterns across many businesses, such as “removing this kind of form field tends to lift mobile sign-ups” — may be kept indefinitely, because it is aggregated and irreversibly anonymised. No person, no message and no individual customer can be identified or reconstructed from it, which is why it is no longer personal data.

The purpose is stated plainly so there are no surprises: we use your data to run the product for you, and we use anonymised patterns derived from it to improve Eric’s analysis and recommendations for everyone. If you would rather your account was excluded from that general layer, tell us and we will exclude it. Business customers can read the detail in the data processing terms.

What you can ask for

• A copy of everything we hold on you, or on one of your visitors.
• Deletion of any of it, including a single visitor’s rows.
• Correction of anything wrong.
• Disconnection of any tool, which revokes the token behind it.

Write to support@everconvert.ai and we will do it within 30 days, usually the same week. If you are in the UK or EU these are your rights under the GDPR; we answer everyone the same way regardless.

Children

Meet Eric is a business tool and is not directed at children. We do not knowingly collect anything about anyone under 16. If you believe we have, tell us and we will delete it.

If this page changes

The date at the top changes with it. If a change matters — a new permission, a new processor, a new kind of data — we will tell you, by email or in Slack, rather than leaving you to notice.

Asking us something

support@everconvert.ai reaches our support team, and a person reads it. Privacy questions, deletion requests and anything about the Google permissions above go to the same address, or use /livechat, which works without signing in.

The controller of your account data is EVERCONVERT.AI LTD, a company registered in England and Wales, company number 17009673, incorporated 3 February 2025. For the personal data we hold on your behalf, see the data processing terms. Cookies and browser storage are listed on the cookie notice.

If you are unhappy with how we have handled your data you can complain to the Information Commissioner’s Office at ico.org.uk, though we would rather you gave us the chance to put it right first.