Build Book Privacy Policy

Privacy Policy for Build Book.

This policy is written specifically for Build Book and is intended to support user transparency, store-review clarity, and a more professional understanding of how product-relevant information may be handled.

Effective Date

August 28, 2026

Developer Information

Build Book is developed and published by MKVSNX, India.

Contact Email

mkvision333@gmail.com

Introduction

Build Book has its own dedicated privacy policy because the categories of information relevant to this product are different from those used by other MKVSNX applications. This policy is intended to help users understand what information may be handled, why certain permissions may be requested, how third-party services may be involved, and how privacy-related requests can be directed to our team.

Information We Collect

Build Book may handle project names, site diary entries, tasks, materials, labour records, bills, receipts, financial observations, and photos that users choose to attach to project records. We may also process limited technical information such as device type, app version, diagnostic logs, crash information, and general product-behavior data where reasonably necessary to operate, secure, maintain, or improve the service.

Permissions Used

Depending on the released feature set and the user’s choices, Build Book may request permissions such as storage or media access, notification access, location access, or camera access. Permissions are intended to support actual app functionality rather than unrelated collection.

Why Permissions Are Needed

Permissions allow the app to deliver features that depend on direct device interaction. For example, a product may need access to user-selected files, locally saved exports, reminders, or location-aware views. Permission requests are expected to remain tied to understandable product behavior.

Location Usage

Location can help associate work with a site context or support weather-aware planning where relevant, but it is not required for every workflow.

Camera Usage

Camera access is only relevant if the released version includes features that need direct capture from the device. If the app does not require camera functionality for normal use, camera access is not required.

Storage Usage

Storage or media access may be used to read user-selected files, save created content, export records, or retain locally relevant data for ongoing use of the application. Users remain in control of what they choose to attach, import, or export.

Notifications

Notifications may be used for reminders, updates, operational prompts, or other app-related communication that supports the normal use of Build Book. Users can generally manage notification preferences through device and app settings where applicable.

Analytics

We may use limited analytics to understand broad usage trends, feature reliability, and general product performance. Analytics are intended to improve usability and stability, not to collect more personal information than necessary for app improvement.

Crash Reporting

Crash information and diagnostic signals may be processed to identify failures, improve reliability, and reduce repeat technical issues across supported devices.

Advertising

Build Book may include advertising in some versions, depending on the release model. If advertising is enabled, users should review both this policy and any relevant third-party advertising provider disclosures.

Google AdMob

If advertising is enabled, Google AdMob may process device-related or advertising-related information according to Google’s own privacy documentation and service policies.

Google Play Services

Google Play Services may be used for Android-related compatibility, diagnostics, notifications, account-adjacent support, or other platform features depending on the actual implementation in the released version.

Build Book Pro and Purchases

Build Book Pro offers Weekly, Monthly, and Annual subscriptions purchased through Google Play. Google Play handles the purchase transaction, and RevenueCat is used for subscription entitlement and purchase infrastructure, including confirming access and supporting restore purchases.

Report Exports

Build Book can create PDF, Excel, and CSV reports from information users enter in the app. Users choose when and where to save or share those exported files.

Advertising for Free Users

Google AdMob may be used to provide advertising for free users. Eligible users with an active Build Book Pro entitlement may receive an ad-free experience.

Firebase

Firebase is not mentioned as an active service unless a released version specifically integrates it and this policy is updated to reflect that use.

Expo Services

Expo Services are not referenced as active services unless a released version specifically adopts them and this policy is updated accordingly.

Third-party SDKs

Camera and storage permissions are especially relevant to documenting progress, capturing bills and receipts, and creating PDF, Excel, and CSV report exports. Third-party SDK use, if present, may also include advertising, analytics, platform support, mapping, or other service providers necessary to operate specific product features.

Data Retention

Information is retained only as long as reasonably necessary to provide app functionality, maintain service quality, troubleshoot issues, resolve disputes, preserve legitimate business records where required, and comply with applicable legal obligations. Retention needs may vary depending on the category of data and the product context.

Data Deletion

Users may request assistance regarding access, correction, or deletion by contacting mkvision333@gmail.com. Some information may also be removable directly by the user through device-level deletion, in-app deletion, or content management controls where available. Certain requests may require verification before action is taken.

Children's Privacy

Build Book is not directed to children under 13 unless the product context specifically involves institution-supervised use, as may occur in school-related scenarios. Even in those cases, data handling is intended to support the service rather than direct marketing to children.

Security

We use reasonable administrative, technical, and organizational measures intended to protect information handled through Build Book. However, no app, device, transmission method, or storage system can guarantee absolute security under all circumstances.

User Rights

Depending on applicable law, users may have rights relating to access, correction, deletion, or objection to certain forms of data handling. The practical response to a request may depend on the nature of the data, the product involved, and any legal or operational obligations that apply.

Changes to this Policy

We may update this policy when features change, service providers change, legal expectations evolve, or documentation needs improvement. The effective date at the top of the policy will be updated when a revised version becomes active.

Contact

For privacy questions about Build Book, contact mkvision333@gmail.com.