Data Retention & Compliance
Data Retention & Lifecycle Management
QRForge applies enterprise‑grade data retention policies to ensure security, compliance, and predictable lifecycle behavior for all API‑generated and dashboard‑managed data. This document outlines how long different categories of data are stored, how deletions are processed, and what can be expected from the platform’s archival and purge cycles.
Applies to: API v1 and QRForge Dashboard
Status: Stable retention policy (subject to future Enterprise‑tier extensions)
QR Code Metadata
Retention: Indefinite, until user deletion.
Includes:
labelproject_idslugredirect_urlanalytics_enabledcreated_at,updated_atcreated_via(dashboard, API, import)
Deletion behavior:
- The public API has no delete endpoint for QR codes. A QR code is archived, not deleted, via
PATCHwithstatus: "archived". - An archived QR code stops resolving for scans (effectively removed from public traffic), but its metadata and slug are retained, and the slug is not released for reuse while the code is archived.
- Archived QR codes can be reactivated via the same endpoint (
status: "active"). - Hard deletion of QR metadata happens as part of full account deletion (see User‑Initiated Deletion below) — a separate, dashboard‑initiated flow, not something triggered per‑QR via the API — or when QRForge support deletes a QR code on request. Either way, the QR code's scan analytics are deleted with it, including the analytics warehouse copies.
Raw Scan Logs
Retention: 540 days (in the analytics warehouse)
Raw scan logs contain:
- Timestamp
- Device + platform metadata
- Country/region (IP‑derived)
- Browser + referrer
- URL parameters (e.g., UTM fields)
Purpose:
- Anti‑fraud intelligence
- Trend‑level analytics
- Real‑time scan monitoring
- Debugging integrations
Where they are kept:
- Analytics warehouse (Google BigQuery, EU): the detailed scan history. Each scan is kept for 540 days after the scan, enforced by BigQuery partition expiration on the scan time.
- Operational working copy (Firestore): the copy written when the scan happens, which is mirrored into the analytics warehouse and kept so a failed copy to the warehouse can be repaired. It is deleted 30 days after the scan, enforced by a Firestore TTL policy on an
expire_atfield set at write time. The daily totals are built from the analytics warehouse, not from this copy.
Deletion behavior:
- Automatically purged on a rolling basis: from the working copy after 30 days, from the analytics warehouse after 540 days.
- After 540 days, only aggregated analytics remain (see Aggregated Analytics below).
Trail Visitor Events
Retention: 30 days
QRForge Trails record one event per trail entry and per stop view, so the funnel report can be built. Each raw event contains:
- A visitor identifier (
visitor_id) stored in a first‑party cookie, used only to distinguish repeat visits within a trail - The trail and stop being viewed
- A truncated user‑agent string
- Timestamp
Deletion behavior:
- Automatically purged after 30 days on a rolling basis, enforced by a Firestore TTL policy on an
expire_atfield set at write time — the same window and mechanism as the operational copy of raw scan logs. - Trail visitor events are not copied to the analytics warehouse, so nothing is kept per visit after 30 days.
- Raw events are rolled up nightly into daily per‑trail funnel totals, which are kept for 3 years under the Aggregated Analytics policy below. The funnel report is served from those totals, so purging the raw events does not remove historical reporting.
- Deleting a trail, or the whole account, removes the trail's raw events and its daily funnel totals as part of the deletion (see User‑Initiated Deletion).
Aggregated Analytics
Retention: 3 years (1,095 days), on every plan
Stored as:
- Daily scan totals per QR code, only in the analytics warehouse table
daily_scans: total scans per day, successful and failed redirects, and country, device, referrer and redirect‑rule breakdowns - Daily trail funnel totals per trail, in the Firestore collection
daily_trail_funnel_stats: visitors and views per trail step
Purpose:
- Long‑term trend analysis
- Reporting
- Enterprise planning
Deletion behavior:
- Automatically purged 3 years after the day they describe: daily scan totals in the analytics warehouse by partition expiration on the day, daily trail funnel totals in Firestore by a TTL policy on an
expire_atfield set to the stats day + 1,095 days.
Retention is not your plan's analytics history
Your plan decides how far back you can view analytics (for example 365 days on Pro, 730 days on Agency, 3 years on Enterprise). That is a view window, not a retention period: the data is kept for the periods on this page on every plan.
Google Analytics 4
If you connect Google Analytics 4, a copy of each scan's anonymous details is also sent to your own GA4 property. That copy is controlled by your GA4 settings and is not covered by the periods above. Deleting your QRForge account does not delete the scan events already sent to your GA4 property. They are in your own Google account. Delete them there if you need to.
Project Metadata
Retention: Indefinite
Project definitions persist until manually deleted by the user.
Stored fields include:
namedescriptionis_defaulthas_custom_domain- Timestamps (
created_at,updated_at) - Ownership (
owner_uid) - Creation source (
created_via)
Deletion behavior:
- Hard deletion removes all project metadata.
- Associated QR codes are not auto‑deleted; they must be deleted separately.
API Logs & Audit Records
API request logs: 30 days
Admin audit log (admin_audit_log): 12 months
Tracks:
- API key usage
- Rate limit evaluations
- Internal error traces
- Authentication and ownership checks
- Admin actions (who did what, when, and from which IP)
Used for:
- Security investigations
- Abuse prevention
- System‑level diagnostics
Deletion behavior:
- Admin audit log entries are automatically purged 12 months after creation, enforced by a Firestore TTL policy on an
expire_atfield set at write time. - The
ipfield on an audit log entry is the administrator's IP address and is stored in full — it is not masked. This is intentional: full IPs on the audit trail are a legitimate security‑logging use case, distinct from customer‑facing analytics data (see Compliance Notes below).
Billing & Payment Provider Events
Retention: 30 days for raw payment‑provider webhook payloads
QRForge's payment provider sends webhook events for subscription and order lifecycle changes. Events that cannot yet be matched to an account, and event types QRForge does not act on, are retained in raw form purely so a billing discrepancy can be reconciled after the fact. A raw payload may contain the customer name, email and billing address held by the payment provider.
Deletion behavior:
- Raw payloads are automatically purged after 30 days, enforced by a Firestore TTL policy on an
expire_atfield set at write time. - Webhook delivery records (used to guarantee each event is processed exactly once — no payload, no personal data) are retained for 90 days.
- Confirmed subscription and invoice records are not covered by this policy; they are billing records retained with the account.
User‑Initiated Deletion
Individual QR codes cannot be hard‑deleted through the public API — see QR Code Metadata above; the only per‑QR write available is archiving.
Full account deletion is a separate, dashboard‑initiated, email‑confirmed self‑service flow that satisfies GDPR's “right to be forgotten.” It cascades and permanently removes:
- All QR codes and their metadata
- All projects and trails
- All scan analytics: raw scan logs, trail visitor events and daily totals, including the analytics warehouse copies
- Personal/account data, billing history, and custom domains
Upon account deletion:
- Metadata, raw scan logs (operational copy), trail visitor events and daily trail funnel totals in Firestore → deleted in the cascade itself
- Analytics warehouse data (raw scan logs and daily scan totals) → deleted within a few hours of the account deletion. A second pass about a day later deletes any copy that arrived late and confirms that none are left, normally within 2 days of the deletion. If a pass fails, it is retried and our team is alerted; a pending purge is never dropped.
- Backups and recovery copies → not edited; they expire on their own. Firestore backups are kept for at most 56 days, and deleted warehouse rows stay recoverable through BigQuery time travel for at most 14 days (7 days of time travel plus a 7‑day fail‑safe).
The same applies when QRForge support deletes a single QR code on request: its scan analytics in Firestore are deleted with it, and its analytics warehouse copies on the same schedule as above.
Expired Free Trials
Applies only to the self‑serve free trial of Pro, which starts without a payment card. It does not apply to paid subscriptions (including a trial started at checkout with a card), to accounts that have ever had a paid or admin‑granted plan, or to food delivery partner accounts.
- When the trial ends without a subscription, the account's QR codes, pages and trails stop resolving (visitors see an inactive page) and the owner can no longer edit them. Static Wi‑Fi QR codes (
wifi_encoding: "static") carry the network details in the code itself, never reach QRForge, and keep working. Subscribing at any time before the deletion restores everything; the owner can also delete the account themselves. - Notice: we email the owner when the trial has ended, with the deletion date, and send a reminder about 2 days before that date.
- Deletion: no earlier than 7 days after the trial ends and no earlier than 7 days after that email, the account is deleted with the same cascade as User‑Initiated Deletion above. Everything listed there is removed on the same schedule.
- Repeat‑trial guard: when the trial starts (or, for accounts that trialled before this guard existed, when the account is deleted), QRForge records a
trial_claimsdocument: a SHA‑256 hash of the normalized email address (or, only when the account has no email address, the phone number), a hash of the account ID, the date and how it was recorded. It holds no email address, phone number or name in readable form and is used only to refuse a second free trial to the same email address (a trial requires a verified email address). It is kept for 2 years (730 days) after it is recorded, also after the account is deleted, and then purged by a Firestore TTL policy on itsexpire_atfield.
Export Windows
CSV exports can include, within your plan's analytics history:
- Up to 540 days of raw scan events (filtered exports, read from the analytics warehouse)
- Up to 3 years of aggregated daily analytics (daily exports, read from the analytics warehouse)
Compliance Notes
QRForge’s retention model supports:
- GDPR (right to erasure, data minimization)
- Long‑term analytics preservation without storing personal identifiers
- Automatic purging of raw, potentially sensitive metadata
QRForge does not store:
- Full IP addresses for scan/visitor traffic. IP addresses are masked before a scan record is written: IPv4 addresses have their last octet zeroed (e.g.
203.0.113.45→203.0.113.0), and IPv6 addresses are truncated to their/64network prefix. Geo fields (country, city, latitude/longitude) are resolved from the request and stored as their own separate fields, so masking the IP does not reduce analytics functionality. - Personal identity data
- Cross‑site or cross‑customer visitor tracking, advertising identifiers, or any visitor profile built beyond the event metadata described above. The one visitor identifier QRForge does set — the first‑party Trails cookie described under Trail Visitor Events — is scoped to a single trail's funnel measurement. The cookie itself lasts 180 days in the visitor's browser; the events that carry its value are deleted after 30 days.
This masking applies to scan/visitor data only. The admin audit log intentionally retains the full, unmasked IP address of the administrator performing each action — a standard security‑audit‑trail practice, and a distinct category from customer‑facing analytics data (see API Logs & Audit Records above).
Self‑Hosted Geolocation Lookup
To resolve the country/city geo fields described above, QRForge looks up the scanning visitor's IP address against a self‑hosted MaxMind GeoLite2 database that QRForge downloads and refreshes on its own infrastructure. This lookup happens entirely in‑process — no visitor IP address is ever transmitted to any third party for geolocation purposes. Only the masked IP and the resolved geo fields are persisted, per the retention rules above.
Summary Table
| Data Category | Retention | Deletion Type | Notes |
|---|---|---|---|
| QR metadata | Indefinite | Archive only via API; hard delete via account deletion | No API delete endpoint — status: "archived" via PATCH |
| Scan logs (raw events) | 540 days | Automatic purge (BigQuery partition expiration) | Analytics warehouse; the operational Firestore copy is deleted after 30 days; IP addresses masked at write time |
| Trail visitor events | 30 days | Automatic purge (Firestore TTL) | Raw per‑visit events; rolled up nightly into daily funnel totals |
| Aggregated analytics | 3 years | Automatic purge (BigQuery partition expiration; Firestore TTL for trail funnels) | Daily totals on every plan: scans in the analytics warehouse (daily_scans), trail funnels in Firestore (daily_trail_funnel_stats) |
| Analytics after account deletion | Within about 2 days | Purge job | Warehouse copies; Firestore copies go in the deletion cascade |
| Raw billing webhooks | 30 days | Automatic purge (Firestore TTL) | Unmatched/unhandled payment‑provider payloads only |
| Project metadata | Indefinite | Hard delete | QR codes not auto‑deleted |
| API logs | 30 days | Automatic purge | Platform logs |
| Admin audit log | 12 months | Automatic purge (Firestore TTL) | admin_audit_log; admin IP stored unmasked |
| Expired free trial account | At least 7 days after the trial ends and after the notice email | Account deletion cascade | Self‑serve no‑card trial only; never‑paid accounts |
| Trial claim (repeat‑trial guard) | 2 years | Automatic purge (Firestore TTL) | trial_claims; SHA‑256 hash of email or phone; kept after account deletion |
If you require custom data retention policies, extended archival windows, or enterprise‑tier data residency options, please contact support.