Mission Desk

Privacy policy

Last updated: November 10, 2026

Who to contact

For Mission Desk privacy, access or deletion questions, contact mehrdad.kheirollahi@gmail.com. Please do not send passwords, access tokens or copies of your mailbox.

Information in the desktop workspace

The workspace stores missions, project records, instructions, execution status, output versions, your review decisions and local activities. When you select email for import, it stores message identifiers, sender and recipient headers, subject, date, labels, a text copy and local activity references.

These records are held in a local application database on your device. Email records are not separately encrypted by Mission Desk. Protect your Windows account and use appropriate device encryption, backups and access controls.

Gmail access and use

The Gmail integration requests only gmail.readonly, which Google describes as permission to view email messages and settings. Mission Desk uses it to verify your connected account, search a range you choose and read up to three messages per manual request. Google grants read-only access at the account level; the three-message limit is an application limit for each manual request, not a limit on the OAuth permission. It has no Gmail send, draft, delete, label-change or mark-as-read operation.

Imported messages are presented as text. The reader does not load remote images or follow message links automatically. The Gmail reader does not fetch message attachments separately. Linking a message to a local activity does not change your Gmail mailbox.

Google sign-in takes place on Google's website. The app stores its OAuth credentials locally using Windows user-bound encryption. Mission Desk does not ask for or store your Google account password.

Mission Desk's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Mission Desk does not sell Google API data, use it for advertising, or use it to develop, improve or train generalized artificial intelligence or machine-learning models.

AI processing is a separate action

When you submit a mission for AI execution, its instructions and selected sources are sent to the connected Codex service. The AI provider processes those submissions on its infrastructure under its own terms and privacy practices. Your subscription, account permissions and provider availability apply.

The Gmail integration does not automatically add imported email bodies to AI mission inputs. An email activity link is a reference; it does not by itself send the message body to the AI provider. Consider the contents of any text you manually submit for AI processing.

Other local integrations

An existing local Yahoo connector can be used through Mission Desk's read-only interface. The interface permits folder listing, search and reading with mark-as-read disabled. The underlying connector may have broader capabilities outside Mission Desk. No Yahoo send or mailbox-change tool is exposed by Mission Desk.

Retention, controls and deletion

Local workspace and email records remain on your device until removed. Pausing a connection stops intake in Mission Desk; it does not revoke the provider's authorization or erase stored copies.

You can revoke Google access through your Google Account connections. Revoking access stops future authorized reads but does not delete existing local records. Contact the support address above for instructions to remove local records. Existing backups must be managed separately on the devices or storage where you keep them.

If you export a mission, its email references contain metadata rather than email bodies. A full application backup can contain locally imported email records. You control where you place exports and backups.

This public website

The public website is hosted on the owner's DigitalOcean infrastructure in Toronto, Canada. The host receives standard connection information, including an IP address and browser request details, and may process operational or security logs. This site does not contain an application login, upload form, advertising tracker or third-party analytics script. A contact email is provided instead of a web contact form.

If you email support, your message and address will be handled to respond to your request. Please provide only the information needed. We do not need access to your mailbox to answer a product question.

Changes

We will update this page when the product's data practices change and show the revised date above. Material changes in data access or processing will be disclosed before the changed feature is used.