Different parts of the site have different storage lifecycles. This policy distinguishes short-lived application processing, browser preferences, email-provider records, and correspondence held in the receiving mailbox.
Inside this application
The application has no database of contact submissions and writes no message body to its own logs. Submitted fields are held while the send request is processed and are not intentionally retained in application storage afterward. Abuse-limiting counters use salted address-derived keys in memory. Their enforcement expires after 15 minutes, but an expired entry is physically removed only on a subsequent submission or process restart, not by a scheduled deletion worker.
In your browser
The essential consent record lasts up to 180 days from the time a choice is saved. It contains category selections and a timestamp, not contact details. The cookie expires and the scripted reader discards an expired local-storage record. You can clear either sooner through browser controls. Ordinary browser history can retain page addresses, including a search query, according to your browser settings.
Email and provider records
After an accepted submission, Resend and the receiving mailbox can hold copies and delivery records under their configured service retention. This application does not run an automatic deletion job against either provider. No fixed deletion deadline for those external copies is claimed here because it has not been verified against the accounts' settings. Hosting operational logs likewise follow the hosting service's lifecycle rather than the application's in-memory counter.
Deletion requests
To request deletion of site-controlled correspondence, use Contact's Privacy request topic or email info@driversoftguidegmail.com. Identify the earlier exchange without resending sensitive content. Legal obligations or a relevant dispute can affect what may be removed, and another recipient's independently controlled copy is outside this site's control. A response should explain the actual action taken rather than imply that clearing a browser preference erased email history.
Email enrollment records
The reading-update form creates a pending record, not an active subscription. Pending confirmation is valid for 24 hours. Expired pending rows are deleted on the next enrollment submission, so an unused row can remain physically stored longer when there are no further requests. A confirmed email record remains until removal or a deletion request. The emailed removal link opens a confirmation form; submitting that form deletes the address and its enrollment record. This is separate from clearing a browser cookie or deleting correspondence in a mailbox.
Records and their lifetimes
The distinctions below describe application behavior and the boundaries of external retention. A browser opt-out is not an email deletion request.
| Data | Where held | Retention and deletion |
|---|---|---|
| Contact fields and pending retry ID | Browser and API request memory | While the page/request is active; no application contact database |
| Delivered correspondence | Receiving mailbox | Until manually deleted; no automatic application mailbox purge |
| Sending logs and retry identifiers | Resend | Provider retention/settings; no verified fixed period or application deletion job |
| Rate-limit hash, count and expiry | API process memory | Stop applying after 15 minutes; removed on next submission or process restart |
| Consent cookie | Visitor's browser | 180 days from save unless cleared earlier |
| Consent localStorage record | Visitor's browser | Ignored and removed when next read after 180 days; may remain physically stored until that read or manual clearing |
| Operational/request logs | Hosting infrastructure | Provider lifecycle; no fixed retention verified in the application |
How to reach us
For questions about Data Retention, email info@driversoftguidegmail.com or use the contact form and choose the topic that fits. Direct email is an alternative when online sending is unavailable. This channel is for website correspondence, not device assistance.
This page describes our practices and is not legal advice.
