Anasa AI Privacy

Last updated: 2026-07-15

Introduction

This page describes how data is handled when you use AI features in Anasa. It complements the [Privacy Policy](/privacy), which covers the app and the account system as a whole.

1. Local-First by Default

Anasa does not send your notes anywhere unless you explicitly choose an AI setup that requires it:

• On-device (Apple Intelligence): On supported Apple hardware, AI features can run entirely on your device. Your content never leaves the machine.
• Local models (Ollama): If you run a local model server such as Ollama, AI requests are processed on your own hardware. Your content never leaves the machine.
• Managed service (Anasa AI) and bring-your-own-key (BYOK) modes send content off-device only when you enable them and only when you invoke a feature. They are described below.

2. What Anasa AI Sends

When you invoke a feature through the managed Anasa AI service:

• Only the note text needed for the requested feature is transmitted — for example, the note you asked to summarize, or the messages of the chat you are having. Anasa does not upload your vault, sync your notes, or send content in the background.
• Content is sent over TLS to anasa.md and forwarded to our AI model provider — currently Azure OpenAI as the primary provider — to process the request.
• Your content is not used to train models and is not stored beyond what is needed to process the request. Anasa's servers do not retain the note text after the response is returned.
• Embedding requests work the same way: the resulting vectors are returned to your device and stored locally there, not on Anasa's servers.

3. What Anasa AI Records

For credit accounting, each successful managed-AI request writes a usage record to our database containing:

• The license id the request was made under.
• The feature invoked (e.g. chat, summarize, suggest tags).
• The credit count deducted (recorded as a negative entry when credits are refunded).
• A timestamp.
• Minimal request metadata used for accounting and debugging — for example, the number of messages in a chat request. This metadata never includes your note text.

These records exist so your credit balance and usage history are correct; they are retained under the same account-data rules as the rest of your account (see the [Privacy Policy](/privacy)).

4. Bring-Your-Own-Key (BYOK)

If you configure your own API key for a provider, requests go directly from your device to that provider. Anasa's servers are not involved, no credits are charged, and no usage records are created on our side. Data handling is governed entirely by your chosen provider's terms and privacy policy.

5. Rate Limits and Abuse Controls

To keep the managed service available and prevent abuse, Anasa AI enforces per-license rate limits and caps on request input size. These controls operate on request identifiers and sizes, not on the content of your notes, and do not involve retaining your content.

6. Contact

Questions about AI data handling: email hey@anasa.md (Entro314 Labs).