1. The short version
This summary is not a substitute for the sections below, but nothing below contradicts it.
- We collect what the product needs to work: your sign-in details, your restaurant’s brand voice settings, and the public reviews from the listings you connect.
- We do not sell your data, and we do not share it for advertising.
- No advertising trackers, and no ad networks. We use no third-party analytics today. If we ever add privacy-preserving usage measurement, it will never be an advertising product and we will say so here first. Your signed-in session is kept in your own browser’s local storage, not in a cookie we read.
- Review text goes to our AI provider to draft a reply. Your email address, password and account identifiers never do.
- Nothing is posted to your listing until you approve it.
2. What we collect
Account information
- Your email address and the display name you choose.
- A one-way bcrypt hash of your password. We never store the password itself and cannot recover it.
- Short-lived email verification codes, and hashed session refresh tokens.
If you sign in with Google
We receive your Google account identifier, your email address and your basic profile name from Google’s OpenID Connect endpoint. We store those three things so we can recognise you next time. We do not receive or store your Google password.
Business information
- Your restaurant or brand name, city, and the locations you add under it.
- Your brand voice settings: the default tone and the keywords you want replies to sound like.
- The public identifiers of the listings you connect, such as a Google Place ID or a Yelp business ID.
Review data
When you connect a listing we retrieve the reviews that are already public on that platform — the reviewer’s public display name, the star rating, the review text and its date. We do not receive reviewers’ email addresses, phone numbers or any contact details, because the platforms do not provide them.
Product activity
We record what happened to each reply so the history is auditable: the draft that was generated, any edits you made, who approved it, and when it was posted. Edits are stored as a before-and-after pair together with the instruction you gave, so that future drafts can be made to sound more like you.
3. What we never collect
- Payment card numbers. ReplyRush is free while it is in early access. If we introduce paid plans, card details will go directly to a payment processor — we would hold a billing record and the last four digits, never the full card number.
- Advertising trackers and ad-network pixels. The site loads no advertising script of any kind, and we do not build advertising profiles. It carries no third-party analytics today either.
- Your guests’ contact details. Review platforms do not give them to us and we do not ask for them.
- The contents of your Google account beyond what is described in section 6 — no Gmail, Drive, Calendar or Contacts access is requested or granted.
4. How we use it
We use what we collect only to run the product:
- To create your account, sign you in and keep your session valid.
- To send you a verification code when you sign up.
- To fetch the reviews from the listings you connect.
- To draft a reply in your tone, and to improve later drafts using the edits you have made.
- To post a reply to your listing — only after you approve it.
- To keep the product running and secure: diagnosing errors, and rate-limiting sign-in and email endpoints to prevent abuse.
We do not use your data to train any third party’s general-purpose AI model, and we do not use one customer’s brand voice to write another customer’s replies.
Aggregated statistics
We may produce aggregated, de-identified statistics across many restaurants — a median reply time by city, for example — and use or publish them. These never name you, never identify a reviewer, and cannot be traced back to an individual review. Information obtained from Google is excluded from this, and is used only for the purposes set out in section 6.
5. What goes to the AI model
Drafting is done by OpenAI. This is the section people most want a straight answer to, so here is exactly what a single request contains:
- Your restaurant’s name and city.
- Your brand voice keywords and the tone you selected.
- The reviewer’s first name only — the display name is truncated at the first space before it is sent.
- The star rating and the text of the public review.
- When rewriting, the current draft and the instruction you typed.
- A short sample of your recent edits, so the reply matches how you normally change things.
What is never sent: your email address, your password or its hash, your session tokens, your account or user identifiers, your billing details (we hold none), and the reviewer’s full name.
If the AI provider is unavailable, ReplyRush falls back to a locally-generated template reply and nothing is sent externally at all.
6. Google user data
ReplyRush uses Google APIs in two distinct ways, and they are worth keeping separate.
Signing in with Google
We request only your basic profile and email address. We use them to identify your ReplyRush account. Nothing else in your Google account is requested or accessible.
Connecting your Google Business Profile
If you connect your Business Profile, you grant ReplyRush permission to read the reviews on the locations you manage and to post replies to them on your behalf. We use that access for exactly two things: showing you your reviews, and posting the reply you approved. We never post without your approval, we never modify anything else on your listing, and we never read data from locations you have not connected.
ReplyRush’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect at any time from your ReplyRush settings, or revoke our access directly at myaccount.google.com/permissions. Revoking access stops all future reads and posts immediately.
7. Who else processes it
We use a small number of service providers. Each receives only what its job requires.
| Provider | What it does | What it receives |
|---|---|---|
| OpenAI | Drafts and rewrites replies | Exactly what section 5 lists — no account identifiers |
| Sign-in, and review data from listings you connect | Your sign-in request; the reply text you approved for posting | |
| Yelp | Review data from Yelp listings you connect | The public business identifier you provided |
| Resend | Sends your verification email | Your email address, display name and the code |
| Supabase | Hosts the database | Everything in section 2, stored at rest |
| Render | Runs the application server | Data in transit while a request is being handled |
| Vercel | Serves the website | Standard web request data such as IP address |
We may also disclose information where we are legally required to, or to protect the rights and safety of our users. We will tell you if that happens unless we are prohibited from doing so.
We may change or add providers as the product grows; this table lists the current set and we will update it here. If ReplyRush is ever acquired or merged, your data may transfer to the new owner — under this same policy, with notice to you beforehand, and with the chance to delete your account first. That is a transfer of a business, not a sale of your data, and we still will not sell it.
8. How it is protected
- All traffic to and from ReplyRush is encrypted with HTTPS.
- Passwords are stored only as bcrypt hashes. Session refresh tokens are stored hashed, and are revoked when you sign out.
- The database is not reachable from the public internet. It is reached only by the application server, and row-level security is enabled on every table as a second barrier.
- The API accepts browser requests only from our own domains, and sign-in, sign-up and email endpoints are rate limited.
- Every request for your data is checked against the locations your account actually has access to before it is answered.
No system is perfectly secure. If we discover a breach affecting your personal data, we will notify you promptly at the email address on your account.
9. Keeping and deleting
We keep your data for as long as your account exists. Verification codes expire within minutes; refresh tokens expire and are rotated.
Ask us to delete your account and we will delete it, along with your restaurants, locations, connected listings, imported reviews, drafts and edit history. Email privacy@replyrush.org and we will action it within 30 days. Replies already published to a public listing are outside our control once posted — those must be removed on the platform itself.
Deleted data can persist in encrypted backups for up to 30 further days before those roll off, and we may keep the minimum needed to meet a legal obligation or resolve a dispute. Neither is used to run the product.
10. Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict how we use it, and to complain to your local data protection authority. We honour these requests regardless of where you live. Email privacy@replyrush.org and we will respond within 30 days. We will not charge you or degrade your service for exercising any of them.
ReplyRush is operated from the United States and your data is processed there and by the providers listed in section 7.
11. Children
ReplyRush is a tool for businesses and is not directed at anyone under 16. We do not knowingly collect data from children. If you believe a child has given us data, email us and we will delete it.
12. Changes
If we change this policy in a way that materially affects how we handle your data, we will update the date at the top of this page and email account holders before the change takes effect.
13. Contact
ReplyRush — privacy@replyrush.org. See also our terms of service.