Business analytics

1. Signals that may be shown

• Restaurant-profile views and discovery impressions.
• Interactions with profile content and aggregate engagement.
• Clicks from Cevor to an external restaurant or reservation link.
• Aggregate interest in featured dishes, when that feature is active.
• Broad language, country, device or period breakdowns where a group is large enough to report safely.

2. What restaurants do not receive

• Names, emails or account identifiers of individual visitors.
• A person’s precise location, favorites, collections or search history.
• A raw person-by-person browsing timeline.
• A guarantee that an interaction becomes a visit, reservation or purchase.

3. Aggregation and thresholds

Cevor may combine, delay, round or withhold small groups to reduce re-identification risk. “Anonymous” is not used as an absolute promise; aggregation and access controls reduce risk but do not make every dataset mathematically anonymous.

4. Purpose and lawful use

Restaurants may use analytics to improve their Cevor presentation, featured content and discovery strategy. They must not attempt to identify users, combine reports to profile a person, or use the data for discrimination.

5. Accuracy and availability

Metrics can be affected by blocked requests, network errors, repeated visits, filters and product changes. They are directional product signals, not audited financial or reservation records. Definitions may evolve and material changes will be documented.

6. Roles and retention

Cevor determines how platform analytics are collected and protected. Restaurant access is limited to authorized members associated with that restaurant. Reports are retained only as long as useful for the service and legitimate operational needs.

Contact

See also