Privacy Policy
Last updated: November 12, 2026
Blomo is operated by UAB DRYND
Vilnius, Lithuania
Website: blomo.app
1. Introduction
This Privacy Policy (“Policy”) explains how UAB DRYND, operating the Blomo service (“Blomo”, “we”, “us”, or “our”), processes Personal Data in connection with the Blomo website, applications, and related services (collectively, the “Service”).
Blomo is a mail client. It lets you connect your Gmail mailboxes so that all of them appear in one interface. Blomo is currently in a closed beta: features are enabled for invited testers, and in this phase only the mail features are switched on. Calendar, files, chat, and paid features exist in the codebase but are not available to beta users, and this Policy will be updated before they are.
UAB DRYND is the Controller of the Personal Data described in this Policy.
We do not sell Personal Data. We do not use Personal Data for advertising. We do not use the content of your mail to train AI models.
2. Definitions
- “Personal Data” means information relating to an identified or identifiable natural person.
- “Processing” means any operation performed on Personal Data, such as collection, storage, use, disclosure, transmission, or deletion.
- “Service” means the Blomo website, applications, and related products and features.
- “User” or “you” means an individual who visits or uses the Service.
- “Connected account” means a Gmail mailbox that you link to Blomo.
- “Controller” and “Processor” have the meanings given to them under the EU General Data Protection Regulation (“GDPR”).
3. What Data We Process
3.1 Account data
When you create a Blomo account we store:
- your sign-in email address;
- a password hash (argon2id), if you set a password; we never store the password itself;
- if you sign in with Google, the identity Google returns to us (openid, email, profile scopes only);
- a second-factor (TOTP) secret, stored encrypted, and backup codes, stored as keyed hashes, if you enable two-factor authentication;
- a recovery email address, if you add one;
- hashes of application passwords, if you create them for mail clients;
- display name and profile settings you choose.
3.2 Connected accounts
You may connect an external mailbox. Connecting is optional and happens only when you click “Connect” and approve the permissions on the provider's own consent screen.
Gmail (Google LLC). We request the Google scopes openid, email, profile, and https://www.googleapis.com/auth/gmail.modify. We do not request full-mailbox scope (https://mail.google.com/); if Google nonetheless grants it, we revoke the grant and ask you to reconnect. We store:
- the refresh token, encrypted with a key unique to you;
- message metadata needed for the message list and search: subject, sender, recipients, snippet, and label names, encrypted with your key; message and thread identifiers, date, label identifiers, and an attachment flag are stored unencrypted;
- the short-lived access token is held in server memory only and discarded when you disconnect.
We do not store Gmail message bodies or attachments. They are fetched from Google each time you open a message. Sending through Gmail is limited to 60 messages per hour and 300 per day per account.
During the beta, our Google OAuth project is in “Testing” status. Google expires the refresh token 7 days after consent; reconnecting is expected and not a fault.
Google API Services User Data Policy — Limited Use. Blomo'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. We use Gmail data only to display, search, organize, and send your mail inside Blomo. We do not transfer it to third parties except as needed to provide the Service, as required by law, or with your consent; we do not use it for advertising; and no human reads it except with your explicit permission for support, for security purposes, or to comply with law.
3.3 Security and activity records
- an event log of significant actions on your account (sign-ins, password and recovery-address changes, account deletion, connections of external accounts) with the IP address and browser identifier (User-Agent) of the request. The log never contains message content, subjects, or addresses of your correspondents;
- active sessions, stored for up to 30 days, with IP address and User-Agent so you can see and revoke devices;
- failed sign-in attempts that cannot be attributed to any account are deleted after 90 days; for all other events the IP address and User-Agent are removed after 365 days and the event itself is kept;
- abuse reports you submit: the reported message is kept for 90 days, then only the report's type, outcome, and date remain;
- bounce and complaint signals for mail we send, kept for 30 days.
3.4 Website and waitlist
The site blomo.app is served by Cloudflare. Requests pass through Cloudflare's network, which sees IP address, browser information, and the requested page in order to deliver and protect the site. Cloudflare keeps its own logs under the Cloudflare Privacy Policy.
If you join the waitlist we store your email address (lowercased), the time, the form that sent it, campaign tags (utm_*) and the referring page if present in the address bar, the country Cloudflare derives from the request, and the version of this Policy you consented to. We do not store the IP address or User-Agent with the waitlist entry. Entries are stored in a Cloudflare D1 database and are also copied to our own database to manage beta invitations. The form is protected by Cloudflare Turnstile, which checks that a browser is operated by a person; Turnstile may process your IP address and browser signals for that purpose. Waitlist entries are kept until you ask us to remove them (section 15).
We do not use analytics or advertising cookies, or third-party tracking, on the website or in the application. The application uses a session cookie strictly necessary to keep you signed in.
3.5 Support
If you contact support, we keep the text of your request and the contact details you give us in order to respond.
3.6 Error reporting
Application errors are collected in an error-tracking system (GlitchTip) that runs on our own servers. Error reports contain technical fields and identifiers only; message content, subjects, and addresses are excluded by design.
4. Purposes and Legal Bases
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the mail client (showing, sending, and searching mail from connected accounts; sessions; export; deletion) | account data, connected-account data | Art. 6(1)(b) GDPR — contract |
| Synchronizing connected accounts | OAuth tokens, message metadata | Art. 6(1)(a) GDPR — consent, given on the provider's consent screen and withdrawable by disconnecting the account |
| Security, abuse and spam prevention, incident investigation | event log, sessions, IP addresses, abuse reports, bounce signals | Art. 6(1)(f) GDPR — our legitimate interest in keeping the Service and other users safe |
| Waitlist and beta invitations | waitlist entry | Art. 6(1)(a) GDPR — consent (the checkbox on the form) |
| Responding to support requests | support ticket | Art. 6(1)(b) and (f) GDPR |
| Compliance with legal obligations, legal claims | the data concerned | Art. 6(1)(c) and (f) GDPR |
Where processing is based on consent, you may withdraw it at any time; withdrawal does not affect processing that took place before. Where processing is based on legitimate interests, you may object (section 11).
5. Retention
| Data | Retained for |
|---|---|
| Connected-account tokens and metadata | until you disconnect the account or delete your Blomo account; on disconnect the token is revoked at the provider |
| Sessions | 30 days of inactivity, or until you sign out |
| Event log: unattributed failed sign-ins | 90 days |
| Event log: IP address and User-Agent of other events | 365 days; the event itself is kept with the account |
| Abuse reports: reported message | 90 days |
| Bounce and complaint signals | 30 days |
| Residual records after account deletion (see section 9) | 365 days |
| Staff action log (section 8) | 12 months |
| Backups: database (logical) | up to 12 months |
| Backups: database (physical chain) | 14 days plus up to 7 days to the next full copy; deleted data lives in it at most 21 days |
| Waitlist entries | until you ask us to remove them |
| Server and proxy access logs | 14 days |
6. Subprocessors
We use the following providers to operate the Service. Each processes Personal Data only on our instructions and under a data-processing agreement.
| Provider | Role | Location |
|---|---|---|
| IP-Projects GmbH & Co. KG | server hosting: application, database, backups | Frankfurt, Germany |
| Cloudflare, Inc. | serving blomo.app, DNS, Turnstile bot check, D1 database for the waitlist | global network; EU and US |
| Scaleway SAS | sending transactional email (sign-in links); encrypted off-site backup copies (Object Storage, Paris) | France |
| Google LLC | Gmail API and Sign in with Google — only when you connect a Google account or sign in with Google | United States |
| Stripe, Inc. | payments — future: not in use during the beta; this Policy will be updated before paid features launch | United States |
Spam filtering (Rspamd), antivirus scanning (ClamAV), the mail server, search, monitoring, and error tracking run on our own servers at IP-Projects and are not separate processors.
Off-site backup copies are stored encrypted (restic, keys held only by us) in Scaleway Object Storage in Paris; the provider cannot read them.
7. International Transfers
UAB DRYND is based in Lithuania and stores your mail and account data in Germany.
Google processes data in the United States when you connect a Gmail account or sign in with Google; the data they receive is the data you already hold with them plus the API requests Blomo makes on your behalf. Cloudflare may process request data on servers outside the EEA. For these transfers we rely on the European Commission's Standard Contractual Clauses incorporated in the providers' data-processing terms, and, where a provider is certified, on the EU-US Data Privacy Framework.
8. Security
- Transport. All connections to Blomo use TLS. Mail between Blomo and other mail servers uses TLS where the other server supports it; we publish MTA-STS for our domain.
- Encryption with per-user keys. Connected-account refresh tokens and message metadata are encrypted with a key unique to you, which is itself wrapped by a master key held only by the application process and never present in backups. When you delete your account your key is destroyed, which makes the encrypted data unreadable even in backups that still contain it.
- Access control. The application database role cannot alter or delete audit records. The support role used by staff cannot read mail content, message headers, tokens, keys, passwords, or your sign-in address.
- Staff authentication. Staff access to the administration interface requires a second factor (TOTP). Every staff action is written to an append-only, hash-chained log kept for 12 months; the chain is verified on a schedule.
- Logs. Application logs and the event log contain identifiers and machine codes only; message content, subjects, addresses, and tokens are excluded and this is checked by automated tests.
- Remote content. Images in HTML mail are not loaded by default. If you choose to load them, our server fetches them so the sender sees our server, not your IP address or device.
- Backups. Backups are encrypted-key-free: all per-user key tables and the Gmail token-revocation queue are excluded from long-term backups.
No system is perfectly secure. If a breach affects your data we will notify you and the supervisory authority as required by Articles 33 and 34 GDPR.
9. Account Deletion and Data Export
Export. You can download all your data as a single archive from the application after re-confirming your identity. The archive contains your drafts, labels, rules, and JSON records of your account; it never contains passwords, tokens, or keys. The archive is streamed to you and not stored on our side. Mail in connected accounts remains with the provider; the archive refers you to the provider's own export (for Google: Google Takeout).
Disconnecting an account. Disconnecting a connected account deletes its stored tokens and metadata and asks the provider to revoke our access. You can also revoke Blomo's access in your Google account settings at any time.
Deleting your account. Deleting your account removes your stored mail data, drafts, labels, rules, signature, contacts, profile, second factor, recovery address, sessions, connected accounts, and the keys that encrypt them. The Gmail revocation queue retries revocation at Google for up to 30 days. What remains after deletion: an anonymized tombstone record of the account, your entries in the event log, and your support requests; these are purged 365 days after the deletion completed. If our token-revocation request to Google is lost, access may remain listed in your Google account until you remove it there.
Backups. Deleted data persists in backups for the periods in section 5. Data encrypted with your key is unreadable there once the key is destroyed.
10. Children's Privacy
Blomo is not intended for children under the age of sixteen (16). We do not knowingly collect Personal Data from children under 16. If we become aware that we have done so unlawfully, we will delete it.
11. Your Rights
Under the GDPR you have the right to:
- access your Personal Data (Art. 15) — the export in section 9 provides a copy;
- rectification (Art. 16);
- erasure (Art. 17) — account deletion in section 9;
- restriction of processing (Art. 18);
- data portability (Art. 20) — the export in section 9;
- object to processing based on legitimate interests (Art. 21);
- withdraw consent at any time (Art. 7(3)) — disconnect a connected account or ask us to remove a waitlist entry;
- lodge a complaint with a supervisory authority (Art. 77).
To exercise these rights, contact us as described in section 15. We will respond within one month, extendable as permitted by Art. 12(3) GDPR. We may ask you to confirm your identity.
13. Legal Requests and Business Transfers
We may disclose Personal Data where we reasonably believe disclosure is required to comply with applicable law or a valid legal process, to respond to a binding request from a competent authority, to investigate or prevent fraud, abuse, or security incidents, or to protect the rights, property, or safety of UAB DRYND, our users, or others. Where legally permitted, we limit disclosure to what the request requires.
If UAB DRYND is involved in a merger, acquisition, financing, reorganization, or sale of assets, Personal Data may be transferred as part of that transaction subject to applicable law. Affected users will be informed where required.
14. Changes to This Policy
We will update this Policy before we enable calendar, files, chat, paid features, or any other processing not described here. The “Last updated” date at the top shows when it was last revised. If a change materially expands how we process Personal Data or reduces your rights, we will notify you in the application or by email where required by law.
This Policy is governed by the laws of the Republic of Lithuania, subject to mandatory rights available to you under applicable data-protection law.
15. Contact Us
For questions about this Privacy Policy or to exercise your privacy rights, contact:
UAB DRYND
Vilnius, Lithuania
blomo.app
Privacy and support contact details may be published or updated on blomo.app.