Annex D — Observability / Logging / Retention Summary

1. Default logging

The Service stores Usage Data and archives usage events for billing, security, and analytics.

2. Observability is opt-in

Where Observability is enabled for a Token/Account, the Service may log and store sanitised request/response bodies and technical metadata (e.g., client IP, country code, edge location, user agent, request/response sizes, timing). Observability Data is processed solely for security, troubleshooting, performance optimisation, billing, and compliance purposes, and shall not be used for model training or profiling unless expressly agreed.

3. Storage locations (current architecture)

• Usage events are archived to object storage (S3/MinIO) as JSON.
• Operational retention for streams/queues and audit tables may be limited per internal retention configuration.
• Long-term retention in object storage/analytics is controlled by lifecycle policies.

4. Customer responsibility

You must configure Observability responsibly and must not enable it for prohibited/sensitive processing without lawful basis and safeguards.

5. Data retention

Unless otherwise agreed in an Order Form, Observability Data shall not be retained longer than ninety (90) days.

6. Minimisation

Infere applies data minimisation and sanitisation techniques where feasible to reduce the inclusion of personal data within Observability Data. Where Observability Data contains personal data from User Content, Infere processes such data as Processor, except where required to process as Controller for security or legal compliance purposes.

7. Access limitation

Access to Observability Data is restricted to authorised personnel and systems with a legitimate operational, support, security, or compliance purpose.