Last updated: 25 October 2026
Your context is never used to train models
Your private context is supplied at the moment of a request and is never used to train models.
- AI works when asked. It runs when someone asks, or when an admin turns on automatic summaries for recorded meetings. Those are off by default.
- It reads what is in front of it. A summary reads the thread, call or record it was asked about, under the asker's own access.
- Every run is recorded. Ishara keeps a record of each model run: what ran, for whom, and a fingerprint of what went in and came out, never the text itself.
Models and agents see only what you allow
Agents reach Ishara through the API and MCP with a key your workspace issues, and they see the same records, threads and calls the key's owner can see, nothing more.
- Scoped keys. Each key carries scopes, such as reading context or proposing changes, and can be narrowed to one object. Keys are stored only as hashes, shown once, expire by default and rotate with an overlap.
- Proposals, not writes. An agent proposes a change with its reason and evidence. A person applies it in Review, unless a member deliberately gives a key the apply scope.
- Every read logged. Each Context API call is recorded with its purpose. Email context carries subjects and senders, never message bodies.
- An off switch. Revoke a key and its next call is refused. An administrator can switch context sharing off for the whole workspace.
How keys, scopes and the MCP tools work: see the developers page.
Only your workspace can reach your records
Every record, value, view, list, email, call and automation belongs to one workspace, and only members of that workspace can reach it.
- Enforced in the database. The rule is held by row-level security in the database itself, not only in the app.
- Four roles. From owner to viewer, roles decide what each member can do.
- Deliberate ownership. Ownership moves only when the current owner confirms the new owner by name.
Mailboxes, calls and WhatsApp stay under your rules
Google Workspace and Microsoft 365 mailboxes connect through the provider's own sign-in screen. Ishara never asks for, sees or stores a mailbox password.
- Visibility per thread and per call. Choose who can open each one: only me, the people on it, my team, or everyone in the workspace.
- Disconnect means gone. Removing a mailbox takes everything synced from it with it.
- WhatsApp Business. A workspace admin connects the business number, and only its business conversations come in, never personal chats.
- Consent that holds. An unsubscribe stops marketing sends and sequence steps, and a bounce or a complaint stops everything to that address. The record of what a person refused outlives the rest of their data, in line with the Saudi Personal Data Protection Law and similar regional laws. Details on the email page.
Approval, history and export
AI you approve before it writes anything: a suggestion waits until a person accepts it, every accepted value stays marked as AI, and a rejected value goes back to what it was. Every value records who or what wrote it. See the AI page.
- Take your data with you. Every view exports to CSV, and the whole workspace exports to a spreadsheet.
- Deletion you control. Archived records stay restorable, Trash & retention lets you choose how long, and deletion always asks you to confirm the count.
- Leaving costs nothing. Nothing is deleted when a paid plan ends, and there is no exit fee.
- Signed webhooks. Every delivery is signed with HMAC-SHA256 and a timestamp, so a receiver can reject a replay.
Hosting, sub-processors and reporting
Ishara runs on its own dedicated database stack, separate from every other Lisan product, with its own keys, TLS on every connection and nightly backups. Hosting region and the sub-processor list on request at support@lisan.com.
Security questions, questionnaires and vulnerability reports go to support@lisan.com. To see these controls on screen, request a walkthrough.