We respect your privacy. This Policy explains what data GeoBuildPro processes, why and for how long, with whom it is shared, and how you can exercise your privacy rights.
1. Scope and controller
This Policy applies to the GeoBuildPro mobile application and related services. The data controller and operator is UMi Studio. Privacy inquiries and rights requests can be sent to support@geobuildpro.com. Independent third-party services follow their own policies.
2. Data we process
Account data may include a phone number, verification code, Apple, Google, or Facebook identifier, name, email, and avatar. Purchase data may include product, transaction, price/currency, membership or subscription status, expiry, and payment result; we do not store full card, WeChat, Alipay, or store payment credentials. Technical data may include a random installation identifier, device model, operating system, app version, IP address, network state, service logs, crashes, and diagnostics. Photos or feedback are processed when you submit them. Calculations, favorites, and preferences normally remain on your device.
3. Permissions and on-device processing
Camera access supports protractor, plumb, and material-counting tools; photo or storage access supports image selection, avatars, and saving results; motion sensors measure angles; network access supports sign-in, membership verification, updates, and online services. We explain and request access when you invoke the related feature. Denying an optional permission does not block unrelated local calculators. Permissions can be revoked in system settings. Camera frames, sensor readings, and calculations are generally processed on-device unless you upload them or separately consent.
4. Purposes and legal bases
Where a first-launch privacy consent prompt is required, online SDKs initialize only after acceptance. In other regions, configured online services, including Firebase Core where supported, may initialize when the app starts. Optional permissions and user-requested features are handled when used. We process data to perform our agreement, with consent where required, to meet legal transaction and security duties, and for legitimate security, fraud-prevention, and debugging interests. We provide a separate notice and obtain separate or explicit consent for sensitive data, regulated international transfers, or whenever applicable law requires it.
5. Service providers and SDKs
Depending on the signed installation channel, GeoBuildPro conditionally uses Supabase, Firebase Analytics and Crashlytics, Sign in with Apple, Google Sign-In, Facebook Login, RevenueCat, App Store/StoreKit, Google Play Billing, and, in selected mainland Android direct-payment builds, WeChat Pay and Alipay. On supported iOS and Google Play Android builds, Firebase Analytics measures screen views and app usage, and Crashlytics collects crash reports and diagnostics. They are enabled after any applicable startup privacy consent; mainland Android builds skip Firebase. Google may process installation and app identifiers, device, OS and app versions, IP address, screen path, crash stack traces, and diagnostic information. We do not add phone numbers or calculator inputs to custom analytics events. This release does not integrate Firebase Cloud Messaging, Firestore, or Firebase Authentication. Google Mobile Ads is disabled in this release and makes no ad request. CSJ and Tencent Ads YLH/GDT are reserved interfaces without an integrated runnable SDK. Other online SDKs run according to platform, channel, configuration, and the feature used.
6. Sharing and transfer
We do not sell personal data or use it for undisclosed purposes. Sharing is limited to your consent, a service you request, restricted processors, or legal requirements. Recipients must process only the agreed minimum and provide protection at least equivalent to this Policy and applicable store rules. A new purpose requires notice and a new lawful basis. International transfers use the notices, consent, contracts, and safeguards required by applicable law.
7. Storage and retention
We retain data only as long as necessary. Account data is removed after account closure and completion of the deletion process. Transactions are retained only for applicable legal, tax, refund, and dispute periods. Security and diagnostic records are deleted or anonymized when troubleshooting, audit, or legal periods end. Local records remain until you delete them or uninstall the app. Data that must legally be retained is isolated and used only for that legal purpose.
8. Your rights and account deletion
You can request access, correction, deletion, restriction, objection, consent withdrawal, and portability where applicable. Permanent account deletion can be initiated in Settings—Account & Security or through GeoBuildPro’s public account-deletion webpage, including after uninstalling the app. Reasonable reauthentication may prevent misuse, without unreasonable barriers. Deletion covers the account, profile, device records, and associated cloud business data, and processors are instructed to delete them. Sign in with Apple tokens are revoked where applicable. Account deletion does not cancel App Store or Google Play billing; immediate deletion remains available and subscriptions are managed separately in the original store.
9. Children
GeoBuildPro is intended primarily for adult professionals and is not directed to children under 14 or the applicable local digital-consent age. Minors should use it only with guardian approval. If child data was collected without valid consent, we will delete it promptly.
10. Security and incidents
We use reasonable safeguards including encryption in transit, access controls, least privilege, auditing, and backups. No online service is completely secure. If an incident may affect your rights, we will mitigate it and provide legally required notice of the event, likely impact, response, and recommended actions.
11. Changes and contact
We prominently announce material changes and seek renewed consent when required. This webpage, the in-app policy, Google Play Data safety disclosures, Apple privacy labels, and other store submissions will match the permissions, SDKs, and behavior of the released build. Contact support@geobuildpro.com with questions, complaints, or rights requests.
12. Personal data collection summary
| Scenario | Data | Purpose and storage |
|---|---|---|
| Local calculations and preferences | Inputs, results, favorites, language, theme, and decimal settings | Provide local features; stored on-device by default |
| Account sign-in | Phone/OTP or authorized provider ID, name, email, avatar, token, and sign-in time | Create and authenticate an account; stored by Supabase Auth as required for the account |
| Two-device account management | Protected installation ID, device label, OS, app version, session, and last sign-in | Security and abuse prevention; retained until device removal or account deletion |
| Membership purchase | User, product, transaction, price/currency, entitlement, expiry, and payment result | Purchase, restore, refund, and entitlement verification; retained for transaction compliance |
| Camera, sensors, and selected photos | Camera frames, motion readings, selected or captured images, avatar, and annotated result | Measurement, counting, avatar, and saving; processed locally unless you request upload |
| Firebase Analytics and Crashlytics on supported iOS and Google Play Android builds | Installation and app identifiers, device/OS/app version, IP, screen path, crash stack traces, and diagnostics | Measure screen usage and diagnose crashes after any applicable startup consent. Mainland Android builds skip Firebase. Calculator inputs and phone numbers are not added to custom analytics events. |
| Online security and support | IP, device/app version, request and diagnostic logs, email, description, and attachments you submit | Operate securely and answer requests; retained only as necessary |
13. Third-party sharing summary
| Service / scope | Purpose and possible data | Provider policy |
|---|---|---|
| Supabase / online account features | Authentication, profiles, devices, entitlements, and deletion; phone/provider ID, profile, protected installation ID, IP, logs, and request data | https://supabase.com/privacy |
| Firebase Analytics and Crashlytics / supported iOS and Google Play Android builds | Screen usage statistics and crash diagnostics after any applicable startup consent; installation/app identifiers, device/OS/app version, IP, screen path, crash stack traces, and diagnostics. Mainland Android builds skip Firebase. | https://firebase.google.com/support/privacy/ |
| Apple, Google, or Facebook / supported sign-in channels | Provider sign-in; provider ID, name, email, avatar, token, authorization state, and necessary network information | https://www.apple.com/legal/privacy/ https://policies.google.com/privacy https://www.facebook.com/privacy/policy/ |
| RevenueCat / App Store and Google Play membership | Products, purchases, restores, and entitlements; app/anonymous user ID, transaction, subscription state, platform, app version, IP, and diagnostics | https://www.revenuecat.com/privacy-policy |
| App Store / StoreKit and Google Play Billing | Store purchase, renewal, restore, and refund; transaction, product, price/currency, and subscription state. We do not receive full payment credentials. | https://www.apple.com/legal/privacy/ https://policies.google.com/privacy |
| WeChat Pay or Alipay / selected mainland Android direct-payment builds only | Called only after the user selects that payment method; merchant order, product/amount, signature or order string, result, and SDK-required device/network data. We do not receive the payment password. | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/RYiYJkLOrQwu0nb8 https://opendocs.alipay.com/open/54/01g6qm |
| Google Mobile Ads | Disabled in this release; no ad request, advertising identifier, impression, or click data is shared by this feature | https://policies.google.com/technologies/partner-sites |
support@geobuildpro.com