Privacy Policy

Effective date: September 9, 2026

Scobasoft (“we,” “us,” or “our”) operates the Can Hacker Mobile Android application, package name com.scobasoft.canhacker (“the App”). This Privacy Policy explains what information the App accesses, stores, uses, and may share.

1. What the App Does

The App connects to compatible vehicle diagnostic and CAN adapters and provides tools such as CAN bus monitoring, protocol analysis, request/response diagnostics, message sending, custom PID processing, ELM tools, logging, ELM proxy functions, and ECU/adapter emulation utilities where supported.

The App does not require registration and does not create a Scobasoft online user account.

2. Vehicle, Diagnostic, CAN, and Adapter Data

When you use diagnostic functions, the App may read and process information exchanged with a vehicle, ECU, CAN bus, or diagnostic adapter. Depending on the selected mode, this can include CAN identifiers, raw frames, diagnostic requests and responses, parameter values, fault-related information, adapter responses, protocol settings, and connection status.

This information is processed on your Android device for the functions you select. Scobasoft does not automatically upload this diagnostic or CAN data to a Scobasoft server.

If you deliberately export, share, or transmit a log or other file using Android sharing features or another application, the destination and further processing are controlled by you and the selected service.

3. Bluetooth, BLE, Wi-Fi, USB, and Local Network Access

The App supports several adapter connection methods:

• Bluetooth Classic and Bluetooth Low Energy (BLE): used to discover, identify, connect to, and exchange data with supported adapters.
• Wi-Fi / local network: used to connect to compatible Wi-Fi diagnostic adapters and for local TCP-based tools such as the ELM Proxy when you start them.
• USB host: used to communicate directly with supported USB adapters connected to the Android device.

On Android 11 and earlier, Android may require Location permission for Bluetooth device discovery. The App requests this legacy permission for Bluetooth discovery compatibility; it is not used by the App to obtain or store your GPS location. On newer Android versions, the App uses the dedicated Bluetooth scan/connect permissions, and Bluetooth scanning is declared as not being used for location.

When you intentionally run a local proxy/server function, diagnostic traffic may be exchanged with a client device on your local network. This happens only as part of the function you start and is not an automatic upload to Scobasoft.

4. Local Logs, Settings, PIDs, and Files

The App stores operational settings and application data locally on the device. Depending on your use, locally stored data can include adapter and profile settings, custom PID databases, activation settings, selected trace files, command files, diagnostic/CAN logs, ELM traces, and exported files.

Temporary trace data may also be stored in the App cache. Files that you explicitly export are saved to the location you select or to an App-managed export location, depending on the function used.

Android device-backup features may include eligible App data in a device or cloud backup if backup is enabled in your Android settings. Such backups are managed by Android and the provider of your device backup service, not by Scobasoft.

5. Account Name Used for Manual Activation

The App can let you choose an existing Google or Yandex account name for the optional manual activation method. The selected account name may be an email address. The App stores the selected account name locally and uses it to verify an activation code on the device.

The App does not request or receive your account password. The selected account name is not automatically uploaded to a Scobasoft server. If you choose to contact support for manual activation and send the account name to us, you deliberately provide that information through the communication method you select.

6. Advertising and Consent — Google AdMob

The non-activated version of the App displays advertising. Activated users have advertising disabled by the App. Advertising and consent management are provided through Google Mobile Ads (AdMob) and Google’s User Messaging Platform (UMP).

Google advertising services may collect or receive information such as IP address, device and advertising identifiers where permitted, general location derived from IP address, App/device information, advertising interactions, and diagnostic information. The exact use of data can depend on your region, consent choices, Google settings, and whether personalized advertising is permitted.

Consent and privacy choices offered through Google’s UMP are handled by Google. Where available, the App also provides access to Google’s privacy-options form.

7. Google Play Billing

The App uses Google Play Billing for the optional purchase that activates the full version. Purchase and payment processing is performed by Google Play. Scobasoft does not receive your payment-card details from the App.

The App receives the information required to determine purchase status, such as the relevant product, purchase state, and purchase identifier/token supplied through Google Play Billing, and may store a local activation-status cache on the device.

8. Firebase Remote Config

The App uses Google Firebase Remote Config to obtain current information used by the manual activation screen, such as developer contact/payment text and the current App price. The App is designed not to fetch Remote Config merely because the App starts; the fetch is initiated when the manual code-information screen is actually opened.

Firebase may process technical information needed to provide this service, including an app-installation identifier and information about the App and device. Diagnostic vehicle data, CAN frames, logs, custom PIDs, and the selected activation account name are not intentionally sent by the App as Remote Config parameters.

9. Internet and Network-State Permission

Internet and network access are used for features that require them, including supported Wi-Fi adapters, local-network proxy functions, Google advertising/consent services, Google Play Billing, and Firebase Remote Config. These permissions do not mean that locally collected vehicle data is automatically uploaded to Scobasoft.

10. Notifications and Foreground Service

The App can use an Android foreground connected-device service while an adapter connection or active mode is running. On Android versions that require notification permission, the App may request permission to show the corresponding service notification. This is used for App operation and does not itself provide Scobasoft with personal information.

11. Information Shared with Third Parties

The App may share or expose information in the following limited circumstances:

• with Google when using AdMob/UMP, Google Play Billing, Firebase Remote Config, and Android platform services;
• with a diagnostic adapter, vehicle ECU, USB device, or local-network client as required by a function you intentionally use;
• with another application or service when you explicitly export or share a file or initiate communication;
• when required by applicable law or a valid legal process.

We do not sell your diagnostic logs, CAN data, custom PIDs, or activation account name to third parties.

12. Third-Party Privacy Information

Google services used by the App are governed by Google’s applicable terms and privacy documentation. Useful references include:

• Google Privacy Policy
• How Google uses information for advertising
• Google Mobile Ads SDK data disclosure
• Firebase Privacy and Security information

13. Data Retention and Deletion

Local App data remains on your device until it is deleted by an App function where available, cleared through Android settings, removed with the relevant exported file, or removed when the App is uninstalled, subject to Android backup/restore behavior and the characteristics of the particular storage location.

If you voluntarily send information to Scobasoft for support or manual activation, correspondence may be kept for as long as reasonably necessary to provide support, document activation, resolve disputes, or meet legal obligations. You can contact us at scoba1986@gmail.com to request deletion of personal information that you previously sent directly to Scobasoft, subject to legal or operational retention requirements.

Information processed by Google or another service is retained and deleted according to that provider’s own policies and your settings with that provider.

14. Data Security

The App uses Android application storage and permission mechanisms to limit access to locally stored data. Communications with Google services use the security mechanisms provided by those services.

Vehicle diagnostic protocols, Bluetooth adapters, Wi-Fi adapters, local TCP connections, and some CAN/ELM workflows are not inherently encrypted. You should use diagnostic adapters and local networks that you trust. No method of electronic storage or transmission can be guaranteed to be completely secure.

15. Children’s Privacy

Can Hacker Mobile is intended for vehicle owners, technicians, developers, and other users working with vehicle diagnostics and CAN networks. It is not designed or directed toward children. We do not knowingly operate a service intended to collect personal information from children.

16. International Processing

Google and other external service providers may process information in countries other than your country of residence. Their processing is governed by their own privacy policies and applicable legal safeguards.

17. Changes to This Privacy Policy

We may update this Privacy Policy when the App, its third-party services, or legal requirements change. The updated version will be published on this page with a revised effective date.

18. Contact

Developer: Scobasoft
Email: scoba1986@gmail.com
Telegram community: https://t.me/econtoolwwe