Privacy policy
My Meeting App is made by Gooder Software LLC, a Tennessee company. This policy covers the app for iPhone and Android and this website. It describes each kind of data we keep, why, and for how long.
In short
- No accounts. We never ask for your name, email or phone number.
- We know your phone only by a keyed hash of the app's ID for it, never the ID itself.
- Our database doesn't record which meetings one phone has tagged. The only link between a phone and a meeting in our database is a 7-day abuse-review log. Your tags on each meeting are stored under an ID made for that meeting alone, so someone with only a copy of our database can't connect your tags on different meetings. Our server finds one phone's tags on different meetings only when you use “Delete all my tags” or when we block a phone for spam.
- No ads, analytics, tracking or cookies, in the app or on this website.
What stays on your phone
These stay on your phone and never reach our server:
- your exact location
- what you type in the search box (to find the place, your phone asks Apple, Google or, on some Android phones, the phone maker's location service, not us)
- your recent searches
- your saved meetings
- your sobriety date
- the list of meetings you've tagged
- your near-the-meeting check results (only a yes or no is sent, with your tags)
- meetings saved for use offline
- anything you add in later features, such as notes, a meeting log or a journal
Your phone's own backups (to iCloud, Google, your phone maker's cloud or a computer) may include them, as they can for most apps. Those backups are yours, and they never reach our server.
What our server stores
Your phone's record
- What
- A keyed hash of the app's ID for your phone (never the ID itself), whether it's an iPhone or an Android phone, the first day the app sent us tags, a suggestion or its app check, and the last day it sent us tags or a suggestion (dates only; the last day is brought up to date each night, so it can lag by one, and until the app first sends tags or a suggestion, the last day is the day of its app check), whether we've blocked it for spam and, on iPhone, the app's App Attest key: Apple's ID for the key, its public key and how many times it has signed a request. The private key never leaves the iPhone's Secure Enclave. On iPhone, the app makes a random ID and keeps it in the iPhone's Keychain, on that phone only: it isn't synced to iCloud Keychain or restored to another phone, and it stays if you delete and reinstall the app. On Android, the app uses Android's own ID for the app (on Android 7, the phone's own ID, shared by every app), which a factory reset changes. The app sends it only when you add, change or remove tags, suggest a tag or use “Delete all my tags”, and, on iPhone, in the two requests of the app check that can come just before those (one asks our server for a random challenge, the other sends it a new App Attest key), never when you search or read meetings.
- Linked to
- Nothing else. It doesn't mention any meeting.
- How long
- Until you use “Delete all my tags”, or until the first nightly cleanup 13 months after the last day on that record. If we blocked your phone for spam, we keep its hash, platform, dates and blocked flag, but not its App Attest key, for as long as the block stands, even after “Delete all my tags” or 13 months without contact. That record still isn't linked to any meeting.
Days your phone wrote to us
- What
- For each day (UTC) your phone adds or changes tags or suggests a tag: your phone's hash, whether it's an iPhone or an Android phone and, on iPhone, which App Attest key signed and the highest count it reached that day. Each night these update your phone's record above.
- Linked to
- Your phone only. It doesn't mention any meeting.
- How long
- 2 days: today's and yesterday's are kept, and older ones are deleted in the next nightly cleanup. “Delete all my tags” deletes them at once.
App check codes
- What
- Before an iPhone proves it's running the real app, our server gives it a random one-time code that the proof must include, and keeps the code and when it stops working.
- Linked to
- Nothing. We don't record which phone asked for it.
- How long
- 5 minutes. A code is deleted as soon as it's used, and unused ones in the next nightly cleanup.
Used DeviceCheck codes
- What
- On an iPhone without App Attest, the app proves each write with a one-time DeviceCheck code from Apple, which our server asks Apple to check. We keep a fingerprint of each code we accept (its SHA-256 hash, never the code itself) and the day (UTC) we saw it, so the same code can't be used twice.
- Linked to
- Nothing. We don't record which phone sent it.
- How long
- 2 days: today's and yesterday's are kept, and older ones are deleted in the next nightly cleanup.
Your tags on a meeting
- What
- The tags you chose for one meeting, whether the app confirmed you were near it (yes or no, never where you were), the dates, and whether we've set them aside because we blocked the phone for spam. They're stored under an ID made for that meeting alone, so someone with only a copy of our database can't connect your tags on two meetings.
- Linked to
- That one meeting. Our server finds one phone's tags on different meetings only when you use “Delete all my tags” or when we block a phone for spam.
- How long
- Until you change or remove them. The counts in the app include them for as long as they stand, unless we block the phone for spam.
Tag counts
- What
- For each meeting and tag, how many phones chose it and how many of those were near the meeting.
- Linked to
- One meeting.
- How long
- Rebuilt every time tags change, and every night.
Abuse-review log
- What
- Your phone's hash, a meeting, whether you added or changed tags, and when.
- Linked to
- Your phone and one meeting. This is the only link between a phone and a meeting in our database, kept so we can find and block spam.
- How long
- 7 days, then deleted in the next nightly cleanup.
Spam flags
- What
- When one tag suddenly gains many new phones on a meeting: the meeting, the tag, how many new and earlier phones, and when we flagged and reviewed it.
- Linked to
- One meeting. No phone.
- How long
- Kept.
Merged meetings
- What
- When two listings turn out to be the same meeting, the old meeting ID and the one it became.
- Linked to
- Meetings only.
- How long
- Kept.
Daily limits
- What
- Your phone's hash, which daily limit it counts (new tags, suggestions or app check codes), the day (UTC) and how many you've used that day. A separate count of failed sign-ins to our admin page covers the whole site and names no phone.
- Linked to
- Your phone only; the sign-in count links to nothing.
- How long
- 2 days: today's and yesterday's counts (UTC) are kept, and older ones are deleted in the next nightly cleanup.
Suggested tags
- What
- The word or phrase you suggested, and whether we added it, merged it into an existing tag or turned it down. Until we review it, it's also linked to your phone's hash.
- Linked to
- Your phone, but only until review.
- How long
- The text is kept. The link to your phone goes when we review the suggestion, or in the first nightly cleanup after 30 days, whichever comes first. “Delete all my tags” deletes any suggestion still linked to you.
Suggestion screening log
- What
- The suggested text, what the screening model decided (merge it into an existing tag, reject it or leave it for a person), which tag it named for a merge, its reason, the model's name and the time.
- Linked to
- One suggestion, and through it your phone for as long as that suggestion stays linked to it (see “Suggested tags”).
- How long
- Kept, including the suggestion's text. “Delete all my tags” deletes it together with a suggestion still linked to you.
Search location
- What
- When you search, the app rounds the location to about 1 km (two decimal places) and sends it in the body of the request, never in a web address.
- Linked to
- Nothing.
- How long
- Not stored. It's used for that one search and never written to a log.
Hosting request logs
- What
- Our host, Vercel, records each request's IP address, the page or API path, and the time. When the app loads a meeting or saves your tags, the path names that meeting.
- Linked to
- Nothing we control. We never add request contents, headers or locations to these logs.
- How long
- For the short time Vercel's plan keeps them. We don't copy them anywhere.
When you email us
Email to admin@goodersoftwarellc.com goes through Google Workspace, so your email address and message are held on Google's mail servers. We keep it only to answer you and act on it, and delete it within 90 days after it's resolved. Deleted mail can remain in Google's trash and recovery for up to about 55 days after that. We never link it to anyone's tags.
Meeting listings
Meeting times and places come from meeting lists that AA intergroups and other service entities publish. We keep the meeting details (name, time, place, format, online links, dial-in numbers and notes), never the separate contact fields (names, emails, phone numbers) some lists include. Meeting notes are shown as the intergroup published them. We look up missing map locations with the US Census Bureau's geocoder, sending it only the meeting's address.
Who else receives data
- Vercel
- Hosts this website and the app's server, so it receives every request, including your IP address, and keeps short-term request logs.
- Neon
- Hosts our database, which holds everything listed above, and keeps its restore history.
- Apple
- On iPhone, Apple Maps draws the map and gives directions, Apple's geocoder turns a place you type into a map point, and App Attest (or DeviceCheck, on an iPhone without it) confirms that tags and suggestions come from the real app.
- On Android, Google Maps draws the map and gives directions, Android's geocoder turns a place you type into a map point (on some Android phones, the phone maker's location service does this instead), and, once switched on, Play Integrity confirms that requests come from the real app.
- Google Workspace
- Carries and holds the email you send to our support address (see “When you email us”).
- Suggestion screening
- When you suggest a new tag, only its text (never your phone's ID or location) goes through Vercel's AI Gateway to a screening model, currently OpenAI's gpt-5-nano, with zero data retention: the provider doesn't keep it or train on it.
When you type a place into the app's search box, your phone asks Apple, Google or, on some Android phones, the phone maker's location service to find it. We never receive what you typed, only the rounded point.
Backups
Deleted data can remain in our database provider's restore history for up to 7 days, and then it's gone. We use that history only to recover from a failure.
Your choices
- Change or remove your tags on any meeting at any time, from the meeting's page in the app.
- “Delete all my tags” on the app's Me tab deletes every tag, daily limit, abuse-log entry and phone record we hold for your phone, and any suggestion still linked to it (one we haven't reviewed, from the last 30 days) with its screening log. Tag counts update at once on our server; the app catches up within 75 minutes. A phone we blocked for spam keeps its blocked record.
- Location permission is optional. Without it, search by city, zip code or address.
Children
The app isn't meant for children under 13, and we don't knowingly collect anything from them. Apart from an email you choose to send us, we don't collect names, contact details or exact locations from anyone.
Changes and contact
We'll post any change here with a new date. Questions go to admin@goodersoftwarellc.com.
Updated 3 October 2026.