Legal

Privacy Policy

Last updated

Notex is an open-source tool that lets you manage lists by voice or chat. This page describes — in plain language — what data it touches, where each piece goes, and what it never sees.

1. Who runs Notex

Notex is an open-source project published at github.com/mazoqui/notex. The hosted instance at app.notex.me is operated by the project's maintainer as a free, best-effort service. Anyone can also self-host the code on their own infrastructure; in that case the operator of that instance — not Notex's maintainer — controls the data.

2. What Notex collects

The hosted instance touches only the data needed to provide the service. Concretely:

2.1 Identity

  • Google account email. Provided by Google Sign-In. Used as the key to open your isolated per-user database on the server.
  • Session token. At sign-in, Notex validates your Google token against Google once, then issues its own session token. That session token is stored in your browser's localStorage and in the server database, and is sent as a Bearer credential on each request so you stay signed in across visits. The short-lived Google OAuth token is discarded after the exchange. Signing out revokes the session token on the server.

2.2 Settings you save

  • The LLM provider you choose (Gemini, OpenAI, or Anthropic), the model name, and the API key for that provider.
  • UI preferences (e.g. language).

These are saved in your per-user database on the Notex server, kept in a directory keyed by your email. Your API key is used only to authenticate the requests Notex forwards to the provider on your behalf.

2.3 Your prompts (in transit)

When you send a chat message, the text is forwarded to the LLM provider you chose, using your API key. Notex does not store the prompt or the model's response on its server. The chat thread you see in the browser is held in memory for the current session and is cleared when the page unloads or when you tap the "clear conversation" button.

2.4 Your lists

When the LLM decides an action is needed (add an item, mark all, delete a list, etc.), the Notex backend writes the change to your isolated per-user database on the server and pushes the update live to your other signed-in devices. Your list contents — item text and checked state — are therefore stored on the Notex server, keyed by your Google email, until you delete them (see §7). Lists you explicitly share are also readable by the members you invite.

3. What Notex does not collect

  • Microphone audio. Speech recognition runs entirely in your browser via the Web Speech API. Audio never leaves your device.
  • Conversation history on a Notex-owned database. Past chats are not retained between sessions on the server.
  • Behavioural analytics for advertising, marketing, or resale.
  • Profile information beyond your Google account email (no name, no picture, no contacts).
  • Payment information. Notex does not sell anything and does not process payments. Charges from your LLM provider go directly to your account with that provider.

4. Third parties involved

Using Notex involves these external services, in addition to Notex itself:

Google Identity Services
Used for "Sign in with Google" to confirm your email at sign-in. Notex validates the resulting token with Google once and then relies on its own session token. Subject to Google's privacy policy.
Your chosen LLM provider
Your text prompts and the model's replies pass through the provider you pick in Settings (Gemini, OpenAI, or Anthropic), authenticated with your own API key. Their handling is governed by their own privacy policy — review it directly: Google Gemini, OpenAI, Anthropic.
MQTT broker (optional, print-to-paper only)
If you use the optional Thermy companion to print lists, the backend publishes the plain-text list body to an MQTT topic keyed by your email. The hosted Notex instance ships this to localhost by default; nothing is published to a third-party broker unless an operator configures one. The published payload is the list contents that the print agent will hand to your local printer.

5. Cookies and local storage

Notex does not set tracking cookies. The web app uses your browser's localStorage to remember two values across reloads:

  • notex_google_token — the Notex session token for your current session.
  • notex_google_email — the email tied to that session.
  • notex_session_expires — when that session token expires.

Clearing your browser's storage for app.notex.me removes both. The website at notex.me (this marketing site) sets nothing.

6. Data retention

  • Settings & API keys persist in your per-user database on the server until you remove them or your account is deleted (see §7).
  • List contents live in your per-user database on the server and are retained until you delete them in the app or your account is deleted (see §7).
  • Chat threads are held in browser memory only and disappear when you close the tab or clear the conversation.
  • Server logs may contain request metadata (timestamp, route, status) for short-lived operational debugging. They are not sold, shared, or used for profiling.

7. Your choices and rights

  • See your data. Your Settings and lists are visible directly in the app. There is no hidden profile.
  • Change your data. Settings and list contents are editable in the app; changes are saved to your per-user database and synced to your devices.
  • Sign out / revoke. Signing out revokes your session token on the server. You can also remove Notex from your Google account at myaccount.google.com/permissions; note that your lists remain in your per-user database until you delete them.
  • Delete your account. To remove your per-user database — including your lists, settings, and API key — from the hosted instance, open an issue at github.com/mazoqui/notex/issues from the email tied to that account, or include enough information to identify it.

8. Security

Traffic to and from app.notex.me and api.notex.me is served over HTTPS. Your per-user database is isolated by Google email at the filesystem level. API keys are stored in plain form within that isolated database, which is why Notex strongly recommends generating keys scoped to this single purpose and rotating them if you suspect compromise.

No system is perfectly secure. Use API keys with the least privilege your provider allows, and review your provider's usage dashboards regularly.

9. Children

Notex is not directed to children under the age required to hold a Google account in their jurisdiction. If you believe a minor's data is in the hosted instance, contact us (§11) and we'll delete it.

10. Changes to this policy

Material changes will update the "last updated" date at the top of this page and, where reasonable, be announced in the project's GitHub repository. Continued use of the hosted service after a change constitutes acceptance of the updated policy.

11. Contact

Questions, data-access requests, or deletion requests: open an issue at github.com/mazoqui/notex/issues. Public issue trackers are not the right place for secrets — do not paste API keys, tokens, or sensitive personal data. If you need to share something private, say so in the issue and we'll arrange a channel.

See also: Terms of Service.