Privacy Policy for BuildQuant

Effective date: July 19, 2026

Last updated: July 19, 2026

BuildQuant is developed and published by abdulazezabb.

This Privacy Policy explains how the BuildQuant mobile application handles information when you use the app.

BuildQuant is a construction material quantity and project estimation application. It allows users to calculate material requirements, create local projects, save estimates, and export or share reports.

By using BuildQuant, you acknowledge the practices described in this Privacy Policy.

1. Information We Collect

BuildQuant does not require users to create an account or provide personal information.

The current version of BuildQuant does not collect, upload, transmit, sell, rent, or share personal information with the developer or third parties.

In particular, BuildQuant does not collect:

Names, email addresses, or phone numbers.

Account credentials or passwords.

Precise or approximate location.

Contacts or address-book information.

Photos, videos, or audio recordings.

Camera or microphone data.

SMS messages or call information.

Advertising identifiers.

Device identifiers for tracking.

Payment or financial information.

Browsing history.

Health information.

Analytics or advertising data.

2. Information Entered into the App

Users may voluntarily enter information such as:

Project names.

Project descriptions.

Site or reference labels.

Material dimensions and measurements.

Quantity estimates.

Prices and currency symbols.

Calculation notes.

Saved project information.

This information is used only to provide the app’s calculation, project-management, history, backup, and export features.

The developer does not receive or remotely access this information.

3. Local Data Storage

BuildQuant is designed as an offline-first application.

Projects, estimates, preferences, calculation history, and other app information are stored locally on the user’s device within the application’s storage area.

This local information is not automatically uploaded to a server or cloud service operated by the developer.

Local data may be removed when:

The user deletes a project or estimate.

The user uses the “Reset All Local Data” option.

The user clears BuildQuant’s application data through Android settings.

The user uninstalls the application.

Uninstalling the app or clearing its data may permanently remove locally stored projects and estimates unless the user created a separate backup.

4. Backups, Exports, and Sharing

BuildQuant may allow users to generate or export:

PDF reports.

CSV files.

JSON backup files.

Text summaries.

These files are generated locally on the user’s device.

BuildQuant does not automatically upload or send exported information. A file leaves the app only when the user intentionally chooses to save, export, or share it using Android’s system interface or another application installed on the device.

Once a user shares or saves an exported file outside BuildQuant, the file may be handled by the selected application, storage provider, messaging service, email provider, or cloud service. Those third parties operate under their own privacy policies.

Users are responsible for reviewing exported files before sharing them and for choosing trusted recipients and applications.

5. Imported Backup Files

If BuildQuant supports backup importing, the app may read a backup file selected directly by the user.

The selected file is used only to restore or merge BuildQuant project information.

BuildQuant does not scan unrelated files on the device and does not automatically upload imported backup content.

Users should import backup files only from trusted sources.

6. App Permissions

The current version of BuildQuant is designed not to request sensitive Android permissions that are unnecessary for its core functionality.

BuildQuant does not require access to:

Location.

Camera.

Microphone.

Contacts.

Phone calls.

Call logs.

SMS messages.

Calendar.

Nearby devices.

Body sensors.

Notifications.

Accessibility services.

Broad device storage.

Exporting or sharing reports may use Android’s secure system file-sharing mechanism. This allows the user to choose where to send or save a file without granting BuildQuant broad access to all files stored on the device.

If a future version requires an additional permission, the permission will be requested only when necessary for a clearly described feature, and this Privacy Policy will be updated accordingly.

7. Internet Access

BuildQuant’s main calculation and project-management features are designed to work offline.

The current version does not require an account and does not transmit project or calculation information to a developer-controlled server.

If a future feature introduces online services, cloud backup, analytics, advertising, or remote support, this Privacy Policy and the Google Play Data Safety declaration will be updated before or when that functionality is released.

8. Third-Party Services

The current version of BuildQuant is intended not to include:

Advertising services.

Behavioral tracking services.

Analytics services.

Social-media tracking SDKs.

Third-party login systems.

Cloud databases controlled by the developer.

BuildQuant may use software libraries required to provide local technical functions such as database storage, PDF creation, file sharing, app settings, and Android compatibility.

These libraries should not be used by BuildQuant to create advertising profiles or track users across apps.

9. Data Sharing and Sale

The developer does not sell user data.

The developer does not share user data with advertisers, data brokers, marketing companies, or other third parties.

Information is shared externally only when the user intentionally uses an export or sharing feature and selects another application or recipient.

10. Data Retention

Because BuildQuant stores project information locally, the user controls how long that information remains on the device.

Local information remains available until it is:

Deleted by the user.

Removed through BuildQuant’s reset function.

Removed by clearing the app’s Android data.

Removed when the app is uninstalled.

Replaced during a user-approved backup restoration.

The developer does not maintain a server-side copy of this local information.

11. Data Security

BuildQuant uses Android’s application sandbox and standard platform security controls to help protect locally stored information from access by unrelated applications.

BuildQuant also aims to:

Request only permissions required for its functions.

Avoid unnecessary background activity.

Avoid advertising and tracking SDKs.

Validate imported backup files.

Generate reports locally.

Use Android’s system sharing interface.

Avoid transmitting project information to developer-controlled servers.

However, no device, application, or storage method can be guaranteed to be completely secure.

Users should protect their devices with an appropriate screen lock and avoid sharing sensitive project files with untrusted applications or recipients.

12. Children’s Privacy

BuildQuant is a general construction and material-estimation utility and is not specifically directed at children.

The application does not knowingly collect personal information from children.

Because BuildQuant does not require an account and does not transmit personal information to the developer, the developer does not knowingly maintain personal information belonging to children.

13. Calculation Disclaimer

BuildQuant provides planning estimates for convenience and informational purposes only.

Results may be affected by:

Incorrect measurements.

Material specifications.

Product coverage.

Installation methods.

Waste and breakage.

Surface conditions.

Construction practices.

Local building requirements.

Users should verify measurements, product specifications, purchase quantities, safety requirements, and professional recommendations before purchasing materials or beginning construction work.

BuildQuant does not replace a licensed engineer, architect, contractor, quantity surveyor, or other qualified professional.

14. User Choices and Data Deletion

Users can manage locally stored information directly within the application.

Depending on the available app features, users may:

Delete individual estimates.

Delete projects.

Clear calculation history.

Export a local backup.

Reset all locally stored app information.

Users may also remove all application data by clearing BuildQuant’s storage through Android settings or uninstalling the application.

Because the developer does not maintain user accounts or server-side project records, there is normally no remote account data for the developer to delete.

15. Changes to This Privacy Policy

This Privacy Policy may be updated when BuildQuant’s features, legal requirements, permissions, or data-handling practices change.

Any updated version will include a revised “Last updated” date.

Users are encouraged to review the Privacy Policy after application updates.

Material changes will be reflected in the app and, when applicable, in the Google Play listing and Data Safety declaration.

16. Contact Us

Questions, concerns, or privacy inquiries regarding BuildQuant may be sent to:

Developer: abdulazezabb

Application: BuildQuant

Package name: com.buildquant.app

Email: abdulazeza@ghaithgrouksa.com