Data Retention

Browser preferences

The privacy-preference record remains in browser local storage until you replace it, clear the site’s browser data, or your browser removes it. There is no application-set expiry. Private browsing, storage restrictions, and browser cleanup can shorten its lifetime.

This local record contains privacy choices, not an account profile or a copy of a contact message. Clearing it does not delete emails or service-provider records.

Contact submissions in the application

The application validates a form submission and sends it through Resend when the service is available. It does not create a contact-message database or a persistent application-side message archive.

The request is handled in server memory. Routine request logs record operational metadata rather than the submitted message body. A failed request is not silently presented as delivered.

Delivered correspondence

Sent messages and replies can remain in the receiving mailbox, its folders, backups, or delivery systems. The website does not run a mailbox-deletion timer and cannot erase a recipient’s copy merely because you clear browser storage.

Retention decisions depend on whether an enquiry is unresolved, follow-up is needed, or information is needed for a security concern, dispute, or applicable legal obligation. Records should not be kept longer than those purposes require. A deletion request is assessed against those purposes and any applicable legal exceptions.

Email contact@driverdepothub.com for privacy questions or requests. You can also choose Privacy request on the Contact page. If the web form is unavailable, email us directly; the form is not the only request channel.

Email-provider records

Resend publishes a standard 30-day retention period for email content, metadata, delivery events, logs, and metrics on its Free, Pro, and Scale plans. Enterprise arrangements can differ. That provider policy does not delete messages already delivered to a recipient’s mailbox.

The provider’s retention rules concern its own records. They are separate from mailbox copies, browser storage, and hosting logs. The linked Resend documentation explains its published retention policy and plan differences.

Temporary abuse-prevention counters

Submission limits use a 15-minute counting window and keep connection counters in server memory. Expired entries are removed as subsequent requests prune the counters, or when the server process ends. This is not a promise that all network records disappear exactly 15 minutes after a visit.

The counters do not contain contact-message bodies. They are distinct from operational logs and email-delivery records.

Hosting and other service records

Replit documents 30-day retention for published-application logs. This is distinct from browser storage, email, analytics records, and other infrastructure or backup records that can have separate provider policies.

Replit and other infrastructure providers process operational information to deliver, protect, and troubleshoot their services. The absence of an application message database does not mean that no provider logs exist.

Optional-cookie rejection does not erase necessary network logs or delivered email. Contact us if you need help identifying which kind of record a request concerns.

Questions and answers