Privacy Policy

This Privacy Policy explains how the Ronic Connect Android application (“Ronic Connect,” the “app”) accesses, collects, uses, shares, retains, and protects information. It applies to the Google Play application with package name ai.ronic.calluploader and to the Ronic CRM services used by the app.

Ronic Connect does not record calls itself. It processes recordings created by a compatible phone or call-recording application. After the phone user grants Music and audio access, the app makes a best-effort folder selection from the phone brand and verifies it from Android’s media index. The user can choose a different folder at any time.

Who is responsible for your information

Ronic Connect is published through the individual Google Play developer account identified on the app’s store listing and is operated under the Ronic name. The publisher is responsible for the app’s handling of data. When a phone is linked to a Ronic CRM workspace, the organisation controlling that workspace is also responsible for the business records it asks the app to upload and for providing any notices, permissions, or lawful basis required for recording calls.

Information Ronic Connect processes

The information processed depends on the features you enable and the contents of the folder you select. It may include:

• Call recordings — audio files stored in the shared call-recording folder that the app predicts from the phone brand and verifies through Android's media index, or in a different folder the user explicitly selects through Android's folder picker.
• Call metadata — the other party's phone number, whether the call was incoming or outgoing, date and time, duration, file name, file type, file size, and a file checksum. The number and direction may be supplied by Android's call-screening service or read from a recording file name produced by your dialler or recorder.
• Contact context — when Contacts access is allowed, the app may read the saved display name for the number involved in a call. It does not upload your address book; only the name associated with a matched recording may be sent with that recording. A caller name may also be returned by the linked Ronic CRM workspace.
• Device and connection information — an app-generated device identifier, this phone's number after the phone user confirms it, app version, workspace and user identifiers, pairing status, upload status, and operational information needed to keep syncing reliable. The number may first be suggested from the linked CRM user's profile or, with Phone Number permission, from the phone's SIM; it remains editable and scanning a QR does not save it.
• Authentication information — short-lived pairing details and device credentials used to connect the phone to the authorised Ronic CRM workspace.
• Notification information — a Firebase installation or registration token and notification routing data when CRM notifications are enabled.
• Support information — information you include if you contact us for support, privacy questions, or a deletion request.

The current Google Play build requests Music and audio, Phone Number, and Contacts access and Android’s call-screening/caller-ID role for the limited purposes described below. It does not request access to the system call log, precise or approximate location, advertising identifier, or payment information. It does not contain third-party advertising.

Permissions and device access

• Music and audio / recordings folder — used to find, display, queue, and upload call-recording audio in shared storage. The app predicts the expected path from the phone manufacturer even before that folder exists, then verifies or corrects the path when Android exposes a recording in its media index. A user-selected folder can override automatic detection. Only when the user enables Delete after sync may the app try to delete a confirmed recording.
• Call-recording setup — Ronic Connect prompts every Android phone user to enable automatic recording in the phone's own dialler and to confirm after making a test call. Android does not provide a standard interface for the app to read or change this manufacturer-controlled setting. Availability and menu names vary by phone, carrier, and region.
• Phone number — used only to make a best-effort suggestion of this phone/SIM's own number during CRM linking. Android or the mobile carrier may provide no number or an inaccurate number. The app displays the suggestion for correction and saves and sends it only after the phone user taps Confirm number and link.
• Call-screening/caller-ID role — Android supplies the phone number and whether a call is incoming or outgoing at call time. Ronic Connect does not block, reject, silence, or answer calls. This access is required to match recordings whose file names do not contain a number.
• Contacts — allows Android to supply call-screening events for calls involving saved contacts and lets the app resolve the matched contact's display name. The app does not read or upload the entire address book.
• Camera — used only to scan a Ronic CRM pairing QR code. QR images are processed on the device and are not retained as photographs or uploaded as camera images.
• Notifications — routine successful uploads and automatic retries are silent. Notifications are used only when sync needs user action and for Ronic CRM alerts when you allow them. Android may separately show a system-required foreground-service indicator in managed-device builds.
• Network and background scheduling — used to connect to Ronic CRM, retry pending transfers, receive configuration, and resume scheduled work after an app or device restart.

How we use information

We process the information described above to:

• Pair an authorised phone with the correct Ronic CRM workspace and user.
• Detect new recordings in the automatically identified or user-selected folder and maintain a local upload queue.
• Securely upload recordings and associated call metadata to the linked workspace.
• Associate a recording with the appropriate CRM record and provide optional CRM caller information.
• Display pending, completed, skipped, and failed sync status and prevent duplicate uploads.
• Deliver requested CRM notifications, apply workspace configuration, diagnose delivery failures, protect the service, and revoke a device when necessary.
• Respond to support, privacy, access, correction, and deletion requests and comply with legal obligations.

When information is sent from the phone

Before a phone is linked, recordings can be detected and held in the app’s local queue but cannot be uploaded to Ronic CRM. After linking, the app sends queued and newly detected recordings, their associated metadata, and device connection information to the authorised workspace. The app may also send a push-notification token and periodic connection status so syncing and CRM notifications continue to work.

The app uploads a recording only after it has this phone’s number, the other party’s real number, and an incoming or outgoing direction. If those details cannot be resolved, including when a caller withholds their number, the recording remains pending on the phone rather than being uploaded as an unknown caller.

How information is shared

We do not sell personal information or use it for targeted advertising.

Information may be disclosed only to:

• The linked organisation — recordings and related metadata become available to authorised users of the Ronic CRM workspace selected during pairing.
• Service providers — infrastructure, storage, security, support, and notification providers that process information to operate Ronic Connect and Ronic CRM. Google Firebase Cloud Messaging is used for app notifications and installation routing.
• Legal and safety recipients — where disclosure is required by law or is reasonably necessary to protect users, investigate abuse or security incidents, or protect legal rights.
• A successor — if the service or relevant assets are reorganised, transferred, or acquired, subject to this policy and applicable law.

Legal basis and call-recording responsibility

Depending on the location and context, information may be processed to provide the service requested by the user and their organisation, with consent, to protect legitimate security and operational interests, or to comply with law. Call-recording laws vary. The user and the organisation controlling the linked workspace must make sure recording is lawful and that every required consent, notice, or other legal basis is obtained before a call is recorded or uploaded.

Storage, retention, and local deletion

• On the phone — recordings remain in the dialler's shared folder or the user-selected override folder by default. Ronic Connect keeps local queue and sync records for operation and duplicate prevention.
• Delete after sync — this option is off by default. A local recording is deleted only after the server confirms receipt, the user enables deletion, and the linked organisation's configuration permits it.
• In Ronic CRM — uploaded recordings and metadata are retained while the linked organisation maintains the workspace or needs the records for the purposes described here, subject to the organisation's retention choices, contractual requirements, and applicable law.
• After deletion — information is deleted or anonymised when it is no longer needed, except where limited retention is required for legal compliance, security, fraud prevention, dispute resolution, or routine backup recovery.

Uninstalling Ronic Connect removes app-controlled information from the phone but does not delete audio in the detected or user-selected folder or information already uploaded to Ronic CRM. Unlinking a device stops authenticated syncing and removes its local connection credentials; it does not automatically erase CRM records.

Data deletion requests

To request access, correction, or deletion of information associated with Ronic Connect, email sumeet@ronic.ai with the subject Ronic Connect data request. Include the workspace name, the phone or device identifier if known, and enough information for us to verify the request. Do not email a call recording or device credential.

We will coordinate with the linked organisation where it controls the relevant CRM records. We may ask for identity or authority verification and may retain limited information where required by law or necessary for security, fraud prevention, or resolving disputes. You may also ask an administrator of your linked Ronic CRM workspace to remove recordings or revoke the device.

Security

Ronic Connect uses HTTPS/TLS for data in transit, Android security controls for locally stored credentials, authenticated device pairing, checksum-based upload verification, and access controls within the linked workspace. We use reasonable administrative and technical safeguards, but no transmission or storage method can be guaranteed completely secure.

International processing

Ronic Connect, the linked organisation, and service providers may process information in countries other than the user’s country. Where required, we use appropriate safeguards for international transfers and apply the protections described in this policy.

Your rights and choices

• Allow or revoke Music and audio access in Android settings. You may replace the automatically detected OEM recording folder with a folder you choose.
• Choose whether to allow notifications and camera access.
• Allow or revoke Phone Number or Contacts access and the call-screening/caller-ID role in Android settings. The phone number can still be entered and confirmed manually. Without call identity access, recordings whose file names lack a real other-party number and direction remain pending and cannot be uploaded.
• Keep local recordings after sync, which is the default, or enable confirmed deletion where permitted.
• Unlink the device from Ronic CRM and ask the workspace administrator to revoke access.
• Request access, correction, deletion, restriction, objection, or portability where applicable, and withdraw consent where processing relies on consent.
• Complain to the relevant data-protection authority where that right is available.

Children's privacy

Ronic Connect is a business application intended for adults and is not directed to anyone under 18. We do not knowingly collect children’s personal information through the app. Contact us if you believe a child’s information has been processed so that it can be investigated and removed where appropriate.

Changes to this policy

We may update this policy as Ronic Connect changes or legal requirements evolve. The “Last updated” date identifies the current version. Material changes will be reflected on this page and, where appropriate, communicated in the app or through the linked organisation.

Contact

Privacy, support, and deletion enquiries for Ronic Connect can be sent to sumeet@ronic.ai. The publisher identity shown on the Ronic Connect Google Play listing is the responsible developer for this policy.

For the separate ronic.ai website policy, see the ronic.ai Privacy Policy.