Privacy Policy

3.1 Personal Information Provided by You at Sign-in

We may collect personal information that you voluntarily provide to us, including:

• Name: Collected at the time of account registration for identification purposes.
• Phone Numbers: We collect your phone number during registration to create and manage your account.Your phone number is also used to identify the SIM card (SIM 1 or SIM 2) on your device, so that calls can be correctly handled when using Callyzer as your default dialer.SIM associated phone numbers may be securely transmitted to our servers only for device identification, SIM configuration, and account management purposes.We do not use your phone number for promotional messages, marketing communication, or SMS campaigns.We do not sell or share your phone number with any third parties.
• Email Address: Collected and used in connection with subscription services, account communication, and support-related correspondence.
• SIM Information: We may access SIM-related details such as carrier name and SIM slot information to identify which SIM card (SIM 1 or SIM 2) is being used for making or receiving calls within the application.
  For users who use Callyzer without creating an account, no SIM-associated phone number is transmitted to or stored on our servers. All core features of the application are fully accessible without account registration.
  For users who choose to sign up for a Callyzer account (required only to access premium features), the SIM-associated phone number linked to your registered account may be securely transmitted to our servers solely to verify your premium subscription and associate your account with the correct device and SIM card. This ensures that premium features are correctly activated and maintained on your device.
  SIM serial numbers (ICC IDs) are not collected, transmitted, or stored on our servers under any circumstances.

3.2 Payment Data

If you make purchases through the application, we may collect certain payment-related information necessary to facilitate such transactions. All payment data is processed and stored by third-party payment service providers, such as Google In-App Purchases.

3.3 Social Media Login Data

We may provide you with the option to register or log in using your existing third-party account credentials, such as your Google account. In such cases, we may receive certain profile information from the relevant third-party provider, subject to your authorization.

3.4 Application and Device Data

Subject to your permissions, we may collect the following information when you use our application:

• Mobile Device Access: We may request access to certain features of your device, including contacts, call logs, phone state, and storage. Access to external storage enables functionalities such as importing and exporting data, including in formats such as CSV, JSON, Excel, and PDF.
• Mobile Device Data: We may automatically collect technical information about your device, including device identifier, model, manufacturer, operating system, IP address, and browser type, to ensure compatibility, security, and performance optimization.
• Push Notifications: With your consent, we may send you notifications related to your account, updates, and application features. You may opt out of receiving such notifications through your device settings at any time.
• Default Dialer Permission: We may request your permission to allow the application dialer to function as your default dialer. You retain full control over this setting and may change it at any time.

3.5 Call Log Data Storage

Your call log data is stored locally on your device within a secure, and is not transmitted to our servers. If you are a premium subscriber and choose to enable backup functionality, your call log data may be backed up to your personal Google Drive account, which remains under your control.

3.6 Diagnostic Log Files

We maintain diagnostic log files within the application for the purpose of troubleshooting and improving performance. These log files are stored locally within the application’s private internal storage and are automatically sanitized to remove any personally identifiable information. You may choose to share such log files with our support team via email; however, such sharing occurs only upon your explicit initiation and consent.

3.7 Grievance mail

In the event of any complaint or issue, you may share the relevant log files with us via email for diagnostic and support purposes. Such log files shall be limited strictly to technical information, including server errors, code exceptions, and system crash reports. It is expressly clarified that the log files shared will not contain any sensitive personal data, confidential information, or any other information of a protected or regulated nature.

3.8 Information Collected Automatically

We automatically collect certain technical and usage-related information when you visit, access, or use the Services. This information does not directly identify you as an individual but may include data related to your device and how you interact with the Services. Such information is collected to ensure the proper functioning, security, and improvement of the Services.

The information collected may include:

• Log and Usage Data: We may automatically collect service-related, diagnostic, usage, and performance information when you access or use the Services. This may include your access times, pages viewed, features used, and other system activity logs.
• Device Data: We may collect information about the device you use to access the Services, including device type, unique device identifiers, hardware model, operating system, system configuration, language preferences, and mobile network information.
• Crash Analytics: We use Firebase Crashlytics to collect anonymized crash reports for the purpose of diagnosing issues and improving application stability and performance. Such crash reports do not contain personally identifiable information.

3.9 Data Access, Storage and User Control

Permissions and Their Usage:

Callyzer only requests permissions necessary to provide its core functionality. All permissions are requested with user consent and can be managed or revoked at any time through device settings.

• Call Log Permission: Required for Callyzer to function as your default phone dialer. As a default dialer, call log access is essential to display call history, manage calls, and provide dialer functionality. Analytics and reports are generated from this data as a secondary feature. All call log data is processed locally on your device and is never uploaded to our servers.
• Phone (Default Dialer) Permission: Enables making and receiving calls when Callyzer is set as the default dialer.
• Contacts Permission: Used to access contact details including name, phone number, profile photo, contact ID, and favourite status to provide contact listing, call matching, and analytics features. All contact data is processed locally on your device and is never uploaded, transmitted, or stored on our servers. See Contacts Data section below for full details
• Storage Permission: Used to save exported reports and backups locally on the device.
• Internet Permission: Enables account-related services and optional features like backup and sync.

User Consent and Control

Callyzer operates with full transparency and requires user permission before accessing any data.

By using the app, you consent to access and processing of call logs and contacts strictly for core features such as analytics and reporting.

Permissions are requested via the Android system, and you can allow, deny, or revoke them anytime.

Data Storage and Data Flow

• Data Stored on Your Device: Call logs and analytics remain locally stored. No upload to servers.
• Data Stored on Our Servers: Callyzer can be used without creating an account. If you choose to sign up to access premium features, we may store limited account-related information on our secure servers, including your name, email address, device details, and SIM-associated phone number. The SIM-associated phone number is stored solely to verify your premium subscription and associate your account with the correct device and SIM card. For users who use Callyzer without signing up, no personal information is stored on our servers.
• Google Drive Backup (Optional): If you choose to enable backup, your call log data may be stored in your personal Google Drive account. This data remains entirely under your control and is not accessed by Callyzer servers at any time.
• Third-Party Services: Callyzer uses Firebase Crashlytics, a trusted third-party service by Google, to collect anonymised crash reports and performance data solely to improve app stability. Firebase Crashlytics does not have access to your call log data, contact data, or any personally identifiable information.
• User Control:: You have full control over your data. You can delete your account and associated data at any time via callyzer.co/delete-account, clear app data through your device settings, or uninstall the application at any time.

Call Log Data

Callyzer functions as your default phone dialer. As a default dialer, access to the Android system call log is essential for the app to operate correctly. Without call log access, the dialer cannot display call history, manage missed calls, or provide any call-related functionality to the user.

Why call log access is required:

• To display your call history within the dialer interface
• To manage and present incoming, outgoing, missed, and rejected calls made through dialer
• To enable the user to review, filter, and act on their own call logs
• To generate call analytics and reports based on the user's own call activity

Call log data accessed includes:

• Call type (incoming, outgoing, missed, rejected)
• Call duration
• Call time
• Phone number

How this data is handled:

• All call log data is processed and stored locally on your device only
• Call log data is never uploaded, transmitted, or stored on our servers
• Call log data is never shared with any third party
• Call log data is never used for advertising, marketing, or any purpose beyond providing dialer and analytics features to you
• Callyzer does not record call audio or call content at any time

This data stays on your device. Callyzer does not record calls or upload call data.

Contacts Data

Callyzer requests access to your device contacts solely to automatically match phone numbers present in your Android system call log with their corresponding contact names. This enables your call analytics, reports, and call history to display recognisable contact names rather than raw phone numbers.

What contact data is accessed::

• Contact name : Displayed in call history, reports, and contact listing for better readability
• Phone number(s): matched against your call log entries to identify contacts in analytics and reports
• Contact profile photo: Displayed alongside the contact name in the contact listing within the app
• Contact ID: Used internally to uniquely identify and match contacts with call log entries accurately
• Contact favourite: Used to highlight favourite contacts at the top of the contact listing, and allows users to add or remove contacts from favourites directly within the app

Why Contact Picker is not sufficient:
The Android Contact Picker allows users to manually select one contact at a time. Callyzer requires automated bulk matching of all phone numbers across your entire call log against your full contact list simultaneously. This core functionality cannot be achieved using the Contact Picker.

How we protect your contacts::

• Contact data is processed locally on your device only
• Contact names or details are never uploaded, transmitted, or stored on our servers
• Contact data is never shared with any third party
• Contact data is never used for advertising, marketing, or any purpose beyond displaying names in your call reports

4.1. We may process your information for the following purposes:

• Account Creation and Management: To facilitate account registration, authentication, and ongoing management of your user account.
• Provision of Services: To enable core functionalities of the application, including call analytics, call management, and call tracking features.
• Quick Call Extension Feature: To facilitate remote call requests initiated through the browser extension, subject to your explicit and informed consent,
• Safety and Vital Interests: To protect your vital interests or those of another individual, including situations involving the prevention of harm, fraud, or misuse of the Services.
• Legal Compliance: To comply with applicable laws, regulations, legal processes, or enforceable governmental requests.

4.2. Furthermore, we process your personal information in accordance with applicable data protection laws, depending on your location.

12.1. How the Feature Works

• a. You establish a secure connection between the browser extension and the application by scanning a QR code within the Quick Call interface.
• b. When a phone number is selected in the browser extension, a request is transmitted to your mobile device via Firebase Cloud Messaging.
• c. Your mobile device displays a push notification containing actionable options, including “Call Now” and “Dismiss.”
• d. A call is initiated only upon your explicit action of selecting “Call Now.” The application does not initiate calls automatically under any circumstances.

12.2. Consent and User Control

• Explicit Consent Requirement: Activation of the Quick Call feature requires your prior and informed consent. You must actively enable the feature through the in-app consent prompt.
• No Automatic Dialing: Calls are never initiated automatically. Each call request requires your manual confirmation through the notification interface.
• Extension Authentication: Only browser extensions that you have explicitly connected through QR code authentication are authorized to send call requests to your device.
• User-Controlled Disconnection: You may disconnect any linked browser extension at any time either through the application settings or the browser extension interface.
• Notification Validity: Call request notifications are time-bound and will automatically expire if no action is taken within the specified period.

12.3. Data Transmission in Quick Call

12.4. Data Minimization and Limitations

No call recordings, call content, contact lists, or browsing history are transmitted, accessed, or stored as part of the Quick Call feature. The feature is designed to operate on a minimal data transfer basis strictly necessary for enabling the requested functionality.