Privacy · updated October 17, 2026

How Teranode Review handles submitted content.

A review necessarily sends the submitted answer and relevant context to external model providers. This notice explains that path, what Teranode stores for workbench, account, and paid Review flows, and the choices that change retention.

Do not submit client identifiers, account numbers, addresses, contact details, government identifiers, credentials, privileged material, or information your firm has not approved for this workflow.

What the operator submits.

The workbench accepts an AI-generated or human-authored source, the original decision question, recommendation, optional facts or constraints, and a confirmation that no client-identifying information is present. An AI source includes its model vendor and model. A human source includes the originating team or role. Teranode applies an identifier-detection backstop before inference, but the operator and firm remain responsible for the submission.

No advertising trackers.

Teranode does not load advertising pixels or trackers from ad networks and does not ask for advertising consent. Site visits are counted with Vercel Web Analytics, which does not use cookies and reports aggregated statistics. Links in our printed materials may include a campaign tag in the web address.

Who receives the review content.

The browser sends the input to a Teranode endpoint hosted on Vercel. The server constructs a separate prompt for each assigned review lens and sends it through OpenRouter to the selected model provider. When the source is AI-generated, its model vendor is excluded from those assignments. A human-authored source is not attributed to a model vendor.

The request sets OpenRouter's per-request ZDR and data-collection-deny controls. OpenRouter documents those controls as routing only to endpoints covered by its Zero Data Retention policy and providers that do not collect user data; handling remains governed by OpenRouter's terms. These are routing-policy controls; Teranode does not operate the routing or inference providers' infrastructure. Current subprocessors are listed on Trust.

Browser-returned reviews without account purchase.

For the standard workbench path that is not tied to a paid Review credit account, the review endpoint does not write the submitted question, answer, context, or completed review to the Teranode firm record database. It returns the structured review and a server-issued integrity token to the browser. Infrastructure providers may process request metadata required to operate and protect their services. On the invite-only firm beta and firm API paths, Teranode keeps the submitted question, answer, context, and completed review for up to 72 hours so the reviewer can open the findings; after that the link stops working and the copy is deleted on a rolling basis. It is not filed as a firm record.

Closing the browser before attestation may remove the working copy from the interface. Teranode does not promise browser recovery.

The operator may download an unattested local draft containing the source input, issued review and integrity token, work-in-progress dispositions, and reviewer fields. Downloading a draft does not file it or store it in Teranode's firm record database. The operator and firm are responsible for handling the downloaded file under their policies.

What Teranode stores when you grade a case

When you grade a case at teranode.ai/grade, Teranode stores your answers, the optional role and years in practice you pick, and any note you write, without your name. If you leave an email and tick the consent box, Teranode stores it separately from your answers and uses it only to send you the results. It is never sold and never used for advertising.

What is stored when you connect or buy a credit.

When you create a Review account or connect a host chatbot to the consumer Review path, Teranode stores account identifiers needed to operate the service, including a verified email address, host connection bindings, promotional and purchased credit balances, and a content-free credit ledger (grants, holds, consumption, releases). Signing in is not a subscription: Teranode writes to that address only about your own account and Reviews. Occasional notes from the founder are a separate opt-in you choose at sign-in, kept on their own list with an unsubscribe link in every message, never sold and never used for advertising.

A paid or credit-backed Review persists server-side state required to prepare, authorize, run, and retrieve that Review. That can include a de-identified prepared packet, execution state, cost and provider call metadata, integrity material, and the issued findings for account retrieval. This is separate from the optional firm archive attestation path described below.

Account Reviews are kept so you can reopen them, until you ask us to delete them. Write to dan@teranode.ai from the email on your account and we delete your Reviews within 7 days. After we delete your Reviews, encrypted backups held by our database provider expire within 30 days. We keep the content-free credit ledger and payment references for accounting, and one-way fingerprints that cannot recreate your content, for integrity checks.

Self-serve credit purchases are processed by Stripe. Stripe receives payment details and billing metadata according to its terms. Teranode stores payment references needed for fulfillment and reconciliation (for example Checkout session and payment identifiers), not your full card number. Refund and dispute events from Stripe may update credit and reconciliation state.

What Teranode gets from Google, and what it does with it.

You can sign in to Teranode with your Google account instead of an emailed code. If you choose Continue with Google, Google shares your name, email address, profile picture, whether Google has confirmed that email address, and an account number Google uses for you. Teranode asks Google for nothing else. It cannot see your Google password, mail, contacts, files, or calendar.

Teranode uses this information only to sign you in. It finds your Teranode account by email address, or opens one if you are new. It also recognizes the same Google account the next time you sign in. It is not used for advertising, and Teranode does not sell it.

Teranode keeps your email address on your Teranode account. It also keeps a scrambled, one-way form of your Google account number, and the dates you first and last signed in with Google. It does not keep your name, your picture, or any Google sign-in token.

Teranode does not share this information with anyone. The companies that host the site and its database (Vercel and Neon) process it only to run the service. To remove the Google link or close your account, write to privacy@teranode.ai.

What is sent when a reviewer creates the record.

Attestation sends the complete review, dispositions and any written bases, reviewer name and role, optional registration identifier, final decision, and integrity token to the server. The server checks the payload and constructs a timestamped review record with the human-entered attestation. Reviewer name, role, and optional registration identifier are supplied by the reviewer or firm; Teranode does not independently verify them. When the reviewer is signed in as a firm member, the server also adds the work email used to sign in, the firm name, the firm-assigned role, and the sign-in method, taken from the sign-in rather than from the browser. The SHA-256 fingerprint is a comparison value, not a digital signature.

Without an authenticated firm archive session, the record is returned without archive storage. The operator may print or download that copy, but Teranode does not store it in the firm record database.

An authenticated firm archive stores the complete record.

When an authenticated firm creates the attestation, Teranode stores the complete record in a firm-scoped database. That includes the source question and answer, supplied context, source and reviewer provenance, findings, limitations, reviewer questions, dispositions, reviewer identity fields, final decision, timestamps, and fingerprint.

If a firm uses member sign-in, Teranode also stores each member's work email, firm-assigned role and status, when they were invited, activated, or removed, who invited or removed them (Teranode or the firm's compliance officer), and a sign-in log recording which member, or the firm's legacy archive link, signed in to which firm, when, and by what method. The log contains no sign-in codes or session tokens. Removed members are marked removed rather than deleted.

If a member creates an AI connection key, Teranode stores a one-way hash of the key and its first characters, never the key itself; the member's work email and firm name on the key; when it was created, last used, and switched off; the member's daily run limit and runs that day; a usage log of each run made with it (time, run type and tier, topic area when one is given, which optional review steps ran, status, duration, an estimated cost and how it was funded, a short error code if it failed, and a request identifier); and a log of key creations, switch-offs, and limit changes recording who made each (the member, the firm's compliance officer, or Teranode). The firm's compliance officer can see a member's connection status, key prefix, dates, and runs, never the key.

The archive is a Teranode service copy and is not represented as the firm's required books-and-records system. Retention, deletion, export, and contractual requirements are addressed with the firm before production use.

Hosting, models, and payments process operational data.

The site uses Vercel hosting, Analytics, and Speed Insights. These services may process device, network, page, performance, and request metadata according to their service configuration and terms. Teranode does not use this notice to claim that infrastructure logs contain no IP addresses or other operational identifiers.

Model inference is routed through OpenRouter to selected model providers as described above. Identity for consumer connect may use an OpenID provider (Auth0 or equivalent) configured for the Service. Credit checkout uses Stripe. See also Trust for the current control summary.

If there is a breach.

If we confirm a breach that affects your data, we notify you within 72 hours.

Ask about a record or this notice.

For a privacy request, identify the firm account or Review account email, review ID if any, and the action requested without sending the record contents by email. Write to privacy@teranode.ai or support@teranode.ai. Requests are evaluated against the applicable agreement and law. To delete your account Reviews, write to dan@teranode.ai as described above; we delete them within 7 days.

This notice changes when the data path changes.

Material changes to providers, content retention, or archive storage will be reflected in this notice and its updated date. Firms under contract receive any notice required by their agreement.

Talk to Teranode Support.

If you need help understanding Teranode, call 1-888-837-6950 (888-TER-6950). What it is, how to connect it to ChatGPT, Claude, or Grok, the privacy statement and how the product implements it, and who we are. That is what this line is for. An AI voice assistant answers it. To reach Dan, email dan@teranode.ai.

A Review of a specific case still starts at teranode.ai/connect. The line is not for walking through a pasted case. Findings are not advice.

Read the implemented controls on Securityand the end-to-end data path on Trust.