BRIXEON REPORT PHISHING · GMAIL ADD-ON

Privacy Policy

How the Gmail add-on accesses and uses information when you report a Brixeon phishing simulation.

Effective date: 22 September 2026

1. Who this policy covers

This policy applies to the Brixeon Report Phishing Gmail add-on, operated by الدرع المتطور لتقنية وتكنولوجيا المعلومات
شارع الملكة رانيا، عمان، الأردن، مبنى قندل سنتر، مكتب 204
Jordan. It is designed for participating organizations using Brixeon simulated phishing campaigns. The participating customer organization receives reporting events through its Brixeon platform and may have its own employee privacy notice or contractual arrangements.

2. Gmail information accessed

When the add-on is opened on an email, it accesses the currently opened Gmail message using the current-message permission. It reads the message HTML and plain-text body to find an embedded simulation reporting URL, and uses the current Gmail message ID to ensure the report action corresponds to that message. This access is limited to the opened message; the add-on does not request unrestricted access to the inbox, send emails, or modify or delete Gmail messages.

The Report Phishing button is shown on all messages. If a message has no valid simulation marker, the add-on displays “Reporting link not found in this email” and does not submit a report.

3. Purpose and reporting

When a user selects Report Phishing for an eligible simulation, the add-on decodes the reporting URL embedded in that message and sends an HTTPS request to it. The URL includes a campaign or recipient identifier, which allows the customer organization to view the resulting reporting event in its Brixeon platform. The reporting records identified by the operator are campaign ID and recipient ID, stored in Brixeon Cloud. The add-on does not intentionally send the full Gmail message body as part of the reporting request.

Operational execution logs and receiving-server request metadata may also be generated as part of running the service. This notice does not represent those logs as part of the confirmed campaign-record fields.

4. Recipients and sharing

Reporting events are available to the participating customer organization through its Brixeon platform. Reporting requests are sent to the HTTPS destination embedded in the simulation email; the destination can vary by campaign. The receiving service and infrastructure involved in delivering the request may process the identifier and ordinary request metadata. The operator states that reporting data is not shared with other third parties for separate purposes.

The add-on currently checks the reporting URL format but does not independently verify that the destination hostname is authorized by Brixeon. This limitation must be addressed in the production reporting flow before public distribution.

5. Storage and retention

Campaign and recipient identifiers associated with reporting are stored in Brixeon Cloud. Reporting-data retention follows the applicable customer contract. The add-on code does not create a separate persistent store of full Gmail message bodies. Google Apps Script and the receiving infrastructure may generate operational logs, whose retention may differ from the customer campaign records.

6. Security

The add-on makes reporting requests over HTTPS with certificate validation enabled and does not follow HTTP redirects during reporting. The current URL-format check is not a verification that the destination belongs to Brixeon. No method of transmission or storage can guarantee absolute security.

7. Access and deletion requests

To request access to, correction of, or deletion of reporting records, contact your organization’s security or privacy administrator or email info@brixeon.com. Requests concerning customer reporting data are handled in accordance with the applicable customer contract. You may also ask your Google Workspace administrator about uninstalling the add-on.

8. Google API data and Limited Use

Use and transfer of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. Information accessed from the current Gmail message is used to provide the simulated-phishing reporting feature described in this policy. It is not used for advertising or sold. Human access to Google user data is limited to circumstances permitted by the applicable Google policy.

Policy changes

We will update this page and its effective date if our data practices change. Material changes to how Google user data is used may require additional notice and consent before the new use begins.

9. Contact

الدرع المتطور لتقنية وتكنولوجيا المعلومات
شارع الملكة رانيا، عمان، الأردن، مبنى قندل سنتر، مكتب 204
Jordan
Privacy and support: info@brixeon.com
Website: https://addins.brixeon.com/