Our security commitments
Queantic builds, hosts and measures websites, and it was built for people tired of surveillance analytics — bloated scripts, consent banners, data brokers. So the measurement layer collects as little as it possibly can, and the hosting layer is run by us rather than handed to you as a control panel. Your site's data is yours.
This page is written to be checked rather than believed. Everything claimed below is verifiable against our code, against our public status history, or by a question you can put to us and expect a straight answer to. The things we have not finished are further down, with the same amount of detail.
The short version
- Hosted and administered in the United States
- All traffic encrypted in transit; certificates renewed automatically
- No per-visitor record exists — aggregate counters and a statistical sketch
- No cookies, no local storage, no fingerprinting, no analytics JavaScript
- Geolocation resolved on our own server, so no visitor address reaches a third party
- Passwords hashed and salted; stored service credentials encrypted per field
- No card data on our infrastructure at all — Stripe handles payments
- Authorisation decided server-side on every request, never by hiding a link
- Availability probed every five minutes, with the history public
- Four subprocessors, named, none with access to your analytics
- No ads, no data sales, no resale, no model training on your data
- Your data exported to you on request within five business days, free
We would rather not have your visitors' data
The strongest privacy claim we can make is not about how carefully we guard a visitor record. It is that there isn't one. The analytics table holds counts — by country, city, browser, operating system and referring page — plus a probabilistic sketch used to estimate unique visitors. There is no row per visit, no session identifier and no visitor profile, because the schema has nowhere to put one.
Nothing is written to the visitor's browser: no cookie, no local storage, no fingerprint. There is no analytics JavaScript on the page at all — collection is a single image request — which also means there is no third-party script on your site that somebody else's breach could reach through.
Geolocation never leaves this server. A visitor's country and city are resolved against a local database of several million address ranges, so no address is sent to a geolocation API and there is nothing to cache.
One qualification, because it is the honest version. On lower-volume sites we keep a truncated hash of the visitor's IP so that unique-visitor counts are exact rather than estimated. That hash is not currently salted, and an unsalted hash of an address space that small is enumerable by somebody determined enough. We are moving it to a salted, rotating scheme. It is listed again further down, because a qualification buried in a paragraph is a qualification nobody read.
Encryption, field by field
Stated field by field rather than as one sentence, because one sentence is how this gets overstated.
- In transit: all traffic over TLS, with certificates issued and renewed automatically — renewal runs daily and does not depend on anyone remembering.
- Mail in transit: SMTP over STARTTLS, with DKIM signing and SPF and DMARC published for every sending domain.
- Passwords: hashed and salted. Never stored or recoverable in plaintext; a reset issues a new credential rather than revealing the old one.
- Stored service credentials: encrypted per field with libsodium authenticated encryption, keyed from a secret held outside the database.
- Card data: never on our infrastructure. Entry and storage are entirely Stripe's; we hold a customer reference and nothing else.
- Disks at rest: not encrypted today. See what we have not finished. We are not going to describe per-field protection as full-disk encryption, because they are not the same thing and anyone evaluating us properly will ask how it is keyed.
Server location: United States
All application servers, databases and mail infrastructure are in U.S. data centres and administered from the United States. No customer or visitor data is stored, processed or replicated outside it. Infrastructure is administered by Queantic directly — there is no outsourced operations provider and no offshore development contractor with production access.
You own the data
We don't mine it, sell it, aggregate it into a wider dataset, or train anything on it. Queantic is a neutral measurement layer, not an adtech pipeline.
On request we produce a complete export — a standard WordPress content export, the uploads directory and a full database dump — within five business days, free, at any time, with no reason required. One thing said plainly: the administrator role a site owner is handed deliberately cannot run an export itself, which is the same restriction that stops it installing code or changing who can reach the site. So the export is a request to us rather than a button, and the commitment above is what makes that acceptable. The full terms are in data ownership, export and exit.
Authentication and access
Passwords are hashed and salted. Sessions are signed and invalidated on password change, and signing out destroys the session token rather than only clearing a cookie. State-changing operations carry CSRF tokens.
Authorisation is decided server-side on every request, against a single membership check, before anything renders. Access is never enforced by hiding a link — that is load-bearing here, because all sites on the network share one cookie domain, so authentication is shared by design and this check is the thing that keeps tenants apart.
The role a site owner is handed can change what the site says and how it looks, and cannot install code, manage users, alter hosting or touch billing. That boundary is defined once, in code, and projected onto every site rather than configured per site.
There is no multi-factor authentication yet. See what we have not finished.
Subprocessors
The complete list: Stripe (payments — billing contact and payment details, no site content, no visitor data), our U.S. hosting provider (physical custody of the disks, no application-level access), Let's Encrypt (certificates — domain names only, which are public anyway) and our domain registrar where we hold a domain on your behalf.
No analytics processor, no advertising network, no customer data platform, no CDN with access to your traffic. There is nothing to remove from that list because nothing was added to it.
Payment security
Payments are handled by Stripe, not by us. We never see or store card data.
Uptime and monitoring
Every component is probed every five minutes — the website, the application, the API, the webhook endpoint, the database and mail, each independently — plus every published customer site. A separate host-level check runs every ten minutes and can restart a failed component without a person present. Certificates and domain registrations are checked daily for approaching expiry, which is why ours do not expire.
You can read the result rather than take our word for it: our status page shows live availability and a rolling 90-day history for every component, with no login. It is written to a static file on every cycle and served by the web server directly, so it still answers when the application is the thing that has failed.
Incident response
Detection comes from those probes, the daily expiry check, and an internal event log that records privileged and unusual actions and raises an alert by mail at its highest severity. Containment comes before explanation: the affected component is isolated or rolled back first, and our gates are designed to fail closed, so something that cannot reach a decision withholds rather than exposes.
If an incident affects your site, you are told what happened, what was affected and what we did. If personal data is implicated we notify you within 72 hours of becoming aware, with enough detail for you to meet your own notification duties. Anything beyond a brief outage gets a written account of cause and the change made, and an entry on the public status page.
Report a vulnerability
If you spot a flaw, tell us privately. We'll fix it and credit you if you want the credit. Please give us time to patch before public disclosure.
What we have not finished
Published rather than omitted. Somebody evaluating us properly finds these in half an hour, and a vendor who waited to be asked has told you something about themselves.
- Scheduled, offsite backups. There is no automated backup schedule today; archives have been taken by hand. This is the most important item on this list and it is being closed first. Until it is, we will not quote a recovery point or recovery time objective, because we would be inventing both.
- Full-disk encryption at rest. Not in place. The per-field protection described above is real and is not the same thing.
- Multi-factor authentication for administrative accounts. Not implemented. Authorisation is strong and server-side; the second factor is missing.
- Salting the per-visitor hash used for exact unique counts, as described above.
- An independent penetration test and accessibility audit. Neither has been performed. The accessibility audit is in progress — what we test today, and how, is on our accessibility page.
- A self-service data export. The export is free and committed to five business days; it is work we do rather than a button you press.
For public agencies and procurement
If you are completing a vendor security questionnaire, the long-form version of this page — hosting location, encryption per field, access control, monitoring cadence, the incident response procedure, the full subprocessor table and the open items above — is written to be attached to a requisition:
Security overview The whole vendor packet
What Queantic does for public agencies, and what it does not yet do, is on Queantic for public agencies.
Built for the privacy-conscious
No cookies. No tracking. No loopholes.
Built and hosted entirely in the United States.
Sustained solely by paying customers. No investors. No ads.