Privacy Policy

1. General provisions

1.1. This Privacy Policy (the “Policy”) describes how information is processed and protected when the micator.com website, the customer account, the licensing service and the Micator installer downloads are used. The Service is run by Developereva, an individual (the “Operator”).

1.2. This Policy does not take away the mandatory protection of personal data that the User has under the law applicable to them. If a particular kind of processing requires consent, it is requested separately; reading this Policy does not replace that consent.

1.3. The installed tracker runs on the User's server. The User decides on their own the purposes and terms of processing visitor data in their installation. This Policy of the Micator website does not replace the User's own notices to visitors and documents on the processing of their data.

1.4. The rules for using the Service are set out in the Terms of Service. Contact details for questions about data are given in section 8.

2. What information is processed

2.1. Account. On registration, the email address, the team name provided, the account ID, the password hash, the creation date and the confirmation status are stored. The role, the access status and whether the trial has been used are also stored. The password is not stored in plain text.

2.2. Sign-in and recovery. The Service processes session identifiers, their expiry, one-time confirmation and recovery tokens, and records of service notifications. Sign-in uses the necessary cookie micator_site_session: it lasts up to 14 days, cannot be read by JavaScript and, when the site works over HTTPS, is sent only over a secure connection. When you log out, the current session is revoked. The customer account does not work without this cookie.

2.3. Licensing. The license number, type, term and status, its link to the account, a protected copy of the key, the domain and the installation ID are stored. On activation and during later checks, the tracker sends the licensing service the key, the domain and the installation ID. This information is needed to check the term and the binding; click and conversion statistics are not part of this request.

2.4. Orders. When an order is placed, the order number, the account, the chosen term, the amount, the promo code and discount, the currency, the status, the link to the license and the dates of changes are stored. When paying through Heleket, the order number, amount, currency and the return and notification addresses are sent to the provider. Micator stores the payment ID, the link to the payment page, the status and the verification results. The email, password and license key are not included in the payment request. Heleket's data processing rules apply on the payment page. For earlier direct USDT TRC20 invoices, the payment details, the transaction hash and the result of the on-chain check are stored. Bank card details, private keys and wallet seed phrases are not collected.

2.5. Support and admin actions. The subject and text of a support request, the replies, their authors, the request status and dates are stored. Attachments are available to the participants of the request and to authorized administrators. The contents of sent files are kept for 90 days, and of unfinished uploads for no more than a day; cleanup runs every hour. The file name, size and file details may remain in the history. Copies in backup archives are kept until the corresponding archive is deleted. The admin action log records who acted, the action, the affected record, the reason and the time. Do not send passwords, private keys or visitor data to support unless they are needed to handle your request.

2.6. Live chat. When a guest opens the chat, the necessary cookie micator_support_guest is set for up to 30 days: it cannot be read by JavaScript and is sent over HTTPS. It lets the guest open their conversation again in the same browser. The database stores a protected guest ID, an optional name, the messages and their times. After sign-in, the live chat is linked to the account and available in the list of support requests; guest history is not attached to the account automatically. The cookie expiring does not mean the conversation is deleted.

2.7. Telegram bot. If you write to @micator_support_bot, your Telegram user/chat ID, name, username if you have one, the message text and message IDs are processed. The conversation is available to the support operator in the Micator admin panel, and replies are sent back to Telegram. Text and PNG, JPEG, PDF, ZIP, TXT and LOG files up to 5 MB are accepted. Voice messages are not stored in the support database. Linking a chat to the customer account requires a one-time link and a separate confirmation of the chat in the profile; a matching name or email is not used for this.

2.8. Technical requests. When the website is opened, a license is activated, or updates are checked and downloaded, the servers and the supporting infrastructure receive the IP address, the time and address of the request, and the browser or client headers. Service logs may contain information about requests and errors. This technical data may be linked to the User and is not automatically considered anonymous.

2.9. Website analytics. Google Analytics and Yandex Metrica are used on the public pages of micator.com: they receive technical information about the browser and device, the IP address, the addresses of the pages opened, the referral source and actions on the site; cookies may be used to tell visits apart. Metrica has the click map and Webvisor (session replay) turned on, which records interaction with the public pages. The counters are not loaded in the customer account, the admin panel, or on the sign-in, registration, access recovery, checkout and invoice pages. The support widget and the content of support conversations are hidden from Webvisor recording. The purpose is to understand site traffic and improve the site; the recipients of this data are Google and Yandex services. You can manage cookies in your browser settings.

2.10. The site's own visit statistics. The site counts visits to public pages itself: it stores the date and hour, the page address, the site the visitor came from, the link tags (utm), the country, the device type, the operating system and the browser family. The IP address and the browser string are not stored, and no cookie is set. Visitors on the same day are told apart by an anonymized code: it is computed with a key that is valid for one day and does not allow the IP address to be recovered. Visit records are deleted after 90 days. Account, sign-in, payment and invoice pages are not counted.

2.11. Registration source. Where a visitor came from the first time — the link tags, the referring site, the first page opened and the date — is kept by the browser in its local storage for up to 90 days and sent to the site once, after registration. This information is stored with the account and deleted together with it. For the duration of a browser tab session, the browser also remembers the address of the last page of the site that was opened: it is needed to note which page a non-existent address was opened from.

2.12. Tracker data. Campaigns, clicks, visitor IP addresses, conversions, spend, uploaded pages and working logs are stored in the User's installation. The standard license check does not upload this database to the Operator. Postbacks, API integrations, the spend extension and backups set up by the User send the corresponding data to the recipients the User has chosen. The Operator may receive additional information if the User shares it themselves when contacting support.

2.13. The Service does not require a passport, photos or documents for regular registration. A request about access or data deletion may require confirming that the account belongs to the person making the request.

3. What the data is used for

3.1. The data is used to register and protect accounts, issue and check licenses, provide updates, process orders and support requests, restore access and fulfill obligations to the User.

3.2. Technical information and logs are needed to diagnose errors, limit abuse and verify actions with accounts and licenses. Processing is carried out to perform the contract, comply with mandatory requirements and protect the Service within the limits of applicable law; separate consent is requested where it is required.

3.3. Account and support data is not sold and is not used by the Operator to show third-party ads. This provision does not govern the activity of the advertising platforms that the User connects to their tracker on their own.

4. Data sharing

4.1. Access to the information is given to the Operator and to the necessary infrastructure providers to the extent required for the Service to work. Data may also be shared under a mandatory requirement of the law or at the lawful request of the User.

4.2. The public micator.com website is served through Cloudflare. When passing a connection through, this provider processes the network address and the HTTP request details. The website server, the API and the download server also receive connection data when they are accessed. The providers' distributed infrastructure may process data outside the User's country; such transfers take into account the requirements of applicable law.

4.3. Telegram is used for communication through the bot: it receives the reply text, files attached by the support operator and the recipient's chat ID. The support operator also receives notifications in their Telegram about new support requests from all channels: the channel, the request number and a link to the protected admin panel, without the conversation text or the customer's contact details. Telegram itself operates under its own terms. You can also contact support through the website chat or the customer account, without Telegram.

4.4. To verify a USDT TRC20 payment, the server sends the provided transaction hash to a TRON node through the TronGrid API. The account stores the amount, the recipient address, the hash, the time and the verification result, and the link to the invoice and the license. Blockchain transfers are public; Micator does not control how they are stored on the network or removed from it. Private keys and wallet seed phrases are not requested.

4.5. Emails confirming an address and restoring access are sent through the SendPulse email service. It receives the recipient's address and the content of the email, including the one-time link. This service operates under its own terms.

4.6. The recipients of data from an installed tracker are chosen by its owner: for example, an advertising network for S2S postbacks or an SFTP server for backups. How such recipients process data is defined by their own documents and agreements with the User.

5. Storage and security

5.1. The account and the information about licenses, orders and support requests are kept as long as they are needed to provide the Service, restore licenses and resolve related issues. Once these purposes no longer apply, the data is to be deleted or anonymized, except for information that has to be kept by law or to resolve an existing dispute.

5.2. A session lasts no longer than 14 days, and a one-time confirmation or recovery link no longer than one hour. Expired access does not mean that the record itself is immediately deleted from the database or a backup. Automatic deletion of accounts and a single calendar period for cleaning up all service records are not set up yet; deletion requests are handled by the Operator through support.

5.3. Backups are used to recover from failures. Deleting a record from the live database does not mean it disappears at the same time from a backup created earlier. On a deletion request, the Operator clarifies what information is kept, on what grounds and for how long, including in backups.

5.4. Security measures include HTTPS, password hashing, protected storage of license keys, access control and logging of administrative changes. The Operator takes reasonable security measures but does not promise that any system or transmission over the internet is absolutely secure.

5.5. Retention periods, access and database backups of an installed tracker are configured by its owner. Deleting an account on micator.com does not by itself delete data from the User's server or from the recipients of their postbacks.

6. The User's rights

6.1. The User may request information about the processing of their data, correction of inaccuracies, a copy, deletion or restriction of processing in the cases provided for by applicable law. Requests can be sent to the email in section 8, including without signing in to the account.

6.2. To avoid disclosing information to someone else, the Operator may ask the User to confirm that they own the account before fulfilling a request. If there is a lawful basis to keep part of the data, the User is told the reason for and the scope of such retention.

6.3. If processing is based on consent, the consent can be withdrawn; this does not affect the lawfulness of processing carried out before. The User keeps the right to apply to a competent authority or a court. Refusing to provide data needed to perform the contract may make it impossible for the account to work and for a license to be provided.

7. Changes to the Policy

7.1. The current version is published on this page with the date of the change. If the purposes, scope or recipients of data change materially, the Operator posts a notice on the website or in the customer account.

7.2. If new processing requires separate consent, it is requested before the processing starts. Continued use of the website does not by itself replace such consent.

8. How to get in touch

8.1. Operator: Developereva, an individual. For questions about data and how this Policy is applied:

8.2. Support in your account or [email protected]. Requests are accepted in Russian and English.