AXXA Agent by AXXA Lab™ Install Menu

AXXA Agent · privacy

Privacy policy.

This policy covers this website and the AXXA Agent plugin for Obsidian, both made by AXXA Lab™. In short: we don’t collect your data, except what you choose to send us by email or share when you sponsor the project. The website sets no cookies and runs no analytics, and the plugin has no telemetry.

last updated · 9 October 2026 · contact · contato@axxalab.com.br

01 Who is responsible

AXXA Lab™, the developer of AXXA Agent, based in Brazil, is the data controller for this website. Write to contato@axxalab.com.br for any privacy question. That address is the privacy channel; as a small processing agent, AXXA Lab™ has not appointed a data protection officer (ANPD Resolution 2/2022, art. 11).

02 This website

  • It is a static site. It has no forms, no accounts, no cookies, no analytics and no advertising.
  • Everything it shows (text, fonts, styles, images and video) is served from this domain. It loads no third-party fonts, scripts or trackers.
  • The site is hosted on GitHub Pages, and Cloudflare answers the DNS lookups for its domain. Like any web server, GitHub receives the technical data your browser sends to load a page (such as your IP address and browser type) and may keep it in logs for security and to deliver the site. That processing is governed by the GitHub General Privacy Statement, and DNS by the Cloudflare Privacy Policy. We don’t use those logs. The legal basis is legitimate interest in keeping the site available and secure (LGPD art. 7, IX).

03 The AXXA Agent plugin

  • The plugin runs on your device, inside Obsidian. It has no telemetry and sends nothing to us.
  • When you use an AI provider (OpenAI, Anthropic, Google Gemini, OpenRouter, NVIDIA NIM, ElevenLabs, or your own Ollama server), your device sends it directly, with the API key you configured, what that feature needs. The chat provider gets your messages, your attachments and the note excerpts used as context; in Agent mode it also gets the notes the agent reads and the results of its actions. The embedding provider gets the text of your notes, and images with a model that reads them, while the Vault Q&A index is built, and then the text of each vault search. Dictation sends your recording to OpenAI, and read aloud sends the answer’s text to OpenAI or ElevenLabs. Each provider handles that data under its own terms and privacy policy. With an Ollama model, that traffic stays between your device and your own server.
  • In Vault Q&A and Agent conversations, a per-chat switch starts on: excerpts of the notes that match your message are sent with it to the chat provider, and keep going with your later messages in that chat even if you turn the switch off afterwards. In Chat it starts off.
  • What goes with a message stays with it. On your later messages in that chat, the chat provider gets the same note excerpts and attached notes again, the agent’s earlier results (longer ones cut short) and, while the chat stays open, the images and PDFs from your three latest messages that have them. When a long chat nears the model’s limit, the same provider is asked to summarize its start, and that summary then goes in place of the older messages.
  • With OpenAI and OpenRouter, each request for an answer also carries an ID the plugin creates for that chat, with nothing from its content, so the provider can reuse its prompt cache. With Claude models (from Anthropic or through OpenRouter), the plugin asks the provider to keep the chat’s requests in that cache for a few minutes.
  • The agent’s Web access is on by default (Settings › AXXA Agent › Agent). With it, the agent can open public web pages and, with your own Tavily key, search the web through Tavily’s search API. Tavily receives the search the agent wrote, and a page it opens receives a plain request for that address. In the Ask and Vault permission levels each search and address waits for your OK, unless you chose Approve all on a web request earlier in that turn; in YOLO they run without asking.
  • Answers are shown as Markdown, so an image link inside an answer is loaded from wherever it points, and that server sees your IP address. A page you attach with + › Link is fetched only when you ask.
  • Your API keys are stored on your device in Obsidian’s secret storage, not in the plugin’s settings file. On computers, Obsidian encrypts them with your operating system’s protection (Keychain, Windows data protection or the Linux keyring) when it is available; on phones they go to the system’s secure storage.
  • Chats, the Vault Q&A index, skills and reports are saved as files in your vault. A chat’s file also keeps what went with each of your messages (note excerpts, and the text of notes, pasted text and pages you attached), the agent’s results (longer ones cut short) and the summary of a long chat, encoded but not encrypted. Images and PDFs are not kept in it.
  • More detail on what the plugin sends, and to whom, is in the Disclosures section of its README.

04 GitHub and the Obsidian directory

If you open an issue, start a discussion or install the plugin from the Obsidian community directory, those services handle your data under their own policies (GitHub, Obsidian).

05 Sponsorships

If you sponsor AXXA Agent through GitHub Sponsors, GitHub processes the payment under its own privacy statement. We then see your GitHub username and the sponsorship, and your email address only if you choose to share it with us. We use this only to thank you and to keep the records the law requires (legal bases: LGPD art. 7, IX and II). Sponsoring gives nothing in the plugin and is never required.

06 Your rights

Under Brazil’s General Data Protection Law (LGPD) and similar laws, you can ask whether we hold data about you, and ask for access, correction or deletion. Because neither this website nor the plugin sends personal data to us, we normally hold none, apart from sponsorships. If you contact us, we use your message only to answer it (legal basis: LGPD art. 7, IX) and delete it when the conversation is no longer needed. You can also file a complaint with Brazil’s data protection authority (ANPD).

07 Changes

If this policy changes, the new version will be posted on this page with a new date. If a paid option is added in the future, this page will be updated before it launches, to explain what the payment provider processes.

08 Contact

Email contato@axxalab.com.br. You can also write in GitHub Discussions, or report a security problem privately through GitHub’s private reporting.