Who we are
A recovery technology company, not a fellowship or treatment provider
MyMeetings operates the MyMeetings website and apps. The public directory helps people browse meeting information; the mobile app adds personal tools such as meeting discovery, check-ins, progress tracking, notes, and online-meeting access. MyMeetings also provides a separate staff-facing product for sober housing organizations.
MyMeetings is not Alcoholics Anonymous. We are not affiliated with, sponsored by, approved by, or endorsed by Alcoholics Anonymous World Services, Inc., the General Service Office, or any local AA intergroup or central office. “AA” and “Alcoholics Anonymous” are used descriptively to help people identify the kind of meeting information they are viewing.
MyMeetings is not a medical provider, emergency service, treatment program, or substitute for advice from a qualified professional.
Meeting-data methodology
How meeting information reaches the directory
Meeting records
Directory pages request meeting records from the MyMeetings meeting API. Individual meeting pages can use a legacy MyMeetings API as a fallback when the primary record is unavailable. Records may include a meeting name, day, time, address, format labels, online access details, source URL, and a reported update timestamp.
Geographic reference data
City routes are supplied by the MyMeetings city catalog and supplemented by local state JSON records in this site repository. Where present, city records include a Census reference year, coordinates, place type, land area, transit context, and a local intergroup or central-office reference.
Source links
When a meeting or local service-office URL is available in the record, the meeting page links to it and asks visitors to confirm details before attending. A source link is a verification path, not an affiliation claim.
Displayed facts
Meeting counts, schedules, format labels, map points, and “last updated” language are generated from the records returned for that page. Editorial location copy is kept separate from live meeting fields.
Updates & quality control
Schedules change; the source listing remains important
- Ingestion: meeting and city records are loaded through MyMeetings APIs used by the public site.
- Page refresh: city pages request current records when rendered and use short web/CDN cache windows. This is periodic refresh behavior, not a promise of instantaneous updates.
- Timestamp handling: when an upstream record supplies an update timestamp, the page can display or use it as the page modification date. We do not infer a timestamp when none is present.
- Visitor verification: every meeting detail page warns that schedules, room assignments, and online access details can change and recommends checking the source listing, particularly before a first visit.
- Correction review: reports are checked against the supplied source and the relevant record. Verified changes are routed to the underlying listing workflow; editorial errors are corrected on the site.
Limits: MyMeetings does not claim that every meeting is listed, that every field is complete, or that every change is reflected immediately. Local groups and service offices remain the best authority for their own schedules.
Corrections
Report a meeting or editorial correction
Email hello@mymeetings.co. To help us verify the change, include the page URL, the field that appears incorrect, the corrected information, and the local group, intergroup, central-office, or organizer source when one is available.
For sensitive personal information, describe the issue without sending medical records, account passwords, or unnecessary private details.