Skip to Content
Gorila docs

Security and privacy

What Gorila keeps, what it never sees, where it lives, who can see it and how you leave.

The short version is on gorila.la/trust; the legal documents are the privacy policy, the data processing agreement and the terms. Here is how it works.

What Gorila stores

Your team's tasks and company rules: short text your AI writes, with pointers back to the source. Your account (email and name). Counts of what was used, without content. Gorila stores distilled summaries and links, never raw documents, emails or chat logs, and the server instructions tell every AI the same.

What Gorila never gets

Your files, documents, emails and chat logs. Your AI reads them where they are, with its own connections, and keeps them there.

No AI on Gorila's side

Gorila generates nothing and reasons over nothing. The only model it calls is an embedding model for search, which turns the distilled text into vectors (an Amazon model in the EU that does not store, log or train on it). Your data is not used to train anything.

Where it lives

In the EU: the database is on Supabase in Ireland (eu-west-1) and the application runs on Vercel in Dublin. The providers that handle data are listed in the privacy policy and the DPA.

Who can see what

Every table has an organization and row-level security, so tenants cannot see each other and the database itself enforces who sees what inside one. A member sees the tasks and knowledge of their areas. Personal knowledge and private tasks are visible only to their owner. Each member's profile (their title and what they handle) is visible to their whole organization: they see it before it is saved, and only they can change it. MCP tools run as the signed-in member, not with a service role.

Authentication and tokens

MCP clients sign in with OAuth 2.1 and act as the person. Access tokens are short-lived. Personal and agent tokens (gor_…) are stored hashed, shown once and can be revoked in Settings. Agent webhooks are signed and Gorila only sends task ids.

Changes need a person

AIs propose changes to the company's knowledge; a person approves them. Every version is kept and can be restored, and an audit trail shows who approved what. Text written by people and agents inside tasks and knowledge is treated by the server instructions as information, never as instructions to the AI.

Leaving

Anyone can export what they see (JSON and Markdown). An owner can delete the whole organization; it is removed at once and drops out of backups within the retention window stated in the privacy policy.

Report a problem

Security reports and questions: hola@malavar.com.

On this page