Skip to main content

​
Availability

Tyk AI Studio assigns a privacy score to LLM configurations, Tools, and Data Sources. This score controls which resources can be used together, so that sensitive data cannot reach a less trusted LLM.

​
The Privacy Score Scale

The UI presents four named privacy levels. Each maps to a fixed integer score:
Privacy scores are stored as plain integers. The four named levels above map to the code’s internal scale, but the live create/edit forms for LLMs, Tools, and Data Sources currently show a raw 0-100 number field, not a named-level selector.

​
How the Comparison Works

A resource with a higher privacy score than the LLM it is used with cannot be attached to that LLM. For example:
  • A Restricted (100) Data Source cannot be used with an LLM Configuration whose privacy score is only Internal (50).
  • A Public (25) Tool can be used with any LLM Configuration, since 25 is the lowest score.
This check applies to:
  • Tools used with an LLM Configuration.
  • Data Sources used with an LLM Configuration in a RAG-enabled Chat.
  • Apps, when an admin approves or edits the App’s associated resources.
If a user tries to combine resources that fail this check, Tyk AI Studio blocks the action and shows an error.

​
Where You Set a Privacy Score

You set a privacy score when you create or edit: Community submissions to the AI Portal also carry a suggested privacy score from the submitter, which an admin can change before approving the submission.