Skip to content
Browse documentation

Data retention

How long TrackCrown keeps clicks, impressions, conversions, postback logs, notifications, sessions and other records, and what is deleted automatically.

Last updated 3 min read

On this page

TrackCrown deletes high-volume tracking data and operational logs automatically on fixed schedules. Business records that you need for accounting and disputes — conversions, invoices, payout statements, the audit log — are kept until you or the platform operator remove them.

Automatic deletion#

DataWhereKept forHow
Clicks (raw click log: IP, user agent, referrer, click IDs, sub IDs, parameters)Click store (ClickHouse)13 monthsTable TTL: rows older than 13 months are dropped.
ImpressionsClick store13 monthsTable TTL.
Received postbacks (every /pb, /px, /lp request with its result)Click store90 daysTable TTL.
Outbound postback log — deliveredDatabase90 daysHourly purge.
Outbound postback log — failedDatabase180 daysHourly purge.
In-app notificationsDatabase180 daysHourly purge.
Contact-form and abuse reportsDatabase24 months after they were handled (or received, if never handled)Hourly purge.
SessionsDatabaseUntil they expire (30 days, extended while in use)Hourly purge of expired sessions.
Password-reset and invitation linksDatabase1 day after expiry or useHourly purge.
Notification queue (internal events)Database30 days after deliveryPurged by the dispatcher.
Compliance probe runsDatabase30 daysPurged by the probe job.
Domain checks (uptime, TLS, reputation history)Database120 daysPurged by the probe job.
Offer link check historyDatabase90 daysPurged by the checker.

Kept until deleted#

DataNotes
ConversionsKept with their money, status and history (needed for statements, clawbacks and disputes). Personal identifiers on a conversion can be erased with a privacy request.
Invoices and payout statementsAccounting records.
Audit logNot purged automatically.
Sign-in eventsNot purged automatically; removed when an account is anonymised.
Terms acceptances, documents and signaturesEvidence of agreements.
Partner and advertiser records, offers, settingsUntil deleted or archived by you.
Webhook and scheduled-report run logs, KPI alert triggersNot purged automatically.

What the 13-month limit means for reports#

  • Reports, the click log and the clicks explorer cannot show clicks older than 13 months; the report builder accepts ranges of at most 400 days.
  • Conversions older than 13 months still exist, so conversion counts and money stay correct in reports, but click-based metrics (clicks, CVR, EPC) for those periods drop to zero once their clicks are gone.
  • Lifetime ("total") click caps are re-seeded nightly; clicks that left the click store remain counted.
  • Transaction journeys of old conversions show "the click is not in this workspace's click log".

If you need clicks for longer, export them before they expire: use raw data export to your own S3-compatible storage, or the CSV exports.

Backups#

The reference deployment takes nightly database backups and keeps them for 14 days. Deleted data can therefore remain in backups for up to 14 days before it is gone for good. Redis caches and counters are not backed up.

  • Erasure requests delete a person's clicks, impressions and received postbacks and remove identifiers from their conversions. See Privacy requests.
  • EU IP masking stores only truncated IP addresses for European visitors from the start. See EU IP masking.
  • Visitor IP addresses in security logs (sign-ins, terms acceptances, signatures) are stored only as keyed hashes.

Your own retention duties#

As the controller of your campaign data you decide how long you need it. If your privacy policy promises a shorter period than 13 months for raw clicks, ask the platform operator before relying on it — the click retention is the same for every workspace on a platform.

Something unclear or missing in this article?Tell us