Privacy, plainly.

RHYKA connects a table plaque to the destination chosen by a restaurant. It does not process guest payments.

Information used to run the service

Restaurant accounts use names, email addresses, protected sign-in credentials, organization membership and two-factor authentication information. The service stores restaurant names, table and plaque settings, and records of account and configuration changes.

When a guest taps

The service records daily scan totals for a plaque. It does not create a guest account or guest profile. Payment details go to the destination provider, whose privacy practices apply once you leave RHYKA.

Operations and security

Hosting, database, email and error-monitoring providers help operate the service. Operational logs may be needed to investigate abuse and failures. Credentials and sensitive request data must be excluded from application logs.

Your account

Ask your restaurant owner about access, correction or removal of your restaurant account. A dedicated privacy contact, retention schedule and jurisdiction-specific rights must be added before this document is adopted as a final privacy notice.

This is an implementation summary for review, not a finalized legal policy.