Reputation Systems

Review Reply for Restaurants Privacy Policy

Effective October 20, 2026

Overview

Review Reply for Restaurants is published by Shrikrishna Gavhane / Reputation Systems. It helps teams draft, edit, copy and approve replies to guest reviews. This policy explains the extension's data handling and the RR account features it uses. Account sign-in and billing also use the relevant Multisystems account and payment services.

Information the extension handles

The extension identifies supported review surfaces on the hosts listed in its permissions; it does not collect a general browsing-history feed. It uses the current page's address and relevant property context to recognize a review surface or listing. A listing identifier is sent to RR when the user saves a restaurant/listing link, rather than sending a history of visited pages.

When data is sent and why

When you request a draft, the extension sends the chosen review information, platform label and applicable reply settings over HTTPS to rr-api.reputationsystems.ai. Applicable settings can include the linked restaurant name, manager signature and reply instructions. The draft-generation request does not itself include the structured menu, cuisine, branch, contact or opening-hours fields; these are stored separately with the restaurant profile. Information included in reply instructions is sent with the draft request. Regeneration includes the previous draft when available. RR uses these inputs to generate the requested content through its model-processing providers. Truth Check guidance runs locally in the extension.

Other requests are separate from drafting. Pairing, connection checks, plan/usage retrieval, and account-instruction or restaurant-profile synchronization can happen when you connect, open or refresh the extension, or before a draft on a linked listing. Saving, editing, migrating older locally saved profiles, or deleting profiles sends the associated account requests. Asking for generated instructions sends the restaurant description and applicable instruction input. A service health check may occur without review content.

Copy places the chosen reply on your clipboard. On supported Google Business Profile and Tripadvisor review forms, clicking the extension’s Post reply action fills and submits the platform’s native reply form. On Yelp, Uber Eats, DoorDash and the manual-input path, Insert fills a reply field and you submit using the platform’s own controls. Neither generation nor insertion alone publishes a reply. The review platform’s privacy policy also applies when you submit. Merely opening a supported review page does not automatically send all its reviews to RR or publish a reply.

Local storage and connection lifecycle

chrome.storage.local holds connection information, reply preferences, device-level instruction overrides, cached account instructions and restaurant profiles, signature suggestions and workspace state. chrome.storage.session holds temporary pairing state, per-tab pasted review input and draft replies. Session data is cleared when the browser session ends; per-tab draft data is also cleared when its tab closes. Local preferences and overrides may remain after disconnecting.

Pairing requests expire after ten minutes and are bound to the initiating browser tab and token. The RR website receives a SHA-256 hash of the private extension credential, not the private credential itself. The private credential is stored in the Chrome profile and attached to RR API requests by the background service worker; it is not provided to review webpages.

An extension session expires after 30 days. Disconnect requests revocation from RR; once that succeeds, or the session is already unauthorized, the extension removes its local connection data and relevant account caches. If revocation cannot be confirmed, disconnect reports an error rather than claiming success. Expired or unauthorized connections cannot be used to request drafts. Local Chrome storage is not a hardware-backed secret vault: protect access to your browser profile.

Account storage, history and retention

RR stores the extension credential's one-way hash with account and extension identifiers, account email when supplied, status, creation/expiry times, last use and revocation information. Expired extension-session records are removed by an automated cleanup process. Usage, security and billing-related records are separate from the text used to generate a reply.

Account-level instructions are stored separately from generation requests. The RR console keeps up to five recent nonempty instruction versions, including generated versions recorded by the console. Clearing the current instructions does not automatically erase that history. Device-only instruction overrides stay in the Chrome profile until cleared or removed, but are sent with a draft when applicable.

Restaurant profiles submitted for account storage include the saved restaurant name, branch or location, cuisine, manager signature fields, instructions, menu items and approved descriptions, service options, contact details, opening hours and linked listing identifiers. These fields are stored with your RR account until you edit or delete the profile or request account-data deletion, subject to the operational, legal and backup retention described below. They are not covered by a claim that all manager signature fields disappear after generation. Local cached profiles and suggestions can persist separately from the account record.

RR's application-server system journal is configured with a maximum retention of 14 days and a 500 MB size limit; entries may be removed earlier when the size limit is reached. This limit applies to that system journal, not to database records, backup copies, other log destinations or model-provider records. Backups can retain copies after a record changes or is deleted from the active service. Those copies remain subject to backup retention and replacement schedules; deleting an active record does not immediately erase every backup copy.

The reply-generation application, as described in the shared RR service policy, does not intentionally persist review text, reviewer names or generated replies as a permanent review archive in its application database. This does not erase profile fields or instruction history saved separately, local drafts, copies posted to review platforms, or processing by service providers. Operational, security, billing records and backups may remain as needed to operate the service, investigate abuse and meet legal obligations. No immediate purge of all logs, provider systems or backups is promised.

Service providers and sharing

RR uses Hetzner for application-server hosting. Contracted infrastructure and model-processing providers process data to operate the service and fulfill requested generations. Model processing can use a primary service or a fallback; configured integrations include Groq, Inc. and Salad Technologies, Inc. (SaladCloud). The selected provider receives the review content, instructions and reply context needed for that request. Provider processing and any provider retention are separate from storage in the RR application database.

Where Groq processes a request, its published data policy says inference inputs and outputs are not retained by default, but permits retention for reliability or abuse investigation for up to 30 days, or longer when legally required. Usage metadata is retained. This policy does not promise zero provider retention. Provider-specific controls, retention terms and legal obligations apply to their processing.

Reputation Systems does not sell extension user data or use it for personalized advertising, creditworthiness or lending. Data is shared to deliver the requested functionality and related security/operations, with the review platform when you post, or when legally required. Information may also be disclosed to protect users and the service from fraud or abuse, or in a merger, acquisition or sale after obtaining explicit prior consent from the user, as required by the Chrome Web Store Limited Use policy. Human access is limited to authorized support with consent, security or abuse investigation, legal requirements, or permitted aggregated/anonymized operations.

Your choices and deletion requests

You choose when to request a draft, generate instructions, save a profile, copy, or post. Drafts remain editable. You can change local preferences, clear device-specific instructions, and request profile deletion through the available controls. Disconnecting revokes the extension connection; it does not delete the RR account, saved account instructions/history, account-side profiles, or replies already posted to another platform.

Uninstalling removes extension-local storage through Chrome, but does not itself send a deletion request for account data. For account/profile deletion, instruction-history removal, retained-record questions or other data requests, contact admin@multisystems.ai. Requests are handled subject to identity verification, applicable legal requirements and any necessary retention of security, accounting or backup records. Avoid including guest payment, medical or other confidential details that are unnecessary for a review reply. Reviews can contain health allegations or other sensitive information; only select and submit the information needed for your response.

Security

Data is transmitted over HTTPS. The background service worker handles the private extension credential, and RR stores its one-way hash. No transmission or storage method is completely secure; disconnect and contact us if you suspect a credential or Chrome profile has been exposed.

Chrome Web Store Limited Use disclosure

Reputation Systems' use and transfer of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Extension data is used to provide or improve the single user-facing review-reply purpose and related security, reliability and operational functions. It is not sold, used for personalized advertising, or used for creditworthiness or lending.

Changes to this policy

The published effective date identifies the policy in force. Material changes to data handling will be disclosed before new practices begin. The effective date above identifies this revision.

Contact

For privacy questions or data requests, email admin@multisystems.ai.