Contevra Privacy Policy

Effective date: 27 September 2026 · Last updated: 3 November 2026

1. Who we are

Contevra is developed and published by YADRITRANS TECH LIMITED LIABILITY COMPANY ("YadriTrans Tech", "we", "us", "our"), a limited liability company registered in Wyoming, United States, with a registered address at 30 N Gould St Ste N, Sheridan, WY 82801, United States. This policy explains how the Contevra Android app handles information. It does not cover the yadritranstech.com website or our other product, YTPublishers — see our general Privacy Policy for those.

2. Information Contevra works with

Contevra is a contact and lightweight CRM app. The CRM information you create in it may include names, organizations, job details, phone numbers, email addresses, postal addresses, websites, profile links, notes, opportunity information, activities and follow-ups. Where that information is stored depends on whether you use Contevra in phone-only mode or a signed-in account workspace, described below.

3. Phone-only local storage

If you use Contevra without signing in ("phone-only mode"), your CRM records are held in the app's private local storage on your device. We do not receive or have access to phone-only information. It is not synchronized anywhere unless you explicitly copy it into a signed-in account workspace.

4. Signed-in account workspace storage

If you sign in with Google and enable Google Drive synchronization, your CRM workspace is stored in the private application-data area of your own Google Drive account, as described in section 12. Signed-in workspace information is not "local only" — it is synchronized to your Google account once you turn synchronization on.

5. Camera access

Contevra requests camera access only at the moment you start a business-card scan. It does not access the camera in the background or for any other purpose.

6. On-device business-card OCR

When you scan a business card, Contevra runs optical character recognition (OCR) on your device to extract Latin-script contact details (such as name, company, role, phone, email and address) from the image. This processing happens on the device. The card image itself is used temporarily to extract this information; it is not uploaded by Contevra and is not retained as part of your CRM record.

7. On-device QR, vCard and MECARD decoding

Contevra can read supported QR codes encoded in the vCard or MECARD formats. Decoding happens on the device. You review the recognized fields before they are saved as a CRM record — nothing is saved automatically.

8. Data entered manually by users

Any information you type directly into Contevra — contacts, notes, opportunities, follow-ups, or edits to scanned or synchronized data — is CRM information under this policy and is stored according to whether you are in phone-only mode or a signed-in workspace.

9. Optional reminder notifications

You can schedule follow-up reminders with an optional notification and sound. Reminders are scheduled locally on your device. We design lock-screen notification previews to avoid displaying detailed CRM information where the device and Android version allow it, but exact lock-screen behavior can vary by device and by your own Android notification settings.

10. Optional Android backup and device transfer

Android backup is off by default inside Contevra. If you separately enable "Allow CRM backup" in Contevra and backup is enabled in Android, Android may back up eligible phone-only CRM data to the backup provider selected on your device or transfer it to a new phone. Eligible data can include contact details, notes, activities and other CRM records. Card images, temporary OCR text, SDK databases, device identifiers and the backup-consent preference are excluded. Cloud backup requires supported device encryption. Android controls backup scheduling and restoration. Disabling future backup does not delete copies already held by the backup provider.

11. Optional Google sign-in

Signing in with Google is optional and is only required if you want to use Google Drive synchronization or Google Contacts synchronization. Signing in by itself does not turn either synchronization feature on — each requires its own, separate consent inside the app.

12. Optional Google Drive application-data synchronization

When you separately enable it, Contevra stores your signed-in CRM workspace in the private application-data area of your Google Drive account. Synchronized CRM information can include contacts, companies, contact methods, profile links, notes, opportunities, activities and follow-ups. Phone-only records are not uploaded unless you explicitly copy them into the signed-in account workspace. Raw business-card images and raw scan content are excluded from synchronization. Google Drive application-data storage is private to your account and is not a folder you browse directly in the regular Drive interface.

13. Optional Google Contacts synchronization

When you separately enable it, Contevra can read and synchronize supported contact fields from your Google Contacts. Supported fields can include names, phone numbers, email addresses, company and job information, postal addresses and websites. CRM notes, activities, opportunities, follow-ups, business-card images and raw scans are not written to Google Contacts. Contevra does not request broad Android device-contacts permissions in order to provide this feature.

Contevra never automatically deletes a Google Contact. Deleting a CRM contact in Contevra suppresses future reimport of that entry but preserves the original in your Google Contacts. Deleting a contact directly in Google Contacts preserves its CRM history in Contevra and unlinks the two records — Contevra does not automatically recreate the deleted Google Contact.

14. User-initiated calls, email, browser and WhatsApp actions

When you choose to call, email, message on WhatsApp, or open a website or profile link from a contact record, Contevra hands the relevant information (such as a phone number or email address) to your device's phone, email, messaging or browser app so that action can proceed. This only happens when you tap the corresponding action — Contevra does not initiate these actions on its own, and it does not perform background discovery of WhatsApp accounts or scrape social networks.

15. Data retention

Phone-only information is retained on your device until you delete it or clear the app's storage. Signed-in workspace information is retained in your Google Drive application-data area until it is removed. Deleting an individual CRM record removes it from the active synchronized CRM state, but earlier versions of that record may remain in Contevra's Drive synchronization history until you use the complete "Delete Drive CRM data" action described in section 19. Revoking Contevra's Google authorization stops future access but does not by itself delete existing copies (see section 20).

16. Pausing synchronization

You can pause Google Drive or Google Contacts synchronization from within Contevra. Pausing stops further synchronization but does not automatically delete information already stored locally on your device or already stored in your Google Drive.

17. Signing out

Signing out of your Google account in Contevra stops the app from accessing that account. It does not automatically delete CRM information already stored locally on your device or already synchronized to your Google Drive.

18. Deleting local records

You can delete individual CRM records from within Contevra. You can also remove all local Contevra data from your device through Android's own app storage settings. See the Contevra Data Deletion page for the exact steps.

19. Deleting Contevra data stored in Google Drive

Deleting an individual CRM record removes it from your active synchronized CRM state, but because synchronization keeps a history, earlier versions of that record may still exist in Contevra's Drive synchronization history. To remove that history completely, Contevra provides a separate, complete "Delete Drive CRM data" action. This full deletion:

• requires you to reauthenticate with Google before it proceeds;
• is permanent and removes Contevra's CRM history from Drive;
• does not delete records that remain on your device locally — those must be deleted separately (section 18);
• leaves an empty deletion marker in place, so that a stale, still-synchronized device cannot later restore the information you erased;
• may require you to finish or pause synchronization on any other signed-in devices first, so they do not immediately resynchronize the deleted data.

The current app cannot restart Google Drive synchronization for an account after a full Drive CRM data deletion on that account. See the Contevra Data Deletion page for the expected in-app steps, and always follow the instructions shown inside the app itself, since exact menu wording can change between app versions.

20. Revoking Google authorization

You can revoke Contevra's access to your Google account at any time at myaccount.google.com/connections. Revoking authorization stops future access but does not, by itself, delete information already stored locally on your device or already stored in your Google Drive.

21. Sharing, transfer and disclosure of Google user data

This section identifies every category of recipient to whom Contevra may disclose or transfer information received from Google APIs. Except as described below, YadriTrans Tech does not share Google user data with any other person or company.

• Google LLC and the Google services you authorize. Contevra sends the minimum information required to Google Identity services and Firebase Authentication to sign you in. If you separately enable synchronization, Contevra exchanges the relevant data directly with the Google Drive API for your private Drive application-data area and with the Google People API for your Google Contacts. Google processes that information under Google's own terms and privacy policies.
• Apps and services you deliberately choose. When you tap a call, email, WhatsApp, website or profile action, Contevra passes only the relevant contact detail to the phone, email, messaging or browser app you selected. If the record originated from Google Contacts, that user-initiated action may therefore disclose part of that Google user data to the selected app or service. Contevra does not initiate these disclosures in the background.
• Your selected Android backup or device-transfer provider. If you separately enable Contevra's backup option and Android backup or device transfer is also enabled, eligible phone-only CRM data may be transferred to the backup provider selected on your device or to your new device, as explained in section 10. Contevra does not choose that provider or start a transfer without your settings and action.
• Legal and safety disclosures. We may disclose information only when we are legally required to do so, such as in response to a valid court order or other binding legal process, or when disclosure is necessary to protect users, the public, or YadriTrans Tech from fraud, abuse, security threats or serious harm. Because Google user data is normally exchanged directly between the app and Google services, we can disclose only information that is actually in our possession or control.

Google OAuth access tokens, Drive application-data content and Google Contacts content are not sent to Contevra's Google Play billing-verification service or to unrelated analytics, advertising or data-broker services. Support personnel do not receive Google user data unless you intentionally include it in a support request.

YadriTrans Tech does not sell, rent or license Google user data; does not share it for advertising or personalized marketing; and does not use it to develop, improve or train generalized artificial-intelligence or machine-learning models. Any transfer or disclosure is limited to providing or securing the user-facing features you request, complying with law, or completing an action you deliberately initiate.

Contevra's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

22. Google services and SDK diagnostics

Contevra uses the following Google and third-party components. We will keep this list matched to the app and to the answers we give in Google Play's Data Safety section.

Contevra uses Google user data only to provide the user-facing sign-in, private Drive synchronization and Google Contacts synchronization features described in this policy.

• Google Identity services and Firebase Authentication — used for signed-in account authentication. These may process your Google account identity and technical connection information (such as tokens and device/network information needed to complete sign-in) as part of authenticating you.
• Google Drive API — processes your Drive application-data only after you separately enable Google Drive synchronization (section 12).
• Google People API — processes your Google Contacts only after you separately enable Google Contacts synchronization (section 13).
• Google ML Kit (bundled, on-device text recognition) — performs business-card OCR on the device; the image and recognized text are not intentionally uploaded by Contevra. Google documents that ML Kit's Android SDKs can themselves collect limited device information, application information, per-installation identifiers, performance metrics, API configuration, feature-event information and error codes, for Google's own diagnostics and usage analytics. We do not claim Contevra has zero SDK diagnostic collection — this is a disclosed exception specific to the ML Kit SDK, governed by Google's own terms.
• CameraX — provides local access to your device's camera once you grant camera permission (section 5); it does not itself transmit images off the device.
• ZXing (QR/barcode decoding) — decodes supported QR codes locally on the device and does not require a network request to function.

23. Security and international processing

We use reasonable technical and organizational measures to protect information Contevra handles, but no method of storage or transmission is completely secure. Synchronization through Google Drive and Google Contacts is not end-to-end encrypted, and when you enable a Google service, Google processes the relevant data under its own terms and privacy policies, which are separate from this one. Information may be processed or stored in the United States or other countries where Google or another recipient identified in section 21 operates.

24. Children's privacy

Contevra is a professional contact-management tool and is not directed to children. We do not knowingly collect personal information from anyone under 18 through Contevra.

25. Changes to this policy

We may update this policy as Contevra's features change. We will update the "Last updated" date above when we do. Material changes will be reflected here before they take effect.

26. How to contact YadriTrans Tech

For privacy questions or data-rights requests about Contevra, email privacy@yadritranstech.com. For technical support, email support@yadritranstech.com. See also our Contevra Data Deletion page and Contevra Support page.