What you authorize when you connect an inbox
Connecting an inbox grants Prune specific permissions through your provider. Here's what each one allows, why it's needed, and how to take it back at any time.
Permissions depend on the features you enable and what you approve at connection. We describe each permission in plain language; advanced users can expand the technical detail.
Gmail & Google Workspace
View messages and metadata
Core- What it allows
- Read senders, subjects, dates, labels, and message content needed to organize your inbox.
- Why it's needed
- Sender-level cleanup and communication features need to understand what is in your inbox.
- When it's used
- During initial analysis and when keeping your view up to date.
▶Technical detail
Maps to read-oriented Gmail API scopes. The exact scopes are finalized in the Google integration and shown to you on the Google consent screen at connection.
Modify, archive, and label
Requires your approval- What it allows
- Apply labels and move messages out of the inbox when you approve a cleanup action.
- Why it's needed
- Cleanup decisions like archive and grouping require modifying mailbox state.
- When it's used
- Only when you approve an action or one is enabled in your settings.
▶Technical detail
Maps to modify-oriented Gmail API scopes. High-impact actions reflect your approvals.
Move to Trash / delete
Requires your approval- What it allows
- Move messages to Trash or delete them when you choose that action.
- Why it's needed
- Some cleanup choices remove messages rather than archive them.
- When it's used
- Only when you choose a delete or trash action.
▶Technical detail
Trash/delete behavior follows Gmail API capabilities; recoverability follows Gmail’s own Trash rules.
Send / draft
Optional feature- What it allows
- Create a draft or send email where a specific feature requires it.
- Why it's needed
- Certain future features may need to draft or send on your instruction.
- When it's used
- Only if you enable a feature that requests it and you authorize the scope.
▶Technical detail
Not requested unless a feature that needs it is enabled and separately authorized.
Outlook, Microsoft 365 & Microsoft accounts
Read mail
Core- What it allows
- Read senders, subjects, dates, folders, and message content needed to organize your inbox.
- Why it's needed
- The same organizing features require understanding your mailbox.
- When it's used
- During initial analysis and ongoing updates.
▶Technical detail
Maps to read-oriented Microsoft Graph mail permissions, shown on the Microsoft consent screen at connection.
Read/write mail (move, folders)
Requires your approval- What it allows
- Move messages and apply folder changes when you approve a cleanup action.
- Why it's needed
- Archive and grouping require writing mailbox state.
- When it's used
- Only when you approve an action or enable it in settings.
▶Technical detail
Maps to read/write Microsoft Graph mail permissions.
Delete mail
Requires your approval- What it allows
- Delete or move messages to Deleted Items when you choose that action.
- Why it's needed
- Some cleanup choices remove messages.
- When it's used
- Only when you choose a delete action.
▶Technical detail
Delete behavior follows Microsoft Graph capabilities and your account’s retention settings.
Send mail
Optional feature- What it allows
- Send or draft email where a specific feature requires it.
- Why it's needed
- Certain future features may need to draft or send on your instruction.
- When it's used
- Only if you enable a feature that requests it and you authorize it.
▶Technical detail
Not requested unless a feature that needs it is enabled and separately authorized.
How to revoke access
You can disconnect an inbox in Prune at any time, and you can withdraw the permissions you granted directly with your provider: Google Account → Security → Third-party access, or Microsoft Account → Privacy / Apps & services. To delete your account and associated data, contact us.
Permission names, behavior, and technical scopes shown here are draft descriptions and are confirmed against the implemented provider integrations before publication.