GMeasure ARLegal and privacy center
EN

Data Safety

See which data goes where

This page summarizes current Android and iOS data practices and distinguishes local measurement content from information processed by integrated SDKs.

Effective

No GMeasure AR account

The app does not require a name, email, or password and has no developer-operated measurement sync service.

Encrypted in transit

Firebase, AdMob, Maps, ARCore, and store connections use their providers' transport protections.

Local work can be deleted

Delete items or projects, clear app data, or uninstall. Exported files must be deleted from their destination separately.

View contents
  1. Data practice summary
  2. Data types
  3. Collection and sharing
  4. Security and deletion
  5. Device permissions
  6. Play Console alignment
  7. Data questions

1. Data practice summary

Measurements and formsPrimarily stored on device and not automatically uploaded to the developer.
Background locationNot requested. Location is used while you operate GPS, map, or Geospatial features.
Sale of measurement contentThe developer does not sell your measurement content. AdMob processes advertising data under consent choices and Google’s policies.
ExportsData is transferred when you choose a file and destination using an export or share command.

2. Data types the app or its SDKs may process

Approximate and precise location

Data
GPS coordinates, accuracy, current location, and coarse location derived from IP address.
Purpose
Map, GPS, and AR Geospatial functionality; geometry calculations; analytics; advertising; and fraud prevention.
Handling
Saved coordinates remain with local measurements. Google Maps, ARCore, Analytics, or AdMob may receive data according to the feature and consent settings.

Camera, images, and AR sensor data

Data
Camera frames, motion, orientation, depth, photos, and map captures created by the user.
Purpose
Surface detection, tracking, measurement, point placement, capture, and optional Cloud Anchor or Geospatial processing.
Handling
Standard AR is processed on device. Cloud or Geospatial data may go to Google after disclosure and consent. Saved images remain local until exported.

App activity and purchase history

Data
App opens, screens, limited feature events, ad interactions, product identifiers, price, and entitlement state.
Purpose
Usage analysis, ad delivery and measurement, Premium verification, and product improvement.
Handling
Firebase Analytics, AdMob, and Google Play or the App Store process data for their functions. Necessary entitlement state is stored locally.

App information, performance, and identifiers

Data
Stack traces, crash-time app state, device and OS metadata, IP address, app-instance ID, Firebase/Crashlytics installation IDs, and available advertising/device IDs.
Purpose
Crash diagnosis, performance, analytics, advertising, and fraud prevention.
Handling
Firebase Crashlytics/Analytics and the Google Mobile Ads SDK transmit data with TLS and retain it under Google's policies.

User-generated content

Data
Project and folder names, geometry, results, coordinates, colors, notes, custom forms, and responses.
Purpose
Organizing, displaying, editing, and exporting measurements.
Handling
Stored in the app database on device and not automatically sent to the developer. It leaves the device when you export/share or use a related external feature.

3. What collection and sharing mean

Under Google Play’s definitions, information sent off device by an SDK may count as collected even when the developer does not see raw records. Data sent to an advertising provider or another third party may need to be declared as shared depending on the provider’s role and Play’s current exceptions. GMeasure AR must therefore account for Firebase, AdMob, Maps, ARCore, Billing, and its own code.

The developer does not automatically upload your project names, geometry, images, or form responses and does not use that content for advertising. Advertising and analytics SDKs still process identifiers, interactions, diagnostics, and coarse location as described above.

4. Security, retention, and deletion

  • Integrated SDKs use TLS/HTTPS for transmitted data according to provider documentation.
  • Local measurements use operating-system app storage; we do not claim separate encryption of the SQLite database.
  • Delete items, projects, or folders in the app, or clear app data/uninstall to remove local app data.
  • Exported PDFs, KML files, images, and other files must be removed from Files, Downloads, cloud storage, or their destination.
  • There is no GMeasure AR server account to delete.

For requests concerning Analytics or Crashlytics data accessible to the developer, email toptoshirou3@gmail.com. Anonymous or aggregated records may not be linkable to your device.

5. Device permissions and their purposes

CameraAR measurement, surface scanning, capture, and measurement imagery.
Approximate/precise locationGPS measurement, current location, map points, and AR Geospatial.
Photos/filesImport, save, and export content at your request; older Android versions may use legacy storage access.
InternetMaps, ads, update checks, Firebase, AR Cloud/Geospatial, and purchase verification.
VibrationBrief haptic feedback for supported measurement actions; it does not collect data.

6. Google Play Data safety alignment

The Play Console declaration should account for at least Location, App activity, App info and performance, Device or other IDs, and Purchase history based on the SDK versions and configuration in the submitted build. Photos/videos, Files/docs, and User-generated content should be assessed against Play’s current definitions and user-initiated-transfer exceptions.

SDK behavior can change after upgrades. Review the official guidance for every release:

Google Play Data safety requirementsFirebase SDK data disclosuresGoogle Mobile Ads SDK data disclosure

7. Data questions

Contact TopToshirou at toptoshirou3@gmail.com and include your platform and app version.