| Code record: destination, fallback address, name, owning account identifier, destination history with author and time · español | For the life of the code. No expiry. · español Built and running · español |
| Scan counter and date of the last scan (UTC day, no time of day) · español | For the life of the code. Each scan tries to update the counter and the date; the update is best effort, so a scan can go uncounted and the date can lag behind the real last scan. · español Built and running · español |
| Operational log line per scan: code identifier, outcome, HTTP status, time. No IP address, no user agent, no referrer. · español | 7 days configured; AWS deletes expired log events asynchronously, typically within a further 72 hours. · español Built and running · español |
| API calls: not logged. Only errors and the Lambda platform’s own start/end lines. · español | 7 days configured; AWS deletes expired log events asynchronously, typically within a further 72 hours. · español Built and running · español |
| File downloads: format, size and duration of rendering. Never the encoded content. · español | Log lines: 7 days configured, deleted by AWS typically within a further 72 hours. The file itself: served from the CloudFront cache for up to 24 hours; CloudFront does not promise removal at that time. · español Built and running · español |
| Point-in-time recovery backups of the code table: every code record, counter and destination history as it was at any moment · español | A rolling 35 days, the AWS default (our code enables recovery and does not set the period). A record removed from the table stays recoverable from these backups for that time. · español Built and running · español |
| CloudFront access logs (IP addresses and similar) · español | Not collected: access logging is off on all three distributions. · español Built and running · español |
| Account: e-mail address (the login) and credentials, held by Amazon Cognito · español | The account-deletion panel requires a complete, multi-part export first; after completion, only a minimal recovery tombstone remains for up to 36 days while routing records and printed-code redirects continue. · español Built and running · español |
| Paid analytics daily pseudonym: derived from IP address, browser information, a day key and code identifier; raw IP and user-agent values are not retained · español | Up to 48 hours from the beginning of the UTC day. Late writes keep their original expiry; disabling, transfer and deletion invalidate access before resumable cleanup. · español Approved, not in use yet · español |
| Paid analytics country and daily aggregates: approximate unique scans and country distribution for completed UTC days · español | 90 days from the beginning of the UTC day. DynamoDB TTL cleanup is asynchronous and usually takes further days; no promise of physical deletion exactly on day 90. · español Approved, not in use yet · español |