What PostDeploy stores, and what it does not

PostDeploy Measure counts visitors without cookies and without storing raw IP addresses. This page states what each part of the product keeps, for how long, and what it deliberately never records. Every claim here describes the running implementation.

Analytics without cookies or raw IP storage

Measure sets no cookies, so a site running it needs no cookie banner for PostDeploy. There is no persistent visitor identifier, and no identifier that works across sites.

Separating browser activity normally needs something stable about a person. Instead of storing one, PostDeploy derives a short-lived value: the project, the source, the IP address and the user agent are combined into a keyed hash, using a secret that is regenerated every day. The inputs are never written to disk. Only the hash is stored, and the raw IP address and user agent are discarded at the point of ingest.

Because the key changes daily, yesterday's hash cannot be matched to today's. That is the deliberate trade: PostDeploy cannot follow a person across days, which also means PostDeploy cannot tell you a visitor returned a week later. The reporting limit and the privacy property are the same fact.

What each pillar stores

Stated per pillar, because they collect different things and a single blanket statement would be false about one of them.

Monitor: the URL or host you asked PostDeploy to check, and the result of each check (status code, latency, error class). Monitor stores nothing about your users.
Observe: the error payloads your application sends, which include stack traces and any context you attach. You control that content; if you attach personal data to an error, PostDeploy stores it.
Measure: a page path, a referrer, a country derived from a request header, a browser name, and the daily visitor hash described above. Not the raw IP, not the raw user agent, not a cookie.

What PostDeploy never stores

These are absences enforced by the code, not policy promises.

No analytics cookies, and no local storage used for identification.
No raw IP addresses in analytics. The address is an input to a hash and is then discarded.
No raw user-agent strings in analytics; only a derived browser name.
No cross-site or cross-project identifier. The project is an input to the hash, so the same visitor on two projects is two unrelated hashes.
No third-party analytics, advertising or session-replay scripts on this site or in the product.

How long data is kept

Retention is a plan limit, enforced by the same registry that bills you, and expired data is deleted by a scheduled job rather than left to accumulate.

Detailed uptime check results are kept 7 days on Indie, 30 on Pro and 90 on Scale, after which they fold into daily uptime history. Error events follow the same pattern. Analytics rollups are kept 90 days on Indie, 730 on Pro and 1095 on Scale. Audit log entries are kept 30, 90 and 365 days respectively.

Deleting a project deletes the data belonging to it.

Where data is processed

ALPLUS TECHNOLOGIES SRL, registered in Romania, is the controller for the data described on this page.

PostDeploy runs on AWS in a single region, us-west-2 , in the United States. Cloudflare sits in front for DNS, TLS and protection against abuse. Uptime and API checks are made from those same application servers, which is why PostDeploy offers one checking region rather than a global probe network.

Read the consequence plainly: if your visitors are in the European Union, the analytics PostDeploy records about them is processed in the United States. PostDeploy stores no cookie, no raw IP and no persistent visitor identifier, which narrows what crosses, but the processing location is what it is.

Analytics telemetry for recent windows is also written to Cloudflare Analytics Engine; durable aggregates and all authoritative state live in the PostDeploy database.

What this page does not claim

PostDeploy holds no SOC 2 report, no ISO certification, and has not commissioned an external penetration test. If your procurement process requires any of those, PostDeploy does not meet it today, and saying so is more useful than a page of reassuring language.

One person operates PostDeploy. Treat the operational maturity accordingly when deciding what to depend on it for.

Questions

Do I need a cookie banner to use PostDeploy Measure?

PostDeploy sets no cookies and stores no persistent identifier, so PostDeploy itself does not create that requirement. Whether your site needs a banner depends on everything else running on it and on your jurisdiction, which is a question for your own advisers rather than for us.

Can PostDeploy tell me if a visitor came back next week?

No. The key used to derive the visitor hash is regenerated daily, so a visitor cannot be matched across days. That limitation is the mechanism that makes the analytics privacy-preserving.

Does PostDeploy store my users' IP addresses?

Not in analytics. The IP address is one input to a keyed hash and is discarded at ingest; it is never written to storage. Error payloads are different: they contain whatever your application chooses to send, which is under your control.

Is PostDeploy SOC 2 certified?

No. There is no SOC 2 report, no ISO certification and no external penetration test. If your review requires one, PostDeploy does not meet that bar today.

Ship your next project with one toolkit, not three.

Read what PostDeploy monitors