Skip to content
Security Controls, approvals, audit

AI that acts, within the limits you set.

Sekia can read files, run commands and make changes in your business apps. Here is how each of those stays under the control of the person using it and the admin who runs the workspace.

Approval before every Mac action

The Mac app shows the exact command, file or click before it runs. The person chooses Allow, Deny, or allow one app for the rest of that chat.

Password apps are never pre-approved

Keychain Access, Passwords, 1Password, Bitwarden, LastPass, Dashlane and System Settings always ask, every time.

App approvals expire

An "allow this app in this chat" approval ends after 24 hours idle, when it's revoked, or when remote control is turned off.

Rules for every app action

Admins set each connected-app action to Allow, Ask first or Blocked, with overrides by role and by person. Blocked actions are hidden from the assistant.

Each person uses their own account

People connect apps with their own login, so the assistant sees only what they could see. Shared logins start blocked for any action that changes data.

No passwords

People sign in with a link sent to their work email. On the Mac, the session is stored encrypted with a key held in the macOS Keychain.

Remote control

Your Mac answers remote requests only when you say so.

  • Off by defaultRemote control can only be switched on from the Mac itself.
  • Same person onlyA browser chat can only reach Macs that belong to the person signed in. API keys can't approve actions.
  • Pause any timePausing from the menu bar refuses new requests, and turning remote control off cancels any that are waiting.
  • Rate limitedEach Mac accepts at most 60 remote actions an hour.
Audit log
TimeActionDecision
09:14HubSpot search contacts · a.leeallowed
09:16HubSpot update deal · a.leeapproved
10:02Mac run command · j.ortizapproved
10:05Box delete file · j.ortizblocked
11:40Mac open Safari · m.chendeclined

Every connected-app call and Mac action is recorded with the person, the action and the decision.

Under the hood

How the Mac app is built

Signed

Signed and notarized

Every release is signed with an Apple Developer ID and notarized by Apple. Updates install only if the signature matches.

Isolated

Sandboxed screens

The interface runs sandboxed with no direct network or file access. All requests go through the app's core, and generated content renders on a separate origin.

Scoped

macOS permissions you grant

Accessibility and Screen Recording stay off until you allow them in System Settings, and the app tells you which actions need them.

See the controls for yourself.

Create a workspace, add an app, and set its permissions. It takes a few minutes.