Authenticated Access
MealLock requires authenticated user sessions before protected application pages and facility records can be accessed.
MealLock Security
Protecting access to organized meal records
MealLock combines authenticated access, facility-separated records, protected application routes, and secure cloud infrastructure to support responsible meal-documentation workflows.
Current Safeguards
Security throughout the MealLock experience
Security is incorporated into how users sign in, access facility information, document meals, and retrieve records.
Facility-Separated Records
Facility-linked records and database access policies are designed to prevent one community from accessing another community’s information.
Protected Application Routes
MealLock checks authentication before allowing access to protected dashboard, resident, meal, compliance, and reporting workflows.
Encrypted Transmission
MealLock is delivered through HTTPS, helping encrypt information while it travels between supported browsers and the application.
Staff Accountability
Meal records can include responsible staff members, dates, and timestamps to support a clearer and more reviewable documentation history.
Established Cloud Infrastructure
MealLock uses established cloud technology providers for application hosting, authentication, database services, and secure application delivery.
Shared Responsibility
Facilities remain an essential part of security
No software can protect information by itself. Each organization is responsible for its users, devices, internal policies, information accuracy, and regulatory obligations.
- ✓Provide access only to staff members who are authorized to use MealLock.
- ✓Use individual user accounts rather than sharing passwords between staff.
- ✓Protect login credentials and report suspected unauthorized access promptly.
- ✓Remove or update access when a staff member changes roles or leaves the organization.
- ✓Use supported devices, current browsers, and appropriately secured internet connections.
- ✓Review resident and meal information for accuracy before relying on exported reports.
- ✓Follow the facility’s own privacy, retention, documentation, and regulatory policies.
Data Access and Requests
Exporting or requesting changes to data
MealLock includes supported report-export functionality. Customers may also contact MealLock regarding account access, data correction, export, retention, or deletion requests. Requests are handled according to the applicable customer agreement and legal or operational retention requirements.
Security Concerns
Report suspected unauthorized access
Suspected credential exposure, unauthorized account activity, or other security concerns should be reported promptly to MealLock for review.
ryansuggs@meallock.com →Healthcare and Regulatory Notice
Technology is only one part of compliance
MealLock supports documentation and operational workflows but does not provide legal, clinical, dietary, regulatory, or compliance advice.
Use of MealLock alone does not make an organization compliant with HIPAA or any other law. Organizations are responsible for determining which laws apply to them and whether a Business Associate Agreement or other written data-protection terms are required before regulated information is entered.
Have a security or implementation question?
Contact MealLock to discuss your community’s access, documentation, and implementation requirements.
Last updated July 30, 2026