Your relationships are valuable. Your privacy matters.
Relationship intelligence only works if people trust it. Here is what Inhere does with your data, in plain language.
What Inhere accesses
An administrator authorises Inhere for the organisation, through a Microsoft 365 app registration or Google Workspace domain-wide delegation, then chooses which mailboxes to include and how much history to import, from six months to everything.
Inhere reads email and calendar data from those mailboxes. It doesn’t edit, move or delete anything in a mailbox or calendar. Inhere doesn’t send email from your people’s mailboxes.
What Inhere analyses
To understand relationships, Inhere processes email and meeting activity: senders, recipients, dates, subject lines and message content. Message content is analysed, including by AI models, for things such as communication topics and contact details in email signatures. Sentiment analysis is optional and off unless an administrator enables it.
We say this plainly because some relationship tools describe themselves as “metadata only”. Inhere is not, and we would rather you knew.
What Inhere keeps, and what it leaves out
Inhere stores the email and meeting information it processes, so it can keep relationship scores, history and trends up to date.
Administrators can exclude domains, email addresses, companies or names, such as legal counsel or personal contacts, and choose whether a rule applies to new data only or to existing data too. Excluded messages are kept only as minimal records, without their content, and are not processed by AI.
What users can see
People see relationship insights: who knows whom, strength scores and trends, Flow and Coverage. They also see interaction details such as dates, participants and subject lines.
Nobody can read a colleague’s email through Inhere. These relationship views are available to everyone with access, not only administrators, so it is worth agreeing how they will be used before you roll out.
What administrators control
Administrators manage the connection, mailboxes, import history, exclusion rules and Flow thresholds, and decide whether optional features such as CRM sync and the MCP endpoint for AI tools are switched on.
Roles separate users from administrators. People sign in with Microsoft or Google single sign-on, or with a password and multi-factor authentication.
Separation, security and accountability
Each organisation’s data is kept separate from every other customer’s. Connections are encrypted in transit, and the service sits behind a web application firewall.
An audit log records sign-ins, record views, imports, exports and administrative changes, and administrators can export it.
Hosting, AI processing and a technical review
Where your data is hosted and how AI processing is arranged can depend on your deployment. We’ll answer those questions specifically for your organisation, and IT and security teams can request a technical review covering architecture, permissions and data handling.
Request a technical reviewWhat could your organisation’s relationships be telling you?
We’ll show you Inhere with the questions your organisation is trying to answer.
Book a demo