Integration transparency
Google Business Profile, connected on the restaurant's terms.
Hoozh gives restaurant owners one place to read their authorized Google reviews and prepare replies. The restaurant keeps primary ownership, chooses whether to connect, and can stop access at any time.
Current availability
The production connector is implemented but remains disabled until Google approves Hoozh's production Cloud project. Hoozh does not treat OAuth credentials, test data, or a public Google preview as proof of API approval.
Owner-authorized
Only an owner or manager who already controls the restaurant's profile can start OAuth. Hoozh never claims or creates a profile for a customer.
Narrowly used
Hoozh uses the business.manage grant only to resolve the authorized restaurant location and import its review history. Tokens are encrypted and tenant-scoped.
Easy to stop
Disconnecting stops future syncs, asks Google to revoke the dedicated grant, and clears Hoozh's stored tokens without deleting the integration card or the restaurant's saved history.
How it works
01
The restaurant initiates access
A Hoozh manager clicks Connect and signs in on Google's own OAuth screen. The consent is bound to that Hoozh location and browser session.
02
Hoozh verifies the exact location
Hoozh lists only profiles the signed-in Google user can manage, then matches the selected location to the restaurant. It does not search for unrelated profiles.
03
Reviews stay inside the tenant
Review identifiers, rating, text, author details, dates, and existing reply state are imported into that restaurant's Hoozh workspace. One restaurant cannot access another's data.
04
The owner remains the publisher
Hoozh can prepare reply drafts for review. Automatic public posting is not enabled; the restaurant owner remains in control of any response workflow.
Restaurant authorization
The business owner always keeps control.
A restaurant remains the primary owner of its Business Profile. Hoozh accepts access only with express authorization, never changes ownership, and does not create a Hoozh profile as a substitute for a real eligible restaurant.
- The restaurant grants and can remove manager or OAuth access.
- Hoozh accesses only profiles the signed-in user is authorized to manage.
- Disconnect clears stored access and refresh tokens immediately.
- A privacy request can remove imported Google data from Hoozh.
Data and policy details
Questions about access or deletion?
Contact Hoozh directly for provider review, restaurant authorization, privacy, revocation, or data-deletion requests.