Your data, explained
Privacy policy
Effective
MailArca is a local-first, read-only Gmail desktop client for Linux. This policy describes the MailArca desktop application and the informational website at mailarca.upbaz.lat.
1. Information the desktop app accesses
After you explicitly authorize an account, MailArca requests only the Google Gmail API read-only scope:
https://www.googleapis.com/auth/gmail.readonly
Depending on the features you use, this permits access to:
- Your Gmail account email address and mailbox synchronization information.
- Message identifiers, labels and unread state, senders, recipients, subjects, dates, and snippets.
- Message bodies, conversation context, original message source, and attachment metadata or content when retrieved.
MailArca does not request permission to send, modify, archive, or delete email. Reading a message locally does not mark it read on Gmail. Google handles your password and multi-factor authentication in your browser; MailArca does not collect your Google password.
2. How and why this information is used
Gmail data is used only to provide the features you request: account-specific and unified inboxes, synchronization, local cached search, message and conversation reading, attachment saving, desktop notifications, and local detection of emailed verification codes or security-related messages.
Code detection and message categories use local heuristics. These results are not a guarantee of authenticity. MailArca does not use Gmail data for advertising, profiling unrelated to its email features, sale, or training generalized artificial-intelligence or machine-learning models.
No built-in analytics or telemetry sends your usage or email data to the website operator. Desktop notifications can expose account information on your device’s notification surface; control notifications in MailArca and your operating system.
3. Storage and protection on your device
- Email cache: synchronized account information, message metadata, and previously retrieved message content are stored in a local SQLite database. The app uses private application-data permissions.
- Refresh tokens: stored in your Linux Secret Service keyring, not in the email database, website, browser storage, or application logs. An unavailable keyring is reported rather than replaced with a plaintext token file.
- Access tokens: held temporarily in the desktop application’s Rust memory for authenticated requests to Google.
- Client configuration: imported Google Desktop OAuth client settings are retained locally by the desktop app. This configuration is not uploaded to this website.
- Saved attachments: files you choose to export are written to the location you select and remain under your control.
The local email cache is not encrypted by MailArca. Use device encryption, a protected operating-system account, a locked keyring, and secure backups. Private file permissions are not a substitute for disk encryption. No application can guarantee protection on a compromised device.
Email HTML is sanitized and isolated. Scripts, forms, and embedded frames are not allowed in the email reader. This reduces active-content risks but is not a guarantee that a message or its sender is trustworthy.
5. Retention, deletion, and your choices
Cached information remains on your device until it is reconciled during synchronization, removed with its account, or otherwise deleted by you. Closing the app does not automatically erase its cache.
- Remove an account in MailArca to remove its local cached account data and stored credentials. If the keyring cannot be accessed to remove credentials, the app reports the problem; unlock or restore the keyring and retry.
- Revoke Google authorization through your Google Account’s third-party connections. Revocation prevents future authorized access but does not automatically erase already cached local messages.
- Control notifications and remote images through MailArca’s settings and per-message image control.
- Delete exported files and backups separately. Account removal does not delete attachments you previously saved outside the cache, operating-system backups, or messages stored in Gmail.
Local deletion is not guaranteed forensic erasure; storage devices, filesystems, and backups can retain traces. MailArca does not delete your Gmail messages.
6. This informational website
This website serves public static pages, the MailArca logo, and locally hosted fonts. It has no account system, email upload, sign-in form, JavaScript analytics, tracking pixels, advertising, or application cookies. It does not use browser storage.
Visiting any website necessarily sends network information such as your IP address, requested URL, request time, and browser information to its hosting infrastructure. Hosting and security systems may retain operational or error logs to operate and protect the service. These website requests do not include your Gmail messages or desktop OAuth tokens. Do not put credentials, tokens, or personal email content in website URLs.
The website uses HTTPS. Fonts and images are served from this same site rather than third-party font or analytics services. External policy and account-control links are contacted only when you choose to follow them.
7. Google API Services User Data Policy
MailArca’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used to provide or improve the user-facing email features described in this policy, not for unrelated purposes.
This statement is a commitment about data handling, not a claim that Google has verified, endorsed, or approved MailArca. Your OAuth project’s audience, publishing status, verification, and administrator restrictions are configured separately in Google Cloud.
8. Questions and contact
For questions about your authorization or the OAuth project you use with MailArca, contact the user support email displayed on Google’s consent screen for that project. For a desktop build, contact the person who supplied it. This site does not collect support submissions.
Never send passwords, OAuth tokens, client credential files, private message contents, or attachments in an unsolicited support request. You can remove local accounts and revoke Google access yourself using the controls described above.
9. Changes to this policy
Updates will be published at this URL with a revised effective date. If a later release introduces materially different data handling, its policy must be updated before that behavior is introduced. Independently modified builds and third-party services may have different practices.