1. Who we are and what this policy covers
The controller responsible for data processing is Ragimov Software, Schönbornstraße 33, 76646 Bruchsal, Germany ("AllTracker", "we", "us"). You can reach us at privacy@alltracker.org.
This policy covers:
- our websites alltracker.org, alltracker.de, alltracker.su, alltracker.cc, alltracker-family.com and alltracker-business.com;
- the apps AllTracker Control Center, AllTracker Video Surveillance, AllTracker Communication Monitoring, AllTracker Family, AllTracker Business and AllTracker X (Anti-Theft and System Security) in the versions named at the top of this page.
For older app versions the previous privacy policy applies. Information on cookies is in our Cookie and Tracking Notice.
2. In short
- Media are not stored on our servers. Photos, videos, audio, call recordings, screenshots and files go from the monitored device directly to your browser during an active session. They stay on the device until you view or download them.
- Relay-blind encryption. Content that passes through our socket relay is encrypted with AES-256-GCM. The relay only sees ciphertext.
- Live streams and direct file transfers are end-to-end encrypted (WebRTC, DTLS-SRTP).
- What we do store: your account, technical details of connected devices, event notifications (for up to 30 days), support requests, payment records and logs. Details below.
- We do not sell your data.
3. What data we process
Account and payments
When you register we store your name, email address and language, and optionally a profile picture, which you can upload on the website or in the Control Center app and which we store in Google Cloud Storage. Sign-in runs through Google Firebase Authentication (also when you sign in with Google, Facebook or VK). For purchases we store your plans, credits and payment records. Card and account details are entered directly with the payment provider and do not reach us.
Using the website
When you use the website, our servers process your IP address, browser details and the pages and functions you use (access and usage logs). To prevent abuse of free trials we compute a browser fingerprint in your browser and send it with the trial request. Error reports from the website are sent to Rollbar. Analytics (Google Analytics) and advertising for free and trial accounts (Google AdSense, Yandex Direct) are only loaded with your consent in the cookie banner.
Technical details of connected devices
So that you can see the state of a connected device and we can fix device-specific issues, the app sends technical details to our backend and we store them:
- device ID (Android ID), manufacturer, model, device name, Android and app version;
- SIM and network details (operator, SIM serial number, mobile/Wi-Fi status, Wi-Fi network name);
- battery level, free memory, time zone, granted permissions and app settings;
- the app currently in use and the last called number;
- technical app logs (connection and session logs) and the device's IP address.
The current location of the device is not stored as part of these details.
Monitoring content
Content the device collects for you — location, messages, call logs, notifications, keystrokes, browser history, contacts, photos, videos, audio, screen and camera — is only transmitted when you request it in an active session. It is sent encrypted through our relay (see section 4) and is not stored on our servers.
| Data | Transport | Stored by us |
|---|---|---|
| Location, messages, call logs, notifications, keystrokes, browser history, contacts, app usage | Socket relay, relay-blind encrypted | No |
| Photos, videos, audio, call recordings, files up to 20 MB | Socket relay, relay-blind encrypted | No |
| Larger files | WebRTC data channel, end-to-end encrypted | No |
| Live camera, screen and audio | WebRTC, end-to-end encrypted (DTLS-SRTP) | No. You save recordings on your own device. |
| Event notifications (e.g. keyword hits, 18+ detection) | Via our backend | Yes, up to 30 days (see below) |
Event notifications
If you set up events (for example keyword alerts or 18+ detection), the device sends a notification to our backend when an event occurs. It contains the type of event, the app, a short text excerpt and, for keyword hits, a preview image. We store these notifications so that you can see them in the Control Center and on the website, and pass them on via push. They are processed by our backend and are therefore not relay-blind. 18+ detection runs entirely on the device with a local model; no images are sent for the analysis.
Support
For support requests we store your messages and attachments. A new request starts with our AI assistant, which runs on the OpenAI API. In the process, your messages, basic account details and, if you select a device, its technical details are sent to OpenAI. Please do not share sensitive data in the chat. You can also write to support@alltracker.org directly.
4. How data travels and how it is protected
All connections between browser, apps and our servers use TLS.
Relay-blind socket encryption
From app version 12.0.0, your browser creates a new 256-bit key for every session. The key is held in memory only and is sent to the device together with the start command, via our backend and Google Firebase Cloud Messaging (on Huawei devices, Huawei Push). Content between browser and device is encrypted with AES-256-GCM. Our socket relay forwards it without being able to read it. Only routing information (action type, account and device identifiers) stays readable.
Because the key passes through our backend and the push service, this is not end-to-end encryption in the strict sense. We call it "relay-blind": the servers that forward your content cannot read it. Our backend does not log the key.
WebRTC: live streams and large files
Live streams and large file transfers use WebRTC and are end-to-end encrypted with DTLS-SRTP. If no direct connection is possible, the encrypted data is forwarded by a TURN server (Turnix, as a fallback Xirsys). These providers receive your IP address but cannot read the content. To establish connections we also use Google's public STUN servers.
5. Service providers and recipients
We only pass data on where this is needed to provide the service, to get paid, or with your consent. Our service providers process data on our behalf and according to our instructions.
| Provider | Purpose | Data |
|---|---|---|
| Google Cloud (App Engine, Datastore, Cloud Storage, Logging, BigQuery) | Hosting of backend and database, storage of support attachments and profile pictures, logs | Account, device details, events, logs |
| Google Firebase | Sign-in, push messages to devices (FCM), crash reports and app statistics (Crashlytics, Analytics) | Email, name, device tokens, session key in the start command, crash diagnostics: device and app info, stack traces and error messages, account and device identifiers (no monitoring content) |
| Huawei Push Kit | Push messages to Huawei devices | Device token, start command incl. session key |
| Hetzner and other hosting providers | Website delivery and socket relay servers in Germany, Russia and Turkey | IP address, encrypted content (relay) |
| Turnix, Xirsys, Google STUN | Establishing and relaying WebRTC connections | IP address, encrypted media |
| Stripe, PayPal and, where offered, YooKassa, YooMoney, CoinGate | Payment processing | Payment and contact details |
| RevenueCat, ProfitWell | Subscription management and revenue statistics | Subscription and payment details |
| Google Places | Address suggestions when entering a billing address | Address entered |
| SendGrid | Sending emails | Email address, email content |
| OpenAI | AI support assistant | Chat messages, account and device details (see section 3) |
| Rollbar | Error reports from the website | Technical error data, browser details |
| Google Analytics, Google AdSense, Yandex Direct | Analytics and advertising, only with your consent | Usage data, cookie IDs, IP address |
| OpenStreetMap | Map tiles for location display | IP address of your browser |
Some of these providers process data outside the EU, for example in the USA. Where this is the case, the transfer is based on an adequacy decision of the EU Commission or on standard contractual clauses.
In addition, we disclose data where we are legally required to, to enforce our terms, or to protect our users or others from harm.
6. How long we keep data
| Data | Retention |
|---|---|
| Monitoring content and media | Not stored (only passed through in an active session) |
| Event notifications | Up to 30 days; you can delete them earlier at any time |
| Website usage logs incl. IP address | 30 days |
| Account usage history | 1 year |
| Account, device details, support requests with attachments | As long as your account exists |
After you delete your account
Within a few hours we delete your login, profile data and profile picture, your devices' files, web sessions and notifications. We separate the remaining data from your email address by replacing it with a random identifier (pseudonymisation) and keep it as follows, counted from the deletion:
- 1 year: usage history (purchased plans, connected devices), support requests with attachments, AI chats, access logs including IP addresses, and reviews that are no longer published — to protect against fraud and abuse and to handle enquiries.
- 1 year: a keyed hash of your email address. It prevents a new registration with the same address during this time and lets us find the record for enquiries.
- 4 years, only for accounts with payments: the same hash, to match payments in case of enquiries or disputes.
- Up to 9 years: payment records and credit movements (statutory retention of accounting records).
- 4 years: records of trial use per device and of redeemed coupons, to protect against abuse.
- No fixed period: a log of the deletion without the email address, as proof that it took place.
Backups still contain deleted data for up to 14 days. A deleted account cannot be restored.
7. Legal bases
We process personal data on the following legal bases of the GDPR:
- performance of the contract with you (Art. 6(1)(b)): account, device connection, transmission, payments, support;
- legal obligations (Art. 6(1)(c)): retention of accounting records;
- legitimate interests (Art. 6(1)(f)): security, prevention of fraud and abuse, error analysis, enforcement of claims;
- your consent (Art. 6(1)(a)): analytics, advertising, AI support chat. You can withdraw consent at any time.
8. Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and to object to processing. Many of these you can exercise directly in your account (for example deleting events or deleting the account); otherwise write to privacy@alltracker.org. You also have the right to lodge a complaint with a data protection supervisory authority.
You can change your cookie choices at any time; see the Cookie and Tracking Notice.
9. Monitored persons
AllTracker is installed on the device itself, and Android permissions are granted there. Use it only on devices you own or that you are legally authorised to monitor, and inform the people concerned where required by law. For the processing of data of monitored persons, the user of the account is responsible for the lawfulness of the monitoring.
The rules for monitoring devices and people differ from country to country. We do not provide legal advice and cannot tell you whether a particular use is permitted where you live; please check the laws that apply to you before you start monitoring.
10. Changes and contact
We update this policy when our services or legal requirements change. The current version is always published on this page; we announce significant changes on the website or by email.
Questions about privacy: privacy@alltracker.org or our support area.