Business owner accounts
Owners sign in using Google or email/password through Firebase Authentication. Email/password accounts need to verify their email before accessing cloud business data. Account information can include the owner’s email address, display name and authentication identifier.
The owner workspace stores business profiles and feedback in Cloud Firestore. Database rules restrict private business data and feedback access to the associated verified owner. Signing out ends access from that browser session; it does not delete cloud records.
The business information customers can see
A shared business QR opens a public customer-facing profile. It can include the business name, category, location, address, website, branding, review topics and official Google destination supplied by the owner. Uploaded logos and cover images are served from public URLs.
The public profile is separate from the private business record. Owner-name and business-phone fields are excluded from the public profile projection in this version. Owners should upload only images and business details they are comfortable sharing publicly.
Customer feedback and drafts
A customer does not need to complete a ReviewDost signup form. The live business journey uses an anonymous Firebase authentication identifier to associate a feedback session with that browser. Sessions can store a rating, selected topics, notes, draft text, timestamps and whether the Google destination was clicked.
The business owner can read the feedback collected for that business. Feedback text is not automatically published on the ReviewDost marketing website. Avoid entering payment details, booking numbers, identification documents, medical information or other sensitive personal details.
What is sent for AI drafting
When a customer requests an AI draft, the application sends the supplied business context and feedback details to its configured Google Gemini service. The service prepares wording for the customer to review and edit. The business category alone is not treated as evidence of an experience.
Requests pass through the application’s server endpoint. AI access keys are not exposed in the page. The provider’s own privacy terms and service settings govern its processing; ReviewDost does not promise that submitted text stays only in the customer’s browser.
Browser storage and service protection
Firebase uses browser persistence for authentication. ReviewDost also stores interface preferences, such as reduced motion, and may store local demo setup information. You can sign out and clear browser site data, but clearing a browser does not remove feedback or business records already saved in the cloud.
The service uses bounded request counters to protect drafting and uploads. AI request limits use a hashed network identifier. Hosting and authentication providers may process technical connection and security data under their own terms.
The Google handoff is your choice
ReviewDost does not automatically submit a Google review. The customer can copy the edited wording and choose to open Google. Pasting and publishing happens on Google under the customer’s own account and Google’s terms.
For a review already published on Google, use the controls in your Google account to manage it. A handoff click recorded in ReviewDost does not confirm that a public review exists.
Practical choices before sharing
- Share only details you want the business to read.
- Review and edit the draft before copying it.
- Keep private information out of public review text.
- Contact the business directly about feedback relating to a specific visit.
- Use a private channel for a sensitive issue rather than the review notes field.
This page describes the current product behaviour and is not a statement that every third-party service has identical retention or privacy practices.