HOW CONTROL WORKS

How Talons keeps you in control.

Talons keeps your account, your machine, your choices, and the actions it can take separate. Saying yes to one thing never quietly says yes to everything else.

Background checks and interactive help are different

Background monitoring happens on your machine and only reads information. Talons can record a local summary of what it finds while it keeps improving checks that respond when something changes. It does not investigate on its own or make repairs while you are away.

Access policies set the limits

Every registered capability has a plain-language permission: Always available, Ask first, or Never. A default policy applies across the machine, and a folder can inherit it, override it, or offer a separately named escalation policy. Being built in or downloaded never means a tool is automatically approved.

Talons checks the complete operation against the current device profile, connection approval, policy, folder rules, and any native confirmation it still needs. If a capability is not registered or its boundary cannot be enforced, Talons refuses it rather than inventing broader access.

Dangerous Mode is deliberately dangerous

Dangerous Mode is the break-glass alternative, not a folder policy. You must turn it on locally after an explicit warning. Until Talons has an operating-system sandbox for arbitrary child processes, a command can use this account's normal files, network, processes, and credentials—so treat it as device-wide authority. The GPT cannot turn it on, broaden it, or keep it alive after you press Stop. It stays visibly active, records what it does, does not survive a runner restart, and shuts off if the device session is no longer authorized.

The online service cannot give itself access

Talons uses an online connection to carry requests between your approved assistant and your machine. Your machine checks each request and keeps its private device key and local permission to run tools. A model cannot grant itself access merely by naming your device.

Repairs and receipts

Normal assessment is read-only. A repair follows the ask-before-action choice you selected and records what was requested and what happened. A finding is evidence to review, not a promise that Talons is always correct. Keep backups and review important changes.

Updates

Before the native installer can replace Talons, the updater verifies a Talons-specific signed release record and the exact downloaded app bytes. Approving an update never grants an assistant permission to operate your device.

Vulnerability disclosure

Email security@owlandkestrel.com with the affected surface, reproduction steps, impact, and a safe way to contact you. Please avoid accessing other people's data, disrupting service, or publishing an unremediated vulnerability. We will acknowledge a good-faith report and coordinate a reasonable disclosure timeline.