Privacy Policy
How Review Agent by ClearStack accesses, uses, stores, shares and deletes personal information, including data from Google Business Profile, in line with South Africa's Protection of Personal Information Act, 4 of 2013 (POPIA).
Effective date: 19 November 2026 · Last updated: 19 November 2026
1. Who we are
Review Agent is a service built and run by ClearStack ("ClearStack", "we", "us"), a South African software company. Review Agent helps restaurants read their Google reviews, draft replies, approve them and post them to Google, and alerts their team to urgent reviews.
Email: support@clearstack.co.za
Website: reviews.clearstack.co.za
Information Officer. POPIA requires us to appoint an Information Officer who is accountable for compliance. You can reach ours at support@clearstack.co.za. Mark your message "For the attention of the Information Officer".
2. Our role for each kind of data
- Review data (the reviews, reviewer names and replies of a restaurant that uses Review Agent) is processed on behalf of that restaurant. For this data the restaurant is the Responsible Party and we act as its Operator under POPIA, processing it only to provide the service the restaurant asked for.
- Account data (the people who sign in to Review Agent, and the restaurant's settings) is processed by us as the Responsible Party, to run the service.
3. Google user data
This section describes exactly how Review Agent accesses, uses, stores, shares and deletes data it receives from Google.
3.1 The permission we request
When an owner of a restaurant clicks Connect Google, Review Agent asks Google for one permission, the https://www.googleapis.com/auth/business.manage scope, which lets an app manage a Google Business Profile. We ask for it only so that we can read the restaurant's reviews and post the replies it approves. We do not ask for access to your Gmail, contacts, calendar, files or any other Google service, and we do not receive your Google password.
3.2 What we access
- Accounts and locations that the connected Google user manages: their identifiers and names. We show these once so the owner can choose the right restaurant, and we store only the identifiers of the account and location chosen.
- Reviews of the chosen location: the review identifier, the reviewer's display name as Google shows it (or nothing, if the reviewer is anonymous), the star rating, the review text, when the review was written and last edited, and any reply already posted.
- Replies: we post a reply to a review when someone at the restaurant approves it, or when it matches automatic posting rules that the restaurant's owner has switched on. We never post a second reply over an existing one.
- A refresh token that Google issues so Review Agent can keep checking for new reviews without the owner signing in to Google each time.
We do not read or change the profile's business information, such as its address, hours, photos or posts.
3.3 How we use it
We use Google user data only to provide the features you see in Review Agent:
- showing the restaurant's reviews in its dashboard;
- classifying each review and drafting a reply (see section 6);
- posting approved replies to Google;
- emailing the restaurant's own team about urgent reviews, a daily digest and a weekly report.
We do not use Google user data for advertising, we do not sell it, we do not use it to build profiles of reviewers, we do not use it to assess anyone's creditworthiness or for lending, and we do not use it to train artificial intelligence models.
3.4 How we store it
Review data is stored in our database, hosted by Supabase in the European Union (Ireland), encrypted at rest and in transit. The refresh token is kept in an encrypted secrets vault, separately from other data, and is readable only by our server-side functions. Database access rules ensure that people at one restaurant can see only that restaurant's data.
3.5 Who can see it
The restaurant's own team sees its reviews in the dashboard. ClearStack staff access a restaurant's Google user data only when the restaurant asks us to help with something, when it is needed for security or to investigate abuse, or when the law requires it.
3.6 Who we share it with
We share Google user data only with the service providers listed in section 7, and only what each needs to perform its part of the service. In short: review text goes to our AI provider to draft replies, and alert emails carrying a review summary go through our email provider to the restaurant's own addresses.
3.7 Disconnecting and deletion
An owner can disconnect Google at any time in the restaurant's settings in Review Agent. This deletes the stored refresh token immediately and stops all access. You can also remove Review Agent's access from your Google Account at myaccount.google.com/permissions; the stored token then stops working and is deleted when the restaurant is disconnected or deleted. To have a restaurant's reviews and replies deleted from Review Agent, see section 9.
3.8 Google API Services User Data Policy
Review Agent's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Other information we collect
- People who sign in. Your email address, the organisation and restaurants you have access to, and your role. We sign you in with a one-time link sent to your email, so we do not store a password.
- Restaurant settings. The restaurant's name, address, timezone, contact email, the email addresses that should receive alerts, its reply style and sign-off.
- Activity records. A log of actions taken in Review Agent, such as who approved, edited or skipped a reply and when, so that every reply posted on a restaurant's behalf can be traced.
- Technical data. When you use the dashboard, our hosting and sign-in providers process your IP address, browser type and request times to deliver the service and protect it from abuse.
- Cookies. We use only the cookies needed to keep you signed in. We do not use analytics, advertising or tracking cookies.
Review Agent is for businesses. We do not knowingly collect personal information from children, and we do not ask for special personal information as POPIA defines it. Reviews are written by members of the public, and if a review contains such information we process it only as part of that review.
5. How we use information, and on what basis
| Purpose | Lawful basis under POPIA |
|---|---|
| Providing Review Agent to a restaurant: reading reviews, drafting, approving and posting replies, alerts and reports | Performance of our contract with the restaurant (s11(1)(b)); for review data, on the restaurant's instructions as its Operator |
| Signing people in and controlling what each person can see and do | Performance of the contract (s11(1)(b)) and our legitimate interest in keeping the service secure (s11(1)(f)) |
| Keeping an activity log, preventing abuse and investigating problems | Our legitimate interests and the restaurant's (s11(1)(f)) |
| Meeting tax, accounting and other legal obligations | Compliance with an obligation imposed by law (s11(1)(c)) |
We do not send marketing to reviewers, and we do not add anyone to a marketing list.
6. How AI is used
To classify a review and draft a reply, Review Agent sends the review text, its star rating, the reviewer's first name, the restaurant's reply settings and a few of its recent replies to an AI model made by Anthropic (Claude). Once a week it also sends that week's review texts, without reviewer names, to find recurring themes for the restaurant's report. Each request contains one restaurant's data only.
Anthropic processes this data to return the draft and keeps it only for a limited period under its commercial terms. Anthropic states that by default it does not use inputs or outputs from its commercial products to train its models.
A draft is a suggestion. A person at the restaurant approves, edits or skips it, unless the owner has switched on automatic posting for simple thank-you replies. Even then, complaints, urgent issues, low ratings and reviews whose rating does not match their text always wait for a person. Review Agent does not make decisions about anyone that have legal or similarly significant effects.
7. Who we share information with
We do not sell or rent personal information. We share it only with the service providers below, who are bound to process it on our instructions and keep it secure, and with Google itself when we post a reply.
| Provider | What it does | What it may receive |
|---|---|---|
| Supabase, Inc. (USA), hosting in Ireland | Database, sign-in, background processing and the encrypted secrets vault | All data held in Review Agent |
| Vercel, Inc. (USA), servers in Ireland | Hosts the Review Agent website and dashboard | Data shown in the dashboard as it passes through, IP addresses and request data |
| Anthropic, PBC (USA) | AI model that classifies reviews and drafts replies | Review text, star rating, reviewer first name, the restaurant's reply settings and recent replies |
| Resend, Inc. (USA), sending from the European Union | Sends sign-in links, alerts, digests and reports | Recipient email addresses, and the content of each email, which can include a reviewer's name and a summary of their review |
| Google LLC (USA) | Google Business Profile, the source of the reviews | The replies we post, and the requests we make to read reviews |
We may also disclose personal information where the law requires it, where it is necessary to establish or defend a legal claim, or to our professional advisers under a duty of confidentiality.
8. Transfers outside South Africa
The providers above are located outside South Africa, so personal information is transferred across borders. Section 72 of POPIA permits this where the recipient is bound by law or by an agreement that gives an adequate level of protection, or where the transfer is necessary to perform a contract. Our database, website servers and email sending are located in the European Union, which is subject to the GDPR. Each provider offers data processing terms, and we rely on those terms and on the transfer being necessary to provide the service.
9. How long we keep it, and deletion
- Review data is kept while the restaurant uses Review Agent. When a restaurant stops using the service we delete its reviews, replies, alerts, reports and activity log within 30 days.
- The Google refresh token is deleted as soon as the restaurant disconnects Google, or when the restaurant is deleted.
- Accounts of people who sign in are kept while they have access, and deleted on request or when their organisation stops using the service.
- Backups. Our database provider keeps daily backups for 7 days, so deleted data disappears from backups within 7 days of deletion.
- Business records such as invoices are kept for as long as South African tax and company law requires, generally five years.
Deletion on request. A restaurant owner can ask us at any time to delete the restaurant and all of its data, and we will do so within 30 days. A reviewer who wants our copy of their review removed can ask the restaurant or email us directly. Either way, email support@clearstack.co.za. Deleting data from Review Agent does not delete a review or reply from Google; that is done on Google itself.
10. How we protect information
Section 19 of POPIA requires us to secure personal information using reasonable technical and organisational measures. In practice:
- the website and dashboard are served only over HTTPS, and data is encrypted in transit and at rest;
- database rules keep each restaurant's data separate, and every write is checked against the person's role;
- Google refresh tokens and API keys are held in encrypted secret stores, never in application code;
- review text is treated as untrusted input, and automated checks run before any reply can be posted;
- every approval, edit, post and settings change is recorded in an activity log that cannot be edited;
- access to production systems is limited to the people who need it.
No system is perfectly secure. If a security compromise affects personal information, we will notify the restaurants affected, and as POPIA requires, the Information Regulator and the people concerned, as soon as reasonably possible.
11. Your rights
Under POPIA you have the right to:
- be told whether we hold personal information about you, and to have access to it;
- ask us to correct or delete information that is inaccurate, irrelevant, excessive, out of date, incomplete, misleading or unlawfully obtained;
- object to processing on reasonable grounds where we rely on legitimate interests;
- withdraw consent where we rely on it, without affecting processing already carried out;
- complain to the Information Regulator, or apply to a court.
To exercise any of these rights, email support@clearstack.co.za. Where we process data on behalf of a restaurant, we will pass your request to that restaurant and help it respond. We may ask for proof of identity so that we do not disclose information to the wrong person, and we will respond within 30 days.
12. Complaints to the Information Regulator
If you are not satisfied with how we have handled your personal information or your request, you may lodge a complaint with the Information Regulator of South Africa:
- Website: inforegulator.org.za
- General enquiries: enquiries@inforegulator.org.za
- POPIA complaints: POPIAComplaints@inforegulator.org.za
The Regulator occasionally updates its contact details and forms, so please check its website.
13. Changes to this policy
We may update this policy when the service, our providers or the law change. The date at the top shows when it was last revised. If a change materially affects how we use personal information, we will tell the restaurants using Review Agent before it takes effect.
14. Contact us
Any question about this policy or about how we handle personal information can go to support@clearstack.co.za. Also see our Terms of Service.