PRIVACY POLICY

Last Updated: September 16, 2025

1. Introduction

Beacon AI Solutions is committed to protecting the privacy and security of the personal data we process. This Privacy Policy ("Policy") describes how we collect, use, process, share, and protect Personal Data in connection with the provision and use of the Beacon service (the "Service"), as well as our websites and related interactions (collectively, the "Platform").

This Policy applies to:

"Personal Data" means any information relating to an identified or identifiable natural person. This can include names, email addresses, IP addresses, and other information defined as personal data under applicable data protection laws.

Please read this Policy carefully. By accessing or using our Platform, you acknowledge that you have read, understood, and agree to the practices described in this Policy. If you are using the Service as an Authorized User on behalf of a Customer, your use is also governed by the agreement between Beacon AI Solutions and that Customer (the "SaaS Agreement").

2. Information We Collect

We collect information in the following ways:

3. How We Use Your Information

We use the Personal Data we collect for the following purposes:

4. How We Share Your Information

We DO NOT sell your Personal Data in the traditional sense. We may share Personal Data under the following circumstances:

Crucially, we treat Customer Data (the data uploaded by Customers/Users for processing by Beacon) as confidential information belonging to the Customer. We will NOT access or share Customer Data except as necessary to provide the Service as instructed by the Customer, for support purposes initiated by the Customer/User, to improve the service (using anonymized/aggregated data as described above), or as required by law.

5. Data Retention

We retain Personal Data for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law. Key retention considerations include:

6. Data Security

Beacon AI Solutions takes the security of Personal Data seriously. We implement and maintain reasonable and appropriate technical, administrative, and physical security measures designed to protect Personal Data from unauthorized access, disclosure, alteration, misuse, loss, or destruction. These measures include, but are not limited to:

7. Third-Party Integrations and OAuth Data

Beacon offers optional integrations that allow you to connect your accounts with third-party services so that Beacon can read information on your behalf to provide meeting and sales-context features. You explicitly authorize each integration through the provider's OAuth consent screen, and you can disconnect any integration at any time from Beacon's Integrations page or from the third party's own account security settings.

7.1 Google (Calendar)

When you connect your Google account and grant the https://www.googleapis.com/auth/calendar.readonly scope, Beacon reads a short window of upcoming calendar events solely so that you can select one to start a Beacon recording session and to pre-populate meeting context (attendees, subject, start time).

Google API Services User Data Policy — Limited Use Disclosure: Beacon's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

7.2 Microsoft 365 (SharePoint, OneDrive, Outlook Calendar)

When you connect Microsoft 365, Beacon requests only the scopes needed for features you use — for example, Calendars.Read for the calendar meeting picker, and Sites.Read.All / Files.Read.All for SharePoint / OneDrive file selection. Data is read on demand; OAuth tokens are stored encrypted at rest.

7.3 Salesforce

When you connect Salesforce, Beacon requests the api and refresh_token scopes and makes read-only SOQL queries to fetch Accounts, Contacts, Opportunities, recent Tasks/Events, Cases, and Notes related to meetings you select. No data is written back to Salesforce. OAuth tokens and instance URL are stored encrypted at rest.

7.4 Pipedrive

When you connect Pipedrive, Beacon requests the Access to basic information, Contacts, Deals, Activities, and Read users data scopes and makes read-only REST calls to fetch Organizations, Persons, Deals, Activities, and Notes related to meetings you select. No data is written back to Pipedrive. OAuth tokens and API domain are stored encrypted at rest.

7.5 Revocation

You can revoke Beacon's access to any connected account at any time:

Disconnecting revokes the refresh token and deactivates Beacon's stored tokens for that provider.

8. Changes to this Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. If we make material changes, we will notify you by posting the updated Policy on this page with a new "Last Updated" date, and/or by sending an email to the address associated with your account, or through a notification within the Service, prior to the change becoming effective. We encourage you to review this Policy periodically. Your continued use of the Platform after any changes constitutes your acceptance of the revised Policy.