Security and Privacy
Connectors let MORATUS reach your data in apps such as Gmail, Notion, or GitHub. Access is limited to the permissions you approve when connecting, and it's used only when a request or a scheduled task you set up needs that data; MORATUS doesn't scan data in the background on its own.
How is the connection protected?
- Permissions are requested incrementally; each connector asks only for what it needs. For example, Gmail read access is requested only when you connect Gmail; Drive and Calendar permissions are asked separately.
- The OAuth flow is protected by a single-use, browser-bound PKCE state record.
- Access and refresh keys are encrypted on the server with AES-256-GCM and are never sent to the client.
- Connections belong to your account; no other user, even on the same team, can use your connections.
Steps that make changes run with your approval
| Operation | Example | Approval |
|---|---|---|
| Read | Searching email, reading a file, listing channel messages | Not needed |
| Create and update | Docs document, Sheets cell, Slides presentation | Needed |
| Send and delete | Sending an email, posting a message, deleting a file | Not done through connectors |
A change you don't approve isn't applied. Scheduled tasks and automations run with your account's permissions and count as actions taken on your account's behalf, so review which connectors a task uses when you set it up.
Ending access
- When you remove a connection on the Connectors page, the encrypted keys are invalidated and MORATUS can no longer access that account.
- You can also revoke access from the app's own security settings; this lets you cut access immediately when you can't sign in to MORATUS at that moment.
- Removing a connection doesn't change your data in the app; it only ends MORATUS's access.
For details, see Permissions and security and Disconnecting.