Privacy Policy

inotrack consists of a self-hosted tracker, a license server that issues and checks licenses, a mobile app and the inotrack.run website. Below is what data each part processes, why, and where it goes. In short:

• We do not receive your tracker statistics. Clicks, conversions, offers, landing pages and finances stay on the customer's own server.
• The license server only knows what a license and a payment require: customer contacts, the license key, technical instance data — including the domains the tracker is installed on and its server's IP address — and USDT payment details.
• The mobile app has no ads, no third-party analytics and no tracking. It talks to your own tracker's panel; push notifications pass through our relay, which stores neither device tokens nor notification texts.
• We do not sell data and do not share it with third parties for advertising.

1. Self-hosted tracker

The tracker is installed on and runs on the customer's server. Visitor and campaign data — clicks, visitor IP addresses and user agents, conversions, postbacks, offers, landing pages, costs and revenue — is written to databases on that server. We have no access to it and receive no copies.

The customer is the controller of that data: they decide what to collect, how long to keep it and how to inform their visitors. Backups (tracker-ctl backup) stay with the customer as well.

To check its license, the tracker contacts the license server and sends technical data (see section 2). It does not include the events themselves, offers, your sites and traffic sources, per-domain statistics or financial amounts — only aggregate counters, plus the domains the tracker itself is installed on and its server's IP address.

2. License server and payments

The license server issues, renews and checks licenses. It processes:

• Customer contacts: the e-mail address you provided when buying a license or requesting a trial, plus your name and Telegram handle if you gave them to us. They are used to deliver the key and to remind you when the license is about to expire. Support may add working notes to the customer and license records.
• Orders and trials: plan, term, amount, order status and the IP address the order or trial request came from — for abuse prevention.
• The license: key, plan, expiry date, status.
• Instance data on activation and license checks: instance ID, a technical server fingerprint (it lets a key tell its own server from a copy), a machine identifier (it keeps one server from getting a trial twice), version, role (main server or edge node), a build stamp that ties the tracker image to the license, and checksums of installed modules. The same key and IP address are used when the server downloads tracker images from our registry.
• Installation domains and server IP address. On activation and on every license check (normally every 15 minutes) the tracker reports the domains it is installed on — the panel domain, tracker domains and edge node domains — and the server's external IP address if it is set in the configuration. The license server also stores the IP address the request came from. This data is needed for licensing and for protection against unlicensed use: it tells us which server each license runs on and lets us notice a key used on someone else's servers. A change of domains or address does not stop the license check. Besides the current values we keep a history: which domains and addresses the installation had and when. The domains of your sites, campaigns and traffic sources are not part of this list. You can see the same domains and IP address next to your server in your account.
• Technical telemetry: click and conversion counters, number of users and domains, version, module errors. These are numbers, not the events themselves.
• USDT payments: the receiving address, the sender's wallet address, the amount and the transaction hash. Blockchain transactions are public by nature and cannot be deleted by anyone. We do not accept or store bank cards or other payment details.
• Security log: license actions (activation, blocking, issuing access credentials) with the request IP address — to investigate abuse such as a leaked key.
• E-mail messages: the outgoing mail queue keeps the recipient address, the message type and dates. The message content (key, links) is erased from the queue as soon as it is sent. If you unsubscribed from trial and setup tips, an unsubscribe mark is kept.
• Website account: sign-in uses a one-time link sent by e-mail (we store only its hash); the session is kept in a lic.inotrack.run cookie required for the account to work, and the sign-in IP address is stored with the session. Revealing a key, exporting data and requesting account deletion are recorded in the security log with the IP address.
• Referral program (if you opened the "Partners" section of the account or arrived via a referral link): your referral code, payout wallet, commissions and payouts; for a customer — which partner they are attributed to.

3. Mobile app

The inotrack app is a client for the panel of your own tracker. It does not create accounts with us.

• Sign-in. The panel address and the panel account e-mail and password are sent only to your tracker's server. The device name and model and the app version are sent to the tracker as well. Session tokens are kept on the device in secure storage (Keychain on iOS, Keystore on Android) and are not transferred to another device via backups.
• Cache. So the app opens quickly and works offline, the most recently loaded panel data (summaries, flows, conversions) is stored in the app's storage on the device.
• The camera is used only to scan the sign-in QR code from the panel; images are not sent anywhere.
• Face ID / fingerprint is checked by the operating system; biometric data is not passed to the app.
• Push notifications. If you allow them, the app receives a device token from Apple or Google and registers it on your tracker's server together with the platform, app version and device language. When the tracker needs to send a notification (for example, about a new conversion), it passes it through our relay on the license server, and the relay hands it to Apple Push Notification service or Firebase Cloud Messaging. The relay does not store device tokens or notification texts: the database and logs keep only delivery counters per license and platform and delivery error codes.
• Updates. The app checks for and downloads updates via the Expo service (EAS Update); Expo receives technical request data — platform, app version and IP address.
• What is not there: ads, advertising identifiers, third-party analytics SDKs, or tracking of your activity across other apps and websites.

Signing out in the app deletes the session tokens and the cached data of that tracker from the device. Panel accounts are created and deleted by your tracker's administrator.

4. inotrack.run website

The purchase, trial and account sign-in forms send the e-mail address you enter to the license server (section 2); there is no password and no separate sign-up. In browser storage the site remembers the referral code you arrived with, the plan you selected and the order payment deadline — these records stay in your browser. Google Tag Manager and Yandex Metrica (including Session Replay, which records page interactions) are used for visitor statistics. These services use cookies and receive visit data: IP address, browser, device, pages viewed. You can disable them in your browser settings or with a blocker — the site keeps working.

5. Who receives data

Only those the service cannot work without:

• Apple and Google — push notification delivery;
• an e-mail service and Telegram — correspondence with customers and license notifications (including internal notifications to our team with the customer's name, e-mail and key);
• Expo — mobile app updates;
• hosting providers of our servers;
• Google and Yandex — website statistics (section 4).

Beyond that, data is disclosed only when required by applicable law.

6. Retention, export and deletion

How long license server data is kept

• The history of an installation's domains and IP addresses is kept for 12 months: a domain or address record is deleted automatically once the tracker has not reported it for longer than that. Current domains and the server address are kept with the instance data.
• Contacts, licenses, instance data, orders, payments and the security log are not deleted automatically: they are kept while the license is active and, after it ends, for renewals, payment records and abuse prevention — until you delete your account (below).
• An account sign-in link is valid for 15 minutes and a session for 7 days; their records are deleted one day after they expire.
• The mail queue keeps the address, message type and dates for 90 days. The message content is erased as soon as it is sent, and after 7 days for undelivered messages.
• Brute-force protection counters that contain an e-mail or IP address are deleted after 48 hours.
• Backups of the license server database are kept for 30 days; deleted data remains in them until that period ends.

Download your data

In your account, the "My data" section has a "Download my data" button that downloads a JSON file with everything the license server holds about your e-mail address: contacts, licenses and servers (with their domains, IP addresses and the history of domains and addresses), orders and payments, the trial request, mail history (subject and dates), the unsubscribe mark, referral data, account sessions and your actions from the security log. License keys appear in the file as the last 4 characters only (the full key is shown by the "Show key" button); support's working notes are not included. The export is available once a day and is recorded in the security log.

Delete your account

In the same section, the "Delete account" button sends a one-time link to your e-mail address (valid for 30 minutes). The account is deleted only after you open the link and confirm. After that:

• the e-mail address is replaced with its SHA-256 hash — it cannot be used to contact you and is kept so that accounting records stay linked to each other; your name, Telegram handle and support notes are erased;
• trial and expired licenses are revoked — their keys stop working. Server domains and IP addresses together with their history, the license's allowed domains and suspicious activation records are erased. The key, plan, dates, the server's identifiers and technical fingerprint and the telemetry counters remain with no link to your e-mail address: the machine identifier keeps the same server from getting a trial twice. If a tracker with a revoked key keeps contacting the license server, the server refuses it and updates the last-contact time and counters;
• orders and payments are kept for accounting: plan, amounts, wallet addresses and transaction hashes. The e-mail address in them is replaced with the same hash and the IP address is erased;
• account sessions, sign-in links, queued messages and counters containing your e-mail address are deleted; in the security log, entries about you and your licenses keep only the action type and time: the e-mail address is replaced with the hash, IP addresses and details (domains) are erased;
• in the referral program the payout wallet is erased and the referral code stops working; payouts already made (amount, wallet, transaction hash) stay in the accounting records;
• a final "account deleted" message is sent to your e-mail address. Once it is sent, the address is erased from the mail queue too (after 7 days if the message could not be delivered).

After deletion the same e-mail address can be used again for a purchase or a trial — it will be a new account.

When an account cannot be deleted. While a paid license is active: without an e-mail address it cannot be renewed or served — wait until it expires or contact support. While an order is being paid (awaiting transfer — including the 7 days after the payment deadline during which a transfer is still accepted — confirming, underpaid or awaiting a refund), and while there is an unpaid referral commission. The account page tells you the reason.

Blockchain transaction records cannot be deleted. To correct your data or ask a question, contact support. Tracker data on your own server (section 1) and panel accounts are not held by us and cannot be deleted by us — they are under your control.

7. Children

The product is intended for businesses and is not directed at children.

8. Changes

If data collection changes, we will update this page and the revision date at the top.

9. Contact

Questions about data — Telegram @SmokeJung or [email protected].