Last updated 20 August 2026.
This policy explains what Infralytiqs does with personal data — both the data you give us to run an account, and the event data your own applications generate. The short version is that the analytics data stays in a database you own, and we keep only what is needed to connect to it and to run your account.
It applies to this website and to the Infralytiqs console at console.infralytiqs.com. If anything here is unclear, ask us at hello@infralytiqs.com before you send us data.
Where your event data lives
Your event rows are written directly to your ClickHouse database. There is no Infralytiqs-hosted event store to opt out of: the platform requires a ClickHouse host you supply, and it provisions its schema there.
What Infralytiqs retains is the connection details needed to write and query — host, database name, clientKey and clientSecret — together with the tenant and report definitions you create in the console. It does not keep a second copy of your events. Revoke the credentials or point them at a different host and the platform stops reading your data; the rows already in your database remain yours and untouched.
What the browser SDK collects
By default the tracking snippet records the page URL and title, the referrer, the viewport and screen size, the user agent, a coarse locale and timezone, and an anonymous visitor identifier stored in first-party storage. It does not read cookies belonging to other domains, fingerprint the canvas, or collect form input.
Any user identifier or custom property beyond that is something you choose to send. That is deliberate: you decide what personal data enters the pipeline, which makes your own data-protection assessment tractable.
Who is responsible for what
For the event data flowing through the SDK and the ingest API, you decide what is collected and why, and the data lands in your own database. Infralytiqs processes it on your instructions when you run a report.
For your own account — the email address you sign in with, your projects, your report definitions — Infralytiqs is the one deciding what to keep, and this policy is our account of it.
If your events include personal data about your users, informing those users and having a lawful basis to collect it is your responsibility, not ours. We cannot see your database contents on your behalf and we do not audit what you send.
Account data
Signing in with SSO shares your email address, display name and identity-provider subject identifier with Infralytiqs. We use these to authenticate you, associate you with your projects, and contact you about your account. We do not sell them and we do not use them for advertising.
We also keep ordinary operational records — sign-in times, audit entries for changes made in the console, and server logs — because without them we cannot tell a support question from an intrusion.
Who else sees it
We do not sell personal data, and we do not share it with advertisers or data brokers.
Data is shared only with the infrastructure providers needed to run the service — hosting, email delivery and the identity provider you chose to sign in with — and only to the extent that running it requires. Those providers act on our instructions and may not use your data for their own purposes.
We will also disclose data where the law requires it. If we are ever compelled to hand over data relating to your account, we will tell you unless we are legally prohibited from doing so.
Security
Traffic to the console and the ingest endpoint is encrypted in transit. Your ClickHouse clientSecret is treated as a credential: it is stored so the platform can authenticate to your database, and it is never rendered back into the console UI or written to a log line.
The security of the database itself is in your hands, because it is your server. Network exposure, ClickHouse user grants, backups and patching are yours to set. We would rather say that plainly than imply a guarantee we are not in a position to make.
If you believe you have found a vulnerability, email hello@infralytiqs.com and give us a reasonable chance to fix it before disclosing it publicly.
Retention and deletion
Retention is entirely yours, because the database is yours. The schema ships with a 24-month TTL on the events table; change it, remove it or shorten it and ClickHouse enforces whatever you set. Infralytiqs neither extends nor archives that data.
To delete your account and the tenant metadata associated with it, email hello@infralytiqs.com. Deleting the account does not touch the event rows in your own ClickHouse — those you drop yourself.
Your rights
Depending on where you live, you may have the right to see the personal data we hold about you, to correct it, to have it deleted, to receive a copy of it, or to object to how we use it. Ask at hello@infralytiqs.com and we will deal with it without unnecessary delay.
One practical limit worth stating up front: for data sitting in your ClickHouse database, we cannot action a request on your behalf, because we are not the ones who decided to collect it and it is not ours to delete. If one of your users asks you to erase their events, you run that deletion against your own database. If you need help writing the query, we will help.
You can also withdraw consent for account emails at any time, and you can stop the SDK collecting anything at all by removing the snippet or gating it behind your own consent banner.
International transfers
You choose where your ClickHouse server lives, so you choose where the event data rests. That is the main reason teams with a data-residency requirement can use the platform at all.
Account data and the infrastructure that serves the console may be processed in a different country from your own. Where that happens, we rely on the safeguards our providers have in place for such transfers. If residency matters for your account data as well as your events, talk to us before you sign up.
Cookies on this website
This marketing site stores your theme preference in browser local storage under the key header-theme (dark, light, or auto). That is a functional preference, not tracking, and it never leaves your browser.
The console additionally sets the session cookie needed to keep you signed in. There are no advertising or cross-site tracking cookies on either.
Changes to this policy
If this policy changes in a way that affects you, we will update the date at the top and, for anything material, tell account holders by email rather than relying on you to re-read the page.
Questions about any of it go to hello@infralytiqs.com. See also our Terms & Conditions.
This page describes how the product handles data. It is written to be read, not to be exhaustive, and it is not legal advice — if you operate under GDPR, CCPA or similar, review your own configuration and what you choose to send.