Security and Privacy Overview for Closeout Pilots
This is a high-level summary. It should not be read as a certification claim, legal warranty, or complete security architecture disclosure.
The purpose is to make the public security posture easier for crawlers, partners and reviewers to understand without exposing private implementation details, secrets, customer data, credentials, or unsupported compliance claims.
Data context
Tillzen may process restaurant operating records such as closeout records, cash counts, deposit evidence trails, variance notes, tip-related records, user account information and workflow metadata provided through the product or website.
Those records can include manager-submitted context and finance review follow-up. Restaurant operators should decide which employees, advisors, partners and reviewers are permitted to see each class of record before a pilot begins.
Security posture
- Use role-based access patterns so users see the operational records they are permitted to review.
- Use secure transport for website and product traffic where applicable.
- Keep sensitive operational records scoped to the customer context.
- Avoid exposing secrets or credentials through public pages or generated assets.
- Prefer reviewable audit trails for records, changes and owner decisions.
Claim boundaries
Tillzen public pages should avoid claiming certifications, native partner status, approved marketplace status, or guaranteed loss reduction unless those claims are verified. Security and compliance language should describe current posture and available review paths rather than overstate assurance.
For a restaurant pilot, the practical security goal is controlled access to the daily record, not public disclosure of the full technical implementation. A buyer can review privacy, terms and security contact details before deciding whether the pilot scope is appropriate.
Privacy posture
Tillzen describes data handling in its privacy policy. Restaurant operators should review the policy and their own legal requirements before adopting any workflow involving employee, payroll, tip, or financial records.
Tip, payroll, wage and employment-related records may create additional obligations depending on jurisdiction and customer workflow. Operators should involve counsel or qualified advisors when a pilot touches those records.