Skip to content

Draft, under legal review.

Privacy notice

What TradeNodus stores, where it is kept, who can read it and how you delete it, in plain language.

Last updated

Who we are

TradeNodus is run by Agrinodus. [Legal entity, registered address and registration number to be added before publication.] For anything in this notice, write to hello@tradenodus.com.

This notice covers two things: this website, including the request-access form, and the TradeNodus service that invited firms use (the bridge, its web app, the Chrome extension and the connection to your AI assistant).

This website and access requests

This website sets no cookies and runs no analytics or advertising scripts. It is hosted by Vercel, which processes the technical details of each request (such as IP address and browser) to deliver the pages.

When you request access, we receive the name, firm, work email, what you trade and any message you enter. The form sends them to us by email through Resend, an email delivery service. We use them only to reply to you and to set up a pilot, and we delete them when they are no longer needed for that, or sooner if you ask. To limit abuse, the site counts requests per IP address for a few minutes in memory; that count is not stored.

What the bridge stores

A bridge is linked to your WhatsApp account as a read-only linked device. It stores the following, and nothing else:

Linked device
The keys WhatsApp gives a linked device, so the bridge can stay connected.
Chat list
For every chat in the account: its name, whether it is a group, the number of messages and the last activity.
Messages
Only for chats you tick: sender, time and text. Media is stored as a short note, such as “[image]”, with its caption; the files themselves are not downloaded.
Activity log
Events such as connected, logged out or linking started, and each assistant call: the key or sign-in it used, the tool, a hash of its arguments, the chats touched and the number of results. Never message text.
People
The email address and name of each person invited to or approved for your firm’s bridge, and when they last signed in.
Keys and sign-ins
Assistant sign-ins (which app you allowed, when, and when it was last used), assistant and extension keys, and browser sessions. Keys are stored as hashes and shown only once.

Messages in chats you have not ticked are not stored. The bridge stores what its linked device receives after linking, plus the recent history your phone sends to a new linked device.

Where it is kept and how it is protected

  • Location. Hosted bridges run on servers at Infomaniak in Switzerland. Each firm has its own bridge instance and its own database file.
  • At rest. The database file is encrypted with Adiantum, and the key is kept outside the data directory. This protects the file and its backups, not a running process.
  • In transit. WhatsApp to the bridge uses WhatsApp’s end-to-end encryption, with the bridge as one endpoint. Your browser, the extension and your assistant reach the bridge over TLS. This is not end-to-end between your browser and your phone: the server shows you your chats and runs search, so it handles the text in plain form.

Who can read it

  • People your firm lets in. The normal way in is email sign-in with approval: colleagues open your firm’s address and sign in with their work email, and someone who is not a member yet gets in only once an approver at your firm lets them in. The access code your firm receives at setup also signs in, but it is the bootstrap and emergency path, not the everyday way in. Everyone signed in to your firm’s bridge sees its linked accounts and stored chats.
  • Assistants and the extension, through a sign-in or a key. They see ticked chats only, and only what they ask for. A revoked sign-in or key stops working at once.
  • Us, as the operator. Whoever operates the server can technically read what the bridge holds while it runs. We do not read your chats. We access stored data only when it is needed to keep the service running, when you ask us to, or when the law requires it. If you need to rule this out, you can run the same bridge on your own machine or server.

Your AI assistant

The bridge calls no AI provider by itself. When you ask your assistant a question, it requests results from the bridge over MCP: chat names and the text of the messages it asks for, from ticked chats only, up to 1 MB per call. Those results then go to the provider you chose (for example Anthropic for Claude, or OpenAI for Codex), under your own plan and that provider’s terms and privacy policy. We are not a party to that relationship and do not receive your conversations with the assistant.

The Chrome extension

The extension stores only your bridge’s address, its key and its own settings, in your browser. Message text stays in memory and is gone when the page reloads. It talks only to your bridge; links to assistants open only when you click them.

Deleting

Untick a chat
Its stored messages are deleted and new ones are no longer stored.
Log out an account
The device is unlinked and the account’s chats and messages are deleted from the bridge. The activity log, which has no message content, is kept.
Unlink on the phone
The bridge is cut off at once. Its stored chats stay until you remove the account on the bridge.
Revoke a sign-in or key
It stops working immediately.
Leave the service
When your firm stops using TradeNodus, we delete its bridge instance and database, including backups [within a period to be confirmed].

Third parties

Infomaniak
Hosts the bridges, in Switzerland.
Your AI provider
The assistant you choose, such as Anthropic or OpenAI, receives what your assistant requests, under your agreement with it.
Resend
Delivers access-request emails from this website to us.
Email delivery
Sends your bridge’s sign-in links and approval requests to the people involved. [Provider to be named.]
Vercel
Hosts this website.
Google, Microsoft
Only if your firm switches on “Continue with Google” or “Continue with Microsoft”: they confirm who you are when you sign in to the bridge.
WhatsApp (Meta)
The bridge connects to WhatsApp as a linked device of your account; WhatsApp’s own terms and privacy policy apply to your account.

We do not sell personal data and do not use your chats to train any model.

Your rights and the law

This notice is governed by Swiss law, in particular the Swiss Federal Act on Data Protection. Where the EU General Data Protection Regulation applies to you, you have the rights it gives as well. You can ask what we hold about you, have it corrected or deleted, and object to its use, by writing to hello@tradenodus.com. You can also complain to the Swiss Federal Data Protection and Information Commissioner.

The chats you tick contain messages from other people. Your firm decides which chats to store and is responsible for having a lawful basis to do so; see the terms.

Changes

When this notice changes, we update the date at the top and tell invited firms about material changes by email.