Privacy Policy
Effective 10 September 2026
Audkit is an audit-logging service. Most of the data we hold is not ours and is not about our own users — it is the record your application sends us about its users. This policy separates the two, because the rights and the responsibilities differ.
Two kinds of data
Account data is data about you, our customer, and we are the controller of it. Audit data is what your application sends to Audkit through the API. For that, you are the controller and Audkit is a processor acting on your instructions — see the Data Processing Agreement.
Account data we collect
- Identity: your name and email address, and a hashed password. We send a six-digit code to your email to confirm you control it.
- Organisation and project configuration: names, membership, roles, invitations, retention settings, alert rules.
- API key metadata: key identifiers, scopes, and project association. Key secrets are stored hashed and shown only once at creation.
- Billing: plan, event and project usage counts. Payment card details go directly to Stripe and are never held by Audkit.
- Operational logs: request metadata needed to run and secure the service, including rate-limit counters and the IP addresses associated with API key use.
Audit data you send us
The content of an audit event is entirely determined by your application: an action name, an actor, an optional target, and arbitrary metadata you supply. Audkit does not inspect, enrich, or profile it, and does not use it to train anything.
Because the metadata field is free-form, it may contain personal data if you put personal data in it. Audkit does not currently perform automatic redaction, so deciding what is appropriate to send is your responsibility as controller. Payloads are encrypted at rest with a per-event key.
Why we process it
- To provide the service you have asked for — performance of a contract.
- To keep the service secure and available, including rate limiting and abuse detection — legitimate interests.
- To bill you and meet our own accounting obligations — legal obligation.
- To send service email you cannot opt out of while holding an account: sign-in codes, security notices, and billing notices.
Where it is processed
Audkit uses subprocessors in the United States and the European Union. The current list, with the purpose and region of each, is published and kept current on the Security page.
What is published publicly
Audkit anchors signed tree roots to a public transparency log every hour. Those entries contain an opaque project identifier, an event count, a root hash, and a timestamp — never event content, actor, target, or metadata. They are permanent and cannot be withdrawn once published. The mechanism and its exact contents are described in full on the Security page; please read it before sending production data.
How long we keep it
Audit data follows the retention window you set per project — 30, 90, 180 or 365 days, 7 years, or indefinitely, defaulting to 90 days. Expired events are crypto-shredded: the encrypted payload and its key are destroyed, leaving only a verifiable skeleton that proves the record existed and was not altered. A legal hold you place will pause this for the events it covers.
Account data is kept while your account is open and deleted within 30 days of account closure, except where we must keep billing records to satisfy accounting law.
Your rights
If you are in the UK or EU you have rights of access, rectification, erasure, restriction, portability, and objection over your account data. Email privacy@audkit.dev and we will respond within one month.
For requests concerning audit data — data about your users — you are the controller and should act on them directly through the service; we will assist you as processor under the DPA. Note the deliberate limit: Audkit is append-only by design and offers no endpoint that edits or deletes an individual event. Erasure is achieved through retention and crypto-shredding, which destroys the content while preserving proof that the record existed. If you need per-subject erasure faster than your retention window, shorten the window or avoid placing personal data in event metadata.
Cookies
Audkit sets a session cookie when you sign in and a theme preference cookie. There are no advertising or third-party tracking cookies, and no analytics that follow you across sites.
Changes and contact
Material changes will be reflected in the effective date above and, for changes that affect how audit data is handled, announced to account owners by email. Questions: privacy@audkit.dev.