PRIVACY POLICY
Last Updated: September 2026
1. Scope & Applicable Applications
This Unified Privacy Policy applies to all mobile software applications, tools, and digital solutions published and maintained by Toar Kumaat - Cvision across all platforms and regions globally.
Because Cvision develops applications with different technical functions, not every application uses every permission, feature, service, or data category described in this Privacy Policy.
The specific data practices applicable to a particular application depend on its actual functionality, permissions, services, and features.
Compliance: We are committed to adhering to applicable privacy and data protection requirements, including the Indonesian Personal Data Protection Law (UU PDP No. 27 Tahun 2022), the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), and applicable Google Play Developer Policies and privacy requirements.
2. Core Philosophy: Offline-First & Zero Server Tracking
At Cvision, your privacy and engineering confidentiality are our highest priorities.
Many applications within the Cvision suite are built using an Offline-First architecture. Where applicable, application data is processed and stored locally on your physical device.
We do not require users to register an account, create a Cvision profile, or submit their name, email, or telephone number merely to use the core functionality of our offline-first applications.
Key Guarantee: Cvision does NOT operate, own, or lease external centralized servers intended to store users' local project files, photographs, formulas, calculation histories, documents, portfolio content, or other locally processed application data for offline-first applications.
Your data remains under your control on your physical device unless you explicitly choose to export, save, share, or otherwise transfer it to another location or third-party service.
Certain platform or third-party services may process limited information where required to provide specific functionality, such as application distribution, In-App Purchases, entitlement verification, operating-system functionality, or user-initiated sharing.
Such platform processing is separate from Cvision maintaining a centralized repository of the user's application data.
3. Permissions & Data Collection (Highest Standard)
Depending on the technical functionality required by each specific application, certain hardware or system permissions may be requested from your device.
The following sections describe permissions and data categories that may be used by particular Cvision applications.
A permission, feature, or data category listed below does not necessarily apply to every Cvision application.
3.1 Precise Location Data
[INCLUDE THIS SECTION ONLY IF APP USES GPS/GNSS]
Technical Scope: Permission: ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION
Purpose: Where applicable, real-time GPS/GNSS location data may be accessed solely to provide location-based functionality such as coordinate capture, cadastral boundary mapping, land polygon calculations, topographic survey traverses, navigation, field measurements, or other location-related functions provided by the specific application.
Privacy Safeguard: Where location information is processed locally, it is processed and stored on the device and is not transmitted to Cvision servers for tracking, profiling, or behavioral advertising.
3.2 Bluetooth & External Hardware
[INCLUDE THIS SECTION ONLY IF APP CONNECTS TO EXTERNAL INSTRUMENTS]
Technical Scope: Depending on the application and Android version, permissions may include BLUETOOTH_CONNECT, BLUETOOTH_SCAN, and applicable legacy Bluetooth permissions.
Purpose: Bluetooth functionality may be used exclusively to discover and establish direct wireless communication with supported external instruments and hardware, such as GNSS/RTK receivers, total stations, laser distance meters, measurement devices, or other compatible equipment.
Bluetooth functionality is not intended for behavioral tracking or advertising.
3.3 Local Storage & File Export
[INCLUDE THIS SECTION IN APPLICATIONS THAT USE LOCAL STORAGE OR FILE EXPORT]
Storage Scope: Standard Android application-specific sandbox storage and, where applicable, user-authorized document access through the Android Storage Access Framework.
Purpose: Depending on the application, local storage may be used to store:
engineering projects;
architectural projects;
calculation data;
photographs;
portfolio information;
inspection checklists;
documents;
user profiles;
professional information;
credentials;
project records; and
other application-specific working data.
Applications may also export documents such as PDF reports, portfolio documents, CSV data, CAD drawings, images, or other supported formats when the user explicitly selects Export, Save, or Share.
3.4 Camera & Photographic Attachments
[INCLUDE THIS SECTION ONLY IF APP CAPTURES OR IMPORTS PHOTOS]
Where applicable, users may optionally capture, select, import, or attach photographs or other media for application functionality.
Photographs may be used for purposes including:
visual documentation;
architectural or design portfolios;
project documentation;
inspection records;
construction documentation;
visual evidence;
reports; or
other functions provided by the particular application.
Where an application is designed for local/offline processing, photographs remain stored within the application's local storage or a user-authorized storage location and are not uploaded to a Cvision server unless explicitly stated otherwise.
3.5 User Profiles, Professional Information & Credentials
[INCLUDE THIS SECTION ONLY IF APP PROVIDES PROFILE, PROFESSIONAL, OR CREDENTIAL FEATURES]
Certain applications may allow users to voluntarily enter information relating to their professional or personal profile.
Depending on the application's purpose, this may include:
name;
profile photograph;
biography;
professional experience;
services;
contact information;
license information;
certification information;
professional credentials;
organization information; and
other information voluntarily provided by the user.
Such information is processed according to the technical architecture and functionality of the particular application.
For offline-first applications, this information is stored locally on the user's device and is not transmitted to Cvision servers.
Where professional licenses or certifications are entered by the user, such information is considered user-provided information.
Cvision does not represent that user-provided credentials have been independently verified unless a particular service explicitly states otherwise.
3.6 Mathematical Logic & Computational Engine
[INCLUDE THIS SECTION ONLY IF APP PERFORMS MATHEMATICAL, ENGINEERING, SCIENTIFIC, OR SYMBOLIC CALCULATIONS]
On-Device Math: Where applicable, mathematical operations, engineering calculations, formulas, matrix algebra, symbolic mathematics, graphing operations, and related computational processes are executed on-device using internal calculation libraries.
No mathematical formulas, calculation histories, or problem sets are transmitted externally by offline-first applications unless explicitly stated otherwise.
4. PDF Generation, Export & User-Initiated Sharing
Certain Cvision applications may generate PDF documents, reports, portfolios, or other files locally on the user's device.
Generated documents may contain photographs, project information, calculations, professional information, documents, or other content selected by the user.
When the user explicitly chooses Save, Export, Open, or Share, the generated file may be transferred to a user-selected storage location or another application through the standard Android sharing mechanism.
This may include applications such as:
messaging applications;
email applications;
cloud storage applications;
document management applications; or
other compatible applications selected by the user.
This transfer is initiated by the user.
Cvision does not receive or store a document merely because the user chooses to share it with another application.
Once a file has been exported or transferred outside the Cvision application's private storage, its subsequent handling is governed by the storage location or third-party application selected by the user.
5. In-App Purchases, Subscriptions & Financial Transactions
Where applicable, monetization features—including Lifetime In-App Purchases and Auto-Renewing Subscriptions—are processed through the official platform billing system, including the Google Play Billing Library for Android applications distributed through Google Play.
Security: Zero Financial Data Access
Cvision does NOT directly process or store:
credit card numbers;
debit card numbers;
CVVs or security codes;
bank account numbers; or
complete billing credentials.
Payment processing is conducted by the applicable platform provider, such as Google LLC through Google Play, under its applicable Terms of Service and Privacy Policy.
Receipt Handling: Where required for entitlement verification, applications may receive limited purchase-related information such as product identifiers, purchase status, transaction information, purchase tokens, or other information made available through the applicable platform billing APIs.
Such information is used for licensing, entitlement, subscription, or premium-feature functionality where applicable.
6. Third-Party Libraries & Telemetry
Cvision applications may use Android platform components, Google Play Services, or other third-party libraries where technically necessary.
The specific services used depend on the particular application.
Our applications do not intentionally include third-party advertising SDKs, behavioral advertising systems, social network tracking plugins, or commercial data brokers unless explicitly disclosed for a particular application.
Third-party or platform services may be used for functions such as:
application distribution;
In-App Purchases;
application integrity;
operating-system functionality;
file handling;
document sharing;
authentication, where applicable; or
other declared technical functions.
Third-party services operate according to their own applicable terms and privacy policies.
The actual data practices of each application depend on its production build, permissions, dependencies, SDKs, and enabled services.
7. Data Retention, Control & Deletion
For offline-first applications, users retain direct control over information stored locally on their device.
Depending on the application, users may delete locally stored:
projects;
photographs;
calculation histories;
portfolio information;
profile information;
professional credentials;
documents;
cached files; and
other application data.
Deletion: Locally stored application data may generally be permanently removed through the application's available deletion functions, by clearing the application's storage through Android device settings, or by uninstalling the application.
Important: Files that users have explicitly exported or saved outside the application's private storage are no longer controlled by the application.
For example, a PDF saved to the Android Downloads folder must be deleted by the user from that location if the user wishes to remove it.
8. Export & Data Portability
Where an application provides an export function, users may export their information into formats supported by that application.
Depending on the application, supported formats may include:
PDF;
CSV;
DXF;
images;
documents; and
other supported file formats.
The availability of a particular export format depends on the specific application.
9. Children's Privacy
Our applications are primarily specialized technical, engineering, architectural, scientific, educational, and productivity tools designed for professionals, engineers, surveyors, architects, designers, students, technicians, and other users.
Our applications are not specifically directed toward children.
We do not knowingly request children to provide personal information for purposes unrelated to the application's stated functionality.
10. Security
Cvision applications are designed with reasonable technical safeguards appropriate to their intended functionality.
For offline-first applications, project information, photographs, calculations, documents, profiles, and other working data are primarily maintained within the application's local storage environment.
Users are responsible for protecting access to their physical device, device credentials, exported documents, and other files outside the application.
No method of electronic storage or transmission can be guaranteed to be completely secure.
11. User Responsibility for Submitted Information
Users are responsible for the information, photographs, documents, professional credentials, project data, and other materials they voluntarily enter, capture, import, export, or share through Cvision applications.
Users should ensure that they have the appropriate authorization to use and distribute information belonging to clients, employers, organizations, or other third parties.
This is particularly relevant to applications that create professional portfolios, reports, inspection records, project documentation, calculations, or other documents intended for distribution.
12. Policy Amendments
We may occasionally update this Privacy Policy to reflect:
application enhancements;
new functionality;
changes in third-party services;
changes in applicable legal requirements; or
changes in Google Play or other platform requirements.
Any modifications will be posted to our official Privacy Policy URL.
Where appropriate, application-specific changes may also be communicated within the relevant application.
13. Contact
Developer: Toar Kumaat - Cvision
Official Support Email: cvision.tools@gmail.com
If you have questions, legal inquiries, or data privacy requests concerning any Cvision application, please contact:
cvision.tools@gmail.com