MailBurrow

Effective November 5, 2026 · Updated November 17, 2026

PRIVACY

MailBurrow Privacy Notice

MailBurrow is developed by Carlos Diaz. Privacy contact: mailburrowsupport@gmail.com.

This notice covers the read-only mobile client, voluntary app-support correspondence, the public source repository and these public support/privacy pages. MailBurrow was previously distributed as MailShelf. Earlier installations may still show that name.

Your independently operated archive

You configure your own Mail-Archiver, Open Archiver or Bichon servers, HTTPS addresses, API keys and any required Tailscale or private network. We do not provide customer archive hosting, mailbox provisioning, a mail relay or managed private networks.

The app sends archive requests directly to the endpoint you are connecting to, reconfiguring or actively browsing. Validating another archive can contact it while the current archive remains open; inactive saved archives are not fetched in the background. A saved key is never sent to another archive. The developer does not receive your archive credentials or mail through a MailBurrow-hosted production backend. Your archive operator controls synchronization, permissions, original mail, server records and backups.

Bichon archives

MailBurrow 0.5.0 and later support Bichon. For a Bichon archive, you enter an access token for your own server's read-only user, stored with the same secure-storage and removal behavior as other archive credentials. Tokens inherit user permissions; use Member and Account viewer for only the required accounts, not an administrator.

Search uses a read-only POST containing search text and filters. The app sends no mail-changing requests. It opens parsed text/HTML with remote content blocked, never raw originals. Attachment files download only when you choose to save them. Pro/Enterprise may include extracted attachment text in message details; it is received and decoded in memory within the response limit, is not displayed, and is discarded with that response without a persistent copy. Compatibility with those editions is unverified.

The reviewed Bichon 2.4.2 implementation emits a search event containing the query and user name. Community discards this event; Pro/Enterprise handlers may record or forward it to a security log. This does not establish that Community deployments or their proxies keep no logs. Your operator controls server logging and retention; the app adds no analytics or search-history database.

Bichon responses use the 8 MiB limit. Message-content has a 60-second body-read/decode timeout after headers; connection/header timeouts apply separately. Search input is limited to 256 Unicode code points before escaping and its serialized request to 4 KiB. Attachment limits and file-provider behavior below apply equally.

Information used to browse your mail

For each saved archive (up to 20), its name, server type, server address, API key and selected account or source identifier are saved using platform secure storage to restore and switch connections. Authentication, relevant account/message identifiers, search text, filters and page requests are sent to the configured archive. Its responses provide account and folder information, subjects, senders, recipients, dates, snippets, message bodies and requested attachments for display or saving. With Open Archiver, search results can also include full message text and text extracted from attachments, and an opened message is downloaded as its original message, which can include inline images within the message limits; separate attachment files still download only when you save one, and messages from sources that keep full original files are not opened.

The app does not intentionally keep a local mail database. Message information and browsing state are processed in memory. HTTPS protects transport to the selected server; it does not prevent your archive operator from reading its stored mail. Open Archiver records searches (including the query) and message opens in its audit log. Your independent server, proxy and network providers may retain requests, access records and connection metadata under their own practices.

Ordinary API responses are limited to 8 MiB. Open Archiver message detail has separate limits: a 40 MiB response, a 10 MiB decoded message and 4 MiB of other JSON fields. Attachment downloads are limited to 50 MiB, with a two-minute deadline and 30-second idle timeout; these limits do not cover the system save picker, file providers or viewer apps.

Demo mode

The optional demo uses fictional sample mail built into the app. It connects to no server, sends nothing over the network and does not save or change your connection or credentials. Saving a demo attachment uses the same save flow and destination you choose as any other attachment, and a demo link you confirm opens in your browser.

Attachments, links and file providers

Attachments download after your explicit action. Saving uses a private temporary file, with cleanup attempted after completion or failure. Interrupted processes or cleanup errors can leave temporary copies. Files exported to Files, Nextcloud, iCloud Drive or another destination remain under your and that provider's control. Selecting a cloud destination can upload or synchronize the attachment through that provider; this is separate from your archive connection and is not developer-operated archive hosting.

On Android, the app retains an offered read permission for the specific saved document so it can be reopened while its message remains open. The app attempts to release read grants acquired during the current native session when its last reader reference is released. Pre-existing retained permissions, cleanup failures or abrupt interruption can leave an operating-system grant in place longer. No broad media-library access or saved-file-history database is added. On iOS, the app keeps a session-only document-picker reference and releases it on normal reader exit.

After an open failure, Choose saved file on Android explicitly reconnects a copy you select; the app does not verify that it matches the original attachment. This action does not download another archive copy or automatically open the file. Opening a saved document or confirmed link hands the file or destination to a viewer, browser or provider you choose. Those services have their own privacy practices.

Remote resources are removed from displayed mail. Explicitly confirmed links can use HTTPS or unencrypted HTTP; the confirmation warns about HTTP. Link query parameters, including possible tracking identifiers, are not automatically removed and can reach the external browser or destination. This does not scan messages, links or attachments for malware or phishing.

Removing information and privacy requests

Forget on this device (Settings → Archives) or Disconnect and forget connection removes that archive's saved local record when successful. If secure-storage key cleanup fails, an unreferenced key entry can remain until cleanup succeeds on a later startup. It does not revoke your server API key, delete your archive account, erase mail/logs/backups or remove exported files. We cannot administer independently operated archives. Direct those requests to your archive operator; manage saved files with your chosen file provider.

To request access, correction or deletion of information you voluntarily sent to app support, email the privacy contact above, preferably from the address used for the original conversation. Describe the request without including keys, private server details or sensitive mail. We may need proportionate confirmation that the information concerns you before disclosing or changing it. We consider requests under applicable requirements; available rights and response requirements depend on your location and circumstances.

Support correspondence and retention

If you contact support, your email address and the information you choose to provide are handled through Google Gmail to investigate and respond. Carlos Diaz is the only person managing the support inbox. Google processes the service data under its Privacy Policy.

Each month, resolved support conversations are reviewed and those resolved 12 months or more ago are deleted, unless an ongoing security issue or legal requirement justifies longer retention. Privacy requests are handled separately from that routine cleanup.

Deleting Gmail messages normally moves them to Trash, where they can remain for up to 30 days before permanent deletion unless removed sooner. Provider backup handling may differ. This support-inbox policy does not control your archive server's retention or copies you export.

Source repository and GitHub issues

MailBurrow's source code, issues and private security reports are hosted on GitHub. Issues, comments and pull requests you post there are public and are processed by GitHub under its Privacy Statement. Do not post keys, server addresses, real messages or unredacted screenshots. Private vulnerability reports are not public; access is limited to authorized participants under GitHub's security-advisory permissions. Contributions and comments you publish remain part of the public project history.

App diagnostics

Normal Android and iOS builds leave file-operation diagnostic tracing disabled. No advertising, analytics or third-party crash-reporting service is configured by the app. It does not automatically send archive data or app-support reports to the developer.

A separately identified diagnostic build may enable local, fixed file-operation event categories for an agreed troubleshooting session. Those events exclude file names, paths, file contents, message contents, server details and credentials; there is no automatic report upload. If you voluntarily share diagnostic information with support, it is handled as support correspondence. Apple, Google and other platform services may process crash reports or feedback under their own settings and policies.

Public information pages

These public information pages use Cloudflare Pages hosting. Cloudflare processes website requests and may process IP addresses and request metadata to deliver and protect its services. Its Privacy Policy describes those practices. This hosting is separate from your archive and does not grant access to your configured server.

These pages contain no forms, analytics scripts, remote fonts or remote images. Optional Cloudflare Web Analytics is disabled. This does not mean the host keeps no operational records. Provider processing and retention follow the applicable service practices; no fixed host-log deletion deadline or processing region is promised here.

Changes and contact

This notice takes effect on November 5, 2026. Changes to our practices will be reflected in an updated notice with its effective date. For questions about app privacy or information sent to support, contact mailburrowsupport@gmail.com.