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 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, campaign domains or financial amounts — only aggregate counters.

2. License server and payments

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

• Customer contacts: the name, e-mail address and Telegram handle you provided when buying a license or requesting a trial. They are used to deliver the key and to remind you when the license is about to expire.
• 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), tracker domains, version, role (main server or edge node), a build stamp that ties the tracker image to the license, checksums of installed modules, and the IP address the request came from. The same key and IP address are used when the server downloads tracker images from our registry.
• 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 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.

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 website has no forms or sign-up. 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 and deletion

License data is kept while the license is active and, after it ends, as long as it is needed for renewals, payment records and abuse prevention. To find out what data about you the license server holds, or to correct or delete it, contact support. Data required to serve an active license can only be deleted together with the license; blockchain transaction records cannot be deleted.

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].