Privacy Policy

Effective date: Nov. 16, 2026.

1. Who we are and what this policy covers

Brightrail helps companies stop sensitive data from leaking into AI tools. In this policy, “Brightrail”, “we” and “us” mean Transparency, LLC, 288 Egg Harbor Road, Sewell NJ 08080.

This policy explains what personal information we handle, why, and what choices you have. It covers three groups of people:

  • visitors to our website,
  • people who sign in to the Brightrail console, usually a company’s IT or security admins,
  • employees of our customers, whose data our product handles for their employer.

Our role. For our website and for admin accounts, we decide how the data is used, so we are the controller. For data about a customer’s employees, we only act on the customer’s instructions. There, we are the processor (a “service provider” under US state laws) and the customer is the controller.

If you are an employee of one of our customers, your employer decides how Brightrail is used at your company. Questions about that usually go to them first. We will help them answer.

2. What we collect

Website visitors

Our website sets no cookies of its own and uses no analytics. If you email us, we keep your email and what you wrote so we can reply.

Admins who sign in to the console

When an admin signs in with Google, we receive their name, email address and a link to their profile picture.

From a customer’s Google Workspace

When an admin connects their company’s Google Workspace, we read:

Users: Google user ID, primary email, full name, whether the account is suspended, the Workspace customer ID, and the department of the user’s main organization.

Connected apps: for each user, the third-party apps they have authorized: the app’s name and client ID, the permissions (scopes) granted to it, and whether it is an anonymous or native app.

App activity: from Google’s OAuth token audit log, when each AI tool was last authorized (last 180 days) or last used (last 30 days). We keep only the latest usage per app. We do not keep who authorized or used it, and we do not request IP addresses.

Organization units: the name of the top-level organization unit, and only when the customer installs the extension through Google.

We do not read groups, sign-in events, or any email, file, chat or calendar content.

From the browser extension

The extension works only on ChatGPT (chatgpt.com, chat.openai.com), Claude (claude.ai) and Gemini (gemini.google.com). On every other website it does nothing.

Daily check-in. Once a day, and when the browser sign-in changes, the extension sends: the company’s ID and a check-in token, a random ID for the browser profile, the email the browser profile is signed in with (where the browser provides it), the extension version, and how it was installed. We use the email only to match the check-in to the right person in the customer’s directory. We do not store it.

When it stops a message. A random record ID and the time, the AI tool, the account type (work, personal, signed out or unknown), the kinds of sensitive data found (for example card number, Social Security number or API key), whether it was in a message or an upload, what the employee did next, and the versions of the extension and its detection model.

When it pauses a file. The file type, its size, how many findings of each data type, and whether the file was uploaded.

When it can’t check a file. The file type, its size and the reason, for example an image or a password-protected file.

Redacted messages. Only when the employee chooses “Redact it and send”, we keep the message exactly as the AI tool received it, up to 10,000 characters. Each sensitive value is replaced by a placeholder, for example “‹Card ending 8812›”. Customer admins can view these messages in the console.

3. What we never collect

  • File contents or file names.
  • Original messages, before anything was redacted.
  • Messages the employee edited or didn’t send.
  • The full sensitive values we find. A placeholder may keep a small hint, such as the last four digits of a card.
  • Anything from websites other than ChatGPT, Claude and Gemini.
  • IP addresses or browser details in our own records. Our hosting providers keep these in their standard request logs (see section 5).

4. How we use information

We use the information above only to run and protect Brightrail:

  • show customers which AI tools are in use and how risky they are,
  • show customers what the extension stopped, and how employees responded,
  • show which employees have the extension and which don’t,
  • send the emails and alerts the customer sets up,
  • give support, keep the service secure, and meet legal duties.

We do not sell personal information. We do not use it for advertising.

No training on your data. The extension’s detection model runs on the employee’s computer. It was trained only on made-up (synthetic) data. We never use customer data to train or improve any model, including messages, files, incident records and redacted messages.

Google permissions (scopes) we request. Required when an admin signs in:

  • openid : confirms the identity of the admin who signs in.
  • email : reads the admin’s email address.
  • profile : reads the admin’s name and profile picture.
  • admin.directory.user.readonly : reads the user directory and confirms the person is a Workspace admin. Read-only.
  • admin.directory.user.security : reads which third-party apps each user has authorized. Google offers no read-only version, and it would also allow removing an app’s access. We only read with it.
  • admin.reports.audit.readonly : reads when AI tools were last authorized or used. Read-only.

Optional, only when an admin installs the extension for the organization:

  • admin.directory.orgunit.readonly : finds the top-level organization unit and its name. Read-only.
  • chrome.management.policy : installs the extension and gives it its settings, only when an admin clicks “Install for all employees”. We change no other Chrome setting.

Section 13 explains how we handle the data these scopes give us.

5. Who we share it with

We share data only with the service providers below, only so they can run Brightrail for us, and under contracts that limit what they can do with it.

ProviderWhat it does for usWhere
VercelHosts our website, console and APIUnited States (Washington, D.C.)
SupabaseHosts our database, which holds all customer dataUnited States (Oregon)
n8n CloudRuns the Google Workspace scan and sends emailsTo confirm with n8n
GoogleSends our emails through the Google Workspace email relayPer Google’s terms

Vercel and Supabase record IP addresses and browser details in their own request logs, as hosting providers normally do.

We also use Anthropic’s Claude to read AI vendors’ public terms and privacy policies, so we can score their risk. It receives no customer data.

We may also share information if the law requires it, to protect our rights or someone’s safety, or as part of a merger or sale of our business. If that happens, this policy keeps applying to your data.

6. Where your data is stored

We store and process customer data in the United States. If you are in the EU, the UK or another region with transfer rules, please contact us before you start using Brightrail, so we can put the right transfer terms in place.

7. How long we keep it

We keep customer data while the customer’s account is open. That includes incident records, redacted messages, counts of files we couldn’t check, the employee directory, connected apps and the latest extension check-in for each browser profile.

  • People who leave a customer’s company are marked as left, not deleted, so past incidents still make sense.
  • App access that ends is marked as ended, not deleted.
  • When a customer closes its account, we delete all of its data within 30 days of a request.
  • One employee’s data: a customer can ask us to delete one employee’s records. We do it within 30 days of the request. If the person is still in the customer’s Google Workspace, the next scan adds back their name and email only.

8. How we protect it

  • All connections to the website, the console, the API and the extension use HTTPS. Database and email connections are encrypted too.
  • Google tokens are encrypted by our app with AES-256. All other data is encrypted at rest by our database provider.
  • Each customer can only see its own data. The database itself enforces this, not just our app.
  • Only two members of our team can access our production systems.
  • Our own logs hold event names, company IDs and outcomes only. Never tokens, emails or message content.

No system is perfectly secure. If a breach affects a customer’s data, we will tell the customer without undue delay, and within 72 hours of confirming it.

9. Cookies

The console uses only the cookies it needs to keep you signed in safely: a session cookie, a security (CSRF) cookie and a sign-in redirect cookie. We use no analytics or advertising cookies. Our public website sets no cookies of its own.

10. Your rights

Depending on where you live, for example in the EU, the UK or California, you may have the right to:

  • see the personal information we hold about you,
  • correct it,
  • have it deleted,
  • object to or limit how it is used,
  • get a copy to take elsewhere,
  • complain to your data protection authority.

Employees of our customers: please contact your employer first, since they control this data. If you contact us, we will pass your request to them and help them answer it.

Admins and website visitors: email us at privacy@brightrail.com. We answer within 30 days.

We do not sell personal information, and we do not share it for targeted advertising.

11. Children

Brightrail is a business product. It is not meant for anyone under 16, and we do not knowingly collect their data.

12. Changes to this policy

When we change this policy, we update the date at the top. If a change is important, we notify customer admins at least 30 days before it takes effect.

13. Google user data

Brightrail connects to Google Workspace through Google APIs. This section explains how we handle the data we receive from them.

What we access. Through the scopes listed in section 4: the name, email address and profile picture of the admin who signs in; each user’s Google user ID, primary email, full name, account status, Workspace customer ID and department; the third-party apps each user has authorized and the scopes granted to them; when each AI tool was last authorized or used, from the OAuth token audit log; and, only when the extension is installed through Google, the name of the top-level organization unit. We do not access email, files, calendars, groups or sign-in events.

How we use it. Only to provide the features customers see in the Brightrail console: finding the AI tools connected in their Workspace, scoring their risk, showing which employees have the extension, and installing the extension when an admin asks. We do not use it for advertising, we do not sell it, and we do not use it to decide creditworthiness or for lending. We do not use it to develop, improve or train generalized AI or machine learning models.

How we store it. In our database in the United States (Supabase, Oregon). Google tokens are encrypted by our app with AES-256, and all other data is encrypted at rest. Each customer can see only its own data.

How we share it. Only with the service providers listed in section 5, so they can run Brightrail for us. We never transfer it to advertising platforms, data brokers or information resellers. Otherwise, we transfer it only to comply with the law, for security purposes, or as part of a merger or sale of our business with the customer’s prior consent.

Who can read it. No one at Brightrail reads it, unless the customer agrees for a specific support request, it is needed for security purposes such as investigating abuse, or the law requires it.

How to request deletion. A customer admin can remove Brightrail’s access at any time in the Google Admin console, under Security > Access and data control > API controls. This stops any new data from being collected. To delete the data we already hold, email privacy@brightrail.com. We delete it within 30 days of the request.

Limited Use. Brightrail’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.

14. Contact us

Transparency, LLC, 288 Egg Harbor Road, Sewell NJ 08080
privacy@brightrail.com