Rose-BrookHotel AI visibility benchmark
BenchmarkingEvidencePricingMethodologyTrustSign inCheck my hotel
Check hotel

Rose-Brook

Hotel visibility evidence

Rose-Brook Benchmark gives hotel teams one clear benchmark for whether AI would recommend their hotel over the competitors guests also consider.

For owners, GMs, and commercial leads

Need help? Submit a support request.

Product

Product overviewHotel AI benchmarkingPublic benchmark evidencePricingMethodologyCheck my hotelSign in

Reassurance

SupportTrust centrePrivacyCookiesTerms
Rose-BrookHotel AI visibility benchmark
BenchmarkingEvidencePricingMethodologyTrustSign inCheck my hotel
Check hotel

Trust centre

How Rose-Brook protects the benchmark workspace

A practical account of data isolation, provider use, payments, retention, and the route for security or privacy review.

Current security read · July 2026

Public hotel evidence in. Protected workspace records out.

Rose-Brook sends controlled hotel benchmark context only to the providers needed to run enabled features. Account, billing, and authentication secrets are not included in benchmark prompts.

Review route

Hotel groups, advisers, and procurement teams can request current data-processing information or send a security questionnaire through support.

Request a trust review

Safeguards

Account and workspace isolation

Authenticated workspace records are scoped to the signed-in user. Database row-level security and server-side ownership checks protect hotel, benchmark, competitor, and analytics records.

Payments stay with Stripe

Checkout and card handling are provided by Stripe. Rose-Brook stores customer, subscription, price, and billing-status references rather than card details.

Sensitive connection tokens

Google Analytics OAuth tokens are encrypted by the application before storage. The connection uses read-only analytics access and can be disconnected from the workspace.

Transport and browser controls

Production traffic uses HTTPS with HSTS. Security headers restrict framing, content types, browser permissions, and the external services that pages may connect to.

Subprocessor register

Services that may handle Rose-Brook data

ProviderPurposeData involved
SupabaseAuthentication, database, and protected workspace recordsAccount, hotel, benchmark, and operational data
VercelApplication hosting, delivery, and product analyticsRequests, technical logs, and page analytics
StripeCheckout, subscriptions, and billing portalBilling identity and subscription references
ResendTransactional and benchmark-report emailRecipient details and message content
OpenAI, Google, and AnthropicEnabled AI benchmark executionControlled prompts containing relevant hotel and competitor context
Google PlacesHotel identity searchThe hotel search phrase
Google AnalyticsOptional customer-connected referral reportingRead-only reporting data when the customer enables it

AI provider use

Controlled benchmark context

Prompts may contain hotel names, locations, competitors, stay attributes, and public positioning details. Enabled providers receive only the context needed for that run.

Retention and deletion

Evidence remains auditable

Workspace and benchmark records are retained while needed to operate the service and preserve the requested audit history. Access, correction, and deletion requests go through privacy support.

Incidents and questions

One accountable route

Report a suspected security issue or request current processing information through the support form. Rose-Brook replies to the verified contact address supplied there.

This overview supports, but does not replace, the full privacy notice and service terms.

Rose-Brook

Hotel visibility evidence

Rose-Brook Benchmark gives hotel teams one clear benchmark for whether AI would recommend their hotel over the competitors guests also consider.

For owners, GMs, and commercial leads

Need help? Submit a support request.

Product

Product overviewHotel AI benchmarkingPublic benchmark evidencePricingMethodologyCheck my hotelSign in

Reassurance

SupportTrust centrePrivacyCookiesTerms