This draft describes personal information handled through the My Temp Shield website, customer application, managed devices, and support workflows. It covers prospects, authorized customer users, and people whose identity or contact details appear in operational records. Our legal business name, address, and privacy contact remain review items shown above.
Restaurant organizations decide who may access their accounts and why their staff use the service. We process their operational records to provide the service. Our role and any additional data-processing obligations depend on the customer agreement and applicable law. Contact your organization about its own employee-monitoring and recordkeeping practices.
Information provided by people and organizations
Account information includes names or usernames, email addresses, roles, store assignments, invitations, and account status. Notification configuration may include email addresses, telephone numbers, recipient roles, and routing preferences. Walkthrough and support requests may include business contact details, store information, and the message you submit.
Operational records include station and device identifiers, temperature measurements, observation times, manual entries, corrective-action notes, incident responses, and the identity of the person taking an action. Internal support and configuration activity can also be recorded for accountability. Please do not enter unrelated sensitive personal information in notes or requests.
Information collected through operation of the service
The service receives equipment readings, connectivity and device-health information, synchronization status, and technical records needed to operate the system. Hosting and security services may process IP addresses, request metadata, browser or device information, and authentication and security events.
Where diagnostic monitoring is enabled, we use error and performance information to investigate failures. Configured session replay may capture masked representations of application activity. Diagnostic settings, exclusions, and masking are subject to configuration; they are not a reason to enter confidential information in an unintended field. Legal review must confirm the final disclosure and any consent requirements for the deployed diagnostic features.
How information is used
We use information to authenticate users, enforce store and role access, operate monitoring, record checks and incident responses, route notifications, provide authorized history and reports, manage installations, and respond to requests. We also use relevant information to investigate errors, protect the service, prevent misuse, and maintain accountable support and configuration activity.
A request for a walkthrough lets us respond about the requested service. It should not be treated as permission for unrelated marketing. Review item: confirm any separate marketing program, its consent mechanism, and its unsubscribe process before describing it as an active practice.
Who can receive information
Authorized people in your organization can access information according to their role and assigned stores. My Temp Shield personnel may access relevant information for installation, support, administration, and service protection within their authorized scope. Notification recipients receive the incident information routed to them.
We use service providers for hosting, storage, message delivery, and diagnostics. The implementation uses Amazon Web Services, Resend for supported email delivery, Amazon SNS for supported SMS delivery, and Sentry where diagnostics are enabled. Which providers process a particular account's data depends on the services enabled. We may disclose information when required by law or necessary to address fraud, security, or legal claims, subject to applicable requirements.
Review item: confirm the complete provider list, processing locations, and whether any practice constitutes a sale, sharing for advertising, or targeted advertising under applicable law. This draft does not infer those legal conclusions solely from the software implementation.
Browser storage, devices, and offline operation
The application uses cookies and browser storage for functions such as authentication, session protection, and preferences. Managed appliances also retain device identity and approved configuration. Blocking or clearing storage can affect sign-in, saved preferences, or managed-device operation.
During supported offline operation, readings and related attribution may be retained on the authorized gateway until synchronization is possible. Pending and rejected evidence can have different retention rules from synchronized cloud records. An offline status does not mean that an entry has been uploaded or that its retention has ended.
Retention and security
Generated PDF and CSV reports require current access to every included store. Download eligibility ends seven days after the request; export files are scheduled for cleanup after seven days in storage, and request metadata becomes eligible for cleanup after 30 days. Cleanup is not instantaneous, and backup retention can differ. Expiring an export does not delete its underlying readings or incident records.
Retention depends on the type of record, the customer's service and configuration, operational and security needs, and applicable obligations. Readings, account records, support records, notification delivery records, and backups do not necessarily share one retention period. The final notice must identify the applicable periods or criteria without substituting a demonstration value for the real service.
We use access controls and technical measures intended to protect information. No storage or transmission system can be guaranteed secure. Removing staff access does not automatically remove attribution from historical checks or audit records. Deletion requests may be subject to identity verification, the customer's authority over the records, and lawful retention requirements.
Your choices and requests
Authorized customer managers can update staff access and supported notification contacts. Review item: the business must provide a working privacy contact and request process for correction, access questions, and privacy concerns. Do not send passwords or offline PINs in a request.
Depending on the law that applies, you may have additional rights concerning access, correction, deletion, portability, objection, or consent. We may need to verify a request and coordinate with the customer organization. Review item: counsel must confirm applicable jurisdictions, response procedures, appeal or complaint routes, and any required international-transfer disclosures before final approval.
Business use and changes to this notice
My Temp Shield is intended for authorized restaurant business use and is not directed to children as a consumer service. Customer organizations may have employees of different ages; they are responsible for authorizing employee access appropriately. Tell us if information was provided without the necessary authority so the situation can be reviewed.
We will keep this notice aligned with the service's actual information practices. Material changes must follow any notice or consent requirements that apply. The date shown above identifies this review draft; it does not imply that legal review has been completed.
Review item: the business must supply a working legal and privacy contact before these drafts are approved. Do not send passwords, offline PINs, or identity documents through a walkthrough request.
