OgnelissSummary
Ogneliss Mail is an email, calendar and contacts app for Android and iOS (iPhone and iPad). It connects your device directly to the mail servers of the accounts you add: Gmail, Microsoft Exchange, Outlook.com, Yandex, Mail.ru and other IMAP/SMTP providers. Your messages, attachments, contacts and events are stored only on your device (in an encrypted database and the App's private storage) and are exchanged only with your own mail providers. The developer has no servers that store your mail and never receives its content. No ads, no analytics, no sale or sharing of data, and your data — including Google user data — is never used to train AI models or to create AI-generated content.
1. Who we are
This Privacy Policy explains how the Ogneliss Mail app for Android and iOS (package / bundle ID com.ogneliss.mail, the "App") and its website https://ogneliss.ru/mail/ handle your information.
Developer and data controller: Ermishin Oleg Andreevich (individual developer)
Contact for privacy questions and data requests: oedante@gmail.com
Current version of this policy: https://ogneliss.ru/mail/privacy
2. What the App is for
The App is an email client. Its only purpose is to let you read, write, search and organise your email and to view and manage the calendar and contacts of the accounts you connect, all in one app. It supports Microsoft Exchange (ActiveSync and EWS), Gmail, Outlook.com, Yandex, Mail.ru and other providers via IMAP and SMTP, with sign-in either through the provider's own sign-in page (OAuth) or with a password / app password.
The App contains no generative artificial intelligence (AI) features and does not send your data to any AI service.
3. Information the App accesses and why
The App accesses only what is needed for the features you use:
| Information | Why the App uses it | Where it is stored | Where it is sent |
|---|---|---|---|
| Account address, password or app password, OAuth tokens | Signing in to your mail, calendar and contacts servers | On your device, in secure storage (encrypted): on Android protected by the Android Keystore, on iOS in the iOS Keychain; see section 10 | Only to your mail provider; with OAuth sign-in, tokens pass through the sign-in server (section 6) |
| Email messages, folders and labels, attachments, drafts | Showing, searching, writing, sending, moving and deleting mail; reading offline | On your device, in the encrypted App database and the App's private storage | Only to your mail provider (when you send, move or delete) |
| Contacts of the account | Showing contacts, suggesting addresses, saving contacts you edit | On your device, in the encrypted database | Only to your mail provider |
| Calendar events and tasks of the account | Showing your calendars, creating and editing events, answering invitations, reminders | On your device, in the encrypted database | Only to your mail provider |
| Basic profile from OpenID sign-in: name, email address, profile photo | Identifying the account and labelling it in the App (account list, sender name) | On your device | Not sent anywhere; the photo is loaded from your provider's server |
| Device contacts and calendar (only with your permission) | Address suggestions; showing events in the system calendar; on iPhone and iPad also saving contacts and meetings from your mailbox to the iPhone or iPad address book and calendar, if you turn this on | On your device | Not sent anywhere |
| Signatures, templates, rules, categories, settings | Running the App the way you set it up | On your device; Exchange server rules are saved on your Exchange server | Exchange rules only to your Exchange server |
| Phrases from messages you have written (for phrase suggestions) | Offering to complete common phrases while you write | On your device | Not sent anywhere |
| Diagnostic log | Troubleshooting | On your device | Only if you choose to share it yourself (for example, send it to support) |
The App does not collect your location, advertising identifiers, browsing history, payment data or the content of other apps.
4. Google user data
This section applies when you add a Google account (Gmail / Google Workspace) using "Sign in with Google".
4.1. Google scopes the App requests and why
| Google scope (permission) | What the App does with it |
|---|---|
https://mail.google.com/ (Gmail: read, compose, send and permanently delete email) | Connects to Gmail over IMAP and SMTP — the standard email protocols that Google makes available only with this scope. Used to download and show your messages, folders (labels) and attachments, to search them, to send the messages you write, and to move, mark, archive and delete messages when you ask. |
https://www.googleapis.com/auth/gmail.settings.basic | Reads your existing Gmail signature ("Send mail as" settings) once when you add the account, so you don't have to type it again. The App does not change your Gmail settings. |
https://www.googleapis.com/auth/calendar | Connects to Google Calendar over CalDAV to show your calendars and events and to save the events you create, edit, delete or respond to in the App. |
https://www.googleapis.com/auth/carddav | Connects to Google Contacts over CardDAV to show your contacts, suggest addresses while you write, and save the contacts you create or edit in the App. |
openid, email (…/auth/userinfo.email) | Identifies which Google account you signed in to (your email address). |
profile (…/auth/userinfo.profile) | Shows your name and profile picture next to the account in the App. |
The App requests no other Google scopes and uses no other Google APIs. Each scope is used only for the feature described above.
4.2. Where Google user data is stored
Google user data (messages, attachments, labels, contacts, calendar events and profile information) is downloaded directly from Google to your device and stored only on your device, in the App's encrypted database (SQLCipher) and private storage. It is not uploaded to, stored on or processed by any server of the developer. OAuth tokens are kept in the device's secure storage (on Android protected by the Android Keystore, on iOS in the iOS Keychain); the refresh token is additionally encrypted (see section 6).
4.3. Limited Use
Ogneliss Mail's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular:
- Google user data is used only to provide the user-facing email, calendar and contacts features that you see in the App's interface, and only on your device.
- Google user data is transferred only to Google itself, to carry out your actions (for example, sending a message or saving an event). It is not transferred to anyone else, except where necessary for security purposes (for example, investigating abuse), to comply with applicable law, or as part of a merger, acquisition or sale of assets with prior notice to you.
- Google user data is not used or transferred for serving advertisements, including retargeting, personalised or interest-based advertising.
- Google user data is not sold, and is not used to determine creditworthiness or for lending purposes.
- Google user data is not used to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models, and is not used to create, train or distribute AI-generated content of any kind.
- No human reads your Google user data. The developer has no access to it. The only exceptions are: (a) you have given explicit consent for specific data — for example, you send a message or a diagnostic log to support yourself; (b) it is necessary for security purposes, such as investigating abuse; or (c) it is required to comply with applicable law.
4.4. No AI-generated content, no NCII
Ogneliss Mail does not use Google APIs or Google user data to create, train or distribute AI-generated non-consensual intimate imagery (NCII) or any other AI-generated content. The App contains no generative AI features that use Google data.
The only text suggestion feature in the App — offering to complete a phrase while you write a message — is a simple local function: it suggests phrases from a built-in list and from phrases you have written before. It runs entirely on your device, uses no AI model and sends nothing anywhere.
5. Microsoft, Yandex, Mail.ru and other providers
The same principles apply to all other accounts: data is downloaded directly from your provider to your device, stored there encrypted, used only for the App's features and sent only back to that provider. If you sign in with Microsoft, Yandex or Mail.ru through OAuth, the sign-in server described in section 6 is used in the same way as for Google.
If you connect a work account (for example, your organisation's Microsoft Exchange), that account's data is also processed by your organisation, on its own server and under its own rules. The organisation's server may require a screen lock and may issue a remote wipe; on such a command the App deletes the work account's data from the device. The developer has no access to your organisation's servers.
6. The sign-in server (ogneliss.ru/oauth)
To sign in with Google, Microsoft, Yandex or Mail.ru, the App uses a small server run by the developer at https://ogneliss.ru/oauth. It exists because the OAuth client secret issued by these providers must not be embedded in an app that anyone can download. Its only job is to exchange the authorisation code for tokens and to refresh tokens. How it works:
- You sign in on the provider's own page (for example, Google's) in the browser. The developer never sees your password.
- The provider sends a one-time authorisation code to the server. The server exchanges it for an access token and a refresh token at the provider's token endpoint, and reads your email address and name from the ID token issued by the provider so that the App can label the account.
- The refresh token is immediately encrypted (AES-256-GCM) with a key that exists only on the server. The access token, the encrypted refresh token, your email address and name are held in the server's memory (RAM) for at most 2 minutes, under a random one-time code, until the App collects them over HTTPS with a PKCE check. They are deleted from memory as soon as the App collects them or the 2 minutes expire. They are never written to disk or to a database.
- The App keeps the encrypted refresh token in the device's secure storage (see section 10). When the access token expires (usually after an hour), the App sends the encrypted refresh token to the server; the server decrypts it in memory, requests a new access token from the provider, returns it to the App (with a new encrypted refresh token if the provider issues one) and keeps nothing.
- The server never connects to your mailbox, calendar or contacts, and never reads, stores or forwards messages, contacts, events or any other content. All of that travels directly between your device and your provider.
- The server has no user accounts and no database of users or tokens.
- For security and troubleshooting, the server writes a technical log: one line per request with the date and time, the request method and path (without query parameters, so without codes or tokens), the response status and duration, and the IP address; when a provider refuses a request, the provider's error code. The log is limited in size and old entries are overwritten automatically.
7. What the App does not do
- It does not show ads and contains no advertising SDKs.
- It does not collect analytics, crash reports or the advertising ID, and contains no third-party tracking SDKs.
- It does not sell your data or share it with third parties, except with your own mail providers to carry out your actions (and your organisation, for work accounts).
- It does not send the text of your messages anywhere other than your mail servers: the App uses no cloud text processing or AI services.
- It does not use your data, including Google user data, to train AI or machine learning models.
- It does not let senders track when you open their messages: a built-in blocker disables tracking pixels.
8. Sharing and disclosure
Your information is sent only to:
- the mail, calendar and contacts servers of the accounts you add (for example, Google, Microsoft, Yandex, VK (Mail.ru) or your organisation's server) — to carry out what you ask the App to do;
- the recipients of the messages you send;
- the sign-in server described in section 6 — tokens only, never content.
The developer does not hold your mail, contacts or calendar and therefore cannot disclose them. The sign-in server log may be disclosed only if required by law.
9. Permissions
9.1. Android permissions
| Permission | Why |
|---|---|
| Internet, network and Wi-Fi state | Connecting to mail servers |
| Notifications, vibration | New mail alerts and reminders |
| Contacts | Address suggestions, contact sync if you choose it |
| Calendar | Showing and syncing events, answering invitations |
| Exact alarms, start at boot, background sync service, wake lock | Timely delivery of mail and reminders |
| Biometrics | Unlocking the App with fingerprint or face |
| Storage (older Android versions) | Attaching files you choose |
| Screen lock complexity | Checking the screen lock requirement of your organisation's Exchange policy |
Permissions are requested when the related feature is needed. Declining disables only that feature. Current status is shown in the App under "Settings → Permissions".
9.2. iOS permissions (iPhone and iPad)
| Permission | Why |
|---|---|
| Notifications | New mail alerts and reminders |
| Contacts | Suggesting recipients from the contacts on your iPhone or iPad; saving contacts from your mailbox to the device's address book — only if you turn this on. Contacts are not sent anywhere |
| Calendars | Adding meetings from your mailbox to the iPhone or iPad calendar — only if you turn this on |
| Photos | Only when you attach a photo or pick a photo for a mailbox |
| Face ID | Unlocking the App instead of entering the PIN. Biometric data is processed by iOS and is never available to the App |
| Background App Refresh | Periodic Inbox check in the background; iOS decides when (usually every 15–60 minutes) |
As on Android, permissions are requested when the related feature is needed, and declining disables only that feature. You can change your choice at any time in iOS Settings → Ogneliss Mail.
10. Security
- All connections to mail servers and to the sign-in server use TLS only (HTTPS, IMAPS, SMTP with TLS), and server certificates are verified. Trusted certificate authorities are the system ones, those you installed on the device and, if you enable them, the Russian Ministry of Digital Development certificates.
- Encryption at rest: the App database is encrypted with SQLCipher; its key is kept in secure storage — on Android in Android secure storage protected by the Android Keystore, on iOS in the iOS Keychain, as an item that is accessible only after the device is first unlocked after a restart, is bound to this device and is not migrated to other devices.
- Passwords and tokens are kept the same way: in Android secure storage, or in the iOS Keychain under the same conditions.
- On Android, cloud backup and device-to-device transfer of App data are disabled, so your data does not leave the device through backups. On iOS, the App's data folders are excluded from iCloud and computer backups; iOS may include only the App's settings, without any mail content, in the device backup.
- You can lock the App with a PIN and biometrics (Face ID on iPhone and iPad).
- The sign-in server encrypts refresh tokens (AES-256-GCM) and hands tokens only to the App instance that started the sign-in (PKCE).
No method of storage or transmission is completely secure, but these measures are designed to keep your data under your control.
11. Data retention and deletion
- Data stays on your device for as long as the account is added to the App. How much mail is kept for offline use is set in the synchronisation settings.
- Remove an account in the App (account settings) — all of that account's data on the device is deleted: messages, attachments, contacts, events, tokens.
- Uninstall the App — all App data on the device is deleted.
- Revoke Google access at https://myaccount.google.com/permissions. After that, the tokens stored in the App stop working. The sign-in server holds no data about you, so there is nothing to delete there.
- Revoke Microsoft, Yandex or Mail.ru access in the security settings of that account.
- Messages, contacts and events on the server are kept and deleted by your mail provider or your organisation, under their own policies.
- The sign-in server log is overwritten automatically when its size limit is reached.
- Backup (Settings → “Backup and transfer”) is created only when you ask for it: account and App settings, signatures, notes stored on the device and — if you choose — passwords and sign-in tokens. The file is encrypted with a password you set (AES-256-GCM) and is saved wherever you send it; the developer never receives it. Google user data is not included, except the sign-in token if you choose to include passwords.
The App creates no accounts with the developer, so there is no developer-side account to delete. For any question or request about your data, write to oedante@gmail.com.
12. Children
The App is not directed at children under 13 (or the minimum age required in your country) and does not knowingly collect children's data. If you believe a child has provided us with information, write to oedante@gmail.com.
13. Your rights
Your data is stored on your device, so you can view, change and delete it in the App at any time. You can also write to the developer to ask a question, to request information about data relating to you (for example, entries in the sign-in server log) or to exercise the rights you have under applicable data protection law.
14. Changes to this policy
A new version is published at https://ogneliss.ru/mail/privacy with a new effective date. The App will tell you about material changes when it updates. If the App ever needs to use Google user data in a way not described here, it will ask for your consent first.
15. Contact
Ermishin Oleg Andreevich — oedante@gmail.com