RynDevice Privacy Policy

App name · RynDevice - Device Info
Developer · Devryner
Contact · cs@devryner.com
Effective date · 2026-09-08
Last updated · 2026-09-23

Public URL: https://cs.devryner.com/en/apps/ryndevice/privacy

1. Summary

RynDevice is an app that shows you information about your own device. The values it reads and displays — model name, OS version, RAM and storage capacity, battery status, sensor readings, network information and so on — are processed only on your device and are not sent to our servers.

There is no account registration or sign-in, and we do not collect registration details such as your name or email address. However, advertising and analytics SDKs may collect device and app installation identifiers. Section 3 describes these data and their purposes.

That does not mean the app communicates with nothing. This app shows advertising and uses diagnostics and analytics tools to keep the app stable. Both are provided by Google, and some information leaves your device for those purposes. Everything that leaves your device is listed in section 3.

2. Information the app reads from your device

The device-information feature reads the following to display it on screen and does not send the values it reads to our servers. See section 3.4 for exports you initiate. Advertising and analytics SDKs may independently collect some of the same types of device information, as described in sections 3.2 and 3.3.

• Device and system — model name, manufacturer, OS version, kernel, build information, uptime
• Performance and resources — CPU/GPU specifications and utilisation, RAM and storage capacity
• Battery and thermal — charge level, charging state, voltage, temperature
• Display — resolution, refresh rate, HDR support
• Sensors — sensor inventory and live readings
• Network and SIM — connection type, IP, Wi-Fi information, carrier, signal strength
• Location — coordinates, GPS satellite status (only while you are on the location screen)
• Camera — camera specifications, preview verification
• Security — whether a screen lock is set, biometric support level, root estimation

What we do not read — we do not query the IMEI, serial number, or phone number. We also do not handle the list of installed apps, SMS or call logs, or body-sensor readings.

Microphone and camera

• The microphone is used only to measure input level in the test tools. Audio is used in memory for level calculation only and is never written to a file or transmitted.
• The camera is used only to verify that preview works. No photo or video is saved or transmitted.

Location

Location is used only to display it on screen, on the location screen and in the GPS test. It is not stored, it is not transmitted, and background location permission is never requested.

Showing the Wi-Fi network name (SSID) also requires location permission, because Android policy classifies the SSID as location information. It is not because we want to use your location for anything else.

Location obtained through the location permission is not used for advertising or analytics. It is not passed to the ad or analytics SDKs. (The approximate location those SDKs infer from your IP address is described separately in 3.2 and 3.3.)

3. Data that leaves your device

3.1 Remote translation updates

So that typos and translations can be corrected without shipping an app update, the app downloads translation files.

• Destination — static files on https://l10n.devryner.com/cdn
• What is sent — only the HTTP request needed to fetch the file. Telemetry is disabled, no installation identifier is created, and no device information is included.
• What unavoidably remains — as with any internet request, your IP address may appear in the server's access logs.

The translations bundled with the app are used when there is no network, so this has no effect on functionality.

3.2 Advertising (Google AdMob)

This app displays Google AdMob advertising.

Where ads appear

• One native ad card below the category grid on the home screen, and at the bottom of category screens and the sensor list
• A rewarded full-screen ad when you turn on "Value source" in Settings (see "Rewarded ads" below)
• There are no ads in the test tools. Those are solid-colour and touch tests, where accidental taps are a structural risk.

What is transmitted — the data controller is Google, and Google's advertising policies apply.

• Advertising and device identifiers — Android uses the advertising ID. On iOS, the IDFA is used only if you allow the ATT request; otherwise it is not accessed. The SDK may also process other app- or developer-scoped device identifiers. Whether and how ads are shown depends on advertising consent and SDK settings.
• Device signals — model, OS version, screen size, language and region settings
• IP address — from which Google may infer an approximate location (country or city level)
• Ad interactions — whether an ad was shown or clicked
• Advertising SDK diagnostics and performance — SDK error logs and performance information such as app launch time may be collected to operate, improve and analyse the advertising service.

The detailed device information the app displays (sensor readings, storage breakdown, SIM information and so on) and the screens you viewed are not passed to the ad SDK.

These identifiers can link activity to the same device or app installation even without a name or email address. When tracking is authorised on iOS, the IDFA may be linked with data from other companies’ apps and websites for personalised advertising and ad measurement.

Rewarded ads — "Value source" in Settings is an auxiliary feature that shows which API or path each piece of information came from. Turning it on requires watching a rewarded ad to the end; once watched, it stays open for 24 hours. Turning it off requires no ad and takes effect immediately. All device-information features work normally whether or not you enable it.

Consent (EEA, UK, Switzerland) — in these regions, the app checks consent status through Google User Messaging Platform (UMP) before requesting ads and shows a consent form when required.

• If the consent status does not allow ad requests, no ad slot is shown. Declining personalised advertising may still allow non-personalised or limited ads where permitted.
• Your consent choices are stored on your device and used by the Google advertising SDK to determine whether and how to serve ads. They are not sent to our own servers.
• You can withdraw consent at any time — "Ad privacy options" in Settings reopens the same form. (This row appears only in regions where the consent form applies.)

Managing your advertising identifier

• Android — Settings → Privacy (or Google) → Ads lets you reset or delete the advertising ID.
• iOS — when tracking authorisation is undetermined and system settings permit a request, the app requests ATT permission before starting the advertising SDK, after any required advertising consent form. You can manage permission under Settings → Privacy & Security → Tracking. ATT and the advertising consent form are separate; declining ATT does not stop all diagnostics and analytics collection.

3.3 Diagnostics and analytics (Firebase Crashlytics and Analytics)

To find out why the app crashes and which screens are used, we use Google Firebase Crashlytics and Firebase Analytics. The processor is Google, and Firebase's privacy policies apply.

• Crash reports (Crashlytics) — the stack trace at the time of the error, app version, device state (model, OS version, free memory and storage, screen orientation, whether the app was in the foreground), and a Crashlytics installation identifier
• Usage statistics (Analytics) — events such as app launches and screen navigation, an app instance identifier, the advertising identifier (the Android advertising ID; on iOS the IDFA only if you allowed the ATT request), device and app information, and an approximate location inferred from your IP address
• We do not set a user ID and do not attach identifying information such as a name or email address to reports.

These values overlap substantially with what this app displays on screen. What is transmitted, however, is the device state needed to diagnose errors and compile statistics — not the content you looked at.

Google retains Crashlytics crash data for 90 days before beginning deletion. Retention of Analytics data is governed by Google's policies.

Related information: Google Privacy Policy, Privacy and Security in Firebase.

3.4 When you export data yourself

Running Export device info in Settings produces a text or JSON file of the information you viewed and passes it, through the system share sheet, to an app of your choosing.

• The file is stored temporarily in the app cache and is not sent to our servers.
• Where it goes is entirely your decision. What happens after that is governed by the policy of the receiving app or service.

4. Permissions and why they are used

Feature permissions such as camera and location are requested only when you open a screen that needs them. Nothing is requested all at once on first launch. If you decline, only that item is marked "permission required" and the rest of the app works normally.

• Camera — display camera specifications, verify preview
• Location (precise and approximate) — display coordinates and GPS satellites, display the Wi-Fi SSID
• Phone state — display SIM and network registration status
• Microphone — measure input level in the microphone test
• Physical activity — display step-counter sensor values
• Nearby devices (Bluetooth) — display the list of paired devices

In addition, the following are granted without a separate prompt: internet, network state and Wi-Fi state (information display and translation updates), vibration (vibration test), and biometrics (used only to query the biometric support level; no actual authentication is performed).

Permissions declared by the ad and analytics SDKs (Android) — the permissions below were added to the app by the Google ad SDK and the Firebase SDK and are not used directly by our code.

• AD_ID — access to the advertising ID (advertising and analytics)
• ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS — Android Privacy Sandbox (Ad Services)
• FOREGROUND_SERVICE, WAKE_LOCK — the background-work library the ad SDK relies on

Permissions we never request — background location, all-files access, the list of installed apps, SMS or call logs, body sensors, phone number.

5. Retention and deletion

• We do not retain the values read by the device-information feature on our own servers. Files you export and data independently collected by SDKs are covered below.
• Your device stores settings (theme, language, temperature and capacity units), advertising consent state, the expiry time for the value-source display, and translation caches. Advertising and analytics SDKs may also store identifiers and caches needed for their operation. Uninstalling the app does not automatically delete data already sent to Google servers.
• Files created by export remain temporarily in the app cache and are removed by the system or when the app is uninstalled.
• Retention of data processed by Google in the course of serving advertising and providing diagnostics and analytics is governed by Google's policies. Crashlytics crash data is kept for 90 days (see 3.3).

6. Children's privacy

This app is not primarily directed to children. Section 3 describes data processing by advertising and analytics services. Please contact us below with questions about the processing of children’s personal information.

For advertising purposes, this app is not classified as a child-directed app and is not part of the Google Play Families programme. It is not intended for use by children under 13 (or under the age set by your jurisdiction).

7. Your rights

• Contact us below to request access, correction, deletion or to exercise other privacy rights. We will respond according to applicable law and the data actually held or processed.
• Permissions can be withdrawn at any time in your device settings.
• Advertising consent can be withdrawn from "Ad privacy options" in the app's Settings (in applicable regions).
• On Android, you can reset or delete the advertising ID; on iOS, you can change tracking permission (see 3.2). These changes do not automatically delete previously collected data or other app installation identifiers.
• If you are in the European Economic Area, the United Kingdom, Switzerland or another jurisdiction whose data-protection law grants you rights (access, rectification, erasure, restriction, objection and so on), contact us below. For data processed by Google we will point you to Google's procedures.
• Contact — cs@devryner.com

8. Changes to this policy

If anything changes we will update this document and revise the last-updated date. For significant changes, such as an increase in what is collected, we will give notice through the app or the store listing.

9. Contact

cs@devryner.com