# Security

> Source: https://minniai.com/security (canonical HTML page)

How to report a problem to us, and the limits built into MinniMemoryAgent so that a mistake or a breach on our side stays small.

Last updated 2026-11-07

## Reporting a vulnerability

Email with what you found and how to reproduce it. We reply within two business days and tell you what we did about it. Please give us a chance to fix a problem before you publish it. We will not take legal action against research done in good faith that avoids other people’s data and does not disrupt the service.

## Limits built into MinniMemoryAgent

- The Minni GitHub App is read-only and has no Contents permission. [Data handling](https://minniai.com/data-handling) lists exactly what it can read.
- We hold no credential that can write to your repositories. Paid upkeep runs on your own CI with your own GitHub App.
- Changes only ever arrive as a pull request on a new branch. Nothing merges unless a person on your side merges it.
- An installation links to a company only for the GitHub user who installed it, proved by signing in with GitHub.
- Webhooks are checked against a signature, and a replayed event changes nothing.
- The process that checks your files runs with no access to our database or keys.
- Client and staff sign-ins are kept apart: a token for one is refused by the other.

## What these limits do not cover

The free Report reads your host files on our side. That they are not kept is a promise our code makes, not one GitHub enforces. The protection against a full breach of our servers is your branch protection, your pull request review, and the fact that we hold no write access.

---

Index for agents: https://minniai.com/llms.txt. Doing a task: https://minniai.com/agents.md
