Stays in your account
Sources, buckets, agents and answers live in your account. Nothing is shared with other customers.
Elephant · Privacy
Your files stay in your account, are never shared with anyone else and never train shared models. Export or delete them whenever you want; Elephant itself never deletes. Each connected AI gets only what you allowed, read only or also save and organise, and when a key lacks a capability the API says which.
Sources, buckets, agents and answers live in your account. Nothing is shared with other customers.
Your knowledge is retrieved for your answers. It is not used to train models that serve anyone else.
Sources delete one at a time or up to 100 in one call. A bucket deletes with its members. A named agent deletes with its id.
On WhatsApp, contacts on the Hidden board are never read, never answered, and never used as knowledge.
The example
A restricted key carries an explicit list of capabilities. Ask it to do something outside that list and the 403 names the exact grant it lacks.
# A restricted sync key can upload and poll files, nothing else.
# Ask it to crawl a page and the API names the missing grant:
{
"error": {
"code": "forbidden_project_key",
"message": "This API key lacks the required capability.",
"retryable": false,
"details": { "required_capability": "knowledge:website:create" }
},
"request_id": "req_abc123"
}Key scopes
Full-access keys carry every capability. Restricted keys carry an explicit list. Provisioning and destructive grants must be given deliberately.
| Capability | Grants | How it is assigned |
|---|---|---|
| knowledge:file:read | Read sources, buckets, tasks, batches | Automatic on any key with the knowledge file API enabled |
| knowledge:file:create | Upload files, sessions, batches, import by URL | Automatic on any key with the knowledge file API enabled |
| knowledge:file:delete | Remove individual sources and detach bucket members | Explicit |
| knowledge:website:create | Ingest web pages | Explicit only, by design: crawling runs third-party analysis per call |
| knowledge:bucket:create | Provision buckets | Explicit |
| knowledge:bucket:delete | Delete a bucket and its member files in one cascade | Explicit |
| rag:agent:create | Provision named agents | Explicit |
| rag:agent:delete · rag:agent:update | Delete or update a named agent | Explicit |
The ask and search surfaces authenticate with the key itself and are governed by your plan’s answer entitlements, not by per-capability grants. Grants take effect on the key’s next request.
How it works
A sync job gets file create and read, nothing else. It can upload and poll without a single checklist grant.
A provisioning script gets bucket create, and agent create if it creates agents, and runs apart from steady-state sync.
Any key with more capability than its integration uses gets replaced by one that has exactly what it needs.
Out of bounds
On a business WhatsApp number, some conversations must never be processed. The Hidden board is not a lower priority; it is exclusion, and it is forward-looking from the moment a contact is placed there.
From the docs
| Isolation | Knowledge is kept within your account and is not shared with other customers |
|---|---|
| Training | Your knowledge is never used to train shared models |
| Export and deletion | Export any time; delete a source, up to 100 sources in one call, a bucket with its members, or a named agent |
| Keys | Full-access keys carry every capability; restricted keys carry an explicit list; destructive and provisioning grants are deliberate |
| On a missing grant | 403 forbidden_project_key · details.required_capability |
| Source visibility | An agent policy: retrieval still happens, and grounded_sources_state reports hidden when titles are suppressed |
| Opening a source | Citations carry a signed access_url when one is available; the original is not served publicly |
| Hidden board | Never read, never answered, never used as knowledge |
Questions and answers
Keep reading
PDFs, screenshots, pages and notes. What it reads and how you save it.
Folders your AI remembers. Ask one, or all of them.
Named assistants with their own buckets and instructions.
A source on every answer: file, page and passage, with a link to open it.
The exact passage, ranked, without a written answer.
The reference this page is written from, with every endpoint and field.
Start today
Connect your AI with only the access you choose, and see exactly what each key can and cannot do.