Who owns our records and everything generated from them?
You own your data, everything generated from it and anything built for it.
That means the minutes, memos, decks and answers your team makes in MainBranch.
Copy all nine questions into your RFP and each answer into your scoring sheet
Last updated
4 questions
You own your data, everything generated from it and anything built for it.
That means the minutes, memos, decks and answers your team makes in MainBranch.
Your admin exports them from the Action Log, each one with who asked and when.
Whole chats export too, grouped by organization, department or person.
Yes, the person you name.
Each saved workflow stops at its review step and waits for their sign-off.
Your admin exports the Action Log and every chat, file and meeting whenever you choose.
You own your data, everything generated from it and anything built for it.
5 questions
Yes.
Single sign-on over SAML 2.0 and OpenID Connect, with Microsoft Entra ID, Okta, Google Workspace, ADFS or Ping Identity.
Two-factor authentication for every member, set by your admin.
The Action Log keeps every sign-in, prompt, answer, upload and export, with when it happened, who did it and what it touched.
Role-based access: Owner, Admin, Member.
Each person reaches only what their own account can open.
Your admin gives each person their role.
U.S. hosting on AWS, with GovCloud for certain backend services, in an isolated tenant.
Regional deploys, in U.S. regions.
Available on request at security@mainbranch.com.
A county, a city, a coalition of governments and a state ask for them in documents you can read in full
Its section 6.2 asks vendors for single sign-on with multifactor authentication, export for public records requests, disclosure of subprocessors and a right to audit. Under section 8.1, a county employee reviews the work before it is used or shared.
Seattle puts terms on data use and ownership, quality and auditing, human oversight and termination into its contracts, and a person must review generated work before each official use.
Every bid under its RFP protocol carries a completed vendor FactSheet, which asks where prompt and output data is stored.
A person in a responsible role must review any recommendation or decision a system makes that could affect someone’s rights, duties or privileges, and can reject or change it.
The Trust Center has the full report and our policies on request, and the team that builds MainBranch answers the rest on a call