Raftaar Legal

Privacy Policy

Effective September 7, 2026 | Version 1.4

Raftaar is an internet performance testing app. This policy explains what information Raftaar processes, why it is used, where it goes, and the choices available to you.

1. Scope and operator

This Privacy Policy applies to the Raftaar Android app and related Raftaar services ("Raftaar," "we," "us," or "our"). Raftaar does not currently require an account and does not ask for your name, phone number, contacts, or payment information.

Privacy questions and requests may be sent to support@raftaarspeedtest.com.

2. Information Raftaar processes

Speed-test measurements

When you start a test, Raftaar measures and records download speed, upload speed, ping, jitter, bytes transferred, test duration, test type, selected test endpoint, and the date and time of the test.

Network information

Raftaar processes whether your connection is Wi-Fi, mobile data, Ethernet, or VPN; your internet or mobile provider name when available; a general signal-quality label; and the selected test server. Signal information may be used transiently for display and is not part of the result uploaded to Raftaar.

Approximate location

If you enable approximate location, Raftaar may process city, region, country, an area key, and coarse latitude and longitude rounded to two decimal places. This information is used to show area rankings and compare provider performance by area. Raftaar requests Android's coarse location permission, not precise location permission.

If you disable approximate location in Settings, location fields are omitted from new Raftaar result records and previously cached area information is cleared from Raftaar preferences. An IP-based network lookup may still infer a rough city or region while identifying a Wi-Fi provider, because any internet service can see the public IP address used to connect.

Identifiers and preferences

Raftaar generates a random installation ID, random session IDs, and random result IDs. These identifiers let the service count anonymous app sessions, sync results without an account, and avoid duplicate uploads. A session start includes the random installation and session IDs, platform, app version, and start time. Raftaar starts a new session after the app has remained in the background for at least 30 minutes. If you opt in to engagement notifications, Firebase Cloud Messaging generates a device registration token. Raftaar associates that token with the random installation ID, app version, language, time zone, broad network type, approximate area key when enabled, notification choices, and last registration time so it can route relevant alerts and remove stale registrations. Raftaar also records whether an anonymous notification campaign was received or opened so delivery and usefulness can be measured. Raftaar does not use the Android advertising ID for this purpose.

Advertising and consent information

Raftaar uses Google Mobile Ads to display advertising and Google's User Messaging Platform to collect and apply advertising privacy choices where required. Google Mobile Ads may automatically process and share the device's IP address, advertising ID or other device identifiers when available, app and ad interactions, and diagnostic information for advertising, measurement, analytics, security, and fraud prevention. An IP address may be used to estimate a general location.

Raftaar does not send your speed-test measurements, saved test history, provider name, or Android coarse-location coordinates to Google Mobile Ads as ad-targeting parameters. Ads may be personalized or non-personalized according to applicable law, availability, your consent choices, and device settings.

Public IP address and technical logs

Your public IP address is necessarily visible to each server contacted during a speed test or metadata request. Raftaar does not add your public IP address to the result payload sent to the Raftaar API, but Raftaar and third-party servers may process it in ordinary request or security logs under their own practices.

Crash and diagnostic information

Raftaar uses Firebase Crashlytics to diagnose crashes, application-not-responding events, and handled speed-test failures. Crashlytics may process stack traces, exception information, relevant app state, app version, device model, operating-system information, and Firebase or Crashlytics installation identifiers. Raftaar may attach limited diagnostic context such as the speed-test phase, endpoint type, retry number, network category, and failure code. Raftaar does not intentionally attach your provider name, location, result ID, Raftaar installation ID, or test URLs as custom diagnostic fields.

Support communications

If you email support, we receive your email address and any information you choose to include. We use it to respond to your request and maintain support records.

3. How information is used

• Run download, upload, ping, and jitter measurements.
• Display current and historical results on your device.
• Select and troubleshoot a suitable measurement server.
• Produce provider and area-level comparisons from submitted results.
• Sync pending results, prevent duplicate submissions, maintain security, and diagnose failures.
• Monitor app stability and investigate crashes, application-not-responding events, and handled technical failures.
• Measure anonymous active users, new users, sessions, and app-version adoption.
• Send opted-in area insights, occasional test reminders, and important product updates.
• Display and measure advertising, apply consent choices, prevent advertising fraud, and support the app.
• Remember your choices and respond to support requests.

4. Where information is stored

On your device

Test history and result details are stored in Raftaar's local database. Preferences and the installation ID are stored in local app preferences. Local history remains until you clear it, delete individual results where available, clear app data, or uninstall the app. Depending on your Android and backup-provider settings, local app data may also be included in a device backup controlled by you and the platform provider.

On Raftaar systems

Raftaar saves completed results locally first, then attempts to sync them to Raftaar. A synced record may include the installation ID, result ID, measurements, provider, network type, client platform, approximate area fields when enabled, transfer totals, duration, endpoint source, and timestamp. Raftaar uses these records to provide rankings, provider statistics, service integrity, and future history-related functionality.

Raftaar also stores anonymous session-start records containing the random installation and session IDs, platform, app version, coarse country code inferred by the server when available, client start time, and server receipt time. Offline session starts may be delivered later. Session records are used for aggregate product analytics and are not used for advertising or behavioral profiling.

If engagement notifications are enabled, Raftaar also stores the Firebase registration token and notification-routing fields described in Section 2. The registration is removed when all engagement notification categories are disabled and may be removed when Firebase reports that the token is no longer valid.

5. Service providers

Measurement Lab (M-Lab)

M-Lab may process performance measurements, connection data including public IP address, timestamp, and environment metadata. M-Lab controls its own processing and public dataset. Review the M-Lab Privacy Policy and Acceptable Use Policy.

Cloudflare

If M-Lab is unavailable or another fallback path is selected, Raftaar may use Cloudflare measurement endpoints. Cloudflare states that its speed service receives the connecting IP address, estimates city and country, identifies the ISP's autonomous system number, and may share anonymized measurement information with measurement partners. Review the Cloudflare Privacy Policy.

IPWhois

On Wi-Fi, Raftaar may call the ipwho.is service to identify the network provider. The service receives the public IP address as part of the request and can return ISP and rough location metadata. Raftaar uses returned location fields only when the location setting is enabled. Review the IPWhois Privacy Policy.

Android platform services

When approximate location is enabled, Raftaar uses Android location and geocoding services. Those services may be provided by your device manufacturer, operating-system provider, or configured location provider and are subject to their policies.

Google Firebase Crashlytics

Google processes crash and diagnostic information for Raftaar as a service provider so we can identify stability problems and fix defects. Crashlytics is not used by Raftaar for advertising or general-purpose usage analytics. Review Privacy and Security in Firebase and the Google Privacy Policy.

Google Firebase Cloud Messaging

If you enable engagement notifications, Google Firebase Cloud Messaging processes a device registration token and message-delivery data to route alerts to your device. Raftaar sends data-only messages and builds the visible notification on your device. Firebase Cloud Messaging is not used by Raftaar for advertising or behavioral profiling.

Google Mobile Ads and User Messaging Platform

Google processes advertising identifiers when available, IP address, app and ad interactions, diagnostics, and consent information to provide, measure, personalize where permitted, secure, and prevent fraud in advertising. Review Google's Privacy Policy and How Google uses information from sites or apps that use its services.

6. Sharing and public rankings

We do not sell personal information and do not use Raftaar speed-test results or location fields for targeted advertising. Google Mobile Ads separately processes the advertising data described in this policy. Information may be disclosed:

• To the measurement and metadata providers described above when needed to provide the feature.
• As aggregated provider or area statistics that are not designed to identify a particular person.
• To service providers acting for Raftaar, including Google Firebase for crash reporting, diagnostics, and opted-in message delivery.
• To Google Mobile Ads and User Messaging Platform to provide advertising, consent management, measurement, security, and fraud prevention.
• When required by law, legal process, or to protect users, the service, or the public.
• As part of a merger, acquisition, financing, or transfer of the service, subject to applicable law.

M-Lab's publication of test data is governed by M-Lab's own policy and is separate from Raftaar's aggregated rankings.

7. Your choices and controls

• Approximate location: enable or disable it in Settings and control permission through Android settings.
• Area ranking: disable the ranking preference in Settings.
• Local history: export it as CSV or clear it from Settings.
• Background test: cancel an active test from the app or its foreground notification.
• Notifications: independently enable or disable area insights, smart test reminders, and product updates in Raftaar Settings, and control the overall permission or channels through Android settings. Active speed-test foreground notifications are operational and only appear during a test.
• Advertising privacy: open Ad Privacy Choices in Settings when a privacy message is available for your region. You can also reset or delete the Android advertising ID and adjust supported advertising controls in Android settings.

To request access to or deletion of records held by Raftaar, email support@raftaarspeedtest.com. Include relevant result IDs or an exported history file if available so we can reasonably identify the records. We may need to retain limited information where required for security, legal compliance, or dispute resolution. Requests concerning M-Lab or another independent provider must also be directed to that provider.

8. Retention

Local data is retained as described in Section 4. Raftaar retains synced result records for as long as reasonably needed to provide historical provider comparisons, maintain dataset integrity, secure the service, resolve disputes, and meet legal obligations. Aggregated or de-identified statistics may be retained longer. Support communications are retained as reasonably needed to handle the request and maintain business records.

Google states that Firebase Crashlytics keeps crash stack traces and associated identifiers for 90 days before beginning removal from live and backup systems.

Push registrations remain active while at least one engagement category is enabled and the token remains valid. Raftaar limits campaigns to recently active registrations and removes tokens reported invalid by Firebase.

Anonymous session records are retained as reasonably needed to measure aggregate app usage, understand version adoption, and operate the service.

Google controls retention of advertising, consent, and diagnostic information processed through Google Mobile Ads and User Messaging Platform under Google's policies and applicable settings.

Third parties set their own retention periods. In particular, M-Lab states that its public experiment data is retained indefinitely.

9. Security

Raftaar uses HTTPS or secure WebSocket connections for current API and test traffic and applies reasonable technical and organizational safeguards. No system is completely secure, and we cannot guarantee that data will never be lost, intercepted, or accessed without authorization.

10. International processing

Raftaar and measurement providers may process information in countries other than your own. Data protection rules may differ in those locations. M-Lab servers are internationally distributed, and a selected server may be outside your country.

11. Children

Raftaar is not directed to children under 16, and users under 16 must not use the speed-test service. This age threshold also reflects M-Lab's current platform policy. If you believe a child has submitted information through Raftaar, contact us.

12. Privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection regarding personal information, and to complain to a data-protection authority. These rights may be subject to identity verification and legal exceptions. Contact us to submit a request.

13. Changes to this policy

We may update this policy when Raftaar's features, providers, or legal obligations change. The effective date and version at the top will be revised. Material changes may also be communicated in the app or store listing where appropriate.