Cookie Policy
OTDR Master Cookie Policy
Version 2.0 of 25 September 2026
1. General provisions
1.1. This Policy sets out what data the Service writes to the User’s browser (cookies, local storage and IndexedDB storage), for what purpose, for how long and to whom it is disclosed. Terms have the meaning given in the Terms of Use.
1.2. The list of records in sections 2–4 is exhaustive. The Service writes no other data to the User’s browser.
1.3. The processing and storage of Files on the Service’s servers are governed by the Terms of Use and are not covered by this Policy.
1.4. The records listed in sections 2 and 3 are not disclosed to third parties. The records listed in section 4 are set by third-party services.
2. Strictly necessary records
2.1. Without the records listed below the Service cannot perform its functions. They are set regardless of the User’s choice in the cookie settings.
| Key | Type | Purpose | Retention |
|---|---|---|---|
otdr_session | cookie | Account sign-in session | 90 days or until sign-out |
otdr.lang | cookie | interface language chosen by the User | 1 year |
otdr.consent | cookie | the User’s choice in the cookie settings | 1 year if accepted, 6 months if declined |
otdr.browser | local storage | random browser identifier by which the Service tells the User’s Files from others | until site data is cleared |
otdr-service | IndexedDB | copies of Files opened in the browser and the workspace list | until the File is removed from the list or site data is cleared |
otdr-handoff | IndexedDB | hand-over of a File dropped on the home page to the application | until the File is opened in the application |
otdr.signin-asked | local storage | mark that a sign-in letter was requested from this browser | until sign-in |
otdr.pay-order | local storage | number of an issued invoice for the Plan | until payment or expiry of the invoice |
2.2. The browser identifier is issued by the Service and contains no information about the User. Once site data is cleared, Files opened in that browser without signing in to an Account become unavailable to the Service.
3. Interface settings
3.1. The records listed below keep the User’s choices in the application interface. They are kept in the browser’s local storage until site data is cleared.
| Key | Purpose |
|---|---|
otdr.theme | colour theme |
otdr.files-width, otdr.report-side, otdr.table-cap | width of the file list and of the report settings column, height of the event table |
otdr.overlaid, otdr.pair | curves on the chart and the selected reverse trace |
otdr.pon, otdr.cable-mode | state of PON and Cable modes, including the drum’s factory data |
otdr.limitsView, otdr.event-hints | threshold view and event hints |
otdr.report-lang, otdr.open-project | report sheet language and the open project |
otdr.cursors-used, otdr.tour-seen, otdr.pon-seen, otdr.report-seen | marks of a completed demonstration and hints already seen |
3.2. Deleting these records does not cause loss of Files: the application returns to its default settings.
4. Analytics cookies
4.1. The Service uses Yandex Metrica and Google Analytics to count visits. If the browser’s time zone belongs to a country of the European Union, the European Economic Area, the United Kingdom, Switzerland or another European state, the counters are not loaded until consent is given with the “Accept” button. Otherwise the counters load immediately and may be switched off as set out in section 5.
| Key | Purpose | Retention | Recipient |
|---|---|---|---|
_ym_uid, _ym_d, _ym_isad | Yandex Metrica: visit counting | up to 1 year | Yandex LLC, Russia |
_ga, _ga_* | Google Analytics: visit counting | up to 2 years | Google LLC, USA |
4.2. The name of an open File is not passed to the counters: on the application page the tab title is replaced with the name of the Service for the counters.
4.3. Session recording (Yandex Metrica Webvisor) is not used.
5. Managing records and withdrawing consent
5.1. The User may give or withdraw consent to analytics cookies at any time in the cookie settings:
5.2. A link to the cookie settings is placed at the bottom of every page of the Service. A refusal is kept for 6 months, during which the request is not repeated.
5.3. All records, including strictly necessary ones, are deleted with the browser’s own tools by clearing site data. The Service will then ask again for the language and cookie settings.
5.4. Files are deleted from the Service’s servers at the User’s request to support@otdrmaster.com as set out in the Terms of Use.
6. Changes to this Policy
6.1. The Service may amend this Policy. The current version is published on this page with its version number and date.