Security & Governance
How Edilitics protects your data at rest, governs AI access, and gives your team full accountability over every action taken in the workspace.
Edilitics is built on two principles: your data stays yours, and every action is accountable. This section covers how data is protected at rest, how AI features are governed, and how your team maintains full visibility over what happens in the workspace.
What Edilitics Stores
Your underlying database or warehouse records are never stored on Edilitics infrastructure. What is stored is metadata, configuration, and conversation history, all encrypted before storage using per-workspace keys.
| Data | Where it comes from | Stored? |
|---|---|---|
| Connection credentials | Integrate: database host, port, username, password, OAuth tokens | Stored, encrypted |
| Schema and column metadata | Integrate: table structure, column names, data types, DQ statistics, AI-generated column insights | Stored, encrypted |
| Pipeline configuration | Transform: operation sequence, source/destination mapping, schedule, compute settings | Stored, encrypted |
| Transform run history | Transform: run status, phase timing, row counts, per-operation metrics, error logs | Stored, encrypted |
| AskEdi conversations | AskEdi: chat titles, prompt text, LLM replies, generated SQL, chart data, follow-up suggestions, runtime metrics | Stored, encrypted |
| Dashboard and chart configurations | Visualize: chart type, column mappings, filters, aggregations, sheet structure, external share tokens | Stored, encrypted |
| Transform sample snapshot | Transform: a temporary 16,600-row preview snapshot used while configuring operations | Temporary, encrypted. Deleted on save or exit |
| Raw data rows | Your source tables and warehouse records | Never stored |
Encryption
All stored data is encrypted at rest using Fernet symmetric encryption with per-workspace keys derived via PBKDF2-HMAC-SHA256 (100,000 iterations). Each workspace key is derived from three independent inputs: a domain-level salt stored in GCS, a user-level salt stored in the database, and a common application key held in the server environment. All three must be present to derive the key. A compromised key from one workspace cannot decrypt data from any other.
See Data Encryption for the full breakdown.
Access Control
Every resource in Edilitics has an owner and an explicit share list. Access is never implicit.
| Module | Who can access |
|---|---|
| Integrate | The user who created the integration (owner) and any users the owner explicitly shares it with. Workspace admins have access to all integrations in the organisation. |
| Transform | The pipeline owner and any users the owner shares it with by email. Shared users can view and run, but cannot edit, delete, duplicate, or reshare. Workspace admins have full access across all pipelines. |
| Visualize | The dashboard owner and explicitly shared users. Dashboards can also be published via a shareable external link with an encrypted access token. Workspace admins have access to all dashboards. |
| AskEdi | The conversation owner and any users the owner explicitly shares it with (view-only). Shared viewers can read the conversation and download a PDF export but cannot continue the chat. Workspace admins have access to all conversations in the organisation. |
AI Data Governance
Edilitics provides three privacy modes that control exactly what schema context is sent to an LLM when you use AskEdi, Visualize, or Integrate AI features. No raw data rows are ever sent in any mode.
The three modes are Private, Balanced, and Full Context. What each mode sends differs per module: Integrate, AskEdi, and Visualize each have their own payload toggles. Private mode is not "no context": it still sends structural metadata while protecting column identities. Full Context sends the most schema detail but never sends actual data rows.
See Privacy & Context Modes for the exact per-module breakdown of what each mode includes and excludes.
Audit Logs
Every action taken in the workspace is logged with the acting user, a timestamp, and a human-readable description. Logs are available to workspace admins and are exportable as CSV. Retention varies by plan, from 7 days on the evaluation plan up to 365 days on Team Pinnacle. Enterprise plans have a custom retention period.
See Audit Logs for the full list of tracked actions per module.
Bring Your Own Key (BYOK)
Workspace admins can configure API keys for OpenAI, Anthropic, or Google DeepMind at the organisation level. When a BYOK key is active, Edilitics routes all AI requests through that key: your quota, your provider account. Admins control which features use the key and can test connectivity before activating it.
By default, most AI providers log API requests and may use them to improve their models. Before activating a BYOK key in Edilitics, explicitly disable logging in your provider's dashboard. Each provider's policy differs: review it before use.
See Bring Your Own Key (BYOK) for setup instructions and provider-specific logging guidance.
File Upload Security
All files uploaded through Integrate are scanned for malicious content before processing and stored in an isolated bucket. Size limits are enforced per format. See Data Encryption: File Upload Security for the full format and size table.
In This Section
Data Encryption
What is encrypted, how key derivation works, and the complete list of data Edilitics stores and protects.
Privacy & Context Modes
Control exactly what schema context is sent to an LLM. Per-module breakdown of Private, Balanced, and Full Context modes.
Audit Logs
Every action logged with user, timestamp, and description. What's tracked per module, who can see what, and how to export.
Bring Your Own Key (BYOK)
Set up your own API keys for OpenAI, Anthropic, or Google DeepMind. Control which features use your key and what your provider logs.
Need help? Email support@edilitics.com with your workspace, job ID, and context. We reply within one business day.
Analysis Credits
How monthly analysis credits are allocated, pooled on Team plans, doubled with BYOK, and topped up with non-expiring add-on packs.
Data Encryption
How Edilitics encrypts every piece of data it stores using per-workspace key derivation. What is stored, what is never stored, and how encryption works.