Private policy

Dear users, we understand that online privacy is important to you when working with our add-on.

This statement governs our private policy for all the users who use the add-on.


Preface

We have implemented this private policy because your privacy is important to us. By reading our private policy, you can get informed on the way your personal information is used.

“Personal Information” means any information that can be used alone or in combination with other information to identify a person, including but not limited to name and surname, personal profile, email address, home address or other actual address or other contact information.


Private Policy

The add-on does not ask you for your name, your home address or any other contact information. It does, however, transmit data about the pages you have chosen to track. The sections below describe what leaves your browser, when it leaves and whether it is tied to your account.

Every time you create a track, the add-on sends the address of that page and its domain name to our server. This happens for every user, whether signed in or not. It is not part of the daily summary described below, and it is sent regardless of anything you can set in the add-on.


Anonymous Daily Summary

Once a day the add-on sends one short summary of how it worked. The summary contains the domain names of the shops you track (example.com, never the address of a page), numeric codes that say why a check failed — the shop blocked the request, the shop answered with a server error, the saved selector no longer matches the page — and counters of how the add-on is used: how many tracks you keep, how many of them are broken, which features and settings you have switched on, whether the installation has a paid subscription, and the version of the add-on. If our own code crashes, the summary also carries a short technical signature of that crash, with addresses, host names and numbers stripped out of it.

The summary carries no installation identifier, no page addresses, no tracked values and no page snapshots. It is sent without your sign-in token and is not tied to your account or to your email address. We use it to learn which shops the add-on has stopped working on.

The add-on has no setting that turns this summary off. It is sent by every installation. If you do not want it sent, remove the add-on from your browser — that is the only way to stop it from your side. We can also switch the summary off centrally, for every installation at once, and the add-on obeys that immediately and permanently.


Tracks Saved in Your Account

If you are signed in, the whole record of a track is sent to our server, where it is kept under your account. It is sent when the track is created, and again every time you save its settings, its filter or its tags. The record contains the address of the tracked page, the title of that page — usually the name of the product — the current value of every tracked element together with the history stored for it, the tags and the filter you have set, and the settings of the track itself. If you switch on email notifications for a track, the same record is sent so that the notification can be composed.

If you are not signed in, none of this is sent and your tracks stay in your browser. Snapshots of a page that the add-on takes when a track breaks are kept in your browser only and are never sent to us.


Installation Report for Support

The add-on gives every installation a permanent identifier — a random string it creates the first time it runs and keeps from then on. Every installation gets one, including an installation that has never been registered and has never signed in. The identifier is not built from your email address, your name or anything about your computer: it is a random string, and its only job is to tell one installation of the add-on from another.

Once a day the add-on sends one report about itself under that identifier. It also sends one out of turn when its state changes — most often when tracking breaks — but never more often than once in six hours. The report contains the identifier, the version of the add-on, the browser, the operating system, the interface language, the time zone your browser is set to, and all the general settings of the add-on. For every tracked item it contains the domain name of the shop (example.com, never the address of a page), whether the item is switched on, whether it is broken, how many checks in a row have failed and the same kind of numeric reason code described above, when it was last checked, how often it is checked, whether the check opens a tab, which kind of filter is set on it — but not the number you set inside that filter — whether the tracked element was picked by you or found automatically, and how many elements the item watches. No more than three hundred items are reported.

The report carries no page addresses, no product names, no tracked values and no history of them, no page snapshots and none of the selectors the add-on has saved. If you are signed in, those are already on our server through the account sync described above, and the report does not repeat them: it names a tracked item by its identifier alone.

If you are signed in at the moment the report is sent, it also carries your email address and whether the account is paid, so that the installation is tied to your account. If you are not signed in, no account data goes with it — but the identifier does, and it stays the same from one report to the next.

Your country is not worked out from your IP address. The add-on sends the time zone your browser is set to — Europe/Moscow, for example — and the country is derived from that time zone alone. We do not look your address up in any geolocation database, and we do not store it with this report.

We use the report for support. When tracking breaks in a particular shop, it shows us the version, the browser and the settings the add-on was really running with, so that we can reproduce the failure on our side instead of guessing, and repair the tracking of that shop.

The identifier is shown at the bottom of the general settings of the add-on, so that you can read it out to us when you ask for help. There is no button that replaces it, and no setting that stops this report: it is sent by every installation. Removing the add-on from your browser stops it and discards the identifier; installing the add-on again creates a new one, and reports already sent stay with us under the old one.

This report is not the anonymous daily summary described above. They are sent separately and contain different things, and neither of them can be switched off inside the add-on.


Security

The security of personal information is important to us. We follow generally accepted industry standards, including the use of appropriate administrative, physical and technical guarantees to protect the personal information provided to us. However, no online transmission method or electronic storage method is 100% protected. Apart from the data described above, we do not collect user data. When you register by email, we save your email address, your user name and a hash of your password.


No Cookies

The add-on does not use cookies by default. Cookies are not stored in a personally identifiable way.


Updates

Private policy may be updated. We inform you in a timely manner of any changes to our private policy by posting updates on this page. You are advised to regularly review the private policy and check the date it was updated. Further use of the add-on after updates to the private policy means that you agree to the updated private policy.


Contact Us

If you have any questions about our private policy or questions about the usage of the add-on, please contact us at support@otsledit.net.