1. Parties, scope and instructions
The customer identified in the order is the controller and Essal LLC, QFC 02195, is the processor for customer-controlled personal data. If the customer acts as a processor, it must have the relevant controller’s authority and communicate applicable instructions. Each party remains responsible for processing for which it independently determines purposes and means. The order and processing schedule identify the product, processing purpose, operations, duration, personal-data categories, data subjects, locations and authorised subprocessors. The customer’s lawful configuration, documented support requests and this agreement provide instructions within that scope. Essal must not process for its own unrelated advertising, sell the data or train unrelated models on it under this DPA. Essal must promptly inform the customer if, in its opinion, an instruction infringes applicable data-protection law. If law requires processing beyond instructions, Essal must notify the customer beforehand unless prohibited by law. The parties will resolve unlawful instructions before continuing affected processing.2. Confidentiality and security
Essal must limit access to authorised persons who need it and are subject to confidentiality duties. It must implement technical and organisational safeguards appropriate to the risks and document the safeguards applicable to the service. The processing schedule must identify implemented access controls, authentication, tenant isolation, encryption arrangements, logging, recovery and deletion measures; this draft does not assert an unverified implementation or certification. Essal must assist the customer with its applicable security and data-protection obligations, taking into account the processing and information available to Essal. Customer administrators remain responsible for their permissions, lawful instructions and connected systems.3. Subprocessors
Essal must obtain the customer’s prior written authorisation before appointing another processor. The accepted order or schedule identifies the initial authorised list. Where the customer gives general written authorisation, Essal must inform the customer in advance of additions or replacements and provide a reasonable opportunity to object on data-protection grounds before access begins. Essal must impose equivalent applicable protection obligations in a written subprocessor agreement and remain responsible for the subprocessor’s relevant performance. An unresolved justified objection must be addressed by an appropriate alternative or ending the affected processing with an agreed remedy. A public provider list alone is not the customer’s written authorisation. See provider information. An independent controller, such as Paddle for its transaction purposes, must not be inaccurately described as a processor for all purposes.4. International transfers
Essal must not transfer personal data outside the agreed processing scope or permitted locations without applicable instructions and lawful safeguards. Transfers outside the QFC must comply with its Data Protection Regulations, including a relevant adequacy determination or another valid mechanism. Use QFC-appropriate clauses where required; EU or UK clauses must be added where those laws also apply and are not automatically a substitute for QFC requirements. The stated application-hosting approach uses Doha or Germany according to user proximity. The accepted schedule must identify actual storage and remote-access locations, backup locations and onward recipients for the product. Routing by proximity alone is not a transfer safeguard or a contractual residency guarantee.5. Assistance and incidents
Essal must assist the customer with rights requests, required notices, DPIAs and consultation with authorities, taking into account its role and available information. If Essal receives a request about customer-controlled data, it must promptly notify or route it to the customer and must not respond substantively except on instructions or as legally required. Essal must notify the customer without undue delay after becoming aware of a personal-data breach affecting the customer’s data. It must provide available information about the nature, affected data and people, likely consequences, mitigation and a contact, and supplement it as information becomes available. It must cooperate with investigation, containment, recovery and notification duties and preserve relevant records securely. The customer remains responsible for its own regulator and individual notifications; the processor’s notice does not replace them.6. Retention, return and erasure
The stated general product-data retention rule is six months from collection, subject to valid shorter instructions, an approved product schedule and specific legal duties. Continuing to use an account does not reset the collection date of older records. Data under a documented legal hold must be limited to what the hold requires. At the customer’s choice, after the processing services end, Essal must return or delete the personal data and delete remaining copies unless applicable law requires retention. Users may request deletion in the app at any time; Essal must assess authority and carry out lawful controller instructions. The agreed procedure must address live data, replicas, exports under Essal’s control and backups, and prevent a restore from silently reintroducing erased data. The schedule must specify the verified process and completion period rather than treating every request as an instantaneous physical backup purge. Where law requires retention, Essal must identify the basis where permitted, isolate the retained information and restrict processing to that requirement. It must provide reasonable confirmation of return/deletion on request. Separate controllers’ accounting records are not subject to customer erasure instructions under this DPA.7. Evidence and audits
Essal must make available information reasonably needed to demonstrate compliance and permit audits or inspections required by applicable law. The parties may agree practical scope, confidentiality and scheduling measures that do not frustrate legal audit rights. Essal must maintain appropriate processing records and cooperate with competent authorities.8. Processing schedule and execution
The following schedule describes the intended categories; the accepted order must select the actual products and complete operational details before processing begins:
Processing operations include collection on instructions, storage, retrieval, display to authorised users, configured transmission, support, export and deletion. Duration is the agreed service term with the retention and termination rules above. Sensitive data is not authorised by a generic product subscription: identify any necessary sensitive processing, legal basis, safeguards and required approvals separately before it starts.
Before execution, the product schedule must identify actual locations, the authorised subprocessor list and legal entities, implemented security measures, transfer mechanism and deletion/backup completion process. Contact legal@essal.it.com to complete the schedule. Until those items are agreed, this draft must not be presented as an executed, complete customer DPA.