Skip to main content
Tuteliq stores an incident record whenever a detection warrants attention, so you can review a moderation queue, run trend reports and produce compliance evidence. If you already run your own moderation infrastructure, you can turn that off. Detection results still come back in full on every API response; Tuteliq simply keeps no record of them.
This setting controls incident metadata only. It does not change Tuteliq’s content policy: original text, images, audio, video and documents are never stored, regardless of this setting.

​
What incident metadata is

An incident record holds the abstracted result of a detection, never the content that produced it: Summaries are encrypted. If you have registered a public key for bring-your-own-key encryption, they are hybrid envelopes that Tuteliq cannot decrypt.

​
Turning it off

The setting is incident_moderation_enabled on your account, and it applies to every detection call made with that account’s credentials. It defaults to true.
1

Open account settings

Go to Settings > Incident Logging in the dashboard.
2

Switch incident logging off

The change applies to new API calls within one minute. Existing incidents are not affected and remain available until they expire under your retention period.

​
Per-call override

Every detection endpoint accepts an optional incident_moderation_enabled field that overrides the account setting for that single request:
  • true forces the incident to be logged for this call, even if your account has logging off.
  • false suppresses logging for this call, even if your account has logging on.
  • Omit it to use your account setting (the default).
Precedence is per-call, then account, then the built-in default (true). Use it to suppress logging for test traffic, or to opt individual calls in or out without changing your account setting. Everything under What changes when it is off applies to a call suppressed this way.
false is honoured as an explicit value, not treated as “unset”. A suppressed call writes no incident, grooming assessment, or notification, exactly as if the account setting were off.
The field is available in the same place as the other tracking fields (external_id, customer_id, metadata) across the REST API, the Node SDK, and the MCP tools.

​
What changes when it is off

Nothing is written, rather than written and then deleted. No record is created at any point. Detection behaviour, accuracy and scoring are unaffected. The only difference is whether a record survives the response.
With logging off, the API response is the only copy. If you need a record, capture it from the response and store it in your own systems. Tuteliq cannot recover an incident that was never written.

​
Retention

While incident logging is on, incidents are retained for 90 days by default. You can set your own period with incident_retention_days, anywhere from 7 days to 2 years. When the period expires, records are permanently deleted.
Retention applies to incident and grooming assessment records. Records Tuteliq holds under a statutory obligation, such as audit logs, consent records and breach logs, are set by that obligation and are not configurable.

​
Choosing a setting

Leave it on if you want a moderation queue, historical trend analysis, or evidence for a DSA, KOSA or COPPA review. The audit receipt for a specific request is the artefact to cite when a regulator asks for proof that a particular assessment happened. Turn it off if you have your own logging infrastructure and would rather no vendor hold a second copy. A shorter retention period is the middle ground: set it to 7 or 30 days and keep incidents just long enough to work a queue.

​
Data subject requests

While incident logging is on, Tuteliq processes incident metadata as a processor on your behalf, and you remain the controller. See GDPR compliance for the export, rectification and erasure endpoints. While it is off, there is no incident data to export or erase, because none was created.