PRE-PUBLICATION DOCUMENT SET
Legal and privacy information
This page records how the current Tablety Manager implementation works. It must receive business and UK legal approval before production publication. The registered address, company number, privacy contact, retention schedule and final commercial clauses have not been supplied and are deliberately not invented here.
- Operator
- Touch Table Limited
- Document version
- 2026-09-28.1
- Status
- Draft for approval
PRIVACY NOTICE
How Manager uses information
Tablety Manager processes administrator account details, organisation and location assignments, table registration and health information, licence and configuration records, security events and audit history so authorised customers and TableBuddy staff can operate the service securely.
Information in the service
- Administrator name, work email address, account status, role and permitted locations.
- Organisation, location, subscription, invoice and licensing records.
- Device identifiers, application version, last contact, configuration state and operational diagnostics.
- Configuration changes, acknowledgements, usage reports and security/audit events.
- Technical request information required to secure and operate the service, such as timestamps and network/security logs.
Current boundaries
The Manager does not provide remote desktop access, collect table-user profiles, or use Google Analytics. Device communication is initiated outbound over encrypted connections. Secret signing keys, database credentials and Cloudflare credentials are not delivered to the browser.
Before publication
The final approved notice must add the controller and contact details, purposes and lawful bases, recipients and processors, international-transfer safeguards, retention periods, individual rights, complaint route and any customer-specific controller/processor responsibilities.
COOKIE NOTICE
Essential sign-in storage only
The current service uses a first-party tablebuddy_session cookie to keep an authorised administrator signed in and rotate the secure session. It is restricted to authentication routes, is unavailable to browser JavaScript, uses SameSite protection and is marked Secure in production. Its maximum lifetime is 30 days and it is cleared on sign-out.
The browser holds the short-lived access token in page memory only. It is discarded on reload or navigation, then restored through the secure HttpOnly refresh cookie. Only in-progress Quick Admin drafts use session storage, which is cleared when the browser tab is closed; signing out explicitly clears the Manager session state and saved drafts.
No advertising, behavioural tracking, Google Analytics or other optional analytics cookies are currently loaded. Consequently, the present implementation does not show a consent banner. If optional tracking is introduced, it must remain disabled until the required consent control is implemented and this notice is updated.
SERVICE TERMS
Commercial terms require approval
The customer contract should govern authorised use of Tablety Manager and the licensed TableBuddy installations it controls. The product boundary is clear: Manager controls content, configuration, visibility, reporting, licensing and recovery; approved Windows or Android deployment tools control installation and operating-system maintenance.
Final terms must be agreed before customers are asked to accept them. They should cover subscription and payment, authorised users, acceptable use, customer content, support and service levels, offline behaviour, security responsibilities, intellectual property, third-party services, suspension, termination, data return/deletion, warranties, liability, governing law and the order of precedence with the customer agreement and DPA.
No acceptance checkbox is enabled while these terms remain a draft. Once approved, the service should record the accepted document version, user, organisation and timestamp.
DATA PROCESSING
Customer DPA framework
A Data Processing Agreement should be made available where Touch Table Limited processes personal information for a customer. It should identify the parties' roles, subject matter and duration, data categories and people, documented instructions, confidentiality, security, subprocessors, international transfers, assistance with rights and incidents, deletion or return, and audit arrangements.
Education and care deployments require particular care. The remote administration design should continue to avoid names or profiles for children, residents, patients or visitors unless a separately assessed feature genuinely requires them.