Cookies and Local Storage

Draft of the next revision. The effective date will be set upon approval. This revision is unpublished and does not replace the current documents.

This document applies to the use of Akmelo in a browser and supplements the Personal Data Processing Policy.

1. Technologies we use

A cookie is a small record that a browser stores for a website and sends with relevant requests. Browser local storage holds interface data and differs from cookies: its contents are not sent automatically with every HTTP request. These technologies may contain identifiers and information associated with a user, so we assess them together with other data processing.

2. Purpose in the application

Once a public assistant conversation is started, a separate functional cookie containing a random identifier provides access to conversations saved on the server from the same browser. The cookie lasts for up to 180 days after it is set; accessing the conversation list or creating a new conversation renews that period. Conversation content is not stored in the cookie. Page scripts cannot read it. It is not used for advertising, establishing identity, or tracking other websites. Viewing the list before starting the first conversation does not set this cookie.

Access to history depends on retaining the cookie and browser profile. Previous conversations are not automatically restored on another device or after site data is cleared. Someone with access to the same browser profile may open the history. The cookie's lifetime does not determine server-side conversation retention. Retention and requests about personal data are described in the Personal Data Processing Policy.

Session mechanisms and protection against forged requests are used to operate accounts. Without the required browser data, signing in and some actions may be unavailable. Local storage saves user preferences and working drafts, including table, editor, and mapping settings, so that they can be restored when work resumes.

The application also uses a first-party security cookie containing a random browser identifier. Each cookie lasts for up to 180 days after it is set or reissued. It helps staff investigate possible circumvention of justified cloud restrictions. A signal received from the browser and linked to an account is retained in a protected derived form for no more than 180 days after it was last observed. A new sign-in or request containing the signal restarts its server-side retention period. Account links confirmed by staff are limited to up to 180 days after creation or the most recent staff review.

The identifier does not itself establish a person's identity. An automated signal match does not create a confirmed account link. A matching shared browser or device is not an independent reason to restrict another account.

This mechanism does not read a hardware serial number, create a hidden browser fingerprint, or serve advertising or observation on other websites. The security cookie is used only to the extent necessary for cloud execution security while respecting user rights. Referring to security needs does not authorise a new purpose or disproportionate collection.

A separate technical signal from a verified native application connection is described in the Personal Data Processing Policy. It is not a cookie, hardware serial number, or proof of identity; its retention is also limited to 180 days after it was last observed.

Do not put passwords, tokens, or other people's personal data in free-form fields or drafts. Local storage does not make a browser a secure store for secrets. On a shared computer, someone with access to the browser profile may see saved information.

This revision does not authorize advertising tracking or claim that a particular analytics system is in use. Before enabling optional analytics or advertising, the Provider must assess the legal basis for processing, update the description of the technologies actually used, and, where required, provide users with a separate choice in advance. Optional technologies must not be described as essential merely to avoid obtaining consent.

3. Managing browser data

You can restrict cookies and clear site data and local storage using your browser controls. After clearing them, you may need to sign in again; drafts and settings stored only in the browser may be lost. Save any results you need through the application's normal functions before clearing data.

Deleting local data does not automatically delete the server-side account, logs, or collection results. For requests about that data, contact support@insoweb.ru. Signing out should not be treated as a guarantee that all previously saved local drafts have been removed. On a shared device, we recommend clearing site data and ending the browser session.

4. Retention and contacts

Removing a public assistant conversation from history hides it in the interface, while the server records remain. Clearing the cookie is not a request to destroy those records. To request cessation of processing or destruction of personal data, follow the enquiry procedure at support@insoweb.ru.

Session duration depends on service settings and sign-in conditions. Local records may remain until the application or the user deletes them. The retention and deletion policy is: Active account data, tasks, and results are retained while needed to provide the service. After a verified request to cease processing, data with no other lawful retention ground is erased within the applicable mandatory period, generally no later than 30 calendar days; a shorter legal deadline prevails. Backups containing such data must be cleared within the same period or isolated until safe erasure without resuming active processing. Technical signals linking accounts are retained for no more than 180 days after last observation; closed review materials for no more than 365 days after closure unless a specific lawful ground requires longer retention. Payment and tax records are kept for mandatory accounting periods, and any such exception is explained when a request is reviewed.. The current list and settings of technologies must match the actual application version. A change in purposes requires an updated document and the necessary legal basis.

Controller: Жужгов Роман Алексеевич, Taxpayer ID (INN) 590618061494; individual applying the professional income tax regime. For technical questions, contact support@insoweb.ru; for personal data questions, contact support@insoweb.ru. Statutory rights of data subjects remain in force regardless of browser settings.