Chapman Young Labs · Seatorix

Privacy Policy

Updated September 15, 2026 · Controlled beta

This notice explains how Seatorix handles information across its customer website, restaurant dashboard, booking pages, and supported iPhone app. Seatorix is developed by Chapman Young Labs.

Features vary by platform, release and assigned access. Local previews and staging are testing environments; their availability does not mean a feature is publicly released.

Information we process and why

Accounts and access: names, email addresses, protected authentication credentials, active sessions, restaurant memberships and tester enrollment help us sign you in and limit access to the right people.
Reservations and waitlists: contact details, party size, dates and times, selected seating, requests, booking status and guest feedback help a restaurant manage visits and communicate with guests. You may use supported guest-booking flows without an account.
Restaurant and staff information: restaurant listings, menus, hours, photos, floor plans, staff profiles, shifts, assignments and operational notes support restaurant operations and the customer-facing information a restaurant chooses to publish.
Product use and reliability: requests, error details, timestamps, device/browser information and network information help deliver pages, prevent abuse and investigate problems. Operational analytics summarize restaurant activity such as reservations, wait times, seating and service outcomes.
Support: questions, contact details and the information you choose to put in an issue report help us investigate and respond.

Use fictional details for beta testing unless your test lead has specifically authorized otherwise. Avoid unnecessary sensitive information in free-text fields. Do not put passwords, payment-card details or private access links in guest notes, chat or support reports.

The restaurant associated with a booking or waitlist entry receives the information needed to manage it. Staff access depends on their active restaurant role. Restaurant administrators manage their own listings, staff access and guest operations. Public restaurant content and eligible customer-facing staff profile details can be visible to customers; private operational notes are not public profile content.

Seatorix uses service providers to host and secure the application, store files, deliver email, diagnose errors and provide optional AI help. Depending on the enabled environment, these include Render for hosting, Cloudflare for infrastructure and screenshot storage, Resend or the configured email delivery service, Sentry for error diagnostics, and OpenAI for Beta Help. Providers receive the information needed for the service they perform.

Support personnel may review information needed to handle an issue. Information may also need to be disclosed to meet a legal obligation or investigate misuse and protect the service. A restaurant's own systems and any external sites you visit have their own privacy practices.

Beta Help, AI and screenshots

When you send a question to live Beta Help, your question, relevant recent conversation, an allowlisted screen hint and approved help material are processed using OpenAI. The helper does not inspect the text of your current page, read your live restaurant records or control your account. Clearly labeled offline picture-preview scenarios use predefined replies instead of live AI.

OpenAI states that API content is not used for model training by default unless the API customer opts in. Its default abuse-monitoring logs may retain content for up to 30 days, with exceptions for legal or safety needs. Uploaded help files and search collections have separate retention until deletion or expiry; deletion does not necessarily mean immediate removal from all provider systems. See OpenAI's data controls. This notice does not promise zero provider retention.

The web helper keeps a bounded conversation and draft in this tab's session storage so navigation and refresh can preserve your place. It falls back to memory if that storage is unavailable. Clear conversation and sign-out remove the app's saved chat; browser tab restoration may otherwise restore it. Clearing chat does not erase an already-sent email or information retained by a provider.

Seatorix does not save Beta Help transcripts or report bodies in its application database. It keeps access and operational diagnostics, and support emails are separate records. Report a problem opens an editable draft; sending requires review and explicit confirmation. The report contains the reviewed fields, not an automatic transcript or screenshot attachment. Local previews disable email sending.

Help pictures are reviewed example captures, not a view of your screen. Hosted libraries use private storage and authenticated image access. Opening a picture does not send a new AI question, advance a test or confirm that you completed a step.

Cookies, device storage and messages

The website uses cookies for sign-in and request protection, and browser storage for preferences, supported guest-link access and the web helper's temporary state. Clearing browser data can sign you out or remove saved preferences and drafts. The iPhone app stores sign-in credentials using its secure device storage and keeps local preferences. Removing the app or clearing browser data is not an account-deletion request.

Account, invitation and reservation actions can generate service emails. During staging, delivery may be limited to approved recipients. A message shown in the app or accepted by an email provider is not proof that an email reached an inbox.

Access, correction and deletion

On the website, open Account to update your profile or select Request deletion under Account deletion. In the iPhone app, open Settings and select Request Account Deletion. You can cancel while the request remains eligible for cancellation; submitting it starts a review rather than immediate deletion.

Active restaurant access must be resolved before account deletion can be completed. The current deletion process disables sign-in and removes or replaces identifying account information and linked guest, reservation and waitlist details. Some non-identifying operational history and audit records remain. Separate restaurant records, support emails and backups may require additional review rather than disappearing with the account.

Guests without an account can contact the restaurant or support@seatorix.com for help locating and correcting or anonymizing their records. We may need to verify that a request relates to you. Depending on where you live and which laws apply, you may have additional rights concerning access, correction, deletion or use of your information. Contact us to discuss a request.

Retention and security

Retention depends on the record's purpose: providing the service, resolving support requests, protecting accounts, maintaining restaurant history and meeting applicable obligations. There is no single automatic deletion period for all records in this beta. Contact Support for the status of a particular deletion request or retention question.

Access controls, protected credentials and diagnostic filtering help protect information, but no service can guarantee that every error or unauthorized disclosure will be prevented. If you see someone else's private data, stop the affected action and contact Support without copying the private contents. Contact us as well if you believe a child provided personal information without appropriate permission.

Contact and updates

For Seatorix privacy questions, email support@seatorix.com or visit Support. We will update this page and its date when these practices change. This notice describes Seatorix; it does not cover unrelated Chapman Young Labs client services.