Privacy Policy

1. Data we handle

Purpose. To run connection measurements and diagnostics and, where consent applies, improve reliability, the product, and advertising.

Legal bases. To provide the features you request, with consent where required, and under legitimate interests for security and improvements, always subject to applicable law.

Roles and third parties. SignallQ determines the purposes of its product. Providers such as Google, Firebase, and Cloudflare process data under their own services and policies; the precise legal role may vary by service and contract.

Security and retention. Data stored locally remains until you delete it or uninstall the app. The audited code does not define one retention period for remote data; it follows the applicable providers’ configuration and policies.

2. In the Android app

The app measures your device’s connection and network capabilities. Results, preferences, and profiles stay on the device; some transmissions occur only according to your consent and the feature you use.

On your device. Measurements, diagnostics, preferences, connection profiles, and network data used by the app are stored in Room/SQLite databases and DataStore.

Permissions. Internet and network-state access; Wi-Fi and location for Wi-Fi features; telephony for mobile metrics when requested; and notifications for alerts. Use depends on the feature and permission you grant.

Sent with consent. Usage events, uncontaminated diagnostic results, an anonymous device identifier, model, Android version, and app version and channel may be sent to Firebase and the SignallQ administrative Worker.

Advertising. Google Mobile Ads/AdMob can receive an ad request only after the applicable UMP flow. Remote ad settings use Firebase Remote Config.

Measurement, diagnostics, and infrastructure. Measurements exchange traffic with network services. Remote diagnostics and ingestion use Cloudflare Workers when the applicable feature runs. IP addresses and technical connection metadata may be processed transiently by the network infrastructure needed for a request; this does not mean that SignallQ stores them.

Analytics and crashes. The code integrates Firebase Analytics and Firebase Crashlytics. Analytics records events, a session identifier, and environment properties, distribution channel, and build type; Crashlytics may receive technical crash data as provided by the Firebase SDK. This policy does not promise absolute anonymity.

Delete, export, and control. Under Settings > Privacy, the app lets you clear history, delete local data, and reset the app, with confirmation. In History, measurements can be exported by period as CSV or PDF and shared through Android; the file is created temporarily in cache. LGPD consent can be changed under Settings > Privacy; ad consent is managed through the UMP flow where applicable.

3. On this website

This website uses Cloudflare Web Analytics to count visits and page views, identify pages and traffic sources, and assess loading performance. Its beacon does not use cookies or access browser storage. Separately, when you manually choose a language, the site sets the functional sq_locale cookie to remember that choice for up to one year across *.signallq.com; it is not used for analytics or advertising and can be removed through your browser’s site-data controls. Cloudflare receives the IP address needed for the connection and states that it discards it at the nearest data center without recording it in central Web Analytics databases. Counts may be sampled; visits do not represent unique people. The internal daily report uses aggregate data only from SignallQ, LagCheck, and Linka websites.

Browser test. When you start a test, your browser exchanges data directly with Cloudflare measurement endpoints (speed.cloudflare.com); Cloudflare receives technical data needed for the connection, such as the IP address. The page also calls our endpoint to show the provider, IP version, and data center without returning the IP address to the page.

Sharing. When you share a result by link, the browser sends the four displayed values (download, upload, ping, and jitter) to our server, which validates their ranges and creates a signed link. The server does not verify that these values came from a measurement. The link contains those values and its issue date, and anyone who receives it can view them. Images and video are generated in the browser.

Website events. The website sends session, page-view, and feature-use events to the server with time, random event and session identifiers, feature name, and session duration. The session identifier remains in the browser tab’s storage. Numeric test results are not included in these events.

Homepage ads. When an ad placement is configured, the homepage may display Google AdSense ads. Google’s script loads only after you accept ads in the page notice; if you decline, no ad request is made. Google may use cookies and identifiers to serve and measure ads under its policy. You can change that choice by clearing site data in your browser. Ads pause while a measurement is running.

4. Your rights and how to contact us

Subject to Brazil’s LGPD and applicable limits, you may request confirmation of processing, access, correction, anonymization, blocking, deletion, portability, information about sharing, and withdrawal or review of consent. For questions or requests, email suporte@signallq.com.

5. Change history

Version 2.3 (October 17, 2026): clarified the functional cookie used for a language preference. Version 2.2 (October 12, 2026): added the browser test, sharing, website events, and ad configuration. Version 2.1 (October 12, 2026): added notice about website Web Analytics without changing the audited Android app sections. Version 2.0 (August 27, 2026): simplified the policy to cover only the Android app after the public website became the app’s promotional landing page. Version 1.0 (August 1, 2026): created the unified policy after an audit of the Android and Web/PWA code.