Skip to content
BitArmor
  • Services
  • Products
  • People
  • Certifications
  • Contact
  • ITEN
  1. Home
  2. BitArmor-Inbox
  3. BitBoard privacy notice

Privacy notice — BitBoard

Last updated: 15 September 2026

1. Who operates the service

BitBoard is the operational notification monitoring service operated by BitArmor S.r.l., with registered office at Via Roberto Serracchioli 5, 41125 Modena, Italy, VAT no. 04149660369. For information and requests concerning personal data, please write to [email protected].

The application is intended for authorised operators and access to it is protected by login. It is available at https://notifiche.bitarmor.it/; on the Google authorisation screen it may be identified as “BitArmor-Inbox”. Publishing this notice does not make any events or emails public.

2. Roles and scope of this notice

BitArmor manages notifications on behalf of its customers under active service contracts. For data processed on the customer’s instructions, the customer determines the purposes and legal basis of the processing; BitArmor’s role and the related instructions are governed by the applicable agreements. This notice does not replace the data processing agreements or the notices that the customer must provide to its own data subjects.

BitArmor acts as controller for the activities within its own remit, such as managing relationships with customers’ contact persons and requests addressed directly to the company. The contact address given above can also be used to identify the competent controller for a specific request.

3. Data collected and its sources

The data comes from notifications sent by the monitored systems to a dedicated Gmail mailbox and from information entered by operators. It may include:

  • sender email addresses, subjects, message bodies, dates, Gmail identifiers and labels;
  • names of customers and of the monitored systems, servers and processes;
  • supported CSV reports, metrics, technical outcomes, errors and warnings;
  • classifications, summaries, suggestions and recognition rules;
  • the operator’s declared name and the date and time at which events were resolved;
  • technical information needed for the service to operate securely.

Technical notifications may contain personal data. Customers and operators must limit the data sent to what is necessary for monitoring, avoiding passwords, credentials and irrelevant personal information.

4. Purposes and bases of processing

BitBoard makes it possible to monitor process outcomes, detect errors and missing reports, associate notifications with a customer and a process, inform operators and document how events are handled. The automated analysis concerns technical facts; it is not intended for decisions about individuals that have legal or similarly significant effects. Suggestions require human assessment.

For data processed on behalf of the customer, the legal basis is identified by the customer as controller in relation to its own purposes. For BitArmor’s direct management of relationships and requests, the applicable bases are the performance of a contract where the data subject is a party to it, the legitimate interest in managing professional relationships with contact persons and in the security of the service, and compliance with legal obligations where applicable.

Providing the operational data and access to the mailbox is necessary for the monitoring functions requested: without them, the service cannot acquire and analyse notifications. OAuth consent enables Google technical access and does not replace the legal basis for processing the data contained in the emails.

5. Access to Gmail

The connection is made via Google OAuth, without entering the Gmail password into the BitBoard application. The permission requested is https://www.googleapis.com/auth/gmail.modify.

The service normally selects emails in the INBOX that have not yet been processed, reads their content, applies labels and marks them as read. Administrative procedures can retrieve messages already recorded by their ID. Retention functions, when enabled, may move individual messages to the bin. BitBoard does not use this connection to send emails. The scope authorises access to and changes in the mailbox; the selection of reports is made by the software and does not constitute a restriction of the Google scope.

The account holder can revoke access in their Google account settings. Revocation stops any further acquisition, but does not automatically delete events, notifications and copies already stored.

6. Services used and recipients

The data can be consulted by authorised operators and administrators for their respective activities. The service also uses the following components:

  • Google/Gmail, for access to the mailbox and management of messages as authorised by the user;
  • OpenAI API, to analyse the sender, subject and text of notifications and produce classifications and suggestions. Rule generation requested by the operator sends the description, subject and text. CSV reports are not added to the analysis prompt;
  • Telegram, if configured, to send identifiers, severity and context of alerts, such as subject, source type, customer and, where necessary, sender. The notifier does not send the email body or the AI summary;
  • hosting and database infrastructure, to store content, rules, analyses, events and management information, including the related backup copies.

OpenAI calls use the store=False option; this setting does not by itself mean that no technical retention takes place at the provider. Requests concerning the providers used and the terms of their use can be sent to [email protected].

7. Data location and external services

The storage infrastructure managed by BitArmor for the service is located within the territory of the European Union. This location does not by itself determine where processing takes place within the external services of Google, OpenAI and Telegram.

Processing by those services depends on the configurations and terms applicable to the relationship with each provider. Any transfers outside the European Economic Area are subject to the requirements of Chapter V of the GDPR; the presence of the server in the EU does not constitute a guarantee that all processing is located in the EU. For information on the locations and safeguards applicable to your service, please contact BitArmor.

8. Limited Use of Google data

BitArmor undertakes to use and transfer information received from Google APIs in accordance with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

The use of Google data is limited to the monitoring and support functions described in this notice. BitBoard does not use it for advertising, for selling data or for creating, training or improving general-purpose artificial intelligence models. Data is sent to the AI to process individual notifications and operational requests, not to train a general model.

9. Retention and deletion

The standard retention period for operational emails and related data is 24 months from receipt of the message, unless otherwise agreed with the end customer. This criterion covers events, analyses, metrics, alerts and resolution data. Corrections and resolutions do not restart the period. Any different retention periods must be defined in the applicable agreements and be consistent with the purposes of the service and with regulatory obligations.

Managing expiry requires deletion procedures that deal separately with the Gmail mailbox, the database, delivered notifications and backup copies. BitBoard does not currently have a general automatic deletion of the database history: compliance with the retention period therefore also requires administrative management of deletions. The retention criterion also applies to copies administered by BitArmor, not only to the data visible in the dashboard.

Marking an event as resolved does not delete it. Deleting the event from the database does not delete the Gmail email, and moving an email to the bin does not delete the event or any copies already present in backups. Permanent deletion must therefore take all the relevant archives into account.

OAuth credentials and configuration rules are kept for the duration of the connection and of the operational need; decommissioning them is separate from the resolution of an event. Technical logs are subject to necessity criteria for operation and security. Specific regulatory obligations or the handling of disputes may require only the relevant data to be kept for the time necessary for the purpose concerned.

10. Security and local preferences

Access to the application is restricted by login. Email content is treated as untrusted data and is not executed as commands. The name entered by the operator when resolving an event is declared data, separate from the identity used to access the service.

The browser stores functional preferences such as theme, refresh intervals and the resolver’s name. On shared workstations, the name must be checked before confirming a resolution. For any tools and cookies used by the website hosting this notice, please refer to the information published by that website.

11. Rights and contacts

In the cases provided for by the GDPR, data subjects may request access to, rectification, erasure, restriction and portability of their data, and may object to processing. Where processing is based on consent, consent may be withdrawn without affecting the lawfulness of processing carried out before its withdrawal.

Requests can be sent to [email protected]. Where the data is processed on behalf of a customer, BitArmor coordinates the request with the competent controller. You may lodge a complaint with the Garante per la protezione dei dati personali (the Italian data protection authority).

12. Updates to this notice

The current version is published on the BitArmor website together with its date of update. Material changes concerning the service are communicated to customers through the channels of the contractual relationship.

BitArmor

BitArmor S.r.l. — cybersecurity, IT infrastructure and compliance for businesses.

If you’re afraid of chaos, you’re not ready for reality

Services

  • Cybersecurity, VA and penetration testing
  • Hybrid infrastructure
  • Strategic consulting
  • Training
  • Systems integration
  • Compliance and regulation

Products

  • BitBox
  • BitWall
  • DMARC Console In testing
  • BitBoard In development
  • BitShield In development
  • BitScan In the lab
  • NGFW BitArmor In the lab

Company

  • People
  • Certifications
  • Contact

Contact

  • [email protected]
  • PEC (certified email): [email protected]
  • Modena (Italy)
  • LinkedIn

© 2024–2026 BitArmor S.r.l. · VAT no. IT04149660369 · Modena (Italy)

Privacy notice ·