Data Retention & Deletion Policy
Last updated June 5, 2026
This policy explains how long TrakSolv.ai (“TrakSolv”) keeps the different categories of data it holds, and how data is deleted. It complements our Privacy Policy (which covers data for which we are the controller) and our Data Processing Agreement (which covers end-user data we process on behalf of customers as a processor).
Our guiding principle is data minimisation: we keep personal data only as long as we need it for the purpose it was collected, plus any period required by law (for example tax and accounting records), and then delete or irreversibly anonymise it.
1. Retention Schedule
| Data category | Examples | Retention |
|---|---|---|
| Account data | Name, email, hashed password, company details, dashboard settings | For the life of the account; deleted within 30 days of account closure (subject to legal-hold and tax exceptions below) |
| Billing & tax records | Invoices, subscription history, payment metadata held with Stripe | Retained for the period required by applicable tax and accounting law (commonly up to 7 years) even after account closure |
| End-user event data (processor) | Event, conversion, identifier, and attribution data flowing through the customer’s sGTM container | Processed transiently for forwarding; stored derived records (e.g. attribution/identity tables) expire on a rolling TTL and are purged on container deletion |
| Request / access logs | Per-container Caddy access logs (the request-metering source) | Kept on-box for roughly 7 days of rolls; archived copies retained for the current and prior billing cycle, then deleted |
| Free-tool submissions | URLs and email addresses submitted to the free tracking audit, and generated audit reports | Retained for a limited period to provide and improve the tool, then deleted or anonymised |
| Backups | Off-box database and report backups | Rolling backup set retained on a short cycle (on-box copies pruned after ~14 days); deleted data ages out of backups within the backup retention window |
| Security & audit logs | Administrative audit log, authentication events | Retained for a limited period for security and accountability, then deleted |
2. Deletion on Account Closure / Termination
When a customer closes their account or their subscription terminates, TrakSolv decommissions the customer’s sGTM container(s) and deletes the associated database records, saved reports, and per-container access logs according to its standard retention schedule, unless retention is required by law. On request, we will instead return Customer personal data before deletion. Residual copies persisting only in routine backups are deleted as those backups age out of the retention window described above.
3. End-User Erasure (Right to Be Forgotten)
Because TrakSolv processes end-user data as a processor on behalf of its customers, an individual end user who wants their data erased should contact the business (the customer / controller) whose website they interacted with. The controller decides on the request and instructs us as needed.
When a customer (controller) sends us a verified erasure instruction for an identified end user, we assist by locating and deleting that individual’s derived records held in the customer’s container — including attribution, identity-stitch, and customer-ledger records keyed to that person’s identifiers — and confirm completion. Much of the end-user data we handle is transient (forwarded, not retained) or is stored only as salted/hashed identifiers; we delete what is retained and identifiable.
Account holders exercising their own rights (access, correction, deletion, portability, restriction, objection, or withdrawal of consent) under regimes such as the GDPR, UK GDPR, CCPA/CPRA, and the Saudi PDPL can do so as described in our Privacy Policy.
4. How to Make a Request
Send deletion, erasure, or retention questions to arif@traksolv.ai. We will verify the requester’s authority before acting, respond within the timeframe required by applicable law, and document completion. Internally, deletion requests are executed against a defined operational runbook to ensure data is purged from the database, reports, container logs, the container itself, and (over the backup cycle) backups.
5. Changes
We may update this policy as our Services and obligations evolve. The “Last updated” date above reflects the latest version.
