Privacy Policy

Last updated: October 6, 2026

GeoCam: GPS Map Camera (“GeoCam”, “we”, “our”, “us”) is published by Mad Over Technology. The current public versions are listed as GeoCam: GPS Location Camera. This Privacy Policy explains how the iOS and Android apps and geocam.madovertech.io website handle information and the choices you have.

1. Information We Collect

a. Information You Provide

No account is required to use GeoCam, and you do not need to provide your name, email address or phone number to use its camera features.

If you email us or submit feedback, we may receive the contact details and message you voluntarily provide. We use that information to respond to your request and improve GeoCam.

The app’s Support & feedback link opens Google Forms outside GeoCam. It includes device model, operating system and app version as prefilled context in the link sent to Google. Google handles the form under its privacy policy.

b. Advertising-related Information in the Current Releases

In iOS 1.09 and Android 1.08, AdMob may collect device identifiers, device and operating-system information, app and ad interactions, and performance or diagnostic information. This includes non-user-related crash logs on iOS. Its advertising and measurement uses are described in Section 3. These AdMob practices are separate from the optional app analytics added in iOS 1.10 and Android 1.09.

c. Optional Usage and Crash Data in iOS 1.10 and Android 1.09

Share usage & crash data is off by default. In iOS 1.10 and Android 1.09, you can turn it on or off in Settings → Privacy → Share usage & crash data. Google’s advertising consent and Apple’s tracking permission are separate choices and do not turn this sharing on. Camera use does not require it.

• Google Analytics for Firebase receives app usage events, such as permission choices, captures saved, save failures, and settings changes; app/device and operating-system information; an app-instance identifier (the Analytics ID); and an approximate region inferred from IP address. GeoCam sends simple values such as “photo” or “video”, yes/no flags and counts. We configure this analytics service not to collect the advertising ID or use this data for ad personalization.
• Firebase Crashlytics receives crash and diagnostic reports, including stack traces, error codes, app/device information, app state and Crashlytics or Firebase installation identifiers. We use these reports to find and fix bugs.

GeoCam does not attach your photos, videos, custom notes, address or precise GPS coordinates to usage events or diagnostic reports. Custom error reports omit the original error message and user content; they use technical error codes or exception types and short diagnostic context labels. The Analytics ID is not attached to Crashlytics reports, and GeoCam does not set an account or user ID for either service.

Turning sharing off stops GeoCam’s usage events and custom diagnostic reporting. Changes to automatic crash reporting take full effect the next time the app starts, so close and restart GeoCam after changing this choice. Turning sharing off does not erase data already sent. See Firebase’s privacy information and Section 8 for deletion requests.

2. Permissions We Use

Location (GPS)

GeoCam uses your device location to:

• Display your current address and coordinates
• Add GPS location and map overlay to photos and videos

Maps and address lookups send location-based requests to platform providers: Apple’s map and geocoding services on iOS, and the system geocoder and OpenStreetMap tile service on Android. Your photos and videos are not uploaded to these providers for map or address requests.

Android 1.09 approximate location: if you allow approximate rather than precise location, GeoCam uses that approximate device fix for its camera stamp, address lookup and map. The fix is sent to the system geocoder for address lookup, and OpenStreetMap tile coordinates are derived from it to obtain the map. These requests support app functionality and are separate from the approximate region Google may infer from your IP address for advertising or optional analytics.

On Android, OpenStreetMap receives tile coordinates that reveal the area around your device’s location fix, which may be precise or approximate depending on your permission, along with your IP address and request information. It records service requests in its logs. See the OpenStreetMap Foundation privacy policy.

Camera

Used to capture photos and videos within the app.

Microphone

Microphone permission is used to record sound in videos you capture. That audio is saved with the video on your device; we do not separately collect microphone recordings or upload them to our servers.

Storage / Photos / Media

Used to:

• Save captured photos and videos to your device
• Allow access to your media for viewing and sharing

3. Advertising

Google AdMob serves ads in the current iOS 1.09 and Android 1.08 apps. The upcoming Android 1.09 and iOS 1.10 updates also use AdMob, subject to the version-specific advertising choices below. Their optional Firebase choice does not control this separate advertising service.

AdMob may collect:

• Device identifiers
• IP address, which can be used to estimate approximate location
• App and ad interactions, including app launches, taps and ads viewed
• Performance and other diagnostic information; on iOS, non-user-related crash logs

This data is used for advertising, ad measurement and analytics. On Android, AdMob also collects and shares data for fraud prevention and security. See Google’s AdMob data disclosures for iOS and Android, and its advertising privacy information.

On Android, you can reset or delete the advertising ID in your device settings.

Upcoming Android 1.09: GeoCam checks advertising consent using Google’s User Messaging Platform and shows a consent form when required before requesting ads. Where required, Settings → Privacy → Privacy choices lets you revisit that choice. Advertising consent does not enable Firebase usage analytics or crash reporting.

Upcoming iOS 1.10: GeoCam checks Google’s advertising consent and asks for Apple’s App Tracking Transparency permission before enabling AdMob ads. GeoCam starts the AdMob SDK and requests ads only when Google’s consent status allows ad requests and Apple’s tracking permission is authorized. If you choose Ask App Not to Track, tracking is restricted, or the choice is not yet settled, AdMob ads are not enabled. Taking and saving photos and videos does not require advertising consent or tracking permission.

When you authorize tracking and Google’s consent allows ads in iOS 1.10, AdMob may use the advertising identifier and the data categories above for advertising and measurement, including tracking across other companies’ apps and websites where your consent permits it. You can change Apple’s permission in iOS Settings → Privacy & Security → Tracking; GeoCam’s Settings → Privacy → Ad tracking shortcut appears when tracking was denied. Where required, Settings → Privacy → Privacy choices lets you revisit Google’s advertising consent. With either required permission withdrawn, GeoCam does not make new AdMob ad requests. These choices do not enable Firebase usage analytics or crash reporting.

4. Data Sharing

We do not sell your personal data.

The services described in this policy receive data for their features:

• AdMob receives advertising and technical data as described above
• Map and address providers receive location-based requests; on Android, this includes approximate fixes when you allow only approximate location, OpenStreetMap tile coordinates representing the area around the fix, and IP/request logs
• In iOS 1.10 and Android 1.09, Firebase Analytics and Crashlytics receive usage or diagnostic data only when you turn on sharing as described in Section 1c
• Google Analytics receives website traffic information only when you allow website analytics, as described in Section 9

5. Data Storage and Retention

• Photos, videos and their saved GPS stamps are stored locally on your device. We do not upload them or store your media, precise or approximate device location, or custom note content on our servers.
• Map/address providers and AdMob handle their service data under their own policies, linked above.
• In iOS 1.10 and Android 1.09, Firebase Analytics retains user/event data according to the project’s configured retention setting. Aggregated reports may remain longer. See Google Analytics retention.
• Firebase Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems; completion may take longer. See Firebase’s retention information.

6. Children’s Privacy

GeoCam is not directed toward children under 13. We do not knowingly collect personal data from children.

7. Security

We take reasonable measures to protect app integrity and user data. However, no method of transmission or storage is completely secure.

8. Your Choices

• You may deny or revoke location, camera, microphone and photo/media permissions in your device settings. In current iOS 1.09 and Android 1.08, doing so may prevent taking or saving photos and videos.
• In upcoming iOS 1.10 and Android 1.09, choose whether to share usage and crash data in Settings → Privacy. It starts off, is optional, and can be turned off again. Restart GeoCam for changes to automatic crash reporting to take full effect.
• In upcoming Android 1.09 and iOS 1.10, change Google’s advertising consent from Settings → Privacy → Privacy choices when that control is required. On Android you can also reset or delete the advertising ID in device settings. On iOS 1.10, change Apple’s tracking permission in iOS Settings → Privacy & Security → Tracking; denying it disables GeoCam’s AdMob ads and does not prevent captures.
• Uninstall GeoCam to stop its future app collection. This does not delete information already received by service providers.

Requests about optional app analytics: in iOS 1.10 and Android 1.09, email hello@madovertech.io with the Analytics ID shown in Settings → Privacy. We can use that ID to request deletion of the associated analytics data through Google’s tools. GeoCam has no accounts, so we cannot identify your analytics data from an account name. The ID can remain visible after sharing is turned off if it was obtained while sharing was on.

Crash reports use separate service identifiers and are not linked by GeoCam to the Analytics ID. Contact us about crash-data requests; we will assist using the tools available from Firebase. You may also contact us about access, correction, deletion or an objection to processing where applicable to you. Provider deletion and retention processes can continue after you stop future sharing.

9. Website Analytics

Website analytics is optional and off by default. We load Google Analytics and use its analytics cookies only after you choose Allow analytics. If you reject analytics or leave it off, Google Analytics does not measure your website visit.

When you allow analytics, it counts visits, helps us understand which pages are useful and measures clicks on the App Store and Google Play buttons. It uses cookies and browser identifiers and collects pages viewed, referring site, browser and device information, and approximate location derived from IP address. We disable Google Signals, advertising storage and ad personalization for website analytics. See Google Analytics data collection.

We remember your choice in your browser for later visits. You can change it at any time using the analytics choices control in this website’s footer. Turning analytics off stops future website measurement; it does not erase data already collected.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Updates will be reflected with a revised effective date.

11. Contact Us

If you have any questions, contact us at:
hello@madovertech.io