Legal

Privacy Policy

Effective September 26, 2026

1. Overview

This Privacy Policy describes how Legacy Sync LLC ("Legacy Sync," "we," "us," or "our") collects, uses, and shares information in connection with Rail.menu, a digital menu product owned and operated by Legacy Sync (the "Service"). The Service has two audiences:

  • Venue operators who sign in to the administrative dashboard to manage their menu, branding, and display settings.
  • Diners who view a venue's menu through a Rail.menu URL (typically by scanning a QR code at the table).

What we collect, and how we handle it, differs between these two audiences. Sections 2 and 3 below cover each.

2. Information We Collect from Venue Operators

When you create or use a Rail.menu operator account, we collect:

  • Account information. Email address, password (stored as a salted hash by our authentication provider), and the venue you are associated with.
  • Authentication metadata. Sign-in times, IP addresses associated with sign-in attempts, and session identifiers. Used to keep your session active and to investigate suspicious activity.
  • Terms acceptance evidence. When you accept our Terms, we record your account identifier, the Terms effective date, the date and time of acceptance, your IP address, and browser information. We use this record to document your acceptance and resolve disputes.
  • Customer Data you enter. Menu items, prices, descriptions, ingredient and allergen information, images, branding settings, and any other content you input into the administrative dashboard. Customer Data is your data; we host and process it to provide the Service per our Terms of Service.
  • Communications. If you contact us by email or support form, we keep the conversation for service-history purposes.
  • Billing and business records. If you purchase the Service, we collect business contact details, invoice status, subscription details, and payment confirmations. Payment-card information is handled by our payment processor; Legacy Sync does not store complete card numbers.

3. Information We Collect from Diners

The diner-facing menu is intentionally minimal. When a diner opens a Rail.menu URL we collect:

  • Standard server logs. IP address, browser type and version, requested URL, referrer, and timestamp. Used for security, debugging, and aggregate traffic analysis. Standard server logs are retained for up to 30 days.
  • Language preference. Read from the browser's Accept-Language header to render the menu in the diner's preferred language. If a diner chooses a language, that choice is saved in a first-party cookie on the diner's device for up to one year. It is not linked to a diner account.
  • Local preferences. If a diner toggles the large-text accessibility setting, that preference is stored in the diner's own browser via localStorage. It never leaves the device.
  • Menu interaction data. We record aggregate menu activity such as menu views, item opens, filters used, and link clicks. First-party item and link events are tied to a venue and menu item, not to a named diner account.
  • Google Analytics data. In production, Google Analytics may collect device and browser information, approximate location, referring pages, pages viewed, and menu interaction events. Google Analytics may use cookies or similar identifiers for measurement.

We do not require diners to create accounts. We do not use diner information for targeted advertising, and we do not knowingly ask diners to provide names, email addresses, or other direct account identifiers through the menu.

4. How We Use Information

We use the information described above to:

  • provide, maintain, and improve the Service;
  • authenticate operator sign-ins and protect accounts;
  • render the venue's menu in the diner's preferred language;
  • measure menu use and provide venue-level analytics;
  • administer subscriptions, invoices, and payments;
  • investigate and respond to suspected misuse, abuse, or security incidents;
  • communicate with operators about service-related matters; and
  • comply with legal obligations.

We do not sell or rent personal information. We do not use operator or diner information to train artificial intelligence models.

5. How We Share Information

We share information only as needed to operate the Service, and only with service providers bound by confidentiality and data-handling obligations. Our principal service providers are:

  • Supabase - database, authentication, and file storage.
  • Vercel - application hosting and content delivery.
  • Resend - transactional email delivery (magic links, password resets, email change confirmations).
  • Google Analytics - traffic and menu-interaction measurement on the production Service.
  • Zoho Books and Stripe - invoicing, subscription administration, and payment processing.
  • Anthropic and OpenAI - AI processing used when an operator imports a source menu or requests generated menu content or images. These providers process the menu content sent to them to return results; we use their business API services, which do not use that content to train their models by default.

We may also disclose information when required by law, in response to a valid legal process, or to protect the rights, property, or safety of Legacy Sync, our users, or others. If Legacy Sync is involved in a merger, acquisition, or sale of all or substantially all of its assets, or if the Service is transferred to an affiliate or to a buyer or successor of the Rail.menu business, information may be transferred as part of that transaction, subject to the receiving party honoring this Policy.

6. Cookies and Similar Technologies

Google Analytics may set measurement cookies on the production Service. We use those measurements to understand aggregate traffic and menu interactions, not for targeted advertising. Browser or device settings, content blockers, and Google's available opt-out controls may limit that collection.

A small amount of local browser storage (localStorage) is used to remember per-device preferences such as theme and large-text mode. Those local preferences stay on the device. A first-party language cookie remembers a diner's chosen menu language.

The operator-facing dashboard uses essential cookies set by our authentication provider to keep operators signed in. These are functional cookies required for the Service to work; they are not used for advertising or cross-site tracking.

7. Data Retention

We retain operator account information for as long as the account is active and for a reasonable period afterward to satisfy legal, accounting, and dispute-resolution obligations. Per our Terms of Service, Customer Data remains available for export for thirty (30) days after termination, after which we may delete it.

We retain Terms acceptance evidence, including the associated IP address and browser information, while the operator account is active and for seven (7) years after the account closes. The paid invoice remains the primary acceptance record for the paying business.

Server logs are retained for up to thirty (30) days unless a longer retention is required to investigate a specific incident. Anonymous first-party diner interaction events are ordinarily retained for ninety (90) days. Google Analytics data is retained according to the retention settings in our Google Analytics account.

8. Security

We use commercially reasonable administrative, technical, and physical safeguards to protect information, including encryption in transit (TLS), hashed password storage, and access controls on our infrastructure. No system is perfectly secure; we cannot guarantee that data will not be accessed, disclosed, altered, or destroyed by breach of those safeguards.

9. Your Rights

Depending on where you live, you may have rights regarding your personal information, including the right to access, correct, delete, or restrict its use. To exercise any of these rights, email privacy@legacy-sync.com from the email address associated with your operator account. We will respond within a reasonable time and in accordance with applicable law.

California residents. California law provides additional rights to California consumers, including the right to know what categories of personal information we collect, the right to request deletion, and the right not to be discriminated against for exercising those rights. We do not sell personal information.

10. Children

The Service is intended for venue operators and adult diners. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact privacy@legacy-sync.com and we will take appropriate action.

11. International Data

The Service is operated from the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States. By using the Service, you consent to that transfer.

12. Updates to This Policy

We may update this Privacy Policy from time to time. Material changes will be posted with a new effective date at the top of this page. Your continued use of the Service after the new effective date constitutes acceptance of the revised Policy.

13. Contact

Questions, requests, or concerns regarding this Policy may be directed to privacy@legacy-sync.com. A mailing address for written requests is available on request from that email address.