Skip to main content
If your firm signs client security questionnaires, you already know the questions: where does our data go, who can see it, and how do you prove nothing was tampered with? ParleHub is architected to give you defensible answers — enterprise SSO tied to your identity provider, project files stored inside your own SharePoint or Google Drive tenant, a tamper-evident append-only audit log enforced at the platform level, and role-based access that limits who can see what down to the project level.

Enterprise SSO

Connect Microsoft Entra ID or Google Workspace. Offboarding a user in your identity provider immediately removes their ParleHub access — no manual deprovisioning required.

Native Storage

On Enterprise, project files live in your own SharePoint site or Google Drive tenant. Client documents never leave your environment.

Audit Log

Every sensitive action is recorded in an append-only log enforced at the core platform level. No one — including ParleHub staff — can edit or delete existing entries.

Role-Based Access

Four roles span org-level and project-level control. Members only see the projects they belong to; private projects are invisible to everyone else.

​
What ParleHub Does Not Do

Understanding the boundaries is just as important as understanding what is included. ParleHub does not:
  • Use personal consumer AI accounts. All model calls run on your own provider API keys — never through a personal OpenAI, Anthropic, or Google account.
  • Store files outside your tenant (Enterprise). On the Enterprise plan, uploaded project files are written directly to your SharePoint or Google Drive. ParleHub processes them in transit to the model but does not retain them in ParleHub-managed storage.
  • Mix session data across organizations. Every organization is fully isolated. Conversations, files, members, and usage data are scoped to your org and never visible to another org on the platform.

​
Answering the AI Security Questionnaire

Use the answers below when completing client or internal security questionnaires. Each answer reflects ParleHub’s Enterprise plan unless otherwise noted.
On the Enterprise plan, project files are stored in your own SharePoint site or Google Drive tenant — the same environment your firm already governs. ParleHub processes file content in transit when sending it to the AI model, but does not persistently store that content outside your tenant. On Free and Team plans, files are stored in ParleHub-managed secure storage.
The provider you choose and connect via your own API key. ParleHub supports Anthropic, OpenAI, Google Gemini, and Azure OpenAI. You control the provider relationship, the key, and — where your provider agreement permits — the data processing terms. ParleHub never routes your requests through a shared or pooled consumer account.
Only members of the project in which a conversation lives. Project membership is explicit — users must be added to a project to see it. SSO-offboarded users have their session invalidated and access removed immediately when their account is disabled or removed in your identity provider.
No. On Enterprise, conversations are stored in your own storage environment. On all plans, conversations are scoped to your organization and are not accessible to ParleHub staff in the normal course of operations. The audit log records any administrative access events so you can verify this independently.
For the complete security and compliance details, visit parlehub.com/security.