SECURAWALL MAILFLOW
How your email data is handled
A delivery queue is temporary storage. Message content, activity records and recovery copies have different purposes.
Current queue lifetime: 14 days
Check the setting applied to your domain. Message age starts at original acceptance; a hold, service pause or release does not reset that age.
While waiting for delivery
Accepted messages remain in the SMTP queue while delivery is pending. A temporary destination failure triggers another attempt within the applied queue lifetime. Quarantine pauses normal delivery until an authorized release or expiry.
After delivery
Destination SMTP acceptance removes the active delivery-queue copy. Separately, captured headers and body text without attachments remain available for 90 days. This is not a mailbox or a restorable original-message backup.
Activity records
Detailed delivery and security history, application logs and web/public-test history are retained for 90 days. After confirmed destination SMTP acceptance, captured headers and text bodies are retained for 90 days without attachments. HTML is represented as plain text; encrypted content is not decrypted. Capture failures and bodies over the 8 MiB extraction limit are reported rather than silently presented as complete. This is not a restorable original-message backup. Rejected message bodies are not archived. Quarantine content is deleted after the customer-configured period, within the administrator limit and never over 14 days. Delivery queue lifetime is configured separately. Administrative and quarantine-action audit records use 180 days. Closed support conversations use 90 days after closure; financial records follow a separate policy. Records of data-deletion operations are retained for at least three calendar years.
Backups and snapshots
Service recovery copies are separate from the active delivery queue. If queues or disks are included in a backup or snapshot, removed queue data can remain in that recovery copy for its retention period. Active queue removal is not a promise of immediate destruction of every copy.
Email transport and data storage
HTTPS protects portal connections. SMTP delivery can require TLS and certificate verification according to the domain policy. Transport TLS is separate from storage encryption and is not end-to-end message encryption.
Hosting and privacy information
Doz Teknoloji develops and operates SecuraWall. Physical hosting, backup locations and storage-encryption details require infrastructure documentation. Request this information for your procurement or compliance review; development location is not a hosting-location guarantee.