jezahost

Privacy Policy

ბოლო განახლება: 16.11.2026
ოფიციალური ტექსტი: https://cloud.jezahost.com/legal/privacy?lang=ka

ამ დოკუმენტის ქართული ვერსია ჯერ არ გამოქვეყნებულა. ქვემოთ ინგლისური ვერსიაა მოცემული.

Last updated: 16.11.2026 · Provider: JEZA CLOUD LLC (TIN 1606154731)

Scope: jezahost.com (website) and cloud.jezahost.com: cloud servers (VPS / IaaS), email hosting, static IP address

This document explains which personal data we process, for what purposes and on what legal basis, to whom we pass it, how long we keep it and what your rights are. It complies with the Law of the Republic of Azerbaijan "On Personal Data" and is built to the standards of the EU General Data Protection Regulation (GDPR) and the ePrivacy rules. Service conditions are in the "Terms of Service" and service levels in the "SLA"; definitions are in Terms of Service §1.

1. Controller

JEZA CLOUD LLC · TIN 1606154731 · Bakı şəh., Nizami ray., Q.Qarayev pr. ev.84, AZ1096

Privacy requests: [email protected] or the ticket system inside the portal. No separate data protection officer (DPO) has been appointed; requests are answered at the address above.

2. Purposes of processing and legal bases

Legal bases are given under Article 6(1) GDPR: (a) consent, (b) performance of a contract or steps prior to entering into it, (c) legal obligation, (f) legitimate interest.

2.1 On the website (jezahost.com)

PurposeDataLegal basis
Answering your enquiry, preparing a quote (contact form, calculator)name, company name (if any), email, phone (if any), message(b) pre-contractual steps
Operating the website, language choice, bot protectionnecessary cookies (§3), network requests(f) secure operation of the website
Anonymous, cookie-free website traffic statistics (Cloudflare Web Analytics)page views, referring page, country, browser and device type, page load performance, without cookies or identifiers(f) legitimate interest: improving the website; no consent required
The website's own visit log (cookie-free)time, page, referring page (from external sites only the address and path), site and browser language, UTM and ref parameters, country, shortened IP address (the last part of IPv4 and everything after /48 in IPv6 is removed); without cookies, identifiers or browser details (user agent)(f) legitimate interest: improving the website; no consent required
Measuring website usage (Google Analytics 4)analytics cookies, usage events (§3)(a) only with your consent
Measuring advertising effectiveness and remarketing (Google Ads)advertising cookies, conversion events, advertising source (jh_utm) (§3)(a) only with your consent
Proof of your cookie choiceconsent record (§3.4)(c) obligation to demonstrate consent

The name, email and phone you enter in a form are not passed to Google, not even in hashed form. This data is not sold, rented or shared with third parties for marketing purposes.

2.2 In the portal (cloud.jezahost.com)

CategoryWhat is storedPurposeLegal basis
Accountfirst name, last name, email, phone, country, customer type (individual / legal entity), cryptographic hash of the passwordsupply of the service(b)
Legal entitycompany name, TIN, registered address, contract number and date, record of TIN verificationcontract, invoicing, accounting(b), (c)
Loginlogin dates, IP address, browser informationsecurity, prevention of abuse(f)
Paymentinvoices, payment records, account balance; for bank transfers, the payer name, TIN, payment reference and document number from the bank statement; for card payments, the transaction number issued by the bank, the masked card number and the token (the card number is not stored)payment, accounting(b), (c)
Serviceserver name, IP addresses, disk and resource configuration, DNS records, mail domains and mailbox namessupply of the service(b)
Technical logsoperation records (start, restore, password reset, network rules), console access, notification emails sentfault investigation, security(f)
Legal acceptancewhich version of which document you accepted, when, and with which IP and browserproof of the obligation(b), (f)
Mail metadatasee §5.4mail search and delivery reports(b)

Passwords are not stored in the clear, only as a one-way hash.

Important: The portal uses no analytics or advertising tools and only necessary cookies (session, security, language). Your account, payment, service and mail data are not passed to Google or any other advertising platform.

Legitimate interest (f) means the security of the service and of our customers, prevention of abuse and investigation of faults. You can object to this processing as described in §9.

Automated decisions and profiling. No fully automated decision with legal or similarly significant effects is taken about you. The mail spam/virus filter (§5.2) evaluates messages; it takes no decision about a person.

Age. The services are not intended for persons under the age of 18 and we do not knowingly collect their data (Terms of Service §2).

3. Cookies and similar technologies (website)

3.1 How consent works

On your first visit a cookie banner is shown: "Decline", "Accept" (the same size) and a "Settings" link, where analytics and advertising are chosen separately. Closing the banner without a choice means rejection.

  • Until you consent only necessary cookies are used; the Google tag (gtag.js) is not loaded and no request goes to Google.
  • Consent is passed on with Google Consent Mode v2: analytics consent: analytics_storage; advertising consent: ad_storage, ad_user_data, ad_personalization. A category without consent stays "denied".
  • You can change your choice or withdraw consent at any time with the "Cookie settings" link at the bottom of the website. On withdrawal the website's own cookies of that category are deleted from your browser (analytics: _ga, _ga_<ID>; advertising: _gcl_*, jh_utm). Cookies on Google's own domains (e.g. IDE) cannot be deleted by the website. After withdrawal the Google tag no longer uses them; you can delete them in your browser or at adssettings.google.com. Withdrawal does not affect the lawfulness of processing before it.
  • Your choice is remembered for 12 months; after that (or when the cookie list changes) you are asked again.
  • The website works fully without consent.
  • The website's anonymous traffic statistics (Cloudflare Web Analytics, §2.1) set no cookies and do not depend on this banner. They run regardless of your choice; they are not used in the portal (cloud.jezahost.com).

3.2 Cookie list

NameProviderPurposeDurationCategory
NEXT_LOCALEjezahost.comthe language you chose; no longer set since 15.11.2026, a cookie set earlier is read until it expires12 monthsnecessary
jh_consentjezahost.comyour cookie choice (consent ID, time, version, choice)12 monthsnecessary
admin sessionjezahost.comaccess to the admin panel for team members only8 hoursnecessary
__cf_bm and Turnstile technical cookiesCloudflarebot and DDoS protection, spam protection of formsup to 30 minutesnecessary
_gaGoogle (GA4)distinguishing visitors by a random identifier, counting repeat visits2 yearsanalytics
_ga_<ID>Google (GA4)session state (page views, form submissions, etc.)2 yearsanalytics
_gcl_auGoogle Adslinking an ad click to a later enquiry (conversion measurement)90 daysadvertising
Google advertising cookies (e.g. IDE)Google (doubleclick.net, google.com)remarketing: showing our ads on the Google network to people who visited the websiteup to 13 monthsadvertising
jh_utmjezahost.comthe advertising source that brought you to the website (UTM: source, medium, campaign), to know which ad an enquiry came from30 daysadvertising

Analytics and advertising cookies carry no name, email or phone; they are random identifiers. The IP address is not stored in Google Analytics. You can also turn off ad personalisation in your Google account (adssettings.google.com).

3.3 Google's role

  • Google Analytics 4: Google acts on our behalf as a processor (Google Ads Data Processing Terms).
  • Google Ads (conversion measurement and remarketing): Google also processes advertising data for its own purposes as an independent controller (Google Ads Controller-Controller Data Protection Terms). On Google's processing: policies.google.com/privacy.

3.4 Consent record

To prove your choice, a record is kept on the website's server: a random consent ID, the time, the banner version, the Policy version, the choice (analytics / advertising) and the action (accept, reject, change, withdraw). No IP address or browser information is recorded. Records are kept for 3 years and then deleted.

4. Data inside your server

Everything you store on your virtual server belongs to you. It may include personal data of third parties (your own customers); in that case the Customer is the controller of that data; the Provider only keeps the server running and does not look at the content.

Important: We do not look inside your server. There are only three exceptions:

1. technical necessity: the minimum needed to remedy a fault; 2. your request: when you contact support yourself; 3. legal requirement: a written request from a competent authority made in accordance with the law (Terms of Service §8.1).

Backups: if you have selected the backup service, your server's system disk and additional NVMe disks are backed up automatically; backups from the last 7 days are shown in the panel for restore (SLA §6). Regardless of this, disaster-recovery copies of the system and NVMe disks of all servers are kept solely for a data-centre disaster (SLA §6.4). Backups are held in an encrypted storage system and are used only for restoration.

Important: The archive disk (SAS) is not backed up; backing up data there is your responsibility (Terms §6.4).

Encryption: encryption of the data on your server (at disk level, at application level) is under your control and we do not do it for you.

Important: Backups are not handed over to you as files. They are an internal disaster recovery mechanism: restoration is performed from the panel, and we have no obligation to supply a disk image or an archive file. You can copy the data on your server yourself at any time: you have full access to it while the service is active. In exceptional cases this may be agreed separately with support where technically possible.

5. Email hosting: content and metadata

Important: The position here is DIFFERENT from a cloud server. Your server's contents are on your machine; your mailbox contents are stored on our systems. This section is therefore written separately.

5.1 Mailbox contents

  • Messages, folders and attachments are stored on our mail servers.
  • The contents of the mailbox belong to the Customer. The Provider stores them solely in order to deliver the service, passes them through spam and virus filtering and delivers them.
  • Human access to content occurs only in the three cases in §4 (technical necessity, your request, legal requirement).

5.2 Automated processing: spam and virus filtering

Incoming and outgoing mail is checked automatically for spam and malicious content. This is not human review: the filter evaluates content by machine rules and records the outcome (accept / quarantine / reject).

5.3 Delivery of outgoing mail

Messages sent from your mailboxes to external addresses are delivered through our delivery partner SMTP2GO (§6). During delivery the message (with its headers, body and attachments) passes through SMTP2GO's servers. SMTP2GO processes the message solely in order to deliver it. Incoming mail and the contents of your mailboxes do not pass through SMTP2GO.

5.4 Message metadata stored in the portal

For the mail search and reports in your panel, the following is copied into and stored in the portal database for each message:

FieldExample
date and time18.09.2026 14:32
directionincoming / outgoing
sender address[email protected]
recipient address[email protected]
subject line"September invoice"
delivery statusdelivered / deferred / rejected
rejection reasonblocklist, no such mailbox, size limit, etc.
spam verdictclean / suspicious / spam
Message-ID<[email protected]>
sender's IP address203.0.113.5

Note: The body of the message and its attachments are not copied into the portal, only the fields above. However, the subject line is part of the content, and we state it separately so that this processing is not hidden.

Why: to answer the question "did the message arrive, and if not why" in the panel, and to show bounce reports. Legal basis: (b) performance of the contract: to show that the service is working and to investigate delivery problems.

5.5 Retention periods (mail)

WhatHow long
Mailbox contentswhile the service is active
Mailbox deleted while the service is active30 days (for restoration), then deleted irreversibly
Mailboxes when the service is cancelleddeleted (Terms of Service §5.2)
Daily statistics400 days
Bounce records180 days
Message metadata (§5.4)180 days

5.6 Where a bank refund is requested

If a return of funds to a bank account is requested, mailboxes and their contents are deleted immediately; the 30-day retention does not apply (Terms §5.3.1).

6. Recipients: processors and third parties

PartyRoleWhyWhat it sees
Cloudflare, Inc.processorwebsite delivery, DDoS and bot protection (Turnstile), anonymous website traffic statistics (Web Analytics), DNS records for the servicerequests at network level, DNS names
SMTP2GOprocessor(a) delivery of email from website forms; (b) delivery of messages sent from your mailboxes to external addresses (§5.3); (c) retrieval of delivery recordsthe content of the messages under (a) and (b); delivery metadata (sender, recipient, subject, status)
Google Ireland Ltd. / Google LLC: Analyticsprocessorwebsite only, with consent: measuring website usageusage events and the _ga identifier (§3)
Google Ireland Ltd. / Google LLC: Adsindependent controllerwebsite only, with consent: conversion measurement and remarketingconversion events, pages viewed, advertising cookies (§3)
Bankindependent controllerbank transfer and card payment; retrieval of bank statementspayment reference, amount, the payer's bank details; for card payments, card data is processed by the bank only
Public authoritiesindependent controlleronly where required by law (tax reporting, a written request from a competent authority)the data specified in the request

Processors process data only on our instructions and for the function stated. We do not sell your data.

Note: The mail filter and the mail server are our own infrastructure: the contents of your mailboxes are not stored with a third-party provider. The exception is the delivery of outgoing mail and the delivery records (SMTP2GO, §5.3).

7. International transfers

Your account, payment and service data (§2.2) and the contents of your servers and mailboxes are stored on infrastructure in Azerbaijan.

The servers of Cloudflare, SMTP2GO and Google may be located outside Azerbaijan and the European Economic Area (EEA), including in the USA; the data in §6 may be processed there for that function. Transfers rely on the safeguards in the providers' contracts: the European Commission's Standard Contractual Clauses (SCC), the EU–US Data Privacy Framework (for certified providers) or adequacy decisions.

8. Retention periods

WhatHow long
Account and service datafor the duration of the service relationship
Enquiries from website formsuntil the reply and quote process ends; if you do not become a customer, no later than 12 months
Backups (system + NVMe disks)7 days in the panel; older copies in technical rotation are deleted no later than 35 days
Disaster-recovery copies (SLA §6.4)no later than 35 days after the deletion event
Website visit log (§2.1)14 days
Archive disknot backed up
On cancellation: VM disks and backupskept for 7 days, then deleted no later than 35 days; deleted immediately where a return of funds to a bank account is requested
Mailboxes and message metadatasee §5.5
Invoice and payment recordsthe period required by law (accounting)
Application logs14 days
Audit records and records of notification emails sent12 months
Legal acceptance recordsfor the term of the contract plus the limitation period
Website cookiesthe durations in §3.2
Cookie consent records (§3.4)3 years

9. Your rights

You have the following rights:

  • access: to learn what data of yours we process and to receive a copy;
  • rectification: to require correction of inaccurate or incomplete data;
  • erasure: to require deletion of your account and data (accounting documents are retained until the statutory period expires);
  • restriction of processing: to suspend processing of disputed data while it is checked;
  • portability: to receive the data you provided to us (account, payment records, the message metadata in §5.4) in a machine-readable format. Important: This right does not extend to the contents of your server or to backups; see §4. You can copy your mailbox contents yourself at any time over IMAP;
  • objection: to object to processing based on legitimate interest (f); an objection to direct marketing is always honoured;
  • withdrawal of consent: to withdraw your consent to analytics and advertising cookies at any time via "Cookie settings"; this does not affect the lawfulness of processing before the withdrawal;
  • complaint: to lodge a complaint with the competent public authority or, if you live in the EU, with the data protection supervisory authority of your country.

To make a request: the support system inside the portal or [email protected]. Requests are answered within 30 days; we may ask for additional information to confirm your identity.

10. Security

  • passwords are stored as one-way hashes;
  • the portal and website run over HTTPS;
  • card data is not stored on the provider's systems; card payments are made on the bank's payment page;
  • mailbox access is by password or app password;
  • access to management interfaces is restricted and logged;
  • staff obtain access to customer data only on a need-to-work basis.

No system is absolutely secure. Protecting your account password and securing the inside of your server are your responsibility (see "Terms of Service" §9).

In the event of a data breach, affected customers are informed within the shortest reasonable time.

11. Changes to this document

The policy may be updated; when the document is updated, the "Last updated" date changes. Changes that broaden the scope of processing are notified by email at least 30 days in advance. When the cookie list changes, the website asks for your consent again. The official text and all versions are at cloud.jezahost.com/legal/privacy.

12. Contact

  • Privacy requests and support: the ticket system inside the portal, [email protected]
  • Payments and invoices: [email protected]
  • Abuse complaints: [email protected]
  • Controller: JEZA CLOUD LLC · TIN 1606154731
  • Registered address: Bakı şəh., Nizami ray., Q.Qarayev pr. ev.84, AZ1096