Privacy

Privacy and cookies

What this site collects, who else sees it, and how to switch the optional part off. There isn't much of it — we run no advertising and sell no data.

Analytics

Nothing is measured until you allow it. Before that there's no analytics cookie, and no request about your visit leaves this site.

If you do allow it, we record which pages you look at, where you arrived from, roughly how long you stay, whether you read to the bottom, and when you click a link that leads somewhere else. Along with that: your browser, operating system, screen size, language, and an approximate location worked out from your IP address.

It runs on Google Analytics 4, but the site loads nothing from Google — no tag, no script, no third-party cookie. Your browser sends the measurement to emyrix.com and our own server passes it on. Your IP address goes with it, because that's what turns a visit into "somebody in Massachusetts" instead of "somebody at our hosting company". Once it reaches Google, Google is processing it under their privacy policy.

If your browser sends a Global Privacy Control or Do Not Track signal, we take that as a no and don't ask.

The forms

There are two: the contact form, and the Magento store health check. Either one keeps what you typed in a database on our own server and emails a copy to ourselves so we see it. From the contact form that's your name, email, company, website, what the inquiry is about, the budget range and the message. From the health check it's your name, email, company and store URL, plus whichever of the optional questions you answered — phone, Magento version, order volume, hosting — and what you described. The health check also sends you a confirmation email.

Both record the IP address and browser string the submission came from, which is how a real inquiry gets told apart from a bot. Those two are blanked automatically after 90 days. What you wrote we keep, because it's the record of a conversation we had with you. It never goes to a mailing list or an advertiser. We read it and reply to it.

The health check also records how you got here: any campaign tags on the link you followed (the utm_source-style parameters an ad or a newsletter adds), the page you arrived on, and the site that sent you if your browser passed one along. That tells us which of our pages and ads are worth keeping. It's stored with your request and it's only read when you actually submit the form.

If you arrived by clicking one of our Google ads, that includes the click identifier Google puts on the link (gclid). We use it for one thing: telling Google Ads that the click led somewhere, so we know which ads are worth paying for. It identifies the click, not you, and we keep it with your request the same way we keep the campaign it came from — a lead can turn into work months later, and that's when it's worth reporting. Ask us to delete it and we will.

Cookies this site sets

  • emyrix_consent — your answer to the banner, kept six months. It's set either way you answer, because "no" only stays no if we remember it.
  • emyrix_lang — which language you chose to read the site in, kept a year. Set only when you choose, with the language links in the header or the bar that offers the Spanish version. If you never choose, it's never set, and the site shows the language of the address you asked for.
  • emyrix_cid — a random number that ties your visits together in the analytics, kept up to 400 days. Only set if you allow analytics.
  • emyrix_sid — a random number for the visit you're on now. It expires 30 minutes after you stop reading. Only set if you allow analytics.
  • XSRF-TOKEN and emyrix-session — set on every page, whatever you answered above. They keep the forms secure against being submitted from another site, and the session is also where the campaign tags described above wait until you submit one. They last two hours, and they don't identify you or track where you go.

None of them holds your name, and no other site can read them. The light and dark setting isn't a cookie at all — it lives in your browser's local storage and is never sent anywhere. The assistant keeps the chat you're in in your browser's session storage, so it's still there when you move to another page, and your browser clears it when you close the tab.

Server logs

Like every web server, ours writes down the requests it handles: the IP address, the page, the time and the browser string. That's what an outage or an attempted break-in gets investigated from. It's separate from the analytics above and isn't joined up with any of it.

The Ask Emyrix assistant

The chat window in the corner of the site is an AI assistant. It answers from the questions we've already answered on this site whenever it can. We store what you ask so we can see what visitors want to know and improve the answers: each question, the answer it got, the page you were on, and where the answer came from. It's tied to your browser session, not to your name, and it's deleted after 90 days.

When nothing we've written answers a question about our work, the assistant may send it to an AI provider (Google Gemini, Google Gemini, Cloudflare Workers AI or Groq) to draft a reply, along with the last few questions from the same chat. Email addresses, phone numbers, links and anything that looks like a password or a key are taken out before anything is sent. We keep those questions, with the same details removed, so we can write a proper answer for the next person who asks.

Please don't type passwords, API keys or your customers' details into the chat. If you ask us to follow up and leave your name and email, that reaches us as a message, the same as the contact form, with the questions you asked in the chat attached.

Invoices and payments

When we invoice you, the invoice is kept in the same database: your name, company, billing email and address, what we billed, and the payments and refunds made against it. It reaches you as an email with a private link. Anyone who has that link can open the invoice, so please don't forward it. Invoice pages aren't measured by the analytics, whatever you chose above, and the link is taken out of our server logs.

You can also see all your invoices at emyrix.com/invoices by signing in with a 6-digit code we email you. While a code is waiting to be used, we keep your email address and a one-way fingerprint of the code (not the code itself), and both are deleted after a day. Sign-ins are also noted in our security log, with your address partly hidden.

Payments go through Stripe. You finish paying on Stripe's own payment page, and your card or bank details go to Stripe and never reach us. We send Stripe the invoice number, the amount, your billing email, and our own reference numbers for the invoice and the payment. Stripe tells us whether the payment went through, whether it was a card or a bank transfer, the fee it charged us, and its own reference numbers. We don't get your card number, not even the last four digits. What you give Stripe, it handles under its privacy policy.

Invoices and payment records are kept for as long as accounting and tax rules require. Unlike an inquiry, they can't be deleted on request.

Who else sees any of this

  • Google, for the analytics described above, and only if you allowed them.
  • Our email provider, which carries contact form messages to our inbox@if ($billingShown), and invoices and receipts to yours@endif.
  • Stripe, which takes invoice payments as described above.
  • An AI provider, for the assistant questions described above that it can't answer from our own answers, with personal details removed first.
  • Our hosting provider, which runs the server the site and the database sit on.

That's the whole list. We don't sell data, we run no advertising, and there is no tracking pixel from anyone else anywhere on this site.

Asking us about your data

Email contact@emyrix.com and ask. If you want a copy of what we hold about you, or you want your inquiry or an assistant conversation deleted, say so and we'll do it. Invoices and payment records are the exception, for the reason above, though you can still have a copy.

Last updated October 7, 2026.