Trust starts
in the details.
Discover our approach to account, content and publication security.
Security is part of the product
Dine treats account access, restaurant data and public menus as separate responsibilities. This security page explains the current technical approach; it is not an independent audit certificate or contractual service level statement.
Account and access boundaries
Authentication uses OIDC Authorization Code and PKCE through central Huzstudio Auth. Dine uses its own session cookie; identity, organization membership and product access are verified on the server. Restaurant content is authorized within organization boundaries.
Use a strong, unique password, do not share it and sign out on shared devices. Support will not ask for your password.
Content and media
Uploads are subject to file type and size restrictions. Preview and published menu access are different; publication is managed separately.
Only include information you intend to share in the visitor-facing menu. Verify QR codes and external links before printing.
Development and quality checks
The source includes TypeScript, unit tests, style ownership checks and browser tests. Shared UI and central token architecture help make changes traceable.
Automated tests do not eliminate every security risk. This page does not claim penetration test results, SOC 2/ISO certification, 24/7 operations or a specific availability percentage.
Report a vulnerability
If you discover suspicious activity or a vulnerability, email info@huzstudio.com with the subject “Security report”. Share the affected URL, your observation and harmless reproduction steps.
Do not access other users' data, modify records, disrupt services or publicly exploit vulnerabilities. This notice does not authorize unauthorized testing or promise a reward program.