Skip to main content
Essal LLC, QFC number 02195, operates Essal and Essal Work. This proposed notice explains personal-data handling across essal.qa, essal.it.com, essal.cloud, admin.essal.cloud and essal.work. It is a review draft and does not yet replace an existing notice.

Who is responsible

Our registered office address is 9th floor, QFC Tower 1, Westbay, Doha, Qatar. Contact legal@essal.it.com for privacy enquiries and rights requests. Essal is a controller when deciding how to use business-contact information, account-administration information, enquiries and information needed for its own security and legal obligations. When a business customer decides why and how personal data is used in its workspace, that customer is the controller and Essal processes it on its behalf under the data processing agreement. Some functions can involve both roles for different purposes; a customer uploading information does not make Essal the controller of every use. If your employer or another organisation provided your account or collected your information through an Essal product, its privacy notice explains its purposes and decisions. Contact it first for workspace-data requests. Essal will help route a request and assist the controller as required, rather than disclosing another customer’s data.

Information and purposes

The information involved depends on the website, product, enabled features and the information you or your organisation supplies. Business-contact processing is not automatically based on a contract with the individual simply because their employer is a customer. Where we rely on legitimate interests, those interests are the business-service, support, security or administration purposes stated above, balanced against your rights. We do not treat submitting a form, accepting software terms or sending an enquiry as blanket marketing consent. Customer-controlled product data can include employee and visitor records, access logs, customer visits and location information, applicant records and recruitment documents, assets and custody records, projects and collaboration content, and security-training or simulation records. The customer’s instructions, enabled product and processing schedule determine the actual scope and lawful basis. Avoid submitting sensitive information that is not necessary or authorised for the service.

Sources and required information

We receive information from you, your organisation’s administrators and authorised users, your device’s service requests, connected systems you authorise, and Paddle for relevant transaction information. If we obtain information indirectly for our own purposes, we provide the required notice within the applicable period or identify a lawful exception. Information needed to identify an authorised user, respond to your request, secure an account or fulfil a purchase may be required for that purpose. If you do not provide it, we may be unable to provide the requested function or response. Optional analytics and marketing choices are not conditions of access to the paid core service.

Recipients and service providers

Authorised Essal personnel and contracted providers receive information only as needed for their roles. Providers confirmed for the service environment include Cloudflare, Railway, Resend, PostHog and Google Analytics. Better Auth is authentication software hosted on Railway; its name alone does not mean personal data is sent to a separate Better Auth service. The role and product scope of each provider are described in service-provider information. Paddle is the reseller and Merchant of Record for Paddle purchases and handles personal information for its transaction, fraud-prevention, tax and legal responsibilities under Paddle’s privacy notice. Its applicable data-sharing arrangements include independent-controller processing; Paddle is not universally an Essal subprocessor. We may disclose information where legally required, to protect lawful rights or investigate security incidents, to professional advisers under appropriate confidentiality, or in a lawful business reorganisation with applicable safeguards and notices. We do not grant an unrestricted right to use customer content for third-party marketing through this notice.

Locations and international transfers

Essal’s stated application-hosting regions are Doha, Qatar, and Germany, with placement selected according to the region closest to the user. This describes the stated hosting approach, not a guarantee that every record, backup, email, support interaction or analytics event remains in those locations. Network services and other providers can process information in additional countries under their applicable arrangements. Transfers outside the QFC require a valid mechanism under the QFC Data Protection Regulations. Depending on the recipient and destination, this may be an applicable adequacy determination, approved contractual safeguards or another legally available mechanism. A hosting region or a provider’s generic GDPR statement is not itself a QFC transfer mechanism. You may ask legal for the relevant recipient, location and a copy or explanation of applicable safeguards, subject to necessary redactions.

Retention and deletion

Essal’s stated general retention period is six months from collection. A new login or unrelated account activity does not restart that period for an older record. Product schedules must distinguish data subject to this general rule from records that must be kept for a specific legal obligation or documented legal hold. We retain those exceptions only for the applicable obligation and do not use an accounting exception to keep unrelated product content. Users can request deletion through the app at any time or contact legal. A request must be assessed in light of identity, the organisation’s controller role, other people’s rights and applicable retention duties. For data processed for a customer, we act on authorised instructions and help the customer respond. A deletion request includes relevant backup copies; the applicable product’s deletion process must address them as well as live data. We do not promise that a request erases a separate controller’s legally required transaction records.

Your rights

Subject to the applicable conditions and exceptions, you may request access, correction, erasure, restriction, objection and portability of personal data, and exercise rights concerning solely automated decisions with legal or similarly significant effects. You may withdraw consent at any time without affecting the lawfulness of processing before withdrawal. Object to direct marketing at any time using an unsubscribe mechanism or by contacting legal. Send a request to legal@essal.it.com, describing the information and relationship concerned. Do not send identity documents unless reasonably requested through an appropriate channel. We may seek proportionate identity or authority confirmation. Under the QFC framework, we must respond without undue delay and ordinarily within 30 days; a permitted extension requires notice and reasons within the initial period. We will explain a refusal or applicable exception and available complaint rights. You may complain to the QFC Data Protection Office if you believe processing infringes the QFC regulations. See the QFC data protection website for current complaint channels. Contacting Essal first is helpful but does not remove your right to complain directly.

Cookies, analytics and decisions

Read the cookie policy for browser storage and controls. Essal has confirmed that optional PostHog and Google Analytics are blocked until analytics consent. You can decline optional analytics and withdraw consent; that choice must not affect access to essential paid functionality. Your organisation remains responsible for its use of product information in hiring, employment, access and other consequential decisions. This notice does not authorise undisclosed automated profiling. If a service uses automated decision-making requiring additional notice or safeguards, those must be provided for that actual use before it occurs.

Security and changes

We must use technical and organisational measures appropriate to the processing risks. The agreed DPA and processing schedule define relevant obligations. We do not claim that a service is risk-free or that a certification exists unless it has been verified. Material changes will be identified with an effective date and communicated appropriately. Changes do not create consent retrospectively or silently amend the basis for previously collected information. See policy versions.