Skip to main content
Platinur’s assistant and Initial Run use the OpenAI Platform with the customer’s own API key. This page states exactly what leaves the deployment.

​
What is always sent

  • Table and column names, column types, and null/distinct/row counts from the selected raw schemas
  • Generated dbt model SQL, dbt test definitions, and dbt run/test logs
  • Evidence dashboard source files
  • The instructions and chat messages users write to the assistant

​
What is sent only in the default mode

In the default Schema + sample values mode, profiling also includes up to three example values per column and min/max ranges for time columns, and the assistant may run bounded read-only SELECT queries against ClickHouse while it works. Columns whose names look sensitive (emails, phone numbers, tokens, and similar) are excluded from sampling in every mode.

​
Metadata-only mode

Set Data Boundary to Schema and statistics only under Configuration → Assistant → Advanced (or ai.profiling_mode: metadata_only in config/platinur.yaml) to guarantee no row values are included in AI requests:
  • Profiling sends column names, types, and counts — no sample values, no time ranges
  • The assistant’s row-level query tool is disabled and returns a policy notice instead of data
Metadata-only mode reduces generation quality somewhat: the model cannot see value formats (date layouts, enum casings, ID shapes), so expect more repair iterations on the first build.

​
What is never sent

  • ClickHouse, GitHub, SMTP, or webhook credentials — secrets are stored encrypted in portal metadata and are redacted from logs, status payloads, and support bundles
  • Portal user accounts and password hashes
  • Dashboard render output or exported data files