cicora.ai
API specificationData handling

Data and privacy

Minimize transmitted data, separate an end-user identifier from content, and control retention in your product.

Integration reference: choose parameters and available capabilities from your account API settings and the model catalogue for your environment.

Compose the minimum request

Send a model only the context needed for an answer. Remove tokens, passwords, payment data, and internal identifiers from a prompt before transmission.

The user field is suitable for an opaque stable identifier in your product; do not send email, phone, or a name in it.

Stable end-user identifier
json
{
  "model": "openai/gpt-5.6-sol",
  "messages": [{"role": "user", "content": "Summarize the supplied note."}],
  "user": "internal-user-opaque-id"
}

Files and journals

  • Set a retention period for attachments and derived artifacts.
  • Redact secrets in your observability application.
  • Restrict access to source requests by role and need.

Handle a subject request

Document where request content, artifacts, and journals live in your application so deletion or export can be performed.

Separate operational metrics from user content: it simplifies diagnosis and reduces sensitive-data volume.