GPS Site Camera: Stamp

Privacy Policy

This policy explains how GPS Site Camera: Stamp handles information when you use the mobile application.

Effective date: August 18, 2026

1. Scope

This Privacy Policy applies to GPS Site Camera: Stamp, including the Android application identified by the package name com.geostamp.gpscamera and the corresponding iOS application (the “App”). The App is provided by Vishal Bhimporwala (“we,” “us,” or “our”).

By using the App, you acknowledge the practices described in this policy. If you do not agree, do not use the App or grant permissions that you do not want the App to access.

Use of the App is also governed by our Terms of Use.

2. Information the App handles

The App may access or process the following information only as needed for its camera and site-documentation features:

Camera and media

Photos, videos, thumbnails, PDF reports, and associated capture metadata created through the App.

Precise or approximate location

Latitude, longitude, accuracy, altitude, provider, date, time, and an address derived from the location.

Audio

Microphone audio only when you record a video with voice enabled.

App settings

Language, onboarding state, camera preferences, stamp templates, custom stamp text, and related local settings.

Purchase information

If paid products are offered, Google Play may process product, transaction, subscription, and purchase-status information.

Technical and configuration information

Mapping providers may receive an IP address, request metadata, and coordinates when map or address features are used. Firebase may process an app-installation identifier, IP address, device and app information, screen and feature interactions, purchase and advertising lifecycle events, performance context, and crash or diagnostic information.

Advertising and consent information

For eligible free users, Google’s User Messaging Platform checks and presents advertising privacy choices during app startup before advertising requests and Meta App Events are enabled. Google and participating mediation partners such as Meta may then process device identifiers, IP address, app-install and advertising interactions, diagnostics, and privacy choices.

Masked session replay

On supported Android devices, Microsoft Clarity may process masked interaction, navigation, device, app, network, and diagnostic data after the required privacy choice permits collection. App content is masked before session replay capture.

The App does not currently require an account, and we do not operate an application server that receives your captured photos, videos, or location history. The Android App uses Firebase Analytics and Firebase Crashlytics to understand feature usage and stability. Analytics are intentionally limited to predefined events and coarse categories. We do not send captured media, exact coordinates, addresses, custom stamp text, filenames, file paths, sharing recipients, purchase tokens, email addresses, or phone numbers as custom analytics parameters.

3. How information is used

  • To provide the live camera preview and capture photos or videos.
  • To add coordinates, address, date, time, accuracy, altitude, custom text, maps, and related details to stamps.
  • To organize captures, generate PDF reports, and let you save, export, or share content.
  • To remember your language, onboarding progress, camera controls, stamp template, and other preferences.
  • To retrieve map images and convert coordinates into a readable address.
  • To process and restore purchases if paid features are made available.
  • To offer an optional rewarded ad that temporarily unlocks an eligible premium feature for the current app session.
  • To show app-open ads to eligible returning free users, subject to configured eligibility and frequency limits.
  • To show interstitial ads to eligible free users after configured capture milestones or when leaving eligible Settings and template screens.
  • To show anchored banner ads on eligible Settings, template, template-editing, and map-data screens for free users.
  • To record and apply advertising privacy and consent choices where required.
  • To attribute app installs and measure advertising campaign performance through Meta App Events.
  • To retrieve and apply operational feature and advertising-placement configuration.
  • To measure predefined onboarding, permission, capture, collection, premium, purchase, and advertising funnel events using coarse, low-cardinality values.
  • To diagnose crashes, application-not-responding incidents, and operational failures using Firebase Crashlytics and privacy-limited diagnostic context.
  • To diagnose usability and navigation issues using consent-gated, masked Microsoft Clarity session replay on supported Android devices.

4. Device permissions

You can deny or revoke permissions in your device settings. Some features will not work without the permissions required for that feature.

Permission Purpose
Camera Provides the live preview and captures site photos and videos.
Location while using the App Adds GPS coordinates and related details to captures. The App does not request background location permission.
Microphone Records sound only when video recording with voice is enabled.
Photos, media, or storage Saves exported captures to your gallery or photo library and accesses media only when you choose a supported media action. On older Android versions, legacy storage permission may be used for export.
Internet and network state Retrieves static maps, supports address lookup through platform services, communicates with Google Play for purchases and app updates, uses Firebase configuration, analytics, and crash reporting, and loads app-open, rewarded, native, banner, or interstitial ads when eligible.

5. On-device storage and retention

Captured media and report metadata are stored in app-controlled storage on your device. Settings and cached addresses are also stored locally. Static map images may be held temporarily in memory to improve performance. Media you explicitly export is copied to your device gallery, photo library, or another destination you select.

App-controlled media and settings generally remain until you delete them, clear the App’s data, or uninstall the App. Exported copies remain in the destination you selected until you delete them there. We do not control retention by your device provider, backup service, sharing destination, or third-party service.

6. Sharing and third-party processing

We do not sell or rent your personal information. Information may leave your device in these limited circumstances:

  • Google Maps Platform: When map thumbnails are enabled, coordinates are sent to Google Maps Platform to retrieve a static map. Google may also receive normal network request information. See the Google Privacy Policy.
  • Platform geocoding services: Android or Apple location services may process coordinates to return a readable address. Their handling is governed by the privacy terms of Google, Apple, your device manufacturer, or the configured service provider.
  • Google Play Billing: If you make a purchase, Google Play processes payment and transaction information under Google’s policies. We do not receive your full payment card number.
  • Google Play In-App Updates: On Android, the App may ask Google Play whether an eligible update is available and may use Google Play’s flexible or immediate update flow. Google may process normal device, app-version, account, network, request, and diagnostic information under the Google Privacy Policy.
  • Google Mobile Ads and User Messaging Platform: If advertising is available, Google may process advertising identifiers, IP address, device and request information, ad interactions, diagnostics, and consent choices. App-open ads may appear to eligible returning free users. Rewarded ads are shown only after you choose the rewarded-ad option. Clearly identified native ads may appear at intervals within the Collection screen, anchored banner ads may appear on the Settings, template-selection, template-editing, and map-data screens, and interstitial ads may appear after configured capture milestones or when leaving eligible Settings and template screens for free users. See Google’s Privacy Policy and Advertising policies and controls.
  • Meta App Events and Audience Network: On Android, after the startup privacy flow permits advertising-related processing, Meta App Events may process app-install, app-launch, device, advertising-identifier, IP-address, purchase or subscription, and advertising-interaction information for campaign attribution and performance measurement. Meta Audience Network may also participate through Google Mobile Ads mediation for eligible rewarded, interstitial, or native ad requests. The App does not provide Meta with captured photos, videos, precise coordinates, addresses, or custom stamp text. See the Meta Privacy Policy.
  • Firebase Remote Config: On Android, Firebase may process an app-installation identifier, IP address, and limited device, app, request, and diagnostic information to provide operational configuration and emergency feature controls. Remote Config is not used to store photos, videos, precise location, or confidential information. See the Firebase privacy and security information and Google Privacy Policy.
  • Firebase Analytics and Crashlytics: On Android, Firebase processes predefined screen, onboarding, permission, feature, capture-result, media-action, billing-status, paywall, consent, configuration, advertising-lifecycle, and advertising-revenue events, together with app-installation, device, app-version, session, crash, ANR, and diagnostic information. Location accuracy, location-fix age, zoom, and collection size are reported only as coarse buckets. Advertising-revenue events may include the placement, format, currency, paid value, precision classification, and mediation adapter, but not the ad-unit identifier. Custom event parameters are designed to exclude media, exact location, addresses, custom text, filenames, paths, contact details, purchase tokens, and sharing recipients. See Firebase privacy and security information and Google Privacy Policy.
  • Microsoft Clarity: On supported Android devices, and only when remotely enabled and the startup privacy flow permits collection, Microsoft Clarity may process masked session interactions, navigation, device, app, network, and diagnostic information to help us identify usability and reliability issues. The App masks its Compose content before replay capture and does not intentionally provide captured photos, videos, precise coordinates, addresses, or custom stamp text to Clarity. See the Microsoft Privacy Statement.
  • User-directed sharing: When you use Save, Export, or Share, the selected photo, video, or report is provided to the gallery, photo library, application, service, or person you choose. The recipient’s privacy practices then apply.
  • Sharing the App: When you choose Share GPS Site Camera in Settings, the App sends a standard app description and store link only to the application or person you select. It does not attach your captures or location information.
  • Legal and safety reasons: We may disclose information if required by applicable law or if reasonably necessary to protect users, rights, safety, or the integrity of the App. Because we do not operate a media-storage server, we generally do not possess your captures.

7. Your choices and deletion

  • Use device settings to review or revoke camera, location, microphone, and photo-library permissions.
  • Disable map thumbnails in the App settings to avoid Static Maps requests for stamp previews.
  • Decline the rewarded-ad option and continue using the free template, or purchase Premium without watching rewarded ads.
  • Use the controls presented by Google’s User Messaging Platform during startup when advertising privacy choices are required in your region.
  • Delete captures using the App’s Collection controls where available.
  • Delete exported copies from your gallery, photo library, file manager, or sharing destination.
  • Clear the App’s storage or uninstall the App to remove app-controlled local data.
  • Contact us using the email below for privacy questions. Because the App does not currently use accounts or store captures on our servers, we may have no server-side personal record to identify or delete.

8. Security

We use platform application storage, permission controls, scoped sharing mechanisms, and encrypted HTTPS connections for Static Maps requests. No method of storage or transmission is completely secure, so we cannot guarantee absolute security. You are responsible for protecting access to your device and reviewing sensitive location details before sharing stamped media.

9. Children’s privacy

The App is a general-purpose site documentation tool and is not directed to children under 13 or the minimum age required by local law. We do not knowingly collect personal information from children through an account or developer-operated server. If you believe a child has provided personal information directly to us, contact us so we can address the request.

10. International processing

Third-party providers such as Google, Apple, Meta, or Microsoft may process request information in countries other than your own. Their privacy policies describe their international data-handling practices and safeguards.

11. Changes to this policy

We may update this Privacy Policy when the App’s features, third-party services, or legal obligations change. The updated version will be posted at the same public URL with a revised effective date. Material changes may also be communicated in the App or store listing where appropriate.

12. Contact

Developer: Vishal Bhimporwala

App: GPS Site Camera: Stamp

Email: vishalbhimporwala@gmail.com