Lana Orchestra
Menu
Workshop
Lana Orchestra

My projects and conversations.

AI, development, servers and World of Warcraft.

Delo / Дело · App privacy · 6 November 2026

Mail data and access

What Delo reads, stores on your Mac and shares with providers when you authorise it.

On this page

Who is responsible for the app

I’m Anton Grushin, the developer of Delo / Дело, a personal project within Lana Orchestra. You can contact me about data handling or the app at grushin.anton@gmail.com.

This notice describes the mail features of the macOS app. Visiting the website is covered by a separate website privacy notice. These pages do not connect a mailbox: the website does not receive emails, mailbox passwords or Google tokens.

Delo’s mail service runs on the user’s Mac. Gmail and Yandex remain the email providers. Synchronisation takes place between the app and the provider; sending a message passes its content to the mail provider and recipients. Mail does not pass through my server or the Lana Orchestra website. I do not automatically receive your correspondence.

Google permissions

Google sign-in takes place in the system browser. The app receives OAuth access, not your regular Google password. It requests openid, email and the selected mail permission:

openid
Identification of the account during Google sign-in.
email
The connected account’s email address.
https://www.googleapis.com/auth/gmail.readonly
Reading mail in read-only mode.
https://www.googleapis.com/auth/gmail.modify
Reading, creating and sending messages, changing their state and labels, and moving them to Trash. The current mail client uses this permission.

The app does not request access to Google Drive, Contacts or Calendar. gmail.modify does not allow permanent deletion that bypasses Trash; Delo has no such action in its interface. Google publishes the Gmail permission descriptions.

Google or an organisation’s administrator may restrict account access. Connecting with an app password requires that the provider and account rules allow this method.

What is stored on your Mac

The local app database contains the data needed by the mail section:

  • the account address, senders, recipients, message headers and folder metadata;
  • downloaded message content, attachment metadata and downloaded attachments within the app’s limits;
  • drafts, draft versions and sending snapshots;
  • summaries, jobs, links between emails and tasks, events and operation receipts.

The full message body is requested when you open it, separately from background header loading. The initial download covers the last 14 days of incoming mail; older messages and folders are loaded separately. Attachments are downloaded using an explicit button and saved through the macOS dialog.

External images, scripts and forms in HTML emails are not loaded. I do not claim end-to-end encryption of correspondence or encryption of the entire local mail database.

Credentials and backups

App passwords, Google access and refresh tokens, and OAuth settings are stored in macOS Keychain. These secrets are not included in the mail database or the ordinary error log.

A full local app database backup includes mail data and files. Keychain is not included in that backup. Additional backups made by the operating system or the user remain under the user’s control. They also need to be considered when deleting data.

The optional assistant

Automatic mail analysis can be disabled, run locally through LM Studio on the same Mac, or sent to OpenAI. Local mode is the default; no analysis runs until a model has been selected.

Cloud analysis is disabled for each mailbox until separately authorised. It requires a selected provider and model, a configured key and permission to process that particular mailbox in the cloud. Connecting Gmail does not enable it.

What OpenAI receives

When cloud analysis is authorised, the app sends the following directly to OpenAI:

  • the subject, sender name and address, and message date;
  • a limited amount of message text or an excerpt;
  • indicators of incomplete content and spam;
  • the names and types of up to 20 attachments.

Automatic analysis does not send the contents of attachments to OpenAI. Classifications and short summaries are stored locally and need your review.

The external provider has its own processing and retention terms. I do not promise zero data retention by OpenAI. Before enabling cloud mode, review OpenAI’s data handling documentation. The selected model may incur charges under the provider’s pricing.

Connected agent access

You can separately permit connected agents to read messages, work with drafts and attachments, and change message state. Permissions are configured per mailbox and are all disabled by default.

An external client or model selected by the user may receive data within those permissions. A local mail service does not mean that every integration you authorise also stays entirely on your Mac.

Agents have no permission to send messages. Before sending, the user confirms the exact saved version of the draft.

Limited Use commitment

I commit to following the Google API Services User Data Policy, including its Limited Use requirements, when Delo uses or transfers information received from Google APIs.

These data are used for the stated mail features and separately authorised assistance. I do not sell emails or use Google data for advertising or to train general-purpose AI or machine-learning models. I do not transfer the data for those purposes. Authorising cloud analysis does not authorise training general-purpose models.

Retention, disconnecting and deletion

There is no fixed automatic deletion period for the mail cache. Deleting an email at the provider does not erase all local historical data.

Disconnecting an account in Delo removes its access credentials from Keychain and stops synchronisation. Local history, drafts and links to tasks remain.

Disconnecting does not automatically revoke access at Google. To revoke Delo’s Google permission, separately visit your Google Account connections settings.

The current interface has no separate button to erase all local data for a mailbox. Full cleanup requires a separate procedure to remove local storage and backups. You can request instructions at grushin.anton@gmail.com. Do not send passwords, tokens or correspondence when requesting those instructions.

Questions and control over data

You choose the accounts to connect, Google permissions, the assistant mode and agent access. Cloud analysis and agent access can be disabled in the relevant mailbox settings; Google access is revoked separately through Google.

For questions about access, correction, deletion or restriction of processing, email me at grushin.anton@gmail.com. Describe the action you need. Because mail storage is on your Mac, I cannot remotely inspect or erase it for you; I can provide instructions.

An email you choose to send to the project contact will pass through mail providers. Do not include unnecessary personal data, mailbox content or secrets. General information about correspondence with me and data requests is available in the website privacy notice.