Privacy Policy

This Privacy Policy explains how DineFork collects, uses, stores, shares, and protects information when you visit our public website, request a demo, create an account, operate a restaurant workspace, or communicate with our team.

For customer data stored inside a restaurant workspace, the restaurant or account owner generally acts as the controller of the data they enter, and DineFork acts as the service provider or processor that hosts and secures that information on their behalf.

• Public website visitors and prospective customers
• Restaurant owners, managers, staff, and authorized operators
• Guests or customers whose information is entered into the platform by a restaurant

We collect information that is necessary to operate the platform, provide support, improve reliability, prevent abuse, and meet legal or contractual obligations.

• Account and profile data such as names, business names, email addresses, phone numbers, and role assignments
• Billing and subscription data such as plan selection, invoices, transaction references, and payment status metadata
• Restaurant operational data such as menus, orders, reservations, tables, modifiers, branches, taxes, settings, and workflow preferences
• Customer-facing data entered by a restaurant such as customer names, contact details, order history, reservation details, and delivery information
• Technical and usage data such as browser type, device information, IP addresses, session events, logs, and diagnostic telemetry
• Support and communication data such as messages, onboarding notes, feedback, or issue reports shared with our team

We use data only for legitimate business and service-delivery purposes. The exact use depends on the relationship you have with the platform and the features you use.

• Provision, maintain, and improve DineFork services and restaurant workflows
• Authenticate users, manage sessions, enforce permissions, and secure accounts
• Process subscriptions, invoices, renewals, and service notices
• Respond to support requests, onboarding needs, and product questions
• Monitor performance, debug issues, investigate incidents, and prevent fraud or abuse
• Measure product quality, adoption, and operational reliability through analytics and diagnostics
• Comply with legal obligations, contractual commitments, and lawful requests

Where privacy laws require a legal basis, DineFork generally relies on contract performance, legitimate interests, legal obligations, and consent where appropriate. Restaurants that use DineFork are responsible for providing any notices or obtaining any permissions required for the customer data they collect and enter into the platform.

If we process customer data on behalf of a restaurant, we do so according to the customer instructions embedded in the service configuration, user permissions, and support requests submitted by the authorized account owner or administrator.

We use cookies, local storage, session technologies, and similar tools to keep users signed in, remember preferences, improve performance, understand feature usage, and support security monitoring.

Where marketing or analytics integrations are enabled, tracking may also be used to measure campaign performance, page interactions, and conversion behavior. Restaurants may independently configure tracking tools on their guest-facing properties, and those restaurants are responsible for the notices they provide to their customers.

• Essential technologies for authentication, session continuity, and security
• Preference storage for interface, localization, or device state
• Operational analytics for product performance and troubleshooting
• Optional marketing attribution or conversion tracking where configured

We do not sell personal information. We share information only when necessary to deliver the service, support our operations, comply with the law, or complete a transaction requested by the customer.

• Infrastructure, hosting, storage, email, and communication service providers acting under confidentiality and processing obligations
• Payment processors and billing partners involved in subscription or transaction workflows
• Professional advisors, auditors, or legal counsel where necessary for compliance or dispute handling
• Government authorities or regulators where disclosure is legally required
• A successor entity in connection with a merger, acquisition, restructuring, or sale of assets, subject to applicable safeguards

We retain information for as long as reasonably necessary to provide the service, maintain records, resolve disputes, enforce agreements, or satisfy legal and accounting obligations.

Retention periods vary depending on the data type, the workspace status, the billing relationship, applicable legal requirements, and whether a customer requests deletion or account closure.

• Workspace data may be retained while the account is active and for a limited period afterward for recovery, billing, or compliance needs
• Logs and diagnostics may be retained for shorter rolling periods to support security monitoring and troubleshooting
• Backups may persist temporarily until overwritten as part of normal retention cycles

DineFork applies technical and organizational safeguards designed to protect information against unauthorized access, loss, misuse, alteration, and disruption. No platform can guarantee absolute security, but we design our systems to reduce risk and respond quickly when issues are detected.

• Role-based access controls and permission boundaries
• Tenant-aware application boundaries for restaurant data separation
• Encryption in transit and secure secret-handling practices
• Monitoring, logging, error reporting, and change-control procedures
• Controlled access to production environments and administrative functions

Depending on your location and relationship to the service, you may have rights to access, correct, export, restrict, or delete certain personal information. In many cases, the fastest route for workspace data requests is through the restaurant administrator that controls the account.

If DineFork is acting only as a processor or service provider for workspace data, we may direct requests to the relevant account owner so they can evaluate and fulfill the request under their own obligations.

• Access and correction requests
• Deletion or restriction requests where legally applicable
• Opt-out choices for certain marketing communications
• Questions about platform data handling or subprocessors

DineFork is designed for business use and is not intended for children. We do not knowingly solicit or market the service to children.

If the service is used across regions, information may be processed in locations where our infrastructure or service providers operate, subject to contractual and organizational protections. We may update this Privacy Policy from time to time to reflect product, legal, or operational changes. Material changes will be reflected on this page with an updated revision date.

For privacy-related questions, data protection requests, or policy clarifications, please contact your workspace administrator first if your request relates to restaurant workspace data. For platform-level privacy questions, billing-account questions, or public website inquiries, contact the support channel made available by DineFork.