Can I configure log retention in iDBQuery?
Yes. iDBQuery lets you configure how long activity and audit logs are retained, so you can match your own retention and privacy policies rather than a fixed default. In self-hosted deployments the logs live in your environment, so you control retention, storage, and deletion end to end.
Log retention determines how long records of activity are kept, and iDBQuery is built to fit your policy rather than impose one.
- Configurable windows - set retention periods for audit and activity logs to match your governance and data-minimisation rules.
- Your environment, your control - in a VPC or on-prem deployment, logs are stored inside your infrastructure, so you own where they live and when they are purged.
- Export before expiry - forward logs to your own systems for longer-term retention if your policy requires it, then let iDBQuery age them out.
- Balance visibility and privacy - keep enough history for investigations and access reviews without retaining personal data longer than needed.
For example, a team might keep 90 days of audit history live in iDBQuery for day-to-day review while streaming a full copy to their SIEM for multi-year retention. Configurable retention supports privacy obligations such as GDPR data-minimisation, since you are not forced to hoard logs indefinitely. It complements iDBQuery's broader posture - audit logging of who did what, RBAC, and encryption in transit and at rest - by letting you decide the lifecycle of that record. Because the underlying data is queried in place, logs describe activity rather than duplicating your source data. Contact us for the retention options available in your deployment.
Updated 2026-06-22