Privacy Policy

Last updated: 2026-07-30

Introduction

Anasa is a local-first desktop application that keeps your notes on your device. This Privacy Policy explains what data we collect, how we use it, and your rights. We take privacy seriously and aim to comply with GDPR, CCPA, and other major privacy regulations.

1. What Data We Do NOT Collect (App Usage)

When using Anasa as a local desktop app:

• Your notes are never sent to us. Notes remain on your device as plain Markdown files.
• No telemetry by default. We do not collect usage data, crash reports, or interaction logs.
• No account required. The app works fully offline and requires no login to function.
• No tracking. Anasa does not track your activity, screen time, or behavior.

Two optional Anasa Cloud services do send content to our servers when you switch them on — capture sync and end-to-end encrypted vault sync. Both are described in section 2, and neither is on by default.

2. Data Collected via the Website and Account System

When you visit anasa.md or create an account to purchase a license or AI credits:

Clerk (Authentication)

• Email address: Used to authenticate your account and confirm your identity.
• Name (optional): If you provide it during signup.
• Clerk securely stores and manages these credentials. See Clerk's Privacy Policy for details.

Polar.sh (Payment Processing)

• Payment data: Card details, billing address, and purchase history are handled directly by Polar as our Merchant of Record.
• Anasa does NOT process or store payment card information.
• See Polar's Privacy Policy for payment data handling.

CapyDB (Database)

• Email address: Linked to your account.
• License key: Generated when you purchase a license.
• Account tier: Free or paid tier status.
• AI credit balance: Number of AI credits remaining in your account.
• Device identifiers: Device names and activation records to enforce per-seat licensing and usage limits (typically a hardware identifier and timestamp).

Account data is stored on CapyDB, our managed PostgreSQL platform, hosted in the EU (Hetzner, Finland). All data is encrypted in transit (TLS) and at rest. We retain this data only as long as your account is active, then delete it within 90 days of account closure.

Anasa Cloud capture sync (transfer queue)

• Capture content: If you use Anasa Cloud capture sync, notes and attachments you capture on mobile are held temporarily (markdown in CapyDB, attachments in Cloudflare R2) until your desktop app imports them.
• Synced captures are deleted from our servers immediately after your desktop imports them — the capture queue is a transfer buffer, not a copy of your vault. Vault sync, described next, is a separate opt-in service that *does* keep a server-side copy.
• Captures are encrypted in transit (TLS) and at rest.

Anasa Cloud vault sync (opt-in, end-to-end encrypted)

If you turn vault sync on in the desktop app, Anasa keeps a durable server-side copy of your vault so your other devices can pull it. This is the one part of the product where your notes are stored on our infrastructure, and it is off unless you enable it and enter a sync passphrase.

It is end-to-end encrypted. All keys are derived on your device from a passphrase that never reaches our servers, and file contents and file paths are sealed with XChaCha20-Poly1305 before upload. We hold no key that can open them, so we cannot read your notes or even their names.

While vault sync is on, we store, per file:

• Encrypted contents — one ciphertext object per file in Cloudflare R2, keyed vault/<license id>/<random id>.
• An encrypted path, plus keyed hashes of the path and contents (in CapyDB, table vault_files). The hashes are computed on your device with a key we do not have; we use them only to tell revisions apart.
• Metadata: ciphertext size, last-modified time, the identifier of the device that uploaded it, a per-vault revision number, and a deleted flag. Deleting a file locally leaves a tombstone row — a path hash and nothing else — so your other devices learn to delete it too.
• Sync parameters (vault_sync_state): the salt your devices use to derive identical keys from your passphrase, and a small sealed value used to reject a wrong passphrase before it corrupts a sync.
• Staged uploads (vault_uploads): short-lived rows for a push that has not finished, pruned automatically about an hour after they are created.

To be explicit about the limit of the encryption guarantee: while vault sync is on, the number of files in your vault, their sizes, when each one changes and which of your devices changed it are retained by us and are visible to us, even though contents and names are not. Live vault revisions also count toward your Anasa Cloud plan's sync quota, alongside in-flight captures.

Retention and erasure. Vault data is kept for as long as vault sync is on — there is no automatic expiry, because its purpose is to be the copy your next device pulls. "Reset vault sync" in the desktop app (Settings → Sync) erases it: every revision, tombstone, staged upload, R2 object and your sync parameters are deleted immediately, whether or not your plan is still active. Deleting your account from your dashboard settings removes the same data. Neither touches the Markdown files on your own machine.

3. How Anasa AI Uses Your Content

When you use optional AI features ("Anasa AI"):

• Content is sent to AI providers. When you invoke an AI feature, the specific note content you select is sent to third-party AI model providers (e.g., Azure OpenAI) to process your request.
• Bring-your-own-key (BYOK) mode: If you provide your own API key, content is sent only to your chosen provider's API. Anasa's servers are NOT involved.
• Local/on-device models: If you run Ollama or other local models, content is processed entirely on your device and never leaves it.
• Anasa-managed AI: If you use Anasa's managed AI service, content is sent via Azure OpenAI to fulfill the request. We do not retain or train on your content.

For details on how your chosen AI provider handles data, review their privacy policy, e.g. OpenAI, Google, or Anthropic.

For a detailed description of exactly what the managed Anasa AI service sends, forwards, and records, see the [Anasa AI Privacy](/ai-privacy) page.

4. Cookies and Authentication Sessions

• Session cookies: Stored only while you are logged into anasa.md. They are cleared when you log out.
• Authentication: Clerk manages session tokens. You may revoke access at any time by logging out or deleting your account.
• Locale preference: A cookie remembers your chosen language for the website.

5. Third-Party Processors

We work with the following data processors (Data Processing Agreements available on request):

6. Data Retention

• Active accounts: Kept as long as your account is active.
• Deleted accounts: Email, license, and device records are permanently deleted within 90 days.
• Captures: Deleted as soon as your desktop app imports them.
• Vault sync: Kept until you reset vault sync or delete your account — see the vault sync section above. There is no automatic expiry while sync is on.
• AI processing: AI providers may retain logs per their own policies; Anasa does not retain AI request content.

7. Your Data Rights (GDPR & Similar Laws)

You have the right to access, correct, delete, and export your data, and to object to non-essential processing (e.g., marketing emails). Deletion is self-serve: your dashboard settings delete your account together with your licenses, devices, credit history, captures and any synced vault data. For anything else, email hey@anasa.md with "Data Request" in the subject line.

8. International Data Transfers

Anasa uses processors that may operate servers outside your country (e.g., the United States). Such transfers are made under appropriate safeguards, including GDPR Standard Contractual Clauses where applicable.

9. Children's Privacy

Anasa is not intended for children under 13, and we do not knowingly collect their data. If we learn we have, we will delete it. Contact hey@anasa.md with concerns.

10. California Privacy Rights (CCPA/CPRA)

California residents may request to know, delete, or correct their personal information, and to opt out of any "sale" or "sharing" of data. Anasa does not sell personal data. Submit requests to hey@anasa.md with "CCPA Request" in the subject.

11. Security

We use TLS for data in transit, encryption at rest, and do not store unencrypted payment data. Vault sync adds end-to-end encryption on top of that: contents and paths are sealed on your device with keys derived from a passphrase we never receive. No method of transmission or storage is perfectly secure, but we work to protect your information.

12. Changes to This Policy

We may update this policy from time to time. Material changes will be announced on our website or by email to active account holders. Continued use constitutes acceptance.

13. Contact

For privacy questions or data requests, email hey@anasa.md (Entro314 Labs). We aim to respond within 30 days, or as required by law.