Skip to content

Draft

Privacy Policy

What NodNod collects, why, who helps us run it, how long we keep it, and how you get it deleted.

DRAFT, not yet approved. This page is a working draft for review. It is not in force and is not our final terms.

Draft of 2026-11-07

Who this covers

This policy covers [PLACEHOLDER: company legal name and entity type, e.g. "NodNod, a product of ..., Inc."] and nodnod.ai. It covers account owners, the AI agents they let use NodNod, visitors who talk with a Nod on a NodNod page or an embedded page, and people in a meeting a Nod joins. Questions: [PLACEHOLDER: contact address, e.g. legal@nodnod.ai or privacy@nodnod.ai].

What we collect

  • Account facts: the owner’s email address, display name and handle; whether the email is confirmed; API keys (we store only a hash of each key).
  • What you build: each Nod’s name, instructions, knowledge, chosen face, voice and parts, and its public page settings.
  • Conversations: what people say to a Nod and what it says back, as text transcripts. To hear people, the Nod receives live audio and turns it into text.
  • Meetings: when a Nod joins a meeting through a meeting service, that service sends us the meeting’s audio and who joined and left.
  • Money: credit grants, top ups, what each session used and cost. Card details go to our payment provider, not to us.
  • Technical records: IP address, browser, times, errors and audit records of important actions (for example a key revoked or an account put on hold).
  • Waitlist: the email address you give us.

Audio and recordings

A Nod listens in real time so it can answer. We do not keep audio recordings of rooms or pages after the conversation. [PLACEHOLDER: confirm no audio is kept by any provider beyond processing; today the meeting service is asked to keep media for 1 hour at most, and our code also deletes it when the meeting ends.]

We keep text transcripts of conversations with a Nod so the owner can read them. [PLACEHOLDER: transcript retention period, e.g. 90 days, then deleted.]

If you send a Nod into a meeting, you must tell the people there that an AI is present and listening, and get any consent your state or theirs requires. Some US states require everyone’s consent to record or listen.

Visitors to a Nod’s page

When you talk with a Nod on its page, the Nod’s owner can read the transcript of that conversation. Do not share private information with a Nod you do not trust.

A public Nod runs with a limited set of abilities and is tested against attempts to make it reveal its owner’s private information before it can go public. It cannot use its owner’s tools while talking with you.

We limit how long and how often a visitor may talk, to prevent abuse. We use a browser session id for that. [PLACEHOLDER: list any cookies or local storage, and whether any analytics run on nodnod.ai.]

Why we use it

  • to run the Nods you build and the conversations they have;
  • to bill by the minute and stop at zero;
  • to keep NodNod safe: abuse limits, holds, security checks and audit records;
  • to send the owner the emails the service needs (sign-in codes, confirmations, notices);
  • to meet the law.

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not use conversations to train AI models. [PLACEHOLDER: confirm each AI provider’s terms for our account match this.]

Who helps us run NodNod

These companies process data for us, only to provide their part of the service:

  • Supabase: our database and sign in.
  • Vercel: hosting for the website and the API.
  • Modal: the computers that run a Nod while it talks (and RunPod, if we switch).
  • LiveKit: the live audio and video rooms.
  • Anthropic, and when an owner chooses them, OpenAI, Google and xAI: the AI models that write a Nod’s answers.
  • AssemblyAI: turning speech into text.
  • Google and OpenAI voices, when an owner chooses them: turning text into speech. The default voice runs on our own computers.
  • Anam, when an owner chooses that face: the animated face.
  • Recall.ai: joining video meetings (Zoom, Teams, Webex) for a Nod.
  • Resend: sending email.
  • Stripe: taking payments.

[PLACEHOLDER: confirm a data processing agreement is in place with each, and where each stores data. Today our Recall account runs in the US (us-west-2).]

Every provider we use or may use, and what each one may see

How long we keep it

  • Account and Nod details: while the account is open. [PLACEHOLDER: how long after an account is closed.]
  • Transcripts: [PLACEHOLDER: e.g. 90 days].
  • Money records: as long as tax and accounting law requires [PLACEHOLDER: e.g. 7 years].
  • Audit and security records: [PLACEHOLDER: e.g. 1 year].
  • Meeting media at the meeting service: at most 1 hour, and deleted when the meeting ends.

Your choices and rights

An owner can read their own account, Nods, sessions and transcripts in their account page, revoke keys, and put their account on hold.

To get a copy of your data, correct it or delete it, write to [PLACEHOLDER: contact address, e.g. legal@nodnod.ai or privacy@nodnod.ai]. [PLACEHOLDER: there is no self-serve delete yet; say how long a request takes, e.g. 30 days.] If you are a visitor or a meeting participant, write to us with the page or meeting and the time, and we will work with the owner.

Depending on your state (for example California, Colorado, Connecticut, Virginia or Texas), you may have rights to know, access, correct, delete and port your personal information, and to opt out of its sale or targeted advertising. We do neither of the last two. We will not treat you differently for using your rights. [PLACEHOLDER: counsel to confirm which state laws apply at our size.]

Children

NodNod is not for children under 13, and owners must be adults. We do not knowingly collect personal information from children under 13. If you think a child has used NodNod, write to us and we will delete it.

Security

Each account’s data is separated in the database by owner, and only the server reads across accounts for NodNod staff, with every staff read recorded. Keys are stored as hashes. No system is perfectly secure; if a breach affects you, we will tell you as the law requires.

Changes

We will post changes here with a new date, and email owners about material changes before they apply.

Contact: [PLACEHOLDER: contact address, e.g. legal@nodnod.ai or privacy@nodnod.ai], [PLACEHOLDER: postal address for legal notices].

Privacy Policy (draft) · NodNod