Privacy and cookie notice — review draft

Complete the actual controller, processing inventory, provider/country list, legal bases and retention schedule before publication. This notice is not a GDPR, UK GDPR, CCPA or UAE PDPL certification. 1. Who is responsible Appwaze at Appwaze Software (appwaze.com) is responsible for the processing described in the final notice. Contact privacy@appwaze.com. Identify any required representative, privacy officer and regulator only after the applicable jurisdictions are confirmed. 2. Information and purposes to verify The implementation supports account/contact details, authentication and session records, orders/payment references, software licence/domain and installation records, support/project attachments, optional recruitment submissions and security/abuse signals. Enable only approved features and accurately disclose the fields actually collected. The final inventory must include edge/CDN providers, device or fingerprint checks, cookies/browser storage, operational logs and backup copies. Do not submit passwords, private keys or full payment-card data in support messages. 3. Lawful processing and choices List each processing purpose and its approved lawful basis in Appwaze Software (appwaze.com). Acknowledging this notice does not constitute consent to every purpose. Where consent is the selected lawful basis, describe the real opt-in, withdrawal and resulting consequences. Separate optional marketing or other optional processing from necessary account/order communications. 4. Providers and transfers Identify actual payment, email, hosting, storage, support and optional AI processors, their purposes, processing locations and applicable transfer safeguards in Appwaze Software (appwaze.com). Do not claim a particular data region, certification, contractual safeguard or lack of subprocessors without evidence. Disclose AI processing only if enabled and approved. 5. Cookies and similar technology Publish Appwaze Software (appwaze.com) with each actual cookie/storage item, purpose, lifetime, provider and applicable consent treatment. Classify security, preference and optional technology against the applicable rules. No claim is made that a banner alone establishes compliance or that every fingerprinting operation is exempt. 6. Retention and security Publish the category-specific periods or lawful criteria in Appwaze Software (appwaze.com), including financial records, support/recruitment, logs, backups and provider copies. Closure does not necessarily erase records that must lawfully be retained. Security measures reduce risk but are not a promise that breaches are impossible. Publish the approved contact and incident procedure; do not promise a fixed response or notification deadline without confirming the applicable obligation and operational capability. 7. Requests and complaints The platform provides an authenticated export and privacy-request channel. Explain the rights actually applicable, identity verification, legal exceptions, response handling and escalation through privacy@appwaze.com. Account closure, erasure and restriction are distinct operations; ensure the final notice matches what the deployed service can complete. Provide the correct supervisory authority and complaint route after jurisdiction review. Custom-work transaction records Accepted custom quotes and changes may record the 50% advance, balance, invoice/credit-note references, exact accepted scope/legal text, service-start request and contract-confirmation evidence. Successful download evidence is distinct from payment or licence issuance. Identify the actual individual controller as Appwaze Software (appwaze.com) and verify the retention/access policy for these records before publication.