Vaimail is a desktop mail and calendar app for Windows (previously named “Pochta” and “Jay Mail”). It runs on the user's computer and has no server for users' mail; the only thing it downloads from the developer's site is the public supporters list (see below).
Data the app uses
- Mail, calendars and contacts of the accounts the user connects (Gmail, Outlook.com, iCloud and others via IMAP/SMTP, CalDAV, CardDAV, Google Calendar API, Microsoft Graph), to display them and let the user read and send mail, create, edit and delete events, and answer invitations.
- Google user data (Google Calendar API, Google People API for contacts, the Google account email address) is accessed only after the user explicitly signs in with Google, and only to show and edit that user's own events and contacts in the app (contacts also suggest addresses while writing mail). Gmail mail is not accessed through Google APIs or Google sign-in: a Gmail mailbox is connected over IMAP/SMTP with an app password the user creates in their Google account, and messages are downloaded directly from Google's servers to the user's computer.
- Microsoft account data (Outlook.com: mail via IMAP/SMTP, calendars and contacts via Microsoft Graph) is accessed only after the user explicitly signs in with Microsoft, and only to work with that user's own mail, calendars and contacts in the app.
Storage
- Mail, events and contacts are cached only on the user's computer, in the app's data folder.
- App passwords and access tokens are stored in the user's Windows Credential Locker.
- The app contains no ads, analytics or telemetry.
- The app's diagnostic log contains no message or event contents, passwords or tokens.
Sharing
- Data is sent only to the mail and calendar servers of the user's own accounts (e.g. Google, Microsoft, Apple), over encrypted connections.
- Company logos. To show a company's logo next to its mail, the app looks up the domain of the sender's company (for example, example.com) in DNS and downloads the logo the company publishes for mail apps (its BIMI logo) or the icon of its website, once per domain, over HTTPS and without cookies. Only the domain name is used: no email addresses, message contents or other user data are sent, although, as with any web request, the server that hosts the logo sees the computer's IP address. Logos are stored only on the user's computer. This can be turned off in Settings → Appearance → Company logos, which also deletes the downloaded logos.
- Tips. Vaimail is free. Its Support page links to the developer's page on Ko-fi (ko-fi.com), where anyone can leave a voluntary tip, once or monthly; a tip unlocks nothing in the app. The page opens in your browser, and Ko-fi processes the payment under its own terms and privacy policy: the app never receives a payment, card number, billing address or other payment detail, and does not know whether you left a tip. Microsoft is not the organizer of this fundraiser.
- Supporters list. The app sends nothing to vaimail.app: it only downloads the public supporters list and the progress of the fundraising goal (how much has been raised in total) to show them. The developer keeps the list by hand, from tips on Ko-fi: a public tip (with the name given on Ko-fi) or a name the supporter wrote in the tip's message. Each entry is checked before it is shown in the app and on vaimail.app, so a name usually appears within a few days; the amount of a tip is never shown. The server keeps the name, the level and the date; IP addresses are not stored. You can ask for your entry to be removed through the contact page.
- Ko-fi payment notices. When someone leaves a tip on Ko-fi, Ko-fi notifies the supporters service on vaimail.app. If the tip was made public on Ko-fi and reaches a level of the list ($3 a month or $10 once and up), the name given on Ko-fi becomes an entry for the developer to check; the level only decides how the name shows. Of the payment itself the service keeps only Ko-fi's id, so a notice sent twice is taken once, and adds the amount to one running total, which is shown as the goal's progress; it does not keep single amounts, email addresses or messages.
- The developer does not receive, collect or store any user data. Data is never sold, shared with third parties, or used for advertising or training AI models.
- The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Data security: how Google user data is protected
Vaimail protects Google user data (calendar events, the calendar list, contacts and the Google account email address) and all other account data with the following measures:
- No developer servers. Google user data travels only between the user's computer and Google's servers. It is never transmitted to, stored on or accessible to the developer or any third party, and no person reads it. The only developer server the app talks to holds the public supporters list, which contains only names users chose to publish.
- Secured transmission. Every request to Google APIs (Google Calendar API, Google People API, Google OAuth) is made over HTTPS with TLS encryption, and the server certificate is verified by Windows. Mail is downloaded and sent over TLS (SSL/TLS or STARTTLS).
- Secure sign-in. Google sign-in uses OAuth 2.0 for installed apps in the user's own web browser, with PKCE (S256) and a state parameter, and returns to the app only through a loopback address on the same computer (127.0.0.1). The app never sees or stores the user's Google password.
- Encrypted storage of credentials. Google refresh tokens and app passwords are stored in the Windows Credential Locker, which encrypts them with the user's Windows credentials. Access tokens are kept only in memory. Credentials are never written to the app's database, settings files or logs.
- Protected local data. Cached events and contacts are stored in the app's private data folder in the user's Windows profile, which is accessible only to that Windows user account. On devices with BitLocker or Windows device encryption, this data is also encrypted at rest.
- Least privilege. The app requests only the Google scopes its features need (calendar.events, calendar.calendarlist.readonly, contacts, openid, email) and uses them only for the user-facing features described above.
- Confidentiality. The app has no analytics or telemetry, and its diagnostic log, which stays on the user's computer, contains no event, contact or message contents, passwords or tokens.
- User control. Disconnecting Google in the app's settings revokes the token at Google and deletes the cached calendars and events; removing the account deletes all of its cached data and credentials from the computer.
Security issues can be reported through the contact page.
Deletion
- Removing an account in the app's settings deletes its local cache and stored credentials; Google access can be disconnected there (the token is revoked) or at myaccount.google.com/permissions.
- Uninstalling the app deletes all of its local data.
This website
- vaimail.app counts page visits with Umami, an analytics tool hosted on the developer's own server. It sets no cookies and stores no IP addresses or other personal data; only anonymous totals such as page views, referrers, country and browser type.
Contact
Use the support address shown on Google's consent screen when signing in, or the contact page.