Belerick Back to sign in

Belerick

Privacy Policy

Last updated: November 6, 2026

This policy applies to the Belerick website and email-analysis service. It explains the information collected, its sources and purposes, who receives it, how it is protected, and how you can remove it.

1. Information we collect and access

When you use Google sign-in, Google provides Belerick with your account email address and Google account identifier. When you authorize Gmail access, Belerick receives the mailbox address and retrieves messages through the Gmail API. Message data may include raw message content (including text and HTML body parts), sender and recipient addresses, subject lines, dates, message headers, Gmail labels, and message and synchronization identifiers. Belerick also creates derived data such as authentication results, links, tracking indicators, sender statistics, and message classifications.

The Google authorization used for sign-in requests the openid, email, profile, and gmail.modify scopes. The gmail.modify scope allows broad Gmail access, including changing mail. Belerick uses it to read and analyze messages; the current Gmail integration does not send messages or change messages or labels in your mailbox.

If your first Google sign-in returns Gmail authorization and you have no existing mailbox connection, Belerick may create a default Gmail connection. Its initial sync retrieves messages from Inbox and Spam received during the previous 30 days, then tracks newly added messages. When you connect Gmail separately, you can choose the initial sync window. We process information you provide, including connection labels, analysis prompts, and settings, as well as account and technical information needed to operate and secure the service. The website uses an authentication cookie to keep you signed in.

2. How we use information

We use your Google email address and account identifier to authenticate you, create or maintain your Belerick user account, and associate mailbox connections with you. We use Gmail data to synchronize the folders described above; store and display messages; enable search, filtering, and sharing features; and generate email analysis, reports, and visual previews. We use connection labels and settings to manage those connections, and technical information to operate, secure, and troubleshoot the service.

When you choose to run subject analysis, Belerick sends the selected message subject lines and the prompt you provide to the configured Google Gemini API and stores the resulting analysis in Belerick. This processing is solely to return the analysis you requested. Google user data is not used for advertising, sold, or used to develop, improve, or train generalized or non-personalized AI or machine-learning models.

3. How and with whom information is shared

We do not sell Google user data. We do not transfer or disclose it to third parties for purposes other than providing, maintaining, securing, or supporting the Belerick features you request, or complying with law. In particular:

  • Google processes the authorization and identity requests involved in sign-in and Gmail access. When you request subject analysis, Google Gemini receives the selected subject lines and your prompt to generate that result.
  • If screenshot storage is enabled by the service operator, screenshots generated from email content may be stored in the operator's configured Amazon S3 bucket.
  • Authorized Belerick service operators may access information to operate, secure, and support the service. We may also disclose information when legally required or when necessary to protect users and the service from abuse or security threats.

We do not allow Google user data to be used for targeted, personalized, or retargeted advertising; sold or provided to data brokers or information resellers; used to determine creditworthiness or lending eligibility; or used to train generalized or non-personalized AI or machine-learning models.

4. Storage and security

Synchronized message content, message headers, derived email information, account identifiers, and connection settings are stored in Belerick's application database so the service can provide its features. OAuth credentials associated with Gmail connections are encrypted before storage. Access to account and mailbox information is restricted through authentication and account permissions. When Belerick is deployed over HTTPS, information in transit is protected by that encrypted connection.

Security measures depend in part on the service operator's deployment and configuration. No method of storage or transmission is completely secure, and Belerick cannot guarantee absolute security.

5. Retention and deletion

We retain account information and synchronized mailbox data for as long as your account and mailbox connection remain active and the data is needed to provide the service, unless a longer retention period is required or permitted by law. Belerick does not automatically delete synchronized messages after the initial sync period; newly added messages continue to be synchronized. You may delete individual messages in the application. Deleting a mailbox connection removes its credentials and associated message records from the active application database. Deleted database information may remain in backups until those backups are rotated. Screenshots already uploaded to an operator-configured S3 bucket may be subject to separate bucket retention and deletion settings.

To remove a mailbox connection and its Belerick data, use the Connections page. To stop future Google access, you can also remove Belerick's access in your Google Account permissions. Revoking Google access stops future access using that authorization but does not by itself delete information already stored in Belerick; delete the connection in Belerick as well. For other privacy or account deletion requests, contact the Belerick operator, Rafael Viana, through the Belerick operator's GitHub profile.

6. Your choices and third-party services

You choose whether to sign in with Google, connect a Gmail mailbox, and use optional analysis or screenshot features. You can disconnect a mailbox or revoke Google access as described above. Google's services and other third-party services have their own terms and privacy practices, which apply to your use of those services.

7. Website use

Use Belerick lawfully and only with accounts and data you are authorized to access. Do not attempt unauthorized access, disrupt or damage the service, bypass its security, upload malware, send spam, or place unreasonable load on the service. You are responsible for activity performed through your account and for keeping your sign-in methods secure.

Belerick and its software and materials remain subject to applicable intellectual-property rights. Features may change or become unavailable. To the extent permitted by law, the service is provided on an “as is” and “as available” basis; nothing in this policy excludes rights or liability that cannot legally be excluded.

8. Policy operator, changes, and contact

Belerick is operated by Rafael Viana. For privacy questions or requests about your data, contact the operator through the Belerick operator's GitHub profile.

We will update this page if our handling of Google user data changes materially and will promptly notify users through the service when required.