The Service runs on Amazon Web Services, in a single AWS region: Sydney (ap-southeast-2). We don’t currently offer a choice of region or a data residency commitment to any particular country or bloc. If your organisation needs one before you can use the Service, tell us at matt@fleetwarrant.com. Every Customer’s data is logically isolated by a tenant identifier on every read and write, and the payload-bearing parts of the audit record are additionally encrypted under an encryption key dedicated to your account, not shared with any other Customer’s. Each raw body, where raw capture is on, is also sealed under a key of its own.
The audit archive uses S3 Object Lock in GOVERNANCE mode. Each archive object is locked for 1 year by default, and you can change that period for your Tenant within the limits of your plan. The lock is a minimum, not a deletion date: our application never deletes an archive object, so an object can outlive its lock, still encrypted. It is deletion-resistant, not tamper-proof: no FleetWarrant application role can bypass the lock, but an administrator of the AWS account that hosts the Service holds a permission that can. The archive holds the redacted preview and the call’s metadata for every Event, and the raw request and response only for a Tenant that has turned on raw capture. Its value as compliance evidence is that records in it aren’t edited or deleted individually.
When your account is offboarded, we remove your data by destroying your account’s dedicated encryption key, which makes the archive unreadable, rather than by editing archived records one at a time. Destroying a key is not the same as deleting the encrypted objects, which our application doesn’t do.
Erasing one record inside an active account works differently for each part of it. A raw body can be shredded on request, or by your Tenant’s raw-body retention; a legal hold pauses shredding until the hold is released. Shredding destroys the body’s key, not the archived object: the body becomes unreadable on every live path at once, and unrecoverable from our backups once their 35-day window has passed. The redacted preview and the call’s metadata can’t be erased one record at a time. They stay in the archive, readable under your account’s key, for as long as the archive is kept. The lock period is a minimum, and our application never deletes an archive object, so in practice that means until your account is offboarded and its key is destroyed. We haven’t designed a per-record erasure for them. If you need this resolved contractually, tell us at matt@fleetwarrant.com before sending regulated data through the Service.
Waitlist and prospect data is kept for as long as reasonably needed to run the waitlist and follow up on it, or until you ask us to delete it.