Privacy Policy

Version 1.0 — Initial review draft. This text describes implemented behaviour, not final legal approval. Before external publication, the operator must confirm legal identity, processing purposes/bases, retention, processors, applicable rights and contact arrangements. Account and business profile: name, email, password hash, email-verification/security state and the business/contact details supplied by the account holder. Passwords are hashed, never stored as readable passwords. Subscriptions and billing: plan, status and dates, plus administrator-entered billing amount, currency, period, reference and payment date. No online payment gateway or card-authorisation service is implemented. Device and licensing: server device ID, installation ID, reported platform/OS/app versions, activation and last-seen dates, signed-license metadata, credential lifecycle, transfer requests and their history. Reported device values are not absolute hardware proof. Signing private keys are not distributed to the app. Legal acknowledgements: user, document/version, acceptance date and source are recorded. This acceptance ledger does not store IP or user agent. Separate security/admin audit records may contain request IP and user agent, event type, actor and redacted change metadata. Contact forms and technical operation: messages/contact fields you submit are stored for authorised follow-up. Necessary session/security data, token digests, rate-limit state and operational logs support authentication, protection and troubleshooting. Do not submit passwords, tokens, private keys or confidential operational exports. Local POS business data: V1 does not upload products, inventory, sales/items, returns, expenses, cash movements or local invoices to this server. They remain in the Windows SQLite database. Printing settings/assets and business backups are also local. There is no cloud synchronisation or hosted POS backup. Local working SQLite is not encrypted; Windows account/disk protection and safe encrypted backups remain your responsibility. Cookies: only necessary session, form-protection, remembered-login (when selected), language/session preference and cookie-notice preference behaviour is configured. No analytics or marketing integration exists. See the Cookie Policy for the current controls. Access and requests: authorised administrators operate accounts, entitlements, releases and enquiries. Contact CTRLZ-tech through the Contact page or official company website about data questions. Final retention/deletion periods, processors and jurisdiction-specific request handling must be approved before external use; this draft does not promise automatic erasure or a response deadline.