Privacy Policy

This policy applies to the OrdoService website, demonstrations, restaurant deployments and platform services. We update this notice before materially different collection or use begins.

1. Our privacy approach

We collect only the personal information reasonably needed for identified purposes, use it for those purposes, protect it with safeguards appropriate to its sensitivity, and retain it only as long as reasonably required. We designate responsibility for responding to privacy questions and requests.

2. Information we may collect

Website and inquiry information

When you contact us or request a demonstration, we may collect your name, business contact information, restaurant or organization name, the content of your inquiry and subsequent correspondence.

Restaurant platform information

We may process account and access information, restaurant configuration, table-session information, orders, menu selections, service events, staff actions, device or session identifiers, consent records and operational logs. The precise information depends on the restaurant configuration.

Payment information

Where payment features are enabled, credit-card payments are processed through an authorized payment service provider. OrdoService does not store full credit-card numbers or card security codes in its application databases. We may receive limited transaction information such as payment status, amount, method category and a provider transaction reference.

Technical information

Our website and platform may automatically record limited technical information such as IP address, browser or device type, timestamps, requested pages, diagnostic events, security events and approximate location derived from an IP address. We may use essential session technologies to provide security and maintain an active session.

3. How we use information

We may use personal information to:

• respond to inquiries and arrange demonstrations or onboarding;
• provide, secure and support authorized platform access;
• route and manage restaurant orders and service events;
• process or reconcile payments through authorized payment providers;
• produce operational records and customer receipts;
• configure menus, tables, stations, staff roles and restaurant sites;
• diagnose problems, prevent misuse and maintain security;
• meet legal, accounting and regulatory obligations; and
• improve usability and performance using aggregated or de-identified information where practical.

4. Consent and choices

We obtain consent where required and appropriate for the sensitivity and context of the information. A restaurant may provide notices or obtain consent from its guests and staff for information it controls through the platform. You may withdraw consent where permitted, subject to legal or contractual restrictions and reasonable notice. Withdrawal may affect our ability to provide a requested function.

5. When information may be shared

We do not sell personal information. We may disclose information to the restaurant or organization responsible for the applicable interaction; providers supporting hosting, email delivery, communications, payments, monitoring or technical operations; professional advisers; or authorities when required or permitted by law. Service providers are expected to use information only for contracted services and apply appropriate safeguards. Some providers may process information outside Alberta or Canada, where it may be subject to another jurisdiction's laws.

6. Restaurant and OrdoService responsibilities

For a restaurant deployment, the restaurant may determine why guest, staff and transaction information is collected and used. OrdoService may process that information on the restaurant's behalf. Privacy questions about a specific restaurant interaction may need to be directed to that restaurant. OrdoService remains responsible for information under its own control.

7. Retention

We retain personal information only as long as reasonably necessary to provide the service, resolve disputes, maintain security and meet legal or accounting requirements. Retention periods differ by record type and restaurant configuration. When information is no longer required, we securely delete, destroy or de-identify it.

8. Safeguards

We use administrative, technical and physical safeguards designed for the sensitivity of the information. These may include role-based access, authentication, encrypted network connections, restricted secrets, logging, backups, software maintenance and service-provider controls. No internet or storage system can be guaranteed completely secure.

9. Access and correction

Subject to applicable law and permitted exceptions, you may request access to personal information under our control, ask how it has been used or disclosed, and request correction of inaccurate information. We may need to verify your identity before responding. Requests relating to a restaurant-controlled account or transaction may be referred to that restaurant.

10. Children

The website and platform are intended for restaurants and their customers and are not designed to solicit personal information directly from children. Restaurants are responsible for age-related requirements relevant to their service, including requirements involving alcohol.

11. External services and links

Third-party services and websites have their own privacy practices. This policy does not govern information handled independently by a restaurant, payment provider or external website.

12. Changes to this policy

We may update this policy as the platform, service providers or legal requirements develop. We post the updated version at this URL and revise the effective date. Material changes may also be communicated through the platform or directly to participating organizations where appropriate.

13. Contact and privacy requests

Questions, access or correction requests, and privacy concerns may be sent to:

Privacy Contact, OrdoService Systems
Calgary, Alberta, Canada
contact@ordoservice.com
403-617-1294

This policy is a general operational notice and is reviewed as service configurations and data practices change.