IPatyj Traffic
Privacy policy
App data, website visits and support enquiries.
Updated: 14 November 2026
App and developer
This policy applies to the IPatyj Traffic Android app, under the IPatyj brand. The app shows mobile data and Wi-Fi usage, measures sessions, provides allowance alerts and tests connection speed.
Data used by the app
The app reads Android network usage statistics and available app names and identifiers. When the floating counter is enabled, usage events identify the active app. These data support usage displays and measurements and are processed on your phone.
Data stored on your phone
Private app storage holds settings, allowances, selected periods, sessions and their history, speed test results, selected servers and test data usage records. No account is required. The current reviewed version has no advertising or analytics SDKs and does not send usage history to the developer’s server.
CSV export you choose
You can export speed test history or saved per-app session measurements as a CSV file. Speed exports contain test dates, connection and server labels, speeds, delays, test data amounts and app version. Session exports include measurement names, app names and package identifiers, dates, duration, and mobile and Wi-Fi data amounts. Review the selected records before saving or sharing a file.
Android’s document picker lets you choose where to save the file, such as local storage or a storage provider available on your phone. IPatyj Traffic does not automatically email or upload the export to the developer. If you choose a cloud storage provider or later share the file, that destination handles the copy under its own terms and privacy policy.
A temporary copy is created in private app cache for the save operation and removed when saving finishes or the dialog is cancelled. If Android stops the process before cleanup, a temporary copy may remain until the cache or app data is cleared.
Network checks
For speed tests and connection information, the app connects over HTTPS to Cloudflare Speed Test. The server receives your IP address, request times, technical headers including the app name and version, and test data. Selecting or probing a server also makes network requests. Your app list and local usage history are not included in these requests.
Permissions
Usage access provides data usage readings. Display over other apps is needed only for the floating counter you enable. Notifications support allowance alerts and the running counter. Network state helps select a connection; basic phone network information labels the mobile connection type. Location permission is used only for optional weather while you use the app; it is not required for traffic counters or speed tests. You can revoke access in Android settings; affected features will then be unavailable.
Optional widget weather
Weather is optional. If you enable it, the app asks for Android location permission while you use the app. You can continue using traffic counters and speed tests without enabling weather. Android may provide approximate or precise location, depending on your permission choice and device settings. The app rounds latitude and longitude to two decimal places before sending them for weather and city lookup. This reduces detail but still discloses your location.
To retrieve a forecast, the app sends these rounded coordinates directly over HTTPS to MET Norway at api.met.no. MET Norway also receives your connection IP address, request time and technical headers, including the app name, version and public project contact information. Your app list and traffic history are not included. MET Norway logs API requests, including IP addresses and requested coordinates, for service operation, troubleshooting, statistics and protection against misuse. MET states that API access logs are stored in its data centre in Oslo, Norway. MET's own privacy policy governs its retention; we do not promise a fixed deletion period for forecast coordinates or that requests are anonymous or processed only in memory.
The app also passes rounded coordinates to Android's system geocoding service to obtain a city name when needed. The provider depends on the Android system installed on your device and may process the request online under its own privacy terms. We do not choose or operate that system provider.
After a successful weather check, the app can also request current precipitation over HTTPS from the IPatyj endpoint at api.ipatyj.com/traffic/v1/precipitation/current. The request contains the rounded latitude and longitude and an area identifier derived from them. The endpoint and its hosting infrastructure receive the connection IP address, request time and technical headers. Your app list and traffic history are not sent. IPatyj and the infrastructure providers process request information to deliver and protect the service. The radar application stores the shared DWD radar frame, not a history of individual location queries. Its application and route access logs are disabled. Hosting and delivery infrastructure may nevertheless retain technical records under their own policies; we do not promise anonymous requests, exclusively in-memory processing or a fixed deletion period for all infrastructure logs. DWD receives a request for a shared radar file from the IPatyj server, rather than your phone IP address or coordinates. This does not change the direct requests your phone makes to MET Norway.
The app requests KNMI observations and nowcast data from the IPatyj endpoint at api.ipatyj.com/traffic/v1/precipitation/nowcast using the same rounded coordinates. IPatyj retrieves shared KNMI radar files on its server; KNMI does not receive your phone IP address or individual coordinate query through this channel. KNMI service access is configured only on the server and no KNMI API credential is included in the app. The sources are KNMI RTCOR-5m and radar_forecast 2.0, licensed under CC BY 4.0. IPatyj samples and formats these data for the selected area. The app does not represent KNMI as endorsing this product.
Current precipitation uses Deutscher Wetterdienst RADOLAN RY radar data under CC BY 4.0. It is an estimate for a 1 km radar cell, with limited coverage, rather than a measurement at your exact position. The app checks the observation time and area before using radar evidence. Missing, stale or out-of-coverage data are not treated as an observation of no rain. DWD observations are separate from the MET Norway model forecast. A separate KNMI channel provides recent radar observations and a deterministic precipitation forecast for the next 0-90 minutes, when complete fresh data cover your area. It uses 1 km grid cells and 5-minute intervals; a radar estimate is not a measurement at your exact position. Missing steps, old data or a failed request are not a forecast of no precipitation. This feature does not provide precipitation type or probability.
The umbrella displays hourly rain probability from WeatherAPI.com through the IPatyj endpoint at api.ipatyj.com/traffic/v1/rain-chance. Your phone sends rounded coordinates to IPatyj.
The IPatyj server forwards these coordinates to WeatherAPI.com with its own IP address, without forwarding your phone IP address, app list or usage history. WeatherAPI.com processes the request under its own privacy policy.
IPatyj uses a shared area forecast cache and a shared API request counter; the rain-probability application does not log client addresses or request URLs. Hosting infrastructure may keep technical records. The API credential stays on the server.
Only rain probability for the matching hour is displayed; snow probability, humidity and daily probability are separate. Forecast cache entries expire after one hour. A stale entry, missing field, failed request or exhausted quota is not treated as zero probability.
Powered by WeatherAPI.com
WeatherAPI.com Privacy Policy
Location is checked when the app opens and every 15 minutes while an app screen is visible. Forecast refreshes respect provider cache expiry and retry pauses; a significant move can request a forecast for the new area. Tapping weather in the home screen widget starts a single location and forecast check through a short foreground location service with an Android notification. The service stops when the check finishes or times out. There is no automatic trip tracking or scheduled background location collection. When weather is enabled, a widget is present and location permission remains granted, Android also schedules forecast updates for the last saved rounded area while the app is closed. These updates use the same weather sources and do not request a new phone location or collect trips. Provider cache expiry, retry pauses, connectivity and Android battery restrictions may delay updates. Open the app or tap widget weather to update the city. Between checks, the widget displays the saved forecast. The widget clock and traffic counters work separately from weather.
Private app storage keeps the latest rounded forecast area, city, forecast including humidity when available, retrieval time, cache expiry and retry information, plus the most recent DWD radar response and a separate current-area KNMI observation/nowcast cache, source times and request error status. Older KNMI area cache entries are evicted on the next completed refresh attempt. Cache entries from earlier test builds may remain until that refresh or until app storage is cleared. The app does not keep a movement history. A new successful forecast or radar response replaces the corresponding saved data. If a request fails or permission is revoked, the saved data are retained; expired weather data may no longer be displayed. Turning weather off stops new weather requests and replaces the weather display with a setup link, but does not erase its saved caches. Clearing the app's storage or uninstalling removes the local caches together with the other app data. This does not delete records retained by service providers.
You can turn weather off in its settings or revoke location permission in Android settings. The app does not request background location permission. Forecast data are provided by MET Norway under CC BY 4.0. The app selects forecast hours, rounds displayed temperatures and computes the high and low for the next 24 hours; these are model forecasts and may differ from actual conditions.
MET Norway Privacy Policy ↗
MET Norway API personal data information ↗
Weather data source and licence ↗
About the project
Project creator: Sergejs Rudenko (IPatyj). He is responsible for IPatyj Traffic and this website and acts as the data controller for the app processing described here, website visitor data and support enquiries. Contact: support@ipatyj.com.
Website technical data are used to deliver content and protect against abuse; information in emails is used to respond and resolve your enquiry. Where GDPR applies, this processing relies on legitimate interests in operating a secure website and providing support (Article 6(1)(f)). Article 6(1)(b) may apply where an enquiry concerns necessary contractual or pre-contractual steps.
Background operation
Allowance checks may run in the background and resume after a reboot. You enable the floating counter; it runs with an ongoing notification that lets you stop it. Android may restrict or delay background work.
Retention and deletion
Local records remain until you delete them or the app’s data; speed test history keeps up to 100 most recent results. Deleting test result cards does not remove the separate test byte usage ledger. Clear IPatyj Traffic storage in Android or uninstall the app to remove all local app data. This does not clear Android’s system usage statistics. Exported CSV files are separate from app storage. Deleting a result, clearing app data or uninstalling IPatyj Traffic does not delete copies you exported. Delete those files with your file manager or the storage provider you selected. Automatic app data backup is disabled. Cloudflare’s policy governs data retained by Cloudflare.
Enquiries and policy changes
This policy will be updated if data handling changes. When contacting support, share only the information needed to resolve your issue.
Website visits and support enquiries
When you open the website, the hosting infrastructure receives technical request information: IP address, page URL, request time, browser and device information and, when supplied by your browser, referrer and language preferences. These data support page delivery, reliability and website protection. OpenAI ChatGPT Sites and Cloudflare infrastructure provide hosting and delivery.
Our pages do not include developer-installed advertising trackers or audience analytics. The language choice uses browser sessionStorage: it is kept for the current session and normally removed when the tab is closed or site data are cleared. A browser that restores a session may also restore this setting. You can clear this site’s data in browser settings; this does not delete Android app data.
Hosting infrastructure may use security cookies during security checks. Cloudflare’s documentation describes their purposes and lifetimes. Providers’ operational policies determine technical log retention; this policy does not specify a fixed site-specific retention period. Provider processing may take place outside the EEA; the provider documents linked below describe applicable terms and transfer safeguards.
When you email us, we receive your sender address, message and attachments. An email service delivers and stores correspondence. We use this information to respond and resolve the enquiry and retain it while needed for that purpose and related disputes or legal obligations. Do not send passwords or unnecessary personal data. Contact support@ipatyj.com to request information about your enquiries or their deletion.
Your rights
Where applicable, you may request access to personal data, correction or deletion, restriction of processing and portability, and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. Contact support@ipatyj.com; proportionate information may be needed to verify your request.
You may also contact a competent data protection authority, including Latvia’s Datu valsts inspekcija. We do not use website visitor data for automated decisions with legal or similarly significant effects.
Provider information
Cloudflare Privacy Policy ↗
Cloudflare Cookies ↗
ChatGPT Sites Data Processing Addendum ↗
Privacy contact
The subject already identifies IPatyj Traffic. Your email app opens a draft; you send it yourself.