Hallify

Legal draft

Terms of Service

Working terms for Hallify accounts, venue workspaces, pilot access, and operational use before final counsel review.

Last updated: June 3, 2026
Prepared for legal review before public launch

This document is a product-accurate draft prepared for lawyer review. It is not final legal advice, and the final legal entity, address, governing law, liability language, breach timelines, and regional notices must be confirmed before launch.

1. Scope and acceptance

These Terms describe the draft rules for using Hallify, including public pages, account access, venue workspaces, and operational modules for restaurants and hospitality teams.

By creating an account, signing in, accepting an invitation, or using a Hallify workspace, users agree to follow these Terms and any role-based rules set by the venue owner or administrator.

  • The final legal entity, address, governing law, and enforceable notices are placeholders until counsel confirms them.
  • If a signed customer agreement conflicts with these public Terms, the signed agreement should control for that customer.

2. Accounts and eligibility

Users must provide accurate account information, protect credentials, and notify Hallify or the venue owner if account access may be compromised.

Venue owners and administrators are responsible for inviting the right staff, assigning appropriate roles, and removing access when a person no longer needs the workspace.

  • Accounts may be used by owners, managers, floor staff, kitchen staff, and other authorized venue personnel.
  • Users may not share passwords or use another person's account.

3. Venue workspaces and customer data

Hallify workspaces are designed for restaurant operations: rooms, tables, reservations, waitlists, guests, POS, kitchen queues, inventory, staff, payroll settings, analytics, and audit-safe workflows.

The venue is responsible for the accuracy, lawfulness, and internal handling of data entered into its workspace, including guest, staff, supplier, order, payment, schedule, tip, and payroll-related records.

  • Hallify may process venue-controlled operational data to provide the service.
  • Venue administrators should configure roles so staff only sees the data needed for their work.

4. Acceptable use

Users must not misuse Hallify, interfere with the service, attempt unauthorized access, upload unlawful content, or use the product to harm guests, staff, venues, or Hallify systems.

Hallify may suspend or limit access when needed to protect security, prevent abuse, enforce these Terms, or comply with law.

  • Do not enter payment card numbers, government identity numbers, health records, or other sensitive data unless Hallify has explicitly provided a supported field and agreement for that use.
  • Do not use guest CRM notes for discriminatory, harassing, or unlawful profiling.

5. Pilot access and future pricing

Hallify is under active development. Features available during pilot or pre-launch access may be free to try until public launch pricing is enabled.

Future paid plans, invoicing, taxes, renewal terms, and cancellation rules must be confirmed in public pricing, an order form, or a signed agreement before they become binding.

6. Availability and product changes

Hallify aims to provide reliable restaurant operations software, but pre-launch features may change, pause, or be removed as the product matures.

The service may be unavailable during maintenance, incidents, infrastructure issues, third-party outages, or events outside Hallify's control.

  • Hallify should not be the only source of legally required employment, payroll, tax, or accounting records unless a signed agreement says so.
  • Venues should maintain operational backups for critical business records during the pilot period.

7. Suspension and termination

A venue may stop using Hallify, and Hallify may suspend or terminate access when a user or venue violates these Terms, creates security risk, or uses the service in a way that could harm others.

Data export, deletion, and retention after termination should follow the Privacy Policy, DPA, signed customer agreement, and counsel-confirmed retention schedule.

8. Disclaimers and counsel-confirmed clauses

Before launch, counsel should finalize warranty disclaimers, limitation of liability, indemnity, dispute resolution, governing law, regional consumer notices, and any mandatory local clauses.

Until those terms are finalized, this page should be treated as a strong product/legal draft and not as the final contract Hallify relies on in production.

Questions or legal requests

Email hello@hallify.co and include the venue, account, or request context so Hallify can route the request correctly.

Contact Hallify