Security
Last updated: November 2, 2026
What this page covers
This page summarizes how Yekar.AI protects the work your organization runs on it, which controls are yours, and what we do not claim yet. Each section links to the article in our documentation that sets out the full detail, including the limits of each protection. The documentation's Governance section is the complete reference.
Your workspace is kept apart
- Every record belongs to one organization and is read within it, so another workspace's records are never loaded and then hidden - they are never loaded.
- A tool from one of our built-in integrations can reach only the addresses it declares. Addresses on private and internal networks are refused before a request leaves, and a redirect never carries one request's clearance to another address.
Details: Platform security and Untrusted content.
Who can do what
People hold a role in the organization and a role in each domain they belong to. Organization Owners and Admins manage members and settings, but that does not let them open a domain's agents or conversations, and personal chats stay private from them. Every request is checked against the person's current access, and an agent's tool call can be held for a person's approval before it runs. Details: Roles and permissions.
Signing in
- Two-factor sign-in - an authenticator app or emailed codes - is available to everyone, and an organization can require it. See Two-factor sign-in.
- Single sign-on through your own SAML identity provider can be turned on for your workspace, and an organization can make it the only way in. See Single sign-on, which also lists what removing someone at your identity provider does not end.
- A browser left unused signs itself out - after three days, or sooner if your organization chooses - and each person can see and sign out any browser signed in as them. Passwords found in known data breaches are refused.
- API keys are shown once, expire, and open only what they were created for. We keep only a fingerprint of each key, so we cannot show one again.
A record of what happened
Before an agent or flow calls a connected app, the call is recorded - what it asked for, whose account it acted as and whether it reads or writes - and the record is completed with the outcome. Sign-ins, access changes, configuration changes, approvals and support access are written to your organization's audit log, which Owners and Admins can read and export on every plan. Audit records cannot be changed once written. Details: Audit before effect.
Credentials and encryption
- The credentials your organization stores for connected apps are encrypted with a key of its own, which is itself protected by a master key. They are decrypted only at the moment a call needs them and are never shown again - only their last four characters.
- Our primary database is encrypted at rest, and every connection to Yekar.AI uses HTTPS.
Details: Credential handling and Data lifecycle.
Your own infrastructure
On the Enterprise plan, an organization can keep its files in a storage bucket it owns, protect its stored secrets with an encryption key in its own key service - revoking that key makes them unreadable to us - or run its workspace on a database it owns. Each is set up with our team. Details: Data residency.
When our staff need access
Support access is never ambient, and it is yours to refuse. Your organization can turn support sessions off, or require one of your Owners or Admins to approve each one first. A session runs under a recorded grant with a time limit, cannot store secrets in your name, and every page it opened is listed for you under Settings → Support sessions. Details: When Yekar.AI staff need access.
Who processes your data
The services we use to run the platform, what each one receives and where, are listed on our Subprocessors page. How we handle personal information is in our Privacy Policy, and how a workspace answers a person's request for a copy of their data or its erasure is in Data-subject requests.
Report a vulnerability
If you find a security problem in yekar.ai, app.yekar.ai, docs.yekar.ai or the Yekar.AI API, email [email protected] with what you found and how to reproduce it. The same contact is published at /.well-known/security.txt. If we confirm an incident that affects your organization's data, we email your organization's Owners without undue delay with what happened, the data involved, what we did and what you should do.
What we do not claim
- We do not hold a SOC 2 report, an ISO 27001 certificate or any other third-party security certification, and our controls have not yet been assessed by an independent auditor.
- We have not yet had an independent penetration test, so we have no test report to share.
- We do not yet publish a standard data processing agreement. If your organization needs one, ask us through our contact page.
- We do not promise that data stays in a particular country or region beyond the locations listed on our Subprocessors page.
Where a specific control matters to your review, ask us - a straight answer about what exists is more useful than a badge.