Privacy policy
Last updated: 2026-10-20. This policy covers the Elo plugin for ChatGPT and Codex and the Elo server at elo.sonaris.us.
What Elo is
Elo is a shared memory: Markdown files that you and the AI agents you authorize write and read through a tool interface (MCP). The content is yours. Elo does not read your chat history; the server only receives the arguments of the tool calls your assistant makes (a file path, text to write, a revision id).
Categories of personal data we collect
| Data | Why | Kept where |
|---|---|---|
| Memory content: the text you or your agents write into files | To store and serve your shared memory | A git repository on the Elo server |
| Participant identity: the participant id and display name the installation owner assigned you | To enforce access rules and sign each change in git history | Installation configuration and git commit metadata |
| Credentials: a SHA-256 hash of your participant token and the OAuth grants issued to ChatGPT/Codex | To sign you in; the token itself is never stored | Server state directory, readable only by the service |
| Server access logs: IP address, timestamp, requested path, user agent | Security and troubleshooting only | Web server logs |
Elo does not collect payment data, government identifiers, health records, precise location or any data about people who are not participants. Do not store such data in your memory; the installation owner may remove it.
Purposes
We use the data only to provide the shared memory service: store what you write, show it to the participants allowed to read it, and attribute each change to its author. There is no advertising, profiling, analytics or sale of data.
Recipients
Memory content is visible to the other participants of the same Elo installation, according to the access rules its owner configured (some folders are private to one participant, some shared, some append-only). ChatGPT and Codex receive the content your assistant reads, under OpenAI's privacy policy. No other third party receives your data. The server is hosted by the author on infrastructure in Brazil.
Retention
Memory content stays until you or the installation owner delete it. Because the memory is a git repository, deleted content remains in git history until the owner purges that history on request. OAuth grants expire with their tokens; participant token hashes are removed when the owner revokes the token. Access logs are rotated and deleted after 14 days.
Your controls
You can view, edit and delete any file you are allowed to write, directly from your assistant. You can disconnect the plugin in ChatGPT or Codex at any time; this revokes its OAuth grant. To revoke a participant token, to have your content removed from git history, or to get a copy of everything stored about you, contact us at support; we answer within 30 days.
Changes
If this policy changes, the date above changes and the new text is published here before it applies.