Privacy policy

01Service and privacy contact

This policy describes how data about visitors and users of cloud.liquidosich.com is processed. Liquidosich Cloud is operated by Liquidosich. For access, correction, deletion or requests to stop processing, contact contact@liquidosich.com or use the owner’s contact links in the website footer.

This policy covers Cloud’s current features. External websites and communication through third-party platforms are also subject to those services’ own policies.

02Account and profile

Registration and account operation use your display name, username, email address, a cryptographic password hash, the inviter username you provide, and registration and email verification dates. Account status, role, access level and storage allowance are recorded to manage access.

Registration records when you accepted the documents and the privacy policy version. A service rules version is not recorded while those rules remain unpublished.

You may provide an avatar, cover image and description, and choose an avatar colour, workspace cover and theme. The username change date is used to limit how often it can be changed. Other signed-in users can view your name, username, profile images, description, role and presence. Your email, password, IP addresses and drive files are not published in your profile. Profile image files are accessible through direct image URLs.

03Personal drive and file transfers

Your account stores the selected Cloud file view: grid or list. It is applied on subsequent visits, including on other devices. The default is grid. This preference is not published in your profile.

Cloud stores uploaded files, file and folder names, folder structure, sizes, types, and creation and modification dates. This data supports uploads, browsing, renaming, downloading, deletion and storage accounting. Files are private by default. Other people can access only individual files whose owner has enabled link access or access for selected accounts; the rest of the personal drive is not disclosed.

Albums are personal photo and video collections. Cloud stores album names, creation and modification dates, and references to files. Adding a file does not duplicate it or change its location; deleting an album does not delete originals. Files in Trash are hidden from albums and become available again if restored. Album covers use image thumbnails generated by the server for authenticated requests and are not published for other users. File lists display photos and videos as icons; video frames are not extracted for covers. A file page shows its type, name and size; file contents are delivered only for an access-checked download or copy.

Cloud history records new file and album activity: creation, upload and upload cancellation, download requests, renaming, moving, moving to Trash, restoration, permanent deletion and collection changes. A record contains the action, time, item name and, where needed, previous and new locations or album name. This metadata is retained while the account exists, including after the corresponding file is permanently deleted, so the history remains understandable. Deleted file contents are not retained in history. A download request does not confirm that the browser completed it.

Traffic between the browser and the website is protected by HTTPS. Files are stored on the service’s server infrastructure separately from the public website. End-to-end encryption with a user-held key is not implemented: the owner and authorised technical staff may access the server to operate the service and handle support requests.

Limited access has an assigned storage allowance. If the allowance is reduced below the space already used, files are retained: browsing, downloading, renaming, moving and deleting remain available. Adding new files and other operations that increase storage usage are unavailable until enough space has been freed. Files in Trash do not count towards the subscription allowance. Restoring them counts their size again and requires enough available space. When the allowance is reduced, incomplete uploads that no longer fit are cancelled, and their temporary data and reservations are removed. Completed files are not deleted. If access is revoked entirely, files are also retained, but drive operations become unavailable. Revoking a subscription does not delete your data. Contact the owner to request deletion if you no longer have access.

04File links and access

Each file receives a random identifier for its permanent link. The URL also includes the owner’s username. The service stores the access mode and, for restricted access, the identifiers of selected accounts. Changing a recipient’s username does not remove their permission. A visitor without access is not given a private file’s name, size or contents; the blurred display uses placeholders.

The owner chooses private access, access for anyone with the link, or restricted access for selected signed-in accounts. With link access, anyone who receives the URL can view and download the file without registration and can forward the link. Authorised visitors see the owner’s username, file name, size and type. The owner may close access or change recipients. This blocks subsequent requests but does not remove copies already downloaded or saved.

A signed-in user with personal Cloud access may save an accessible file as an independent copy if storage is available. The copy counts towards their quota, receives its own private link and is unaffected by subsequent changes to the original’s permissions. Copies are grouped in a Shared by @username folder. To reuse the folder for the same owner, the service stores an association between the recipient account, original owner account and folder. This association is removed when the folder is permanently deleted or either account is deleted. Removing the association does not delete the saved copies. History records access changes and copies saved, without file contents. Permissions and the link are deleted when the file is permanently deleted; a recipient’s permission record is deleted when that account is deleted.

Files in Trash are unavailable through their links. Restoring them resumes their previous access settings. Blocking the owner’s account or revoking their Cloud access suspends file links while retaining files and selected permissions.

05Sessions, security and service emails

Downloads use a temporary authorisation bound to the current browser session, valid for two minutes to start the transfer. Access is checked again before contents are delivered. A browser transfer handler streams the file and reports transfer progress; file contents are not stored in the website’s offline cache. Active transfer information supports the progress indicator and a warning when leaving the page.

Sign-in protection and session management use IP addresses, browser and device information, sign-in and last activity times, and session expiry and revocation records. Presence is derived from these records. Server logs may contain request paths, times, IP addresses and response codes; file contents and passwords are not intended to be logged.

Email verification codes for registration and email changes are sent when you request them. Codes are valid for 10 minutes; a protected verification value is stored in the database. Delivery uses the mail infrastructure for contact@liquidosich.com. Providing an email for account operation does not constitute consent to marketing emails.

06Yandex ID linking

At your request, Cloud links an existing account to Yandex ID. Yandex provides your user identifier and primary email address, which are stored for account linking and subsequent sign-in. Cloud does not receive your Yandex password; the token is used only to retrieve these details and is not stored. Access to Yandex Disk or its files is not requested. Yandex sign-in does not create a Cloud account, and matching email addresses do not automatically link accounts.

You can remove the link in settings by confirming your current Cloud password. Removing it disables sign-in with that Yandex ID and deletes the stored link and its email address. Yandex’s own documents govern authentication on Yandex’s side.

07Cookies and browser preferences

The website uses a secure session cookie for sign-in, language and theme cookies, a device time zone cookie, and browser local storage for interface preferences. The browser provides the time zone used to display dates and times and name downloaded archives; database events remain in UTC. Document revision dates are fixed and are not converted. The sign-in cookie lasts 30 days and is renewed with activity; a fresh sign-in is required no later than 90 days after authentication. Individual sessions can be ended in security settings. Disabling cookies may prevent sign-in.

08Retention and deletion

Account and personal drive data is retained to provide the service while the account exists and the data has not been deleted. Deleted files and folders move to your personal Trash for 24 hours and immediately stop counting towards the subscription allowance. During that time you can restore them to their original location if enough storage allowance is available; name conflicts are resolved by giving the restored item an available name. Once retention ends, items can no longer be restored and are automatically deleted by the next background cleanup, normally within one minute. Emptying Trash or deleting an item from it manually starts permanent deletion immediately. If storage is temporarily unavailable, cleanup retries when it becomes available.

Incomplete transfers expire after 24 hours and temporary snapshots for folder and selection downloads expire after one hour. Background cleanup removes expired data. An active download snapshot may retain files deleted from the drive until that transfer finishes.

To delete your account, obtain a copy of your data, correct details you cannot edit or request restricted processing, contact the owner. Account ownership may need to be verified to protect your data. Do not send passwords or verification codes. Data needed to meet applicable obligations or resolve a specific dispute may be retained separately to the extent necessary.

09Data disclosure and policy updates

Data is used to operate Cloud and is not sold. Technical processing involves server hosting and delivery of service emails; access is limited to what is needed for the relevant task. Disclosure in response to a binding lawful request is limited to the applicable scope.

The current policy is published on this page. Material changes to features, data collected, processing purposes or retention are reflected in the policy and its revision date. Material updates are communicated through the service’s available channels.