ReviewMuse redesign previewBack to redesigned homepage
← Back to ReviewMuse
PRIVACY

Collect what the product needs. Not everything it can.

Customer review flow

When a customer opens a ReviewMuse link, the service may store a random browser identifier and journey events such as link opened, writing started, draft generated and continued to Google. These events help the business understand where customers complete or abandon the process.

The review-writing notes are sent to the ReviewMuse-controlled AI service so a draft can be generated. The current core flow does not store the generated review text as a marketing profile or customer-history record.

Business account information

For business users, ReviewMuse stores the information needed to operate the account, including login email, password hash, account role, business profile, branding settings, review destination and dashboard analytics. Passwords are never stored in plain text.

Pilot and contact requests

If you request pilot access, we store the name, business name, email address, optional website and optional note you submit so we can evaluate the request and contact you about ReviewMuse.

Cookies

ReviewMuse uses essential cookies for business login security and a random visitor identifier for review-journey analytics. The product does not require third-party advertising cookies for its core operation.

Infrastructure

The production design keeps the application database and AI processing on ReviewMuse-controlled infrastructure. Public web traffic may pass through infrastructure providers used for DNS, TLS, security and connectivity.

Retention and access

During the pilot, data is retained as needed to operate, secure and improve the product. Businesses can contact ReviewMuse to request account-data corrections or deletion. More specific retention periods will be published before broad commercial launch.

What we do not want the product to become