This page should settle the fast trust questions before the conversation turns into a generic support thread.
Legal & privacy summary
HospiEdge Tool Legal, Privacy, and AI Use Overview
This page is the plain-language summary for policy, AI limits, record handling, and where human judgment still matters.
Important: this page is a practical product summary, not legal advice. Your company policies, employment requirements, and legal counsel still control how your organization must operate.
Read-before-action rule: if a record, incident, or coaching note could materially affect a person, verify facts first, limit access, and make sure the record is calm and defensible before saving or sharing it.
The public product story belongs on the overview page once the question becomes commercial instead of legal.
That keeps renewals, credits, and rollout help inside the owner desks after activation becomes real.
Audits, incidents, shift follow-up, coaching, accountability, and operational visibility.
Especially for discipline, safety, staffing, compliance, and guest or team-impacting decisions.
Use role-based access carefully and avoid casual sharing of internal operating data.
Write entries so a future manager can understand what happened and what still matters.
Fast rule: if the question is about policy, privacy, AI use, or whether a record is safe to keep and share, read this page first. If the question is about setup, scheduling, pricing, or rollout, route into the matching desk instead of guessing from memory.
Use legal first when the team is unsure whether AI guidance, access, retention, or a sensitive record is safe to act on.
Use support or the scheduling lane when the blocker is setup, bundle fit, rollout sequencing, or a live workflow question.
Once the account is live, owner billing, renewal, and support follow-through should move through the owner desks instead of restarting in the public funnel.
See the scheduling lane
Use the labor-planning desk when the next question is swaps, requests, scheduling rollout, or bundled labor value.
Route a policy or trust questionSend support the legal page context when the question is real and you need a routed follow-up instead of a generic ticket.
Return to the platform overviewUse the overview when the conversation shifts back to buyer fit, rollout shape, or the broader product story.
Go to the owner billing deskActive owners should move into billing, plan, renewal, and support follow-through without losing the story.
✅ Acceptable Use
Use HospiEdge Tool for restaurant operations, standards, accountability, leadership visibility, and documented follow-up. The system is meant to make real operating records easier to trust and easier to review later.
Use it for
- Audits, incidents, manager notes, daily review, and operating follow-up.
- Leadership coaching and accountability records tied to a real operating context.
- Tracking actions, timestamps, and workflow history across locations or shifts.
Do not use it for
- Harassment, unlawful monitoring, retaliation, or misuse of employee or guest information.
- Sharing credentials, invite codes, or internal operating data with unauthorized people.
- Entering false, exaggerated, or intentionally misleading records.
Plain language: if a record would be embarrassing, unclear, or impossible to defend later because it is emotional instead of factual, rewrite it before saving.
🤖 AI Advisory Notice
AI summaries, coaching prompts, drafts, and operational suggestions are support tools. They can help a manager move faster, but they do not replace investigation, judgment, policy review, or legal compliance steps.
Check the facts first
Make sure the people, dates, events, and operating details in the record are accurate before using any AI-generated summary.
Use human judgment
Managers remain responsible for decisions involving staffing, discipline, safety, guest recovery, and escalation.
Follow policy before acting
When a decision touches compliance, employment rules, or legal risk, company policy and professional advice matter more than generated suggestions.
Do not rely on AI alone for disciplinary decisions, termination decisions, pay issues, safety incidents, legal notices, or anything that could materially affect an employee, guest, or business obligation.
🗂️ Data Handling
The platform may store the information needed to power operational workflows and preserve useful history. That can include identity details, notes, scores, timestamps, incident details, attachments, and location context.
Data principle: collect what the workflow truly needs, keep access limited, and write entries as though another authorized leader may need to rely on them later.
- User context: account identity, role, or location-linked workflow access.
- Operational records: audits, incidents, handoff notes, scores, comments, and follow-up activity.
- Timing context: service dates, timestamps, and shift or location history needed for continuity.
- Workflow evidence: notes, attachments, or photos when the product surface supports them.
🕰️ Retention & Continuity
Historical records often matter long after a shift ends. Removing them too casually can damage accountability, reporting continuity, and leadership visibility.
Usually the better move
Disable or change a user’s access while keeping legitimate historical records intact so leadership still has a consistent business history.
Why continuity matters
Past audits, incidents, and manager notes may be needed to understand repeat issues, training gaps, guest problems, or accountability history.
Plain language: do not treat record deletion as normal cleanup. If the business may need the history later, preserve it and adjust access instead.
📋 Operator Checklist
Use this checklist before saving a sensitive record, sharing a report, or acting on AI-supported guidance.
- Confirm the record is factual, specific, and readable by another authorized leader.
- Make sure the people, dates, and location context are correct.
- Check whether AI output needs human edits before it is used or shared.
- Keep access limited to the managers or leaders who should actually see it.
- Preserve records needed for continuity instead of deleting them casually.
- Escalate to company policy, HR, legal counsel, or ownership when the situation exceeds a normal operating decision.
❓ Quick FAQ
Fast answers to the questions operators usually ask first.
Can AI decide what action to take?
No. AI can suggest language or summarize context, but a human manager must review the situation and make the decision.
Should old incident or audit records be deleted?
Usually no. Historical records often matter for continuity. Adjust access first and preserve legitimate operating history when it may still be needed.
Who should access records in the app?
Only authorized users with a real need to view that information as part of their management or leadership role.
What makes a good record?
A good record is factual, specific, calm, and useful to another leader who may need to understand the situation later.
Confidence handoff
Keep trust answers, buyer proof, and owner follow-through on one connected route.
Use legal for AI, privacy, access, and record-trust questions. Use the platform overview for fit and pricing context. Use support and billing when the question becomes routed follow-through for a real owner or rollout path.