Security

How BuildNod protects your projects, your stakeholders and their approvals.

Summary

Your requirements and prototypes describe products that haven't been built yet, so we treat them as confidential. Projects are visible only to the people who created them and their team. Approvals are confirmed with a code sent to each approver's email and recorded in a permanent activity log. We never sell your information or use it for ads.

Where your data lives

  • Accounts, projects, comments, approvals and the activity log are stored in a Supabase database.
  • The BuildNod server runs on Render and the website on Vercel. All traffic uses encrypted (HTTPS) connections.
  • Your browser never connects to the database directly. Only the BuildNod server can, using a secret key that is never sent to browsers.
  • Our providers may store or process information outside your country, including in the United States.

Accounts and sign-in

  • Passwords are stored only as bcrypt hashes. Nobody at BuildNod can read your password.
  • Email confirmation and password-reset codes are stored only as hashes, expire after a short time and allow a limited number of tries.
  • Repeated sign-in, sign-up and code attempts are rate-limited to slow down guessing.
  • Sign-in sessions expire. “Remember me” keeps you signed in for up to 30 days.

Who can see a project

  • A project can be opened only by the person who created it and, on the Team plan, members of their team. Only the creator or the team owner can delete it.
  • Stakeholders see a project only through its review link, which contains a long random code that can't be guessed.
  • You can protect a review link with a password (stored only as a hash) and an expiry date. Moving a project back to Draft or approving it closes the link.
  • Projects that are in review or approved are locked, so what stakeholders approve can't change underneath them.

Verified approvals

  • Only the approvers you list can approve or request changes.
  • Each approver confirms with a 6-digit code sent to their email. Codes are stored only as hashes, expire after 10 minutes and allow 5 tries.
  • A project is marked Approved only when every listed approver has approved.
  • Every publish, comment, approval and change is written to a permanent activity log with who did it and when. Entries can't be edited or deleted, and you can download them as a CSV file.

AI and your content

To generate screens, questions, test scenarios and gap analyses, BuildNod sends the content you provide to our AI provider,Anthropic. Under Anthropic's commercial terms, this content is not used to train its models. BuildNod sends only what is needed for the feature you use.

Payments

Payments for the Team plan are handled by Stripe. You enter card details on Stripe's own pages; BuildNod never sees or stores your card number.

Error monitoring

When something breaks, BuildNod can report the error to Sentry so we can fix it quickly. Before a report is sent, passwords, sign-in details, codes and the content of your requests are removed.

Deleting your data

Deleting a project permanently removes its screens, versions, comments, approvals and review link. The activity log keeps a record that it was deleted. To close your account and delete your data, email us at hello@buildnod.com.

What we don’t have yet

BuildNod doesn't yet hold a formal security certification such as SOC 2, and it doesn't offer single sign-on (SSO). If your company needs these, tell us — it helps us decide what to build next.

Report a security issue

If you think you've found a security problem, email us at hello@buildnod.com. We'll look into it straight away.