Trust
Security at ReviewNudger
Plain answers to the questions a business owner asks before handing over a customer list.
Last updated: November 2, 2026
Encrypted when sent and when stored
Every connection is encrypted. The database is encrypted while stored. Logins for your connected apps get their own extra encryption before we store them.
Verified texting numbers
Texts send from the toll-free number set up for your business after carrier approval, usually about 3 business days. Email can cover requests until then. See pricing for full terms.
Export or delete any time
Download everything as a ZIP of spreadsheets. Or delete the account yourself in Settings, and its records and files go with it. If you cancel and ask us to delete it instead, we do that within 30 days.
No review gating, ever
Every customer gets the same ask and the same public review link, including unhappy ones. That is what the FTC and Google require.
What we protect
Two kinds of data pass through ReviewNudger. The first is yours: your account, your team, your billing status, your Google reviews, and your request settings. The second belongs to your customers: the name, phone number, or email address we send the request to, and the job or payment that triggered it. We treat both as confidential and keep them to your account. We never sell or share either, or use it for anything other than running the service for you.
Encryption
Every connection uses HTTPS, the padlock in your browser. Browsers are told not to fall back to an unencrypted connection. Our own connections to the database are encrypted too. The database and stored files are encrypted while stored.
Some logins and keys get their own strong encryption before they are stored. That covers the logins for your connected apps and your texting account. It also covers the signature keys some apps use to prove a message came from them. The key that unlocks them is kept in our hosting provider's encrypted store, never in our code. A secret you create is shown to you once and never again. The sign-in codes our own integrations issue are stored in a scrambled form that cannot be read back. The technical details are lower on this page.
Who can see your data
ReviewNudger is founder-run. Access to live customer data is limited to the founder. Every outside service we use has its own login, kept in a password manager with two-step sign-in turned on. Any contractor who needs access gets the least access that does the job, for a set period. They are removed when the work ends.
Inside the app, every lookup is limited to your account. A database rule means only our server can read business data. Team roles are owner, admin, and replier. Only the owner can handle billing or delete the account. Some actions are written to an activity log that cannot be edited: team changes, plan changes made in the app, disconnecting most connected apps, and edits to your message templates.
Your texting number is yours
Each account gets its own Twilio texting account and toll-free number, registered under its business name. Texts can send from the toll-free number set up for your business only after carrier approval, which usually takes about 3 business days. Until then, email requests can send when your sending rules allow them.
The free trial includes unlimited texts and emails. Texts send from the toll-free number set up for your business once carriers approve it, usually in about 3 business days.
STOP and HELP replies are handled by the phone carriers and recorded on the customer. Other rules apply automatically, however a request was started: quiet hours, a waiting period between asks to the same customer, do-not-contact marks, and unsubscribe links in every email.
Every customer gets the same ask
Every customer gets the same review request. When a location turns on the optional pre-screen, unhappy customers still see the public Google review link. We do not filter, suppress, or delay negative reviews, and we never will. The FTC's rule on consumer reviews and Google's review policies require this. It also keeps your listing safe.
Connected apps
Connected apps are read-only. We take only what a request needs: the customer's name and contact details, the job or payment number, amount, currency, and completion time. Nothing is written back to your payment or scheduling software beyond what it takes to connect. Data from one business's connected app is never combined with another's.
Before anything is stored, we check that each notice from a connected app really came from that app. A notice that fails the check is thrown out. When you disconnect Square or Clover, the data that came from them is deleted, as those companies require. We keep a record that the deletion happened.
AI features
Reply suggestions and review protection checks send OpenAI only public review content: the review text, star rating, reviewer display name, and your business name. Your customer list and anything from a connected app never leave ReviewNudger. We ask OpenAI not to store these requests. Under its terms, it may still keep them for up to 30 days to watch for abuse. It does not use them to train its AI. We never use your data to train any AI.
Texting registration check. Before you submit, we may send your business details, message text and public web page text to OpenAI. It points out anything that doesn't match. Repeated unchanged details can reuse a recent result. Your registration number, representative contact details and images are not included. The check does not verify your identity, submit a registration or guarantee approval.
Your data stays yours
The account owner can export everything at any time as a ZIP of spreadsheets. Deleting the account in Settings permanently removes every record we hold for it, including the activity log and uploaded files. It also releases your Twilio number and account, and cancels billing. You can also cancel and ask for deletion by emailing support@reviewnudger.com. We delete your data within 30 days, except where the law requires us to keep it.
Where it runs
ReviewNudger runs on Vercel. The database, sign-in, and file storage are managed by Supabase on Amazon Web Services in the eastern United States. We run no servers of our own. Software updates, physical security, and network defense come from those companies, under their own audits. Vercel and Supabase each publish SOC 2 security audit reports. ReviewNudger itself has not yet been independently audited. We will say so here when that changes.
Backups are automatic and run by those companies. We log every failed send and broken connection. The founder gets a daily email about them. If an app loses access, we email you how to fix it. Separate automatic checks watch our public pages and important background work. Error reports leave out customer content. Identifying details are removed from any web address in them.
How we build
Every change goes through a formal change request. It must pass our full set of automatic checks before it goes live. Nothing goes live from someone's own computer. We get alerts about security problems in outside code we use. Serious ones are looked at within 7 days and fixed within 30. Passwords and keys never go in our code. Development uses its own databases with no live customer data.
If something goes wrong
A suspected exposure is treated as an incident. Affected passwords and keys are changed and the affected part of the service is paused within 24 hours of confirmation. If an incident touches your data, we tell you within 72 hours what happened, what data was involved, and what we did about it. We write up the cause and the fix within 14 days.
Who processes customer data
- VercelHosting the app, running scheduled work, and storing our encrypted keys
- Supabase (on AWS, us-east-1)Database, sign-in, and file storage, all encrypted while stored
- TwilioText delivery from a separate Twilio account and toll-free number for your business, plus the paperwork for approval from the phone companies
- Microsoft ClarityMasked session recordings and heatmaps under the existing analytics permission. See our privacy policy for details.
- ResendEmail delivery for review requests and account mail
- GoogleReading reviews and posting replies for your connected Google Business Profile
- OpenAIReply suggestions, review protection checks, and the optional check of your texting registration wording
- StripeSubscription billing on a checkout run by Stripe. Your card details never reach us
Your own connected apps (Square, Jobber, QuickBooks, and the rest) send us data with the permission you approve. We only read from them. Marketing and advertising tools see people who have not signed up yet, account owners and team members on our own updates list, and visitors and accounts that allowed tracking, never a customer record. The privacy policy lists them.
Technical details for your IT person
The same answers in the terms partners and security questionnaires ask for.
Encryption
- HTTPS everywhere, the database encrypted at rest, and every connected-app credential encrypted with AES-256-GCM before it is stored.
- Every connection uses HTTPS, with HTTP Strict Transport Security for a year. Every page has a strict Content Security Policy. Database connections are TLS-only. The database and file storage are encrypted at rest by Supabase on AWS.
- Credentials for your connected apps, your Twilio subaccount, and webhook signing secrets are encrypted with AES-256-GCM before they are stored. The master key lives only in the hosting provider's encrypted environment store, never in source control. A secret you create is shown to you once and never again. The sign-in codes and tokens our own integrations issue are stored as hashes.
Access control
- We treat both as confidential and scope every read and write to your account. We never sell, share, or use either for anything other than running the service for you.
- ReviewNudger is founder-run. Production access is limited to the founder. Every provider account uses its own credentials from a password manager with multi-factor authentication turned on. Any contractor who needs access gets the narrowest role for a defined period. They are removed when the work ends.
- Inside the app, every query is scoped to your account. Postgres row-level security means only the server can read business data. Team roles are owner, admin, and replier. Billing and account deletion are owner-only, and operator actions recorded in the audit log cannot be edited.
SMS senders
- Each account gets its own Twilio subaccount and toll-free number, registered under its business identity.
- STOP and HELP replies are honored at the carrier layer and recorded on the customer. Other rules apply automatically, whichever way a request was started: quiet hours, a wait between asks to the same customer, do-not-contact marks, and unsubscribe links in every email.
Connected apps and webhooks
- Integrations are read-only and pull only what a request needs: the customer's name and contact details, the job or payment id, amount, currency, and completion time. Nothing is written back to your payment or scheduling software beyond the connection handshake. Data from one customer's connected app is never combined with another's.
- Before anything is stored, every webhook is checked against that provider's signature or token, using your connection's own secret. An unsigned or unknown delivery writes nothing. Provider-mandated deletions are honored. When you disconnect Square or Clover, the data that came from them is purged, and an audit receipt records it.
- Your own connected apps (Square, Jobber, QuickBooks, and the rest) send us data under the grant you approve. We only read from them. Marketing and advertising tools see pre-signup leads, account owners and team members on our own updates list, and consented visitor and account measurement, never a customer record.
AI providers
- Reply suggestions and review-policy screening send OpenAI only public review content: the review text, star rating, reviewer display name, and your business name. Your customer list and anything from a connected app never leave ReviewNudger. Requests are sent with provider-side storage turned off. Under OpenAI's API terms, inputs may be kept for up to 30 days for abuse monitoring. They are not used to train its models. We never use your data to train any model.
- SMS submission text review. When you open the Review step, and after you pause editing relevant details, selected business and messaging text and accessible public-page extracts may be sent to OpenAI. It suggests inconsistencies before you submit. Repeated unchanged details can reuse a recent result. Registration-number and representative-contact fields and images are not included. The review does not verify official identity, submit a registration or guarantee approval.
Export and deletion
- The account owner can export everything at any time as a ZIP of spreadsheets, one per business record. Deleting the account is a full hard delete of every row we hold for it, including the audit trail and uploaded files. It also releases your Twilio number and subaccount and cancels billing.
Hosting and monitoring
- ReviewNudger runs as serverless functions and scheduled jobs on Vercel. The database, sign-in, and file storage are managed by Supabase on AWS in us-east-1. We operate no servers of our own. Patching, physical security, and network defense come from those platforms under their own audits. Vercel and Supabase each publish SOC 2 reports. ReviewNudger itself has not yet been independently audited. We will say so here when that changes.
- Backups are provider-managed and automatic. Every failed send, failed inbound event, and broken connection is recorded as visible state. Each is reported to the founder in a daily digest. A revoked connection also emails you with the fix. Independent scheduled checks watch public entry points and critical background jobs. Runtime error reports use limited diagnostic context. They leave out customer content and remove identifiers from any page address.
Development and incidents
- Every change ships through a pull request and a full test, lint, build, and type-check gate. Nothing is deployed from a working copy. Dependency alerts are on for the repository. High or critical advisories are triaged within 7 days and fixed within 30. Secrets never enter source control. Local development uses its own databases with no production data.
- A suspected exposure is treated as an incident. Affected secrets are rotated and the affected endpoint or integration is paused within 24 hours of confirmation.
Service providers
- Vercel: Application hosting, scheduled jobs, and the encrypted secrets store
- Supabase (on AWS, us-east-1): Postgres database, sign-in, and file storage, all encrypted at rest
- Twilio: Text delivery from your own subaccount and toll-free number, plus carrier verification
- Google: Review sync and reply publishing for your connected Google Business Profile
- OpenAI: Reply suggestions, review-policy screening and advisory SMS submission text review
- Stripe: Subscription billing on Stripe-hosted checkout; card data never reaches us
Report a security issue
Found something? Email support@reviewnudger.com with “Security” in the subject line. The founder reads it and replies within two business days. Please don't access other customers' data or run tests that could disrupt the service while you look.
This page summarizes ReviewNudger LLC's written information security policy (version 1.0, effective August 18, 2026). It is reviewed at least once a year, after any incident, and whenever a control described here changes.
