daywingA useful agent needs access to do real work. Daywing keeps that access tied to the person, the account, and the action you authorized.
Personal conversations, tasks, and memory are scoped to the employee and their own agents. Company knowledge is shared separately. Administrator app assignments do not make another employee’s private conversation visible.
Administrators can assign specific systems to each agent. Employees can connect their own accounts. Permissions are checked again when an action runs, including after an account or delegation is revoked.
Daywing can prepare an exact external change for review or act within a matching saved delegation. Approved writes are checked against the saved result. Uncertain sends or changes are recorded for reconciliation instead of being repeated blindly.
Provider credentials configured in Daywing are encrypted on the server with AES-GCM and kept out of model context. Connected-app accounts and employee browser sessions have their own access boundaries.
Saved jobs retain objectives, source references, prepared results, and action receipts. A prepared draft and a verified external change are represented separately.
Daywing is in private pilot. It does not currently hold a SOC 2 attestation. We document what has been tested and what still requires a real company-account pilot.
Work context is sent to the AI and integration providers needed to perform the job. This page describes the implemented access controls; it is not a compliance certification.
Review pilot evidence ↗We’re welcoming pilot teams.