What the product does
Comita is a live service-quality platform for restaurants. It uses browser-based microphone capture during a shift, real-time service records, structured scoring, and evidence-backed alerts to help managers respond in the moment.
What data is collected
Depending on how an account is configured, the service may process live microphone input, service records, scoring events, alert feedback, session metadata, and account information needed to provide the product.
How microphone capture works
Microphone capture begins only when a user starts a visible live session in the web app. Recording status, stream health, and session controls are surfaced in the interface while a session is active.
What is stored by default
Raw audio is not stored by default. The product is designed to focus on the records and service signals needed to review service quality and improve shift operations.
How employee identities are handled
Comita is intended to support anonymized, team-level service review rather than individual employee profiling. Customers should configure operational use of the product so service insights are used to improve shift performance and guest experience without tying routine review workflows to named employees.
How service records and scoring data are used
Service records and scoring data are used to generate live alerts, support service review, improve shift summaries, and maintain product quality. Evidence and confidence signals are included so managers can judge whether an alert is actionable.
Retention windows
We retain data only for as long as needed to provide the service, support service review, meet contractual obligations, and satisfy legal requirements. Current settings use limited retention windows for service records and scoring data, including active processing for live session state, about 30 days for service records, and about 90 days for scoring events and alert feedback.
Deletion requests
Deletion workflows are supported for customer data. Requests are reviewed through the applicable support or customer-success channel and processed according to product configuration, contractual commitments, and legal requirements.
Access controls
Access to account data is limited by role. Customers are responsible for managing user permissions, reviewing account access, and removing users who no longer need visibility into session or service review data.
Third-party processors
Comita may rely on infrastructure, analytics, hosting, and processing providers that help deliver service records, scoring, application hosting, and security operations. Subprocessor details should be reviewed through customer documentation and contractual materials before launch.
Customer responsibilities for notice and consent
Customers are responsible for determining whether notice, signage, consent, policy updates, or local workflow changes are required for their teams, guests, and jurisdictions before using browser-based microphone capture in a live environment.
Contact information
For privacy questions, access requests, or deletion requests, use the support or customer contact channel provided with your Comita account or commercial agreement.