Security

Last updated: November 19, 2026

This page describes how Barrow and Barrow for Word, our Microsoft Word add-in, are deployed and operated, for the people who review and administer software at our customers' firms. What we collect and how we use it is set out in our Privacy Policy.

Barrow for Word, for IT administrators

Barrow for Word is published by Barrow AI, Inc. in Microsoft Marketplace: https://marketplace.microsoft.com/en-us/product/office/WA200012258

  • What it is. An Office web add-in that runs in Word's task pane. Word loads it from https://word.barrow.site. No software is installed on the user's device.
  • Deployment. A user can add it to Word from Microsoft Marketplace, or a Microsoft 365 administrator can deploy it from the Microsoft 365 admin center (Settings, then Integrated apps) to everyone, to chosen users or to groups. Removing the assignment removes the add-in.
  • Permission. The add-in's manifest requests one permission, ReadWriteDocument: it can read and change the Word document that is open. The manifest is public: https://word.barrow.site/manifest.production.xml
  • Where it runs. Word on Windows, Word on Mac and Word on the web.
  • Account. Using it requires signing in to a Barrow account that belongs to a firm with access to Barrow for Word.

Network destinations

The add-in connects to these hosts, all over HTTPS:

  • word.barrow.site: the add-in's own pages
  • api.barrow.site: the Barrow service
  • barrow.us.auth0.com: sign in
  • accounts.google.com: Google's sign-in page, only for a person who chooses to sign in with Google
  • login.microsoftonline.com: your firm's own Microsoft sign-in, for single sign-on and for the OneDrive and SharePoint file picker
  • graph.microsoft.com: finds the user's own OneDrive when they open the file picker
  • Your firm's own *.sharepoint.com hosts: Microsoft's OneDrive and SharePoint file picker, and the files the user picks
  • appsforoffice.microsoft.com: Microsoft's Office library
  • barrow.site: links to support, billing and these pages

graph.microsoft.com and your *.sharepoint.com hosts are reached only when a user brings in files from OneDrive or SharePoint, so a firm that has turned drives off never reaches them.

Signing in and access

  • Sign in. Sign in is handled by Auth0. A person signs in with an email address and password, with Google, or with their firm's Microsoft Entra ID account through single sign-on, described below. Barrow does not receive or store passwords.
  • Verified email. A new account must verify its email address before it can use Barrow. With single sign-on, a firm's directory vouches for the addresses in the firm's own domains.
  • One account, one identity. An account belongs to the sign-in that created it. Barrow does not join or move accounts because two sign-ins carry the same email address. There is one exception: when a firm turns on single sign-on, an account one of its people made earlier with a password or Google becomes their company account the first time they sign in through the firm's directory.
  • Access by firm. Every project, source document and report belongs to one firm and is available only to that firm's members. A person joins a firm through an invitation sent to their email address, which only a verified account with that address can accept. A firm's administrators can remove a member at any time.
  • Failed attempts. The service limits repeated failed sign-in tokens from one network address.

Single sign-on with Microsoft Entra ID

A firm can have its people sign in to Barrow, on the web and in Barrow for Word, with their company Microsoft accounts.

  • How it works. Barrow connects to your firm's own Microsoft Entra ID tenant with OpenID Connect. Your people sign in at Microsoft, under your firm's own sign-in rules, including multi-factor authentication and Conditional Access. Barrow never sees their passwords.
  • What Barrow asks Microsoft for. Sign-in and basic profile only: the OpenID Connect scopes openid, profile and email. The email scope shares the email address of the person signing in, and nothing more. Barrow keeps the address on that person's Barrow account and uses it to confirm they are in your firm's email domains and to match the invitation that adds them to your firm; our Privacy Policy sets out how account details are handled. The scope does not open anyone's mailbox, and Barrow asks Microsoft for no mail permission, so it cannot read or send anyone's email. Single sign-on gives Barrow no access to your directory, groups, mail or files.
  • Your domains only. Your directory can sign in only addresses in the email domains your firm has confirmed with us. A sign-in that arrives from your directory with any other address is refused.
  • Enforced for your domains. Once your firm is on single sign-on, Barrow refuses password and Google sign-in for addresses in your domains.
  • Removing a person. A person signed in through your directory is asked to sign in through it again at least every 12 hours. Someone you disable or remove in Entra ID can no longer sign in, and loses access to Barrow within 12 hours. A firm administrator can also remove a member in Barrow at any time.
  • Ending a sign-in on demand. In a firm that uses single sign-on, an administrator can choose Sign out now for any other member on the Team page. That person's next request is refused until they sign in through your directory again, and your directory refuses anyone you have disabled. Disable the account in Entra ID, then choose Sign out now, and access ends at once.
  • Accounts and membership. A person's Barrow account is created the first time they sign in. They join your firm in Barrow through an invitation from one of your firm's administrators. Once your firm is on single sign-on, only addresses in your email domains can be invited or can join it, so every member signs in under your firm's own rules. Barrow creates no accounts in your Entra ID tenant.
  • Where people sign in. On the web at barrow.site/sso, and in Barrow for Word by choosing Sign in with SSO.

Setting it up

Single sign-on runs through an application that your Microsoft Entra administrator registers in your own tenant, so your firm holds the registration, its secret and the rules for who may sign in. Barrow sends your administrator a setup link, good for five days, that walks through these steps and takes the application's details directly, so the client secret never passes through Barrow staff. Steps 1 to 5 are done in the Microsoft Entra admin center, at entra.microsoft.com, and use the names Microsoft shows there. Registering the application takes at least the Application Developer role. Granting consent (step 4) and limiting who can sign in (step 5) take at least the Cloud Application Administrator role.

  1. Register the application

    • Go to Entra ID, then App registrations, and select New registration.
    • For Name, enter Barrow. Your people see this name when they sign in.
    • For Supported account types, choose Single tenant only (older screens say "Accounts in this organizational directory only"), so that only accounts in your directory can use it.
    • Select Register. The application's Overview page opens and shows its Application (client) ID.
  2. Add Barrow's redirect address

    • In the application, under Manage, select Authentication.
    • Select Add Redirect URI (older screens say "Add a platform"), choose Web, and enter this address exactly: https://barrow.us.auth0.com/login/callback
    • Select Configure.
  3. Create a client secret

    • Select Certificates & secrets, then Client secrets, then New client secret.
    • Give it a description and choose when it expires. Microsoft allows up to 24 months.
    • Select Add, then copy the secret's Value straight away. Microsoft shows it only once. The setup link asks for the Value, not the Secret ID.
  4. Grant consent for sign-in

    • Select API permissions. Barrow asks Microsoft for three delegated Microsoft Graph permissions and no others: openid (sign users in), profile (view users' basic profile) and email (view users' email address).
    • To list them, select Add a permission, then Microsoft Graph, then Delegated permissions. Tick email, openid and profile, and select Add permissions.
    • Select Grant admin consent for your tenant and confirm. Your people then sign in without being asked to approve anything. Without it, a firm that does not let users approve applications sees Microsoft's "Need admin approval" message.
    • The email permission shares the address itself. Reading or sending mail takes separate Microsoft permissions, such as Mail.Read and Mail.Send, and Barrow requests none of them.
    • Barrow needs no application permissions.
  5. Choose who can sign in (optional)

    • As Microsoft sets it up, every account in your tenant can sign in through the application. To limit it, go to Entra ID, then Enterprise apps, open the application and select Properties.
    • Set Assignment required? to Yes and select Save.
    • Under Users and groups, select Add user/group and assign the people or groups who should have Barrow.
    • Your Conditional Access policies apply to the application as they do to your others.
  6. Enter the details in the setup link

    • Your tenant's Primary domain, shown on the Entra ID Overview page.
    • The Application (client) ID from step 1.
    • The client secret's Value from step 3. It is saved directly to Barrow's sign-in service and masked once saved, so no one at Barrow sees it.
    • The setup link then runs a test sign-in through your directory to confirm the connection works.
  7. Barrow turns it on

    • Tell us the email domains your people sign in with (the part after the @) and the date the secret expires. These are identifiers, not secrets. Barrow reads each person's email address from their Entra ID account and accepts only addresses in these domains. Each account needs its Email property set in Entra ID: a sign-in that arrives without an email address is refused.
    • The connection serves your tenant alone. Barrow turns on single sign-on for your email domains at a time agreed with you.
    • A person you choose then signs in at barrow.site/sso to confirm it.
    • It can be turned on for one domain first, such as a test domain, and for the rest once you have confirmed it.

Microsoft's own instructions for these steps: register an application, add a redirect URI, add a client secret, grant admin consent and limit an application to chosen users.

Setting it up with SAML

A firm that prefers to share no secret can connect with SAML 2.0. To set it up, you and Barrow exchange identifiers, a sign-in address and your public signing certificate, so email is fine for all of them. Barrow gives you a connection name to use in step 2.

  1. In the Microsoft Entra admin center go to Entra ID, then Enterprise apps, and select New application, then Create your own application. Name it Barrow and choose the option for an application not found in the gallery.
  2. Open Single sign-on and choose SAML. Under Basic SAML Configuration set Identifier (Entity ID) to urn:auth0:barrow:connection-name and Reply URL to https://barrow.us.auth0.com/login/callback?connection=connection-name.
  3. Under Attributes & Claims, edit Unique User Identifier (Name ID): source attribute user.objectid, name identifier format Persistent. Leave the other claims as Microsoft sets them. Each person needs an email address on their account.
  4. Under Users and groups, assign the people or groups who should have Barrow.
  5. Send Barrow the Login URL and the Certificate (Base64), with the email domains your people sign in with.
  6. Barrow connects your tenant and turns it on at a time agreed with you, and a person you choose signs in at barrow.site/sso to confirm it.

With SAML, Barrow for Word signs in the account that is signed in to Windows. Your signing certificate expires on the date Microsoft shows beside it; send the new one before then.

Keeping it running

  • Renewing the secret. Before the secret expires, ask us for a new setup link, create a new secret as in step 3 and enter its Value there. The old secret keeps working until then, so sign-in is not interrupted. If a secret expires first, sign-in through your directory stops until a new one is in place.
  • Changing your domains. Tell Barrow which email domain to add or remove.
  • Stopping all sign-ins. In Enterprise apps, open the application, select Properties and set Enabled for users to sign-in? to No. Microsoft then lets nobody sign in through it. Because Barrow refuses password and Google sign-in for your domains, nobody with an address in them can sign in to Barrow, and people already signed in lose access within 12 hours.

If a sign-in fails

  • Microsoft shows "Need admin approval". Admin consent has not been granted. See step 4.
  • Microsoft shows error AADSTS50011. The redirect address does not match the one in step 2 exactly.
  • Microsoft shows error AADSTS50105. The person is not assigned to the application. See step 5.
  • Barrow shows "SSO isn't set up for this domain." The address is not in one of the email domains you gave us.
  • Barrow shows "Barrow did not receive an email address for this sign-in." The person's account has no Email property in Entra ID. Set it on the account and sign in again.

Your data

  • How it is used. Your documents and report content are processed only to provide the research, drafting and review features you request.
  • What the add-in sends. When a user asks the add-in to draft a section, answer a question about the sources, or check the writing, the relevant content of the open Word document is sent to the Barrow service so the request can be fulfilled. The add-in also reads the document's structure and content locally, to list its sections and to protect existing edits.
  • Source documents. Users add source documents by uploading them from their computer, or from their drives in one of two ways, chosen for each firm. With pick-only access, the user picks files in Microsoft's own OneDrive and SharePoint file picker in Barrow for Word, signed in as themselves through Word, and Barrow downloads only the files they pick. Barrow keeps no access to their OneDrive or SharePoint afterward. The picker asks Microsoft for the user's basic profile (User.Read) and SharePoint's MyFiles.Read to open the user's own OneDrive, and SharePoint's AllSites.Read only when the user opens a SharePoint site; a firm that approves only the first two picks from OneDrive alone. These permissions act only as the signed-in user, so the picker shows only what that person can already open, and the sign-in stays inside Word on their computer: Barrow's servers never receive it. With a standing connection, the user connects OneDrive or Google Drive once and can browse and import from it at any time. That connection asks Microsoft for read access to the files the user can open (Files.Read and Files.Read.All), the user's basic profile (User.Read) and offline_access, and the read-only credentials it gives Barrow are stored encrypted. Both use Barrow's own Microsoft application, separate from the one your firm registers for single sign-on; a firm that does not let users approve applications grants admin consent to it once in Microsoft Entra. A firm can also turn drives off, so source documents arrive only by upload. Tell us which your firm wants and we set it up.
  • AI processing. Barrow uses Anthropic, Google and OpenAI, through their paid business APIs, to read source documents and produce the drafts, answers and checks a user requests. Each firm's data is processed in isolation, with no exposure to other customers. Your data is never used to train or improve AI models.
  • Where it is stored. Customer files are stored in Amazon S3 in United States regions, and the Barrow service runs in the United States.
  • Encryption. Data is encrypted in transit with TLS 1.2 or higher. Customer files are encrypted at rest with AES-256.
  • Separation and access. Each firm's data is kept separate by application-level access controls and is available only to that firm's members. Access by Barrow personnel is limited to authorized staff, on the principle of least privilege.
  • Ownership. Everything you upload and the reports you produce remain yours. We do not sell customer information.
  • Retention and deletion. See sections 10 and 11 of our Privacy Policy.

Activity and logs

  • Your firm's activity record. Barrow records what your firm's members do and when, including company sign-ins, invitations, people joining, leaving, changing role or being signed out, source documents added and removed, analyses and final reports started, and report download links issued. It lists your own members only. Your firm's administrators read it on the Team page and export it as a CSV file. It is kept for as long as your firm has an account.
  • Your own sign-in logs. With single sign-on every sign-in to Barrow happens in your Entra ID tenant, so it appears in your Entra sign-in logs beside your other applications.
  • Service logs. The Barrow service's own logs, which record every request the service receives and every refused sign-in, are kept for 12 months.
  • Access by Barrow staff. Barrow staff have no account inside your firm, and all access to Barrow's production systems is logged and kept for 12 months.

Information security program

  • Policy. Barrow maintains a written Information Security Policy covering access control, data classification and handling, encryption, AI data use, incident response, backup, monitoring and vendor management. It is reviewed annually and is available to customers on request.
  • Service providers. Barrow relies on third-party service providers for sign in, cloud hosting and storage, AI processing, payments and email. They process customer data only as needed to provide the service. The current list is available to customers on request.

Security incidents

When we become aware of a security incident affecting customer information, we investigate it, contain it, and notify affected customers as required by law and by our agreements. See section 9 of our Privacy Policy.

Reporting a security concern

Email support@barrow.site with "Security report" in the subject line. Tell us what you found and how to reproduce it, and do not include passwords or access tokens. We will acknowledge your report and keep you informed while we look into it.