Privacy

What leaves your computer, and when

When you press an action or type a question. The card's fields, its deck and note type, the last few messages in that conversation, and any standing instructions you have set. If the Library is switched on, the passages it retrieved for that question go too. If Neighbours is switched on, short excerpts of the handful of related cards it found.

When you build the Neighbours index. The text of the notes being indexed, in batches, so it can be turned into vectors. This is the one operation that sends a large amount of card text, and it happens when you start it and not otherwise. The vectors come back and are stored on your machine.

When you sign in or manage your subscription. Your email address, and a device identifier so the account can enforce its device limit.

Nothing while you are simply reviewing. Showing a card, answering it and moving on involve no network traffic at all.

What never leaves

• Your collection as a whole. There is no upload, sync or backup of it here.
• The Neighbours index and the style profile. Both are computed locally and written to the add-on's user_files folder.
• Reference notes you import. They are parsed and stored on your machine; only the few thousand characters actually retrieved for a given question travel with that request.
• Your Anki review history, scheduling, and deck structure.

Where it goes after our server

Nexora's server does not do the processing itself. It passes your request on to the provider's server and streams the answer back. That provider handles the text under its own terms, which govern retention and whether it may be used for training, and we cannot make promises on its behalf. The add-on's own privacy notice carries the full detail, and if you need to know which provider handles your requests, ask us at support@nexoracards.app.

What the server stores

Per request, an accounting line: your email, which action ran, which model and provider served it, how many tokens went in and out, what it cost, whether it succeeded, and, if it failed, the error message. The card text is not in that row. It is used to answer the request and then it is gone; it is not written to the database.

Per account: your email address, a hash of your password (never the password), your plan and remaining credits, and identifiers for the devices you have signed in on. Session tokens are stored hashed, so a copy of the database is not a set of working logins.

Nothing for payment. Paddle handles billing as merchant of record. Card numbers never reach our server, and we could not see them if we wanted to.

Why we hold it

• Your account. To give you the service you asked for and to enforce the plan you are on.
• The accounting lines. To count your allowance honestly, to work out what the service costs us, and to find faults. We keep them while the account exists.
• Nothing for advertising. We do not sell your data, and there are no trackers of any kind in the add-on or on this site.

Your rights over it

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Email support@nexoracards.app from the address on the account and we will do it. Deleting the account removes it and its accounting rows.

Removing the add-on from Anki deletes everything held locally, including the index and the style profile. Those live in user_files and go with it.

If you are in the UK or the EU, you also have the right to complain to your data protection authority.

This website

These pages run no analytics and no tracking of any kind.

Exactly one page on this site runs a script, and it is the checkout. Paddle, who take the payment, provide a script that opens the payment window; without it there is nothing to pay on. It loads only on the checkout page, only when you are on your way to paying, and it is Paddle's code doing Paddle's job. Every other page here -- everything you can read without buying anything -- is built from forms and links with no script at all.

The only other thing loaded from elsewhere is the typeface, from Google Fonts.

One cookie exists, and only after you sign in: a session cookie named nexora_session that says which account this browser is signed into. It is what makes the account page possible at all. It holds a random token and nothing else -- not your address, not your plan, nothing readable. It is marked HttpOnly (no script can read it), Secure (it never travels over plain http) and SameSite=Strict (it is not sent when another site links to us, which is what stops another site acting as you). Signing out deletes it, and it expires on its own after two weeks.

No cookie is set before you sign in, and there is no cookie banner because there is nothing to consent to: a sign-in cookie is strictly necessary for the thing you asked for.

The server keeps ordinary request logs for a short period to diagnose faults.

Changes

If what is sent or kept ever changes materially, this page changes with it in the same release, and the change is named in the release notes rather than left to be discovered here.

Asking about any of this

support@nexoracards.app. If something here does not match what you observe the add-on doing, that is a bug in this page and worth reporting as one.