Trust

Security at Nvoka

Prompts carry how your team works. Here's how Nvoka keeps them private, and what stays under your control.

Access rules live in the database

Every app table has row-level security, so the database itself checks who is asking before it returns or changes a single prompt. A bug in the app can't hand your library to someone else.

Team prompts stay in the team

Owners, admins, editors and viewers, per workspace. Removing someone ends their access at once, and team prompts can't be shared by public link or published to the Public Library.

Encrypted in transit and at rest

Every connection uses HTTPS. Data is stored in Supabase's managed Postgres, encrypted at rest, and the app is served from Cloudflare's network.

Sign-in you already trust

Sign in with Google, Apple or Microsoft, whose passwords Nvoka never sees, or with an email and password that is stored hashed. Sessions are short-lived tokens that renew themselves.

Payments by Stripe

Checkout runs on Stripe, a PCI DSS Level 1 certified processor, through Link. Card numbers never touch Nvoka's servers.

Your data, under your control

Download your whole library any time, restore deleted prompts from the Trash for 30 days, and delete your account and personal data yourself in Settings.

Where Nvoka runs

Nvoka is built and hosted on Lovable, which holds ISO/IEC 27001:2022 certification and has completed SOC 2 Type I and Type II audits. These are Lovable's certifications for its platform, not Nvoka's. Lovable's trust center

Lovable
Builds and hosts the app, and runs a security scan each time a new version is published.
Lovable Cloud, on Supabase
Keeps your data in a managed Postgres database, encrypted at rest, with daily backups.
Cloudflare
Serves every page over HTTPS from its global network, with protection against attacks that try to flood the site.
Stripe
Runs checkout as a PCI DSS Level 1 processor, so card numbers never touch Nvoka's servers.

How we build

  • Every change is reviewed and runs through hundreds of automated tests before it ships. Changes to access rules come with database tests that try to reach other people's data and must be refused.
  • Secret keys live only on the server. The browser gets nothing it could use to reach another account.
  • Capture devices (the extension, iPhone app and Shortcut) each get their own token, stored hashed and revocable in Settings. Saved page addresses drop anything after "?" or "#".
  • AI assistants you connect, such as ChatGPT or Claude, sign in with your Nvoka account and an approval screen on nvoka.com. They can find, read and save the prompts you can see, back up artifacts and bookmark chats only you can see. They never edit or delete anything, within per-person request limits. Disconnect any assistant in Settings.
  • AI features send text to Google's Gemini models only when you use them. Nvoka doesn't train AI models on your prompts.

Report a vulnerability

Found something? Email ryan@nvoka.com with the details. We reply quickly and credit good-faith research. Please don't access, change or keep other people's data while testing.

Security reviews for your company

Need a questionnaire answered or have questions about how Nvoka fits your policies? We're happy to walk through it.

Talk to us