Privacy Policy

Effective October 30, 2026 · Developer: mglazebrookdevs

This policy covers every app published by mglazebrookdevs on the Apple App Store and Google Play. Each app links back to this same page as its Privacy Policy URL, so the section that applies to the app you're using is the one you want.

Apps with no account or server

This section covers every app above except First Light, TailMark, CatchJournal, Hailmark, AuroraCue, JobSignal, LeaseLine, Geodeo, Seamline, Lapforge, Blotter and Coil, which have their own sections below. These apps have no account, no sign-in, and no server — they don't know who you are.

What we collect

Nothing. We (the developer) do not collect, store, or transmit any personal data.

What stays on your device

App On-device data
Skycharted The optional streak reminder is off unless you turn it on in Settings, and is scheduled by your own device from what is stored on it: nothing is sent to us to trigger it, and no device or push token is collected. Your location (captured via the device's GPS) is used to compute which real constellations, planets, and moon phase are visible from that spot right now — all calculated entirely on-device — and is stored only in the app's local storage. It is never sent to us except, if you choose, rounded to about 10 km with a sky photo you send (below). The sky-pointer feature uses the camera only to show a live viewfinder with a constellation overlay on top of it, along with the device's compass and motion sensors to align that overlay with the real sky — the viewfinder is never recorded, saved, or transmitted. Sending a sky photo is optional: from tonight's sky or an event's page you can take a photo or pick one in the system photo picker, which shows Skycharted only the photo you pick, and nothing is uploaded until you press Send. We then receive that one photo (reduced to 2048 pixels and re-saved as a JPEG, which drops its location and camera data), when it was taken, the event or sky target it shows, the credit name you typed if any, whether you allowed us to share it publicly, and, only if you turn on "Include approximate location", your location rounded to a tenth of a degree (roughly 10 km). It is stored privately on our server (hosted on Supabase), is not linked to your device or any identifier, and is never shown to other users of the app; a one-way hash of a random install key limits how many photos one phone can send per day. We post a photo publicly only if you allowed it, with the credit name you gave, or none; email us to have one removed. Sky events (meteor showers, eclipses, full moons) and their viewing plans are also computed on-device; peak alerts are local notifications scheduled by the app itself, and the events you mark "I saw it" stay in local storage. Skycharted shows no ads. If you subscribe to Skycharted Pro (or bought its earlier one-time unlock), the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to validate your purchase across devices. RevenueCat receives a device/purchase identifier and your entitlement status — never your location, events or collected-constellation data, which stay local as described above.
Duck Drake Your streak, collected gear, and Coins/Pearls balance are stored only in the app's local storage, never sent to us. If you buy Pearls, Coins, or gear with real money, the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to credit your purchase — RevenueCat receives a device/purchase identifier and what you bought, never your game progress, which stays local. If you use the "Share" button after a Daily Skip, a random per-install id, your chosen display name, and that round's score are included in the text you share — this goes only to whoever you choose to send it to (via your device's own share sheet, e.g. Messages), never to us, and a friend who opens the link only sees that same information to compare scores.
WortLog Your batches and gravity readings are stored only in the app's local storage, never sent to us. If you buy the optional one-time "Brew Day Companion Pro" unlock with real money, the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to validate your purchase — RevenueCat receives a device/purchase identifier and your entitlement status, never your batch data, which stays local.
Rail Trail The optional streak reminder is off unless you turn it on in Settings, and is scheduled by your own device from what is stored on it: nothing is sent to us to trigger it, and no device or push token is collected. Your logged trails, streak, unlocked badges, notes, and any photos you attach are stored only in the app's local storage, never sent to us. Photos you pick are copied into the app's own private storage on your device and are never uploaded anywhere. If you use "Near you", your device location is sent to OpenStreetMap's Overpass API only to look up rail-trails near you, and to Nominatim if you search by town or ZIP code instead. It is not stored by us, in the app, or anywhere else — each search sends a fresh location and nothing is retained afterward. See OpenStreetMap Foundation's privacy policy. If you buy an optional one-time region-pack unlock with real money, the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to validate your purchase — RevenueCat receives a device/purchase identifier and your entitlement status, never your trail log, which stays local.
All others No location, files, or personal data are read or stored at all.

Advertising

Ask Orb, First Light, Rail Trail, TailMark, CatchJournal, Duck Drake and WortLog are dropping their Google AdMob ads: each app's first update from November 2026 removes them along with the Google Mobile Ads SDK, and no new version will show ads. Until you install that update, the version you have makes its ad requests with requestNonPersonalizedAdsOnly: true: we don't build an advertising profile of you or track you across other apps or websites, but AdMob itself processes a device/advertising identifier and coarse technical signals to serve an ad, under Google's Privacy Policy. Updating the app ends that.

TailMark

TailMark is a plane-spotting logbook. It has no account or sign-in — everything you log is stored only in the app's local storage on your device.

What we collect

Your logbook — tail numbers, aircraft details, airports, notes, dates, and any photos you attach — never leaves your device and is never sent to us. Looking up an aircraft or airport is answered entirely from a database bundled inside the app; no network request is made to do it. TailMark drops ads in its first update from November 2026 (earlier versions show AdMob ads on the free tier; see Advertising) and reports anonymous usage events as described under Anonymous usage analytics.

If you use the camera or photo library to attach a picture to a sighting, that photo stays on your device and is never uploaded anywhere. The same is true of the tail-number scanner: the text is read from the picture entirely on your device by the operating system, and neither the picture nor the text is sent anywhere.

Location

When you log a sighting you can let TailMark record where you were standing, so your sightings appear on your own map. This is optional and can be switched off for any sighting before you save it, and the app will not ask for location permission until you do. Coordinates are stored in your logbook on your device like any other field — they are never sent to us and never sent to anyone else. The only exceptions are the Overhead screen and Overhead alerts, described below, which use your location only when you open or turn them on. Sightings logged without location fall back to whichever airport you tagged, and sightings with neither simply do not appear on the map.

Live flight tracking

If you ask TailMark to check whether an aircraft in your logbook is flying right now, it sends that aircraft's tail number (and, if it is airborne, the flight callsign the aircraft itself is broadcasting) to two public aviation data services — adsb.lol and adsbdb — to get back that aircraft's public position and route. The flight map additionally reads that aircraft's publicly recorded flight paths for the past few weeks from adsb.lol's archive of volunteer receiver data. A tail number is a public aircraft registration, not information about you: nothing identifying you, your device, your location, or the rest of your logbook is included in those requests. They are only made while you are looking at that aircraft's screen, and never in the background.

Overhead

The Overhead screen shows aircraft near you right now. While it is open, TailMark asks your device for your current location (only while the app is in use; there is no background location) and sends those coordinates to adsb.lol to get back the public positions of aircraft within about ten nautical miles. adsb.lol receives the coordinates as part of that request, like any web request; nothing else identifying you or your logbook is included. The requests are repeated every 20 seconds or so while the screen is open, never in the background, and the location is not sent to us. If you tap Log it, the aircraft and your location are saved to your logbook on your device like any other sighting.

Streak reminder (optional)

The optional streak reminder is off unless you turn it on in Settings, and is scheduled by your own device from what is stored on it: nothing is sent to us to trigger it, and no device or push token is collected. Turning it off in Settings, from the notification itself, or by revoking notification permission stops it.

TailMark Pro (optional upgrade)

If you buy TailMark Pro, the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to credit your purchase — RevenueCat receives a device/purchase identifier and what you bought, never your logbook data, which stays local.

TailMark Pro also includes an optional "rare aircraft daily digest." If you turn it on for an airport in Settings, your device's push-notification token and the airport you chose are sent to and stored on a server we control (Supabase), so a scheduled job can check once a day for notable aircraft reported near that airport and notify you. That token and airport are the only data the digest sends to a server we control; the server can only add or remove that one row for a token it already has (nothing about you can be read back from it), and it is never combined with your logbook or any other data. Turning the feature back off in Settings deletes that stored row immediately.

TailMark Pro also includes optional "Overhead alerts." If you turn them on in Settings, your device sends a saved spot (your current location rounded to about 110 metres), its push-notification token, your device's time zone, your alert choices and the aircraft type codes (such as A320) in your logbook to the same Supabase server, so a scheduled job can check for notable or new-to-you aircraft over that spot and send you a notification. Aircraft that have already been alerted are recorded briefly against the token to avoid repeats. The server can only add, change or remove the row for a token it already has, and nothing can be read back from it. It is never combined with the rest of your logbook (your tail numbers, photos, notes and sighting locations stay on your device). Turning Overhead alerts off in Settings deletes that stored row immediately.

Your controls

Deleting a sighting in the app permanently removes it from your device. Turning off the rare-aircraft digest in Settings deletes your tracked airport and push token from our server, and turning off Overhead alerts deletes your saved spot, push token, time zone and type codes. You can revoke location or camera access at any time in your device settings, and TailMark keeps working without either. Uninstalling the app removes everything TailMark stored locally.

CatchJournal

CatchJournal is a fishing catch log with a species-collection game layer. It has no account or sign-in — everything you log is stored only in the app's local storage on your device.

What we collect

Your catch log — species, dates, measurements, notes, whether you released a catch, and any photo you attach — stays on your device and is never sent to us unless you send a catch photo yourself, as described under Sending a catch photo. The species reference data (habitat, size, facts) is bundled inside the app; looking it up makes no network request. CatchJournal drops ads in its first update from November 2026 (earlier versions show AdMob ads on the free tier; see Advertising) and reports anonymous usage events as described under Anonymous usage analytics.

Location

When you log a catch you can let CatchJournal record where you were, using the device's GPS. This is entirely optional, and the app will not ask for location permission until you choose to use it. The coordinates are stored in your catch log on your device like any other field — they are never sent to us, never sent to anyone else, and never shown on a map inside the app.

Catch cards and sending a catch photo (optional)

A catch with a photo gets a catch card: the photo with the species, size, date and a "Logged with CatchJournal" mark drawn on it. Making the card happens on your phone. Share hands it to the share sheet you pick, and Save to Photos only adds it to your library (it never reads the photos already there).

You can also send a catch photo to us. Nothing is sent until you press one of the two Send buttons. A send carries the photo, re-encoded first so the camera's location tag and other metadata are gone, plus the species, length, weight, whether you released the fish, the day you caught it, and a credit name if you type one. It never includes your catch's coordinates, bait, or notes. "Send, OK to feature it" means we may post the photo on CatchJournal's own social accounts and pages with your credit name; "Send privately" means only we see it. Photos are kept in private storage on Supabase, the host of our backend, and the submission record holds no device identifier. To have a photo removed, email the address at the bottom of this page with the day and species.

Streak reminders (optional)

You can turn on a single reminder in Settings, sent the evening before an active streak would lapse. It is scheduled by your own device from your local catch history — there is no push server, nothing is sent to us to trigger it, and no device or push token is collected. The reminder is off unless you switch it on, and turning it off in Settings or revoking notification permission in your device settings stops it.

Content packs (optional one-time purchases)

If you buy a content pack or the All-Access Bundle (or bought Remove Ads in an earlier version), the purchase is handled entirely by Apple/Google and processed via RevenueCat, which we use to credit your purchase across devices. RevenueCat receives a device/purchase identifier and what you bought — never your catch log, which stays local as described above. Every product is a one-time unlock; CatchJournal has no subscription.

Your controls

Deleting a catch in the app permanently removes it from your device. You can revoke location, camera, photo-library, or notification access at any time in your device settings, and CatchJournal keeps working without any of them — a catch just won't have that field. Uninstalling the app removes everything CatchJournal stored locally.

Hailmark

Hailmark is a map of radar-estimated hail. It has no account or sign-in. It shows no ads.

What stays on your device

Your saved areas, pins and the notes you write on them are stored only in the app's local storage on your device and are never sent to us. Pins you export to a CSV file are shared only through the share sheet you choose.

Radar data

The map is drawn from small data files that we publish from NOAA's public Multi-Radar/Multi-Sensor hail-size product. The app downloads those files from a server we control (Supabase Storage) without sending any account information, so that server sees the same technical request data any website would, such as your IP address. Nothing about your location or your saved areas is included in those requests.

Location

If you tap "My location" or "Add my current location," Hailmark asks your device for your position once, to center the map or create a saved area there. This is optional, the app never reads your location in the background, and declining does not block anything. A spot you tap on the map is checked against the radar data on your device.

Alerts (Hailmark Pro, optional)

If you turn on alerts for a saved area, Hailmark sends the following to a server we control (Supabase) so it can notify you: that area's coordinates, radius, minimum size and label; your device's push-notification token; a random device identifier and a hashed secret generated on your device; and the anonymous identifier RevenueCat uses for your purchase, so the server can confirm your subscription is active. We use this only to decide whether new radar-estimated hail falls inside an area you chose and to send you that notification. It is kept until you delete it: the About screen's "Turn off alerts and delete my alert data" removes everything the server holds for your device, and removing a single area removes its alert.

Hailstone photos you send us (optional)

From a spot you check you can tap Send a hailstone photo. The app asks for the camera only when you tap Take a photo, and opens the system photo picker, which shows Hailmark only the photo you pick, when you tap Choose. Nothing is uploaded until you press Send. We then receive that one photo (reduced to 2048 pixels on its long side and re-saved as a JPEG, which drops its location and camera data), when it was taken, the hailstone size you chose if any, the credit name you typed if any, whether you allowed us to share it publicly, and, only if you turn on "Include approximate location", the map spot you checked rounded to a hundredth of a degree (roughly 1 km). It is stored privately on our server (hosted on Supabase), is not linked to your device or any identifier, and is never shown to other users of the app. We use it to compare the radar's hail estimates with what fell. To limit abuse, the server counts how many photos each install sends per day using a one-way hash of the app's random device key, kept only for that count. We post a photo publicly only if you allowed it, and then with the credit name you gave, or none. To have a photo removed, email us with roughly when you took it and the credit name you used.

Hailmark Pro subscription

Purchases are handled by Apple and processed through RevenueCat, which receives an anonymous purchase identifier and what you bought, never your saved areas, pins or notes.

Analytics

Hailmark reports anonymous usage events as described under Anonymous usage analytics.

AuroraCue

AuroraCue shows a forecast of tonight's aurora visibility for where you are, and helps you capture a brighter aurora photo than a phone camera can manage in a single shot by taking several quick photos in a row and combining them into one image. It has no account or sign-in and shows no ads. It reports a few anonymous usage events (a forecast loaded, a photo captured, alerts changed): see Anonymous usage analytics.

What we collect

Apart from those anonymous usage events, nothing is sent to us unless you turn on aurora alerts or choose to send us a photo. The frames AuroraCue captures to build a combined photo are processed entirely on your device using temporary files and are never uploaded to us or to any third party. Each finished photo is also kept in Your shots, in the app's own storage on your device; it is deleted when you delete it in the app or remove the app. A combined photo only reaches your photo library if you tap Save to Photos, only leaves the app if you choose a destination in the share sheet, and only reaches us if you tap Send to AuroraCue (below). Without AuroraCue Pro, saved and shared copies carry a small "Shot with AuroraCue" mark.

Tonight's cloud forecast

To show how cloudy your dark hours look, the app asks the Norwegian Meteorological Institute (MET Norway) for the cloud forecast directly from your device. It sends your position rounded to one decimal place of latitude and longitude (roughly 10 km), with nothing that identifies you or your device. Like any web request, it also reaches MET Norway from your device's IP address. Nothing about it is sent to us or stored by AuroraCue.

Aurora alerts

Aurora alerts are off until you turn one on. The strong-night forecast alert is free; the others are part of AuroraCue Pro. To send them, our alert server (hosted on Supabase) stores: this device's push-notification token; your location rounded to the nearest whole degree of latitude and longitude (roughly 100 km), which is all it needs to work out when it gets dark where you are and how strong the aurora has to be to reach you; your time zone; the language the app is showing (English, Spanish, Danish or Norwegian), so alerts arrive in it; which alerts you turned on and when each last fired; the anonymous RevenueCat identifier used to confirm your subscription; and a random device key that only this app knows. Notifications are delivered through Apple's push notification service. Turning both alerts off deletes that record from the server. Before sending an alert, the server asks the Norwegian Meteorological Institute (MET Norway) for the cloud forecast at that rounded location; only the rounded latitude and longitude are sent, with nothing that identifies you or your device. Weather data from MET Norway, licensed under CC BY 4.0.

Photos you send us

After you take a photo you can tap Send to AuroraCue, and the app also offers it the first time you save or share a photo. Nothing is uploaded until you tap one of its two Send buttons: "Send, OK to feature it" or "Send privately". We then receive that one combined photo (reduced to 2048 pixels on its long side, without the AuroraCue mark), the time you took it, the geomagnetic activity level (Kp) at the time, the credit name you typed if any, whether you allowed us to post it, and, only if you leave "Include roughly where I took it" on, a location rounded to a tenth of a degree (roughly 10 km). A photo taken with the camera also carries how it was taken: hand-held or steady, the number of frames, the shutter time and ISO, how much the phone moved, how far it was tilted above the horizon, and, only if you already allowed location access, which compass direction it faced. From the time and the rounded location (if sent), our server adds what the sky was doing: the forecast cloud cover from MET Norway (asked with only that rounded location), how much of the moon was lit, and how high the sun and moon were. None of this describes you; it helps us see why a photo came out dark and improve the camera. It is stored privately on our server (hosted on Supabase), is not linked to your device or any identifier, and is never shown to other users of the app. To limit abuse, the server counts how many photos each install sends per day using a one-way hash of the app's random device key, kept only for that count. We post a photo publicly (for example on AuroraCue's social media accounts) only if you sent it with "Send, OK to feature it", and then with the credit name you gave, or none. To have a photo you sent removed, email us with roughly when you took it and the credit name you used.

Photo library access

AuroraCue asks for permission to add photos to your library, and asks only when you first tap Save to Photos. It requests add-only access, so it cannot see or read the photos already in your library.

AuroraCue Pro

AuroraCue Pro is an optional subscription, billed and managed by Apple, that unlocks aurora alerts, the live aurora map, the three-day outlook, and saving and sharing photos without the AuroraCue mark. Subscriptions are validated through RevenueCat, which receives an anonymous app-generated identifier and your purchase record so Pro can be restored on your other devices. It receives nothing about your location, your photos, or your forecast.

Location and the forecast

AuroraCue asks for your location so it can estimate whether the aurora will be visible at your latitude tonight. Your coordinates are read on the device to compute that estimate; the only copies that ever leave it are the rounded location described under Aurora alerts, and only while an alert is on, and the roughly 10 km location sent with a photo, only if you choose to include it. To show current and predicted geomagnetic activity and the live aurora map, the app fetches public, keyless feeds from NOAA's Space Weather Prediction Center; those requests carry no information about you or your location.

Camera access

AuroraCue asks for camera access so it can capture the frames it combines. If you decline or later revoke camera access in your device settings, capture won't work, but nothing else about the app is affected.

JobSignal

JobSignal shows contractors the building permits that cities publish on their official open-data portals, as sales leads. It has no account or sign-in and shows no ads.

Information about homeowners

JobSignal does not collect, store or show homeowners' personal information. When our server reads a city's permit records it keeps the address, the kind of work, the declared job value, the contractor of record, the permit number and dates, and a description of the work; owner and applicant names are discarded, and phone numbers or email addresses written into a description are removed. Permits older than 90 days are deleted.

Emails to contractors

A few cities publish the contractor's business email in their own permit records (currently Raleigh, NC and DeKalb County, GA). We use those published addresses, and only those of businesses, to write once by hand to the contractor of record with that week's permit list, and at most once more a week later. We keep the business name, the email address, the city, when we wrote and whether you replied or asked us to stop, so that nobody is written to twice and nobody who opts out hears from us again. Reply "no thanks" or use the link in the email and we will never contact you again; to have the record deleted entirely, email mike.glazebrook.apps@gmail.com. These addresses are never sold, shared or used for anything else.

Permit data sources

Each city's source, license and any notice it requires are listed in the app under Settings > Data sources and licenses. For cities that publish only a street address, the address and its city are sent to the U.S. Census Bureau's public geocoder to place the permit on the map; nothing about you is sent. Kansas City asks that this notice appear where the app is offered: "This site provides applications using data that has been modified for use from its original source, www.data.kcmo.gov, the official open data website of the City of Kansas City. The City of Kansas City makes no claims as to the content, accuracy, timeliness, or completeness of any of the data provided at this site. The data provided at this site is subject to change at any time. It is understood that the data provided at this site is being used at one’s own risk."

What we collect from you

So the permit server (hosted on Supabase) can apply your plan, it stores a record for this device: a random device key that only this app knows, the anonymous RevenueCat identifier used to confirm a subscription, the one metro a free plan covers and when it was chosen, and when the device was last seen. It does not receive your name, email or contacts.

Your metro and trade choices, your saved leads, their statuses and your notes stay on your device. They are never uploaded, and an export only leaves the app if you pick a destination in the share sheet.

Permit alerts

Permit alerts are part of JobSignal Pro and are off until you create one. For each alert the server stores the metro, the trades, the distance and the minimum job value you chose, and a center point: your location when you created the alert, rounded to about a kilometer, or the center of your metro if you didn't share your location. It also stores this device's push-notification token so Apple's push notification service can deliver alerts. Removing an alert deletes it, and Settings > Delete my data from JobSignal's server removes the device record and every alert.

Location

JobSignal asks for your location only when you create a permit alert, to center it on where you work. It is optional, is never read in the background, and is not used for anything else.

JobSignal Pro

JobSignal Pro is an optional subscription, billed and managed by Apple, that unlocks permit alerts, 90 days of history in every metro, an unlimited pipeline and export. Subscriptions are validated through RevenueCat, which receives an anonymous app-generated identifier and your purchase record, and nothing about your leads or your location.

Analytics

JobSignal reports anonymous usage events as described under Anonymous usage analytics, such as which metro a feed was loaded for and how many permits it showed. They never include an address, a note or a location.

LeaseLine

LeaseLine helps oilfield drivers find well sites from the well records that the Railroad Commission of Texas and the New Mexico Oil Conservation Division publish, and lets drivers record and share the lease road to a pad. It has no account or sign-in and shows no ads.

Information about people in well records

LeaseLine shows wells, their operators and their locations. It does not show landowner or mineral-owner information, and when a well's operator of record appears to be a private person rather than a company, LeaseLine shows "Individual operator" instead of the name and does not let anyone search by it.

Location and recorded routes

LeaseLine uses your location only while the app is open: to show where you are next to a pad, and to record a route when you tap Record. It never reads your location in the background. A recorded route stays on your device unless you choose to publish or share it. Before anything is uploaded you trim the start of the route and see exactly what will be sent.

A route you publish to a pad is visible to every LeaseLine user; a route you share by link can be opened by anyone who has the link. Either way the server (hosted on Supabase) stores the trimmed track, its entrance point, your optional note (phone numbers and email addresses are removed), the pad it belongs to, and when it was published. It is linked only to a random device key that this app created, never to your name or contact details. You can delete your published routes at any time from My Routes or Settings.

What else the server stores

So the server can apply your plan and your deletions, it keeps a record for this device: the random device key, the anonymous RevenueCat identifier used to confirm a subscription, and when the device was last seen. Your saved wells and unpublished routes stay on your device.

LeaseLine Pro

LeaseLine Pro is a subscription, billed and managed by Apple, that the app requires after its free trial. Opening a route someone shared with you does not require it. Subscriptions are validated through RevenueCat, which receives an anonymous app-generated identifier and your purchase record, and nothing about your location or your routes.

Analytics

LeaseLine reports anonymous usage events as described under Anonymous usage analytics, such as that a county's well data was downloaded or that a route was published. They never include a location, a track or a note.

Geodeo

Geodeo shows whether public land is open to hobby rock collecting, using land-ownership, protected-area, mining-claim and mineral-site records published by the Bureau of Land Management and the U.S. Geological Survey, and keeps a log of the specimens you find. It has no account or sign-in, no server of its own, and shows no ads.

Location

Geodeo uses your location only while the app is open: to show where you are on the map, to check the land at your spot, to record where you logged a find and which 7.5-minute quadrangle it was in, and to point back to the spot where you pinned your vehicle. It never reads your location in the background, and your location is never sent anywhere.

Finds and photos

The finds you log, their photos, notes and weights, your field briefs and your vehicle pin are stored only on your device. Geodeo does not upload them. If you share a specimen label or export your finds as a GPX or CSV file, the file goes only where you send it.

Map data and claim records

Offline state packs and map tiles are downloaded from public file hosting (Cloudflare Pages and the U.S. Geological Survey's National Map); those services see the usual request details, such as your IP address, but nothing that identifies you to Geodeo. When a Geodeo Pro subscriber looks up claim records, the app sends only the map coordinates of that spot to the Bureau of Land Management's public claims service. Geodeo never requests or shows the names of claimants.

Geodeo Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for this app, not your name or email address.

Analytics

Geodeo reports the anonymous usage events described under Anonymous usage analytics, such as which verdict a tap returned or that a find was logged. Events never include coordinates, site identifiers or quadrangle names.

Seamline

Seamline maps trout water using records published by state fish and wildlife agencies, the U.S. Geological Survey and the PAD-US public lands database. It has no account or sign-in and shows no ads.

Location

Seamline uses your location only while the app is open, to center the map on you and list nearby waters. It never reads your location in the background, and your location is never sent to us.

Saved waters and alerts

The waters you save, and the markers, lines and areas you draw on the map, stay on your device. If you turn on alerts (Seamline Pro), our server stores a random install identifier, the push-notification token Apple issues for this app, and the identifiers of the waters and stream gauges you asked to watch, with the flow or temperature settings you chose. It does not store your location, name or email address. Deleting alerts in Settings removes that record.

Map and conditions data

State packs, stocking reports and gauge readings are downloaded from public file hosting (Cloudflare Pages and Supabase Storage) and map tiles from the U.S. Geological Survey's National Map. Those services see the usual request details, such as your IP address, but nothing that identifies you to Seamline. To show the rain forecast on a water card, the app asks the National Weather Service for the forecast at that water's location, which is the water's position, not yours.

Catch photos kept in the app

A water's card has a Your photos here strip. The app asks for the camera only when you tap Take a photo there, and opens the system photo picker, which shows Seamline only the photo you pick, when you tap Choose a photo. Seamline keeps its own copy of that photo in the app's storage on your phone, filed under that water, re-saved as a JPEG so the copy carries no location or camera data, along with the date it was taken, the species you chose and whether you have sent it to us. Kept photos stay on your phone and are not uploaded or backed up by Seamline; deleting one in the app, or removing the app, removes it. The catch card made from a kept photo (the photo with the water's name, the species and the days since stocking) goes into your photo library only when you tap Save to Photos, and for that Seamline asks for add-only access, which cannot see what is already in your library. It leaves the app only through a destination you choose in the share sheet. Without Seamline Pro, saved and shared cards carry a small "Found with Seamline" mark.

Catch photos you send us (optional)

Right after you keep a photo, and on any kept photo you have not sent, Seamline offers to send it to us. You choose between Send, OK to feature it and Send privately, or Not now; neither is chosen for you. What is sent is the plain photo, never the catch card. Nothing is uploaded until you press one of the Send buttons. We then receive that one photo (reduced to 2048 pixels on its long side and re-saved as a JPEG, which drops its location and camera data), when it was taken, the name, identifier and state of the water whose card you sent it from, the species you chose if any, how many days after that water's last stocking it was taken, the credit name you typed if any, and which Send you pressed. Your location and the spot where you fished are never sent. The photo is stored privately on our server (hosted on Supabase), is not linked to your device or any identifier, and is never shown to other users of the app. To limit abuse, the server counts how many photos each install sends per day using a one-way hash of the app's random install identifier, kept only for that count. We post a photo publicly only if you pressed Send, OK to feature it, and then with the credit name you gave, or none. To have a photo removed, email us with roughly when you took it and the credit name you used.

Seamline Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for this app.

Analytics

Seamline reports the anonymous usage events described under Anonymous usage analytics, such as that a water card was opened or an alert was set. Events never include coordinates or water identifiers.

Lapforge

Lapforge is a lap timer for track days. It times laps from your phone's GPS against a start line you set, and draws circuits from OpenStreetMap outlines bundled inside the app. There is no account or sign-in, no server of our own, and no ads.

Location

Lapforge reads your location only while its timing screen is open, to tell when you cross your start line and how far around the lap you are. It does not run in the background, and your position is never uploaded. The Grid and Tracks screens use a position you have already allowed, to suggest the circuit you are at; they never ask for it on their own.

Laps, start lines and GPS traces

Your sessions, lap times, the GPS points of each session and the start lines you set are kept only on your device, including the copy Lapforge writes while you drive so a session survives the app being closed. If you share a lap card or export a session as CSV, the file goes only where you choose to send it. Deleting a session removes it from the device.

Track weather

When a session starts at a circuit from the Lapforge list, the app asks the National Weather Service for the latest reading at the nearest station. The request carries the coordinates of the circuit, not of your phone, and the weather service sees the usual request details such as your IP address.

Lapforge Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for Lapforge.

Analytics

Lapforge reports the anonymous usage events described under Anonymous usage analytics, for example that the paywall was opened, a lap card was shared or a session was exported. Events never contain coordinates, lap times or circuit names.

Shelf Hunt

Shelf Hunt is a map of collectible finds at real stores. People post what they found on a shelf (the kind of collectible, the aisle, how many) and scheduled drops such as restock days or card shows. There are no accounts, usernames, profiles, comments or messages, and no ads. The store list is built from OpenStreetMap and ships inside the app.

Age and children

The app asks for a birth year the first time it opens and keeps it only on your device; only an age group (adult or teen) is ever sent, never the year. Anyone under 13 can browse the map but cannot post, upload photos, vote, report, set alerts or buy Pro. For them the app registers nothing with our server, turns analytics off, deletes any analytics identifier it had stored, and never starts the purchase service, so no persistent identifier is collected from a child. Posts from teens (13-17) cannot include photos and appear on the map an hour after they are made.

Location

Your location is used on the phone to sort nearby stores and centre the map. To show finds, the app sends the corners of the map area you are looking at; our server uses them to answer the request and does not store or log them. A post carries only the store you picked, never your position, and post times are rounded to 15 minutes.

If you are an adult with Pro and set up an alert area, the server stores that area's centre, rounded to about 0.7 mile (1 km), with the radius you chose, so it can tell you about finds inside it. An area set to follow you is re-centred, at the same rounding, when you open the app after moving; the app never tracks your location in the background. Removing the area deletes it. Teens cannot set alert areas, so no location is ever stored for them.

Finds, photos and drops

When you post, our server stores the store, the details you chose, a three-character shelf code if you add one, and the time. Each install has a random identifier and a secret created on the device; the server keeps the identifier, a one-way hash of the secret and your age group, so it can limit posting and stop someone voting twice. Posts are not shown with any identifier. An adult may attach up to four photos of a shelf, which must not show people. Photos go live 30 minutes after posting, can be removed by reports before or after that, and are deleted from public view after 7 days. Finds drop off the map after 7 days.

Store checks

You can mark a store “Checked, nothing here”. The server stores the store, the kinds of collectible you looked for and the time rounded to 15 minutes, with your install identifier so it can limit how often you check. Checks are shown to others without any identifier, a teen’s only after an hour, and carry no text.

My hunt

The stores you add to My hunt, the things you are hunting and when you last checked each store stay on your device. They are never sent to our server.

Hunt crews

If you are 13 or over and start or join a crew, the server stores which crew your install belongs to and the crew’s six-character code, so it can tell the other members about your finds (and you about theirs). Members never see who the others are: the app shows only how many are in the crew. A crew holds one age group, so adults and teens are never in the same crew. Leaving the crew, or Delete my data in Settings, removes your membership.

Sharing

Sharing a find or a crew invite uses your phone’s share sheet, so you choose where it goes. A shared find is an image of what was already public (the find, the store, the time) with the Shelf Hunt mark; nothing about you is added. Sharing is off for anyone under 13.

Reports

You can report any find, photo or drop. A report records the post and the reason. Reported posts are hidden automatically once enough reports arrive, and at once for a photo reported as showing a person.

Alerts

If you turn on alerts, the server stores your device's push token, the stores and kinds of collectible you chose, your quiet hours and your time zone, so it can notify you of matching finds, drops starting soon and confirmations of your own finds without waking you. Alerts you receive are also kept for 14 days so the app can show them in its alerts inbox, then deleted. Turning alerts off, or Delete my data in Settings, removes all of it.

Shelf Hunt Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for Shelf Hunt.

Analytics

Shelf Hunt reports the anonymous usage events described under Anonymous usage analytics, for example screen views, that the paywall was opened or that alerts were turned on. Events never contain locations, stores or photos. Analytics are off for anyone under 13.

Store data

Store names, locations and opening hours come from © OpenStreetMap contributors, available under the Open Database License. The store list is published at shelfhunt-stores.json.

First Light

First Light works out legal shooting hours for a spot and, in the Score tab, measures deer and elk antlers on photos you choose. There is no account or sign-in and no ads.

Location and weather

Your location (captured via the device's GPS, or entered manually) is used to calculate legal shooting hours for that spot and is stored only in the app's local storage on your device. It is never sent to us. If you look up a location by city or zip code, that text is sent to OpenStreetMap's Nominatim service to resolve it to coordinates. Once a location is set, the app also sends its coordinates, rounded to about 1 km, to the Norwegian Meteorological Institute's weather service (MET Norway) to show a forecast, but only while you have a connection. Weather is simply hidden when you don't, and the app's core legal-hours calculation never needs it. Neither service receives anything else about you.

Photos and the camera

First Light uses the camera only when you tap Take photo, and the system photo picker, which shows First Light only the photos you select; it never reads the rest of your library. Each photo is re-saved inside the app with its location and camera details removed. The capture date is read first and kept, so trail-camera photos stay in order. Your photos, scores, measurements and hit list stay on your device. Saving a score card to Photos asks for permission to add images only. Clearing the app's data deletes everything it stored locally.

Sending a score (optional)

If you tap Help First Light get more accurate and choose Send, the app sends one score to our server: the species, which way the animal faces, the points you tapped (as fractions of the photo's size), any tape values, the app's estimate, an official score if you entered one, the month the photo was taken, and an optional credit you type. The photo goes too unless you turn that switch off; it is shrunk to 2048 pixels and carries no location or camera data. Nothing sent includes your location, the exact date or any account. A separate "OK to feature it" switch, off by default, lets us share the photo on our own pages with your credit; it is never shown to other people in the app. Submissions are stored privately in Supabase and used to improve the measurement. A random install identifier is used only to limit how many submissions one phone can send per day; it is stored as a one-way hash, separately from the submission. Email us to have a submission deleted.

Sending a rack photo (optional)

From a finished score you can tap Send this rack to First Light. It sends the photo you already scored, so it needs no new permission, and nothing is uploaded until you press Send to First Light. We then receive that photo (shrunk to 2048 pixels, with no location or camera data), the day it was taken, the species, typical or non-typical, First Light's gross and net scores, your own tape score if you typed one, the credit name you typed if any, and whether you allowed us to share it publicly. No location is ever sent. It is stored privately in Supabase, is not linked to your device or any identifier, and is never shown to other people in the app. We use it to check the photo measurement against tape scores. The same one-way hash of a random install identifier limits how many photos one phone can send per day. We post a photo publicly only if you allowed it, and then with the credit name you gave, or none. Email us to have a photo deleted.

Reminder

The Sunday trail-cam reminder is off unless you turn it on in the Score settings. It is a notification scheduled on your device for Sunday evening; nothing is sent to us or anyone else to make it work.

First Light Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for First Light.

Analytics

First Light reports the anonymous usage events described under Anonymous usage analytics, for example that a score was finished, a card was shared or the paywall was opened. Events never contain photos, measurements or locations.

Tinewise

Tinewise measures deer and elk antlers on photos you choose. There is no account or sign-in and no ads.

Photos and the camera

Tinewise uses the camera only when you tap Take photo, and the system photo picker, which shows Tinewise only the photos you select; it never reads the rest of your library. Each photo is re-saved inside the app with its location and camera details removed. The capture date is read first and kept, so trail-camera photos stay in order. Your photos, scores, measurements and hit list stay on your device. Saving a score card to Photos asks for permission to add images only.

Sending a score (optional)

If you tap Help Tinewise get more accurate and choose Send, the app sends one score to our server: the species, which way the animal faces, the points you tapped (as fractions of the photo's size), any tape values, the app's estimate, an official score if you entered one, the month the photo was taken, and an optional credit you type. The photo goes too unless you turn that switch off; it is shrunk to 2048 pixels and carries no location or camera data. Nothing sent includes your location, the exact date or any account. A separate "OK to feature it" switch, off by default, lets us share the photo on our own pages with your credit; it is never shown to other people in the app. Submissions are stored privately in Supabase and used to improve the measurement. A random install identifier is used only to limit how many submissions one phone can send per day; it is stored as a one-way hash, separately from the submission. Email us to have a submission deleted.

Sending a rack photo (optional)

From a finished score you can tap Send this rack to Tinewise. It sends the photo you already scored, so it needs no new permission, and nothing is uploaded until you press Send. We then receive that photo (shrunk to 2048 pixels, with no location or camera data), the day it was taken, the species, typical or non-typical, Tinewise's gross and net scores, your own tape score if you typed one, the credit name you typed if any, and whether you allowed us to share it publicly. No location is ever sent. It is stored privately in Supabase, is not linked to your device or any identifier, and is never shown to other people in the app. We use it to check the photo measurement against tape scores. The same one-way hash of a random install identifier limits how many photos one phone can send per day. We post a photo publicly only if you allowed it, and then with the credit name you gave, or none. Email us to have a photo deleted.

Tinewise Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for Tinewise.

Analytics

Tinewise reports the anonymous usage events described under Anonymous usage analytics, for example that a score was finished, a card was shared or the paywall was opened. Events never contain photos, measurements or locations.

Pet Sitting Business: Booking

Sitter Desk runs a pet sitting business from one phone: clients, pets, bookings, payments and the messages a sitter sends. There is no account, no sign-in, no ads and no Sitter Desk server. Everything a sitter enters about their clients stays on the sitter's device, and we never receive it.

Client and booking records

Client names, phone numbers, email and home addresses, pets, care notes, vet and emergency contacts, bookings, prices and payments are stored inside the app on your device. Removing a client deletes their records. A backup or an Excel export is created only when you tap it, and goes wherever you choose in the share sheet.

Door codes and keys

Home-access notes are kept in the iPhone Keychain and shown only after Face ID or your passcode. Face ID is handled by iOS; Sitter Desk never sees your face data. Home access is never put in an export, a backup or a message.

Photos, files and signatures

Sitter Desk uses the camera or the system photo picker only when you add a photo to a visit update or a pet. Each photo is re-saved inside the app with its location and camera details removed. Spreadsheets you import, files you attach to a client and agreements signed on the screen stay in the app's own storage on your device.

Walks and location

Sitter Desk uses your location only between the moment you tap Start walk and the moment you finish or discard that walk, including while the phone is locked, so it can draw the route on a map. iOS shows the location indicator the whole time. The route and the pee and poop marks are saved on your device with the booking, and they are deleted when you delete the walk or the client. A route leaves your phone only as a map picture in a text you choose to send; Apple Maps draws that picture from the route's area, as it does for any map. We never receive your location.

Messages and email

Confirmations, reminders, visit updates and walk maps open in Messages or Mail for you to send. They go through your own phone and email account, never through us. Venmo payment links open in Venmo or on venmo.com.

Calendar

If you turn on calendar sync, Sitter Desk adds each booking to the calendar you pick, with the pets' and client's names, the client's address and phone number, and the booking's times. It changes or removes only the events it created, and it does not read your other events.

Analytics

Sitter Desk reports the anonymous usage events described under Anonymous usage analytics, such as which screens are opened. Events never contain client, pet, booking or payment details.

Sitter Desk Pro

The subscription is sold by Apple. To confirm it, RevenueCat receives a random identifier made by the app and the subscription history for Sitter Desk Pro, never your clients or anything else you keep in the app. A logo you add stays on this phone and appears only on documents you choose to send.

Snow Removal Log

Snow Removal Log keeps a snow contractor's sites and visits and builds a storm record for each site. There is no account, no sign-in, no ads and no Snow Log server. Your sites, visits, photos and records stay on your device, and we never receive them.

Sites, visits and photos

Site names, addresses, contract terms, client email addresses and notes, the arrive and leave times of each visit, services and materials, conditions and photos are stored inside the app on your device, and in your iCloud device backup if you use one. An address you type is turned into a map position by Apple's geocoder. When you tap Arrive, Snow Log reads your location once (only while you use the app) and stores it with the visit, so the record shows the visit happened on site. Photos keep their time and position on the visit record; Snow Log uses the camera or photo picker only when you add a photo.

Weather lookups

To build a record, the app asks public weather services for the observations near each site: the National Weather Service's API (api.weather.gov), NOAA's National Operational Hydrologic Remote Sensing Center (nohrsc.noaa.gov), the Iowa Environmental Mesonet at Iowa State University (mesonet.agron.iastate.edu) and, for sites in Canada, Environment and Climate Change Canada's weather API (api.weather.gc.ca). These requests contain only a map position rounded to about 10 meters, a weather station ID and a time range. They never contain a site name, an address, a client or anything else you entered.

Records, exports and email

Storm record PDFs, the season CSV and the full export are created only when you tap them, and go wherever you choose in the share sheet. Send to client opens your own Mail app with the record attached; it goes through your email account, never through us.

Analytics

Snow Log reports the anonymous usage events described under Anonymous usage analytics, such as which screens are opened and paywall steps. Events never contain sites, addresses, visits, photos or clients.

Snow Log Pro subscription

The subscription is sold by Apple. To confirm it, RevenueCat receives a random identifier made by the app and the subscription history for Snow Log Pro, never your sites or anything else you keep in the app.

Lake Depth Maps

Lake Depth Maps shows depth contours drawn from state and federal surveys (Michigan, Iowa and Connecticut natural resources agencies, and NOAA for the Great Lakes), places you on them, and keeps the holes you drill. It has no account or sign-in and shows no ads.

Location

Depth Maps uses your location only while the app is open, to show where you stand on a lake's depth lines and to read the depth under you. That happens on your phone, including with no signal. It never reads your location in the background, and your location is never sent to us or anyone else.

Holes and trips

The holes you drop, their depths, results and notes, and the trips they belong to are stored only on your device. If you share a trip, the picture and the link carry only that trip's holes and break line, and only to the people you send them to. The holes travel inside the link itself, after the #, so the web page that draws them never receives them. A GPX export goes only where you send the file.

Lake files and ice cover

Lake depth files and the lake list are downloaded from public file hosting (Supabase Storage), and map tiles from the U.S. Geological Survey's National Map. Those services see the usual request details, such as your IP address, but nothing that identifies you to Depth Maps. For Great Lakes ice cover, the app asks NOAA's Great Lakes Environmental Research Laboratory for the ice data inside the map box you are looking at; the request carries that box, not your position.

Depth Maps Pro

Purchases are handled by Apple and confirmed through RevenueCat, which receives an anonymous app-user identifier and your purchase history for this app, not your name or email address.

Analytics

Depth Maps reports the anonymous usage events described under Anonymous usage analytics, such as that a trip was shared or the paywall was opened. Events never include coordinates, hole positions or depths.

Homeport (formerly Benefactor)

Homeport keeps a day-by-day record of the US states you are in, to help you show where you lived for state income tax. There is no account, no sign-in and no ads.

Location

With your permission, Homeport reads your location a few times a day, including in the background if you choose Always. Each position is matched to a state on your iPhone, using US Census boundaries bundled in the app, and saved as that day's state with the time and its accuracy. Positions are never sent to us or to anyone else.

Photos and documents

If you ask Homeport to fill missing days from your photos, it reads the date and place each photo was taken, on your iPhone. Photos are not copied, uploaded or kept. Receipts, boarding passes and documents you attach, or photograph with the camera, are stored in Homeport's own folder on your iPhone.

On your phone

Your days, homes, notes, checklist and attached files stay on your device and in your own device backup; we have no copy. Homeport also keeps a copy of your record as a file in its folder in the Files app, and "Save a copy" sends one wherever you choose in the share sheet. Sharing the audit packet makes a PDF or spreadsheet you send the same way. If you save your tax advisor's name and email, they stay on your device and are used only to address the email you choose to send.

State rules

When it opens, Homeport downloads the current list of state residency tests from our server, so new states and corrected rules arrive without an app update. The request carries nothing about you: no identifier, location, state or record. Like any web request it reaches our host, Supabase, which keeps short-lived technical logs.

Subscriptions

Homeport Private is sold by Apple. To confirm it, RevenueCat receives a random identifier made by the app and your Homeport purchase history. We never receive your name, email or Apple ID.

Analytics

Homeport reports the anonymous usage events described under Anonymous usage analytics, such as which screens are opened and whether a trial was started. Events never contain locations, states, dates you were somewhere, or anything you typed.

Blotter

Blotter republishes the police incident reports and dispatched calls that cities and counties release as open data, placed on a map by block. It has no account or sign-in and shows no ads.

People in police records

Blotter never takes a name, age, race or any other detail about a person from a police record: our server requests only the offense, the block, the times and the agency, and the rest of each record stays with the city. Every location is rounded to about 110 meters. Sexual offenses, domestic and family incidents, abuse, missing persons, deaths and medical or mental-health calls are dropped before anything is stored, as are records an agency marks sensitive. Reports are kept for 120 days and calls for 3 days, then deleted.

Record sources

Each city's agency, dataset, license and any required notice are listed in the app under Settings > Data sources and licenses. Where a city publishes a street and block but no map position (Dallas and San Jose live calls), that street address is sent to the U.S. Census Bureau's public geocoder; nothing about you is sent. Kansas City asks that this notice appear where the app is offered: "This site provides applications using data that has been modified for use from its original source, www.data.kcmo.gov, the official open data website of the City of Kansas City. The City of Kansas City makes no claims as to the content, accuracy, timeliness, or completeness of any of the data provided at this site. The data provided at this site is subject to change at any time. It is understood that the data provided at this site is being used at one’s own risk."

What the server keeps about you

Blotter's server (hosted on Supabase) keeps a record for this phone: a random key only the app knows, the anonymous RevenueCat identifier that confirms a subscription, the push-notification token if you allow notifications, and when it last sent you an alert or a weekly summary. For each place you save it keeps the name you typed, the distance and kinds of record you chose, and the spot, rounded to about 110 meters. It never receives your name, email or contacts.

The city you picked and your map filters stay on your phone. Settings > Delete my data from Blotter's server removes this phone's record and every saved place.

Location

Blotter asks for your location only when you tap "Use my location" or "Near me", or save your current spot as a place. It is used to center the map or find your city, is never read in the background, and is sent to the server only as a saved place.

Blotter Pro

Blotter Pro is an optional subscription, billed and managed by Apple, that adds instant alerts for saved places, five places instead of one, 90 days of records and an area report. Subscriptions are confirmed through RevenueCat, which receives an anonymous identifier and your purchase record, and nothing about your places or location.

Analytics

Blotter reports anonymous usage events as described under Anonymous usage analytics, such as which city was chosen. They never include a place, a location or a record you opened.

Coil

Coil is a golf swing analyzer. It has no account and no sign-in. Your swing videos and measurements stay on your device, and nothing is uploaded for analysis. The only exception is a swing you choose to share with us, described under Swings you share with us.

Swing videos and measurements

Coil films your swing with the camera, reads your body's pose from each frame on the device, and computes the measurements shown in the app. Videos, body-pose data, measurements, focus choices and plans are kept in the app's own storage on your phone and included in your phone's own backup. Videos and swing records are encrypted while the phone is locked. We never receive them. Sharing or exporting a swing happens only when you tap it, and it goes wherever you pick in the share sheet.

Camera and motion

Coil uses the camera only while you record or measure a swing or use the level guide. It reads the phone's motion sensors only to show its tilt and to check the phone is level. Both are used for measuring and nothing else. Coil does not use the microphone or your location.

Photos and files

You import slow-motion video through the system photo picker, which gives Coil only the clip you choose. Saving an export asks for add-only access to your photo library.

Swings you share with us (optional)

On a swing's screen you can tap Share with Coil. Nothing is sent unless you tick the consent box and tap Send. We then receive a short, watermarked clip of that swing (about address to finish), a still frame from it, the credit name if you typed one, and one measurement, the value of your current focus metric. The upload carries a random install identifier, which we keep only as a one-way hash to limit shares to two a day. To stop one connection sending many, we also keep a salted one-way hash of the IP address the share came from, never the address itself. Neither is linked to your name or to RevenueCat. Our hosting provider's request logs record the IP address and approximate location of each request and keep them for about a day. We use clips and stills for Coil's marketing, such as its App Store page and social accounts. Your name appears only if you add a credit. Clips and stills we do not feature are deleted automatically after 30 days. To have one removed sooner, email mglazebrookdev@gmail.com with the approximate time you sent it. Filming from behind keeps your face out of the clip.

Coil Pro and Coach

The subscriptions are sold by Apple. To confirm them, RevenueCat receives a random identifier made by the app and your subscription history, never your videos or measurements.

Reminders

Practice-plan reminders are local notifications scheduled on your phone. Nothing about them is sent from a server.

Analytics

Coil reports the anonymous usage events described under Anonymous usage analytics, such as which screens are opened and whether a paywall was shown. Those events never contain swing video, body measurements or any free text you type.

Anonymous usage analytics

Every app on this page reports a small number of anonymous usage events to a single Google Analytics 4 property shared across the whole collection. We use it to see which features people actually use and whether a change made an app better or worse — nothing else.

What an event contains:

What an event never contains: your name, email address, phone number, contacts, photos, files, precise location, or the contents of anything you type. Because the request is sent from your device, Google receives your IP address with it; Google's handling of that is governed by its own policies, not ours.

The credential embedded in our apps for this is send-only: it can add events and cannot read anything back. We only ever see totals and averages across everyone — never a single person's activity, and we have no way to look you up.

Apple Ads attribution

Apps on this page that sell a purchase or subscription through RevenueCat also send RevenueCat the attribution token from Apple's AdServices framework. Apple turns that token into the Apple Ads campaign, ad group and keyword that led to the download, or reports that no ad did. We use it only to tell whether our own ads on the App Store bring people in. It does not use your advertising identifier, does not track you across other companies' apps or websites, and does not need the "Allow Apps to Request to Track" permission. The result is tied to the same anonymous RevenueCat purchase identifier described in each app's section, never to your name or email.

Children's privacy

None of these apps are directed at children. We do not knowingly collect data from anyone under 13.

Questions or a data request?
Email mglazebrookdev@gmail.com.

Changes to this policy

If this policy changes, the "Effective" date at the top of this page will be updated. We won't reduce your rights over previously collected data without your consent.