Connectors and Integrations
MORATUS can read data in connected apps; steps that change something in an app run only with your approval.
Which permissions are requested?
- Each connector asks only for the permissions it needs for its job, and the consent screen shows which data it will access.
- Permissions are requested incrementally: for example, Gmail read access (
gmail.readonly) is requested only when you connect Gmail, and Drive and Calendar permissions are asked for separately. - MORATUS accesses an app only when a request of yours, or a scheduled task you set up, needs that data; it does not scan data on its own in the background.
Steps that change something
For steps that leave a mark in a connected app, such as adding text to a Google Doc, updating cells in Sheets, or creating a new presentation, MORATUS first shows what it will do and waits for your approval. Connectors don't send email, create calendar events, or delete files.
| Action | Example | Approval |
|---|---|---|
| Read | Searching email, reading a file, listing channel messages | Not needed |
| Create | Google Docs document, Sheets spreadsheet, Slides presentation | Required |
| Update | Sheets cell, adding text to a Docs document | Required |
| Send and delete | Sending an email, sharing a message, deleting a file | Not done through connectors |
- A change you do not approve is not applied; you can ask for corrections in the chat before approving.
- Every action appears as a separate step in the chat, so you can see later what changed and when (see How do tools work?).
How tokens are protected
- Access and refresh tokens are encrypted on the server with AES-256-GCM and are never sent to the client.
- The OAuth flow is protected by a single-use, browser-bound PKCE state record.
- Connections are private to your account; no other user can use your connections.
Note
For MORATUS's overall security approach, see Security and Privacy.