Itnetic TechnologiesData Retention Policy
Itnetic Technologies
Last updated: 21 August 2026
This policy states how long Itnetic keeps each category of data and what enforces that limit. It expands Section 11 of the Privacy Policy and supports Section 11 of the DPA.
The principle throughout: a retention period that depends on someone remembering to run a clean-up is not a retention period. Wherever the data lives in our database, expiry is enforced by a TTL index — the database itself deletes the record when it expires.
1. End-user traffic data (Itnetic acts as processor)
| Data | Retention | Enforced by |
|---|---|---|
| Request logs — IP, timestamp, host, path (query string stripped), method, status, bytes, user-agent, referer, country/ASN, TLS and HTTP version, cache status, security signals | 30 days | Database TTL |
| Per-minute analytics aggregates derived from those logs | 30 days — the same window as the raw logs they summarise | Database TTL |
| Request and response bodies | Never stored | Not written in the first place |
| Cached response bodies (CDN cache) | Until the cache TTL expires or the cache is evicted or purged; per-node disk cache, wiped on redeploy | Cache LRU + TTL |
| Rate-limit and traffic counters | Minutes to hours — the length of the counting window | Database TTL |
| Mitigation counters (attack graphs) | 1 hour | Database TTL |
| TLS client-software reputation scores (JA4 fingerprint + score; no IP, URL or request content) | 30 days after the fingerprint was last observed | Database TTL |
| Bot-detection model | Numeric weights only, refreshed continuously. Contains no personal data and nothing traceable to a request, a visitor or a site | — |
| Kernel firewall blocks and solver allowlists | Minutes to a maximum of 1 hour, in memory on the edge node only | In-process expiry |
Nothing in this section is recoverable after its window closes. A law-enforcement preservation request must reach us inside the 30 days to be actionable.
2. Customer account data (Itnetic acts as controller)
| Data | Retention | Enforced by |
|---|---|---|
| Account record, domains and configuration | Life of the account. Deleting your account in the dashboard removes it immediately | Self-service deletion |
| API tokens and their usage counters | Deleted with the account. Usage counters otherwise: 90 days (per-minute buckets), 400 days (daily buckets) | Deletion + database TTL |
| Stored origin credentials (object-storage keys, AES-GCM encrypted) | Deleted with the account or when you remove them | Self-service deletion |
| Passkeys | Deleted with the account or when you remove them | Self-service deletion |
| Dashboard session records (IP, user-agent) | 30 days after last activity; deleted immediately on account deletion | Database TTL + deletion |
| Email-verification tokens | Until they expire (short-lived) | Database TTL |
| Unverified domain claims | 7 days | Database TTL |
| Anything remaining after account deletion | Deleted or anonymised within 90 days | Manual review |
3. Everything else
| Data | Retention | Why |
|---|---|---|
| Billing and accounting documents | 5 years generally; up to 10 years for tax documents where VAT applies | Czech Act No. 563/1991 Coll.; tax law |
| Support communications | 24 months | Legitimate interest — continuity of support and defence of claims |
| Website analytics (self-hosted Umami, no cookies) | 12 months | Consent-based; deleted on withdrawal |
| Marketing preferences and consent records | Until withdrawn, plus a short record of the withdrawal | Proof of compliance |
| Incident records | 3 years | Accountability (Art. 5(2) GDPR) |
| Backups | Rolling, overwritten within 35 days | Provider backup cycle |
Backups and erasure. An erasure request removes the live data immediately. Backups are not surgically edited — the deleted data disappears as the backup cycle rolls over, within 35 days. In the meantime it is not used for any purpose other than restoring a failed system.
4. Customer control over retention
Request logging is currently a fixed part of the Service: it is not switchable per domain, and the 30-day window is not shortenable in the dashboard. If your data-protection assessment needs a shorter window or no logging at all, contact us before routing traffic — we will tell you honestly whether we can meet it.
You can, at any time and without asking us:
- delete a domain, which stops any further logging for it;
- delete your account, which removes everything in Section 2 immediately.
5. Questions
chlibekbusiness@gmail.com. For rights requests (access, erasure, portability), see Section 12 of the Privacy Policy.