Command.Restaurant — Privacy Policy

Last updated: October 26, 2026

This Privacy Policy explains how Command.Restaurant ("Command.Restaurant", "we", "us") collects, uses, and protects information in connection with the Command.Restaurant online ordering service and the owner control center. It applies to restaurant owners and staff who use Command.Restaurant and to diners who place orders through a Command.Restaurant ordering page.

Command.Restaurant is operated by Liasse Technologique. Command.Restaurant is the product name shown when you sign in with Google.

Information We Collect

From restaurants (owners and staff):

• Account and business details — business name, address, contact email and phone, operating hours, and branding you provide.
• Menu content — items, descriptions, prices, options, categories, and images you create or import.
• Device and notification identifiers — e.g. a push-notification token used to deliver new-order alerts to your tablet or phone.

From diners placing an order:

• Order details — items, options, quantities, special instructions, order type (dine-in or takeout), and pickup time.
• Name and, where required, a mobile phone number used to verify the order and send order-status updates (for example, for scheduled pickups).
• We do not collect or process payment-card data through the ordering service; diners pay the restaurant directly.

Automatically: basic technical data such as IP address, device/browser type, and service logs, used to operate and secure the service.

How We Use Information

• To accept, route, display, and (where enabled) print orders, and to notify the restaurant of new orders.
• To send diners order confirmations and status updates for orders they place.
• To verify phone numbers in order to reduce fraudulent orders and pickup no-shows.
• To build and update menus at your request.
• To provide support, maintain security, prevent abuse, and meet legal obligations.

Google Sign-In and Business Profile Access

If you choose Google Sign-In, we request your Google account identifier, verified email address and basic profile information. We use your identifier and email to create or authenticate your restaurant account, and your name to display your identity during signup. Your Google password is never provided to us. Basic sign-in does not grant access to your Business Profiles.

When the Business Profile connection is available, connecting it is a separate, optional consent step. With your permission, we read the accounts and restaurant locations you manage to let you choose a restaurant and confirm your access. We retain the selected restaurant details and an encrypted authorization grant for its ordering-link integration. When you later sign in with the same Google account and ask to add another restaurant, we use that grant to list the locations you manage again instead of asking for a new consent, and save it with the restaurant you add. Connecting alone does not publish an ordering link. We do not import Google menus or photos.

Signup-session details are encrypted and expire after 15 minutes; expired sessions are removed. The Google identifier and contact email associated with your restaurant are retained with your account. Business Profile authorization grants are encrypted and removed when the restaurant owner account is reset or deleted.

We use Google user data only to provide these account and restaurant-connection features. We do not sell this data or use it for advertising. Our use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements. Infrastructure providers process the data on our behalf to operate and secure these features.

You can revoke Google access at any time in your Google Account connections. Revoking access stops future authorized Google access; it does not itself delete your Command.Restaurant account or restaurant records. To request deletion of stored Google-related data or your account, contact info@command.restaurant.

Sharing With Third Parties

We do not sell or rent your information, and we do not share it with third parties for their own marketing. We use the following service providers strictly to operate the service, processing data on our behalf under confidentiality obligations:

• Google — push-notification delivery (Firebase Cloud Messaging) and AI features.
• Twilio — SMS one-time codes and order text messages.
• SendGrid — transactional email.
• Cloudflare — network routing and security.
• Cloud hosting and storage providers that run our infrastructure.

We may also disclose information where required by law or to protect the rights, safety, and security of our users and our service.

Data Retention

• Order records are retained as needed to operate the service and for the restaurant's recordkeeping, then deleted or anonymized.
• Account and menu data is retained while the account is active and deleted on request.

Security

We use industry-standard safeguards, including TLS encryption in transit and encryption at rest for sensitive credentials. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

Your Rights

You may request access to, correction of, or deletion of your information, and ask questions about this policy, by emailing info@command.restaurant.

Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date above reflects the most recent revision; material changes will be communicated through the service before they take effect.

Contact

Command.Restaurant — operated by Liasse Technologique
Product email: info@command.restaurant
Company email: info@liassetechnologique.com