Privacy Policy

ASSURA processes application data including contact details, trip dates and traveller passport data to provide the application channel and support. Data required for the insurance process is passed through Ghost CRM and to Imedi L for policy issuance and servicing.

When passport scan is used, the image is sent to the configured OCR service for recognition. Recognised fields return to the form for customer review. ASSURA also processes essential service logs and, where configured, attribution and analytics data such as UTM parameters and click identifiers.

When an order has an available online payment link, payment data is processed on the configured payment provider's secure page. ASSURA does not receive full card details. Data is not sold. Requests for access or correction can be sent to info@assura.ge.

Messages sent through ASSURA website live chat, Telegram and other support channels are processed by the relevant communications provider and ASSURA operators for customer-support purposes. Do not send passport images, payment credentials or other unnecessary sensitive data in support messages.

Cookies and browser storage

Necessary storage keeps the site working and is always on. It covers signing in to a personal or partner account, the demo gate, the short-lived receipt of an application in progress, and the support-chat session, which is created only after you send a message. The draft of your application — dates, travellers, contact details — is kept by your browser for the current tab so a reload does not empty the form; it is not sent anywhere by that storage.

Analytics storage measures how the site is used: which pages are opened and where an application is abandoned. It is switched on only after you allow the analytics category, and only on deployments where a measurement tool is configured. If none is configured, nothing is loaded whatever you answer.

Marketing storage records which advertisement brought you to the site and helps avoid showing you the same ones again. It is switched on only after you allow the marketing category. Until then, advertising click identifiers such as gclid or fbclid are not written to your browser and no advertising tag is loaded.

Advertising performance. If you separately agree to it in the order form, ASSURA may send the order number and the amount paid to Google Ads to measure how well its advertising works. That transfer may take place outside Georgia. Nothing else goes with it — no name, e-mail, telephone, passport, payment identifier or policy link — and the permission is optional: refusing it changes nothing about buying or receiving a policy.

Partner links. A link from a partner carries a code in the address. While you are on the site that code stays in the address and is submitted with your application so the order can be attributed to the partner — this needs no storage on your device and happens whatever you answered. Separately, with the marketing category allowed, the code is also kept in a cookie for 30 days so a later visit is still attributed. We also log the click itself on our servers, without storing anything on your device.

Your decision is stored in a first-party cookie named assura_consent for up to 365 days, together with the version of this notice that it answered. Changing the answer, or clearing your browser data, replaces or removes it. If we materially change what the categories cover, the version changes and the question is asked again — the previous answer was given to a different question.

You can change or withdraw your decision at any time through the “Cookie settings” link at the bottom of every page. Withdrawing takes effect immediately for anything not yet loaded, and from the next page for tags already running in the open one.