You can request access, correction, an export or deletion without having the app installed. Closing a login, closing a business account and disposing of food-safety evidence are separate requests. Make a request Email info@salixtech.co.nz. Include your business name or kitchen code, the account email where applicable, the request type and records/date range concerned. We verify identity and authority before disclosing, changing or deleting information. Do not email your password, staff PIN, recovery codes or unnecessary health details. Staff can contact us directly or their employer. We coordinate with the business responsible for its records; asking a manager is not a condition of exercising your personal information rights. For access and correction requests we respond as soon as reasonably practicable and normally within 20 working days, subject to lawful extensions and notification. For deletion or full exports we confirm scope, any retention constraints and an estimated timeframe; we do not promise automatic deletion within a fixed period. Export your business evidence Authorised managers and owners can export supported operational evidence as PDF and CSV. The verifier pilot also provides supported review reports and structured exports under its access controls. These are evidence exports, not a self-service download of every database row or attachment. For a complete customer exit, contact us before closing access. Agree the sites, record range, attribution, attachments, scope/review snapshots and other required formats. Verify delivery and completeness before authorising disposal. Recipient copies and downloaded files remain under the recipient’s control. Delete a login or close a business account An individual login or roster identity can be deactivated or removed where appropriate. This does not automatically remove historical records they created for a food business. An organisation owner can request business account closure. We confirm authority, subscription arrangements, export requirements and retention obligations before changing access or disposing of data. If Jane recorded a cooking check and then leaves, her access can end while the cooking evidence retains necessary attribution. Any correction or redaction must preserve required evidential integrity. Retention, legal holds and backups Retention depends on the record, the customer’s applicable food-safety duties and agreements, and any lawful hold. There is no single deletion period that applies to every operational record, attachment, health detail, log and backup. We explain applicable constraints when handling a request. Existing health-detail redaction uses a default of 365 days from the applicable clearance/review/report anchor, subject to configured policy and review. Website enquiry cleanup targets enquiries older than 24 months. These are service settings, not a statement that every record must legally be kept for those periods. Immutable review/scope snapshots, attachments and audit history may contain names even after a login is removed. They need their own authorised retention/disposal decision. We do not promise blanket anonymisation that would silently rewrite evidence. Backup copies have a separate expiry cycle. The revised database recovery process is designed for 35-day daily-copy retention; production activation and uploaded-file coverage remain to be verified. Restoring a copy must reapply authorised deletion/redaction decisions before restored information is made available. Information on your devices Signing out does not automatically erase unsynced food-safety records. Reconcile pending work before replacing, resetting or uninstalling a device. A deletion request cannot remotely erase recipient downloads or an offline device; contact us for a safe reconciliation and disposal process.
This page needs JavaScript to display in full.