June 2026 Transparency Report

Why this exists

Same deal as May and April: every month I publish a plain-language log of what changed on the data and platform side — what we collect, what we removed, who we rely on, and any government or legal request we received (this month: none). If a number or a third party shows up that should not be there, you will see it here first.

June was the v4.2 month — one concentrated ship on June 2 (git 26f8558 and the same-day companion commits), then a quiet rest of the month. The Privacy Policy got a material update the same day; this report is the companion piece. Nothing after that commit landed in June on the product path (July work is next month’s report).

Headlines

• Web marketing line at end of June: 4.2. The App Store binary is still on the 4.0 marketing line (build 21) — same as end of May; no new store submission in June.
• Leave-by push without a Live Activity. Remote “time to head out” alerts can now fire for any install that has saved a meet and has an APNs token — Lock Screen activity optional. Traffic-aware timing still needs an active Live Activity (drive-minutes echo); otherwise timing is relative to the published start. New server table: leave_by_push_target (0029).
• Saved-meets ICS download. Menu / saved view can POST public meet IDs to POST /api/calendar/saved and get a one-time .ics file back. No installation id, account, or personal fields in that request — rate-limited to 30 / minute / IP.
• Editorial Spotlight. Staff can mark one meet as an editorial pick (editorialPick + short editorialBlurb, migration 0028). Presentation-only; no new visitor PII category.

Release timeline (from git)

This is the month in ship order — useful if you are diffing the repo against last month’s report. Scope starts at 26f8558 (June 2) as the v4.2 product baseline after the May report.

What we collect, in plain English

Everything from the May report still applies unless noted below. There is still no anonymous telemetry beacon and no third-party analytics SDK.

New or expanded in June

Leave-by push target rows. When leave-by remote push runs without (or alongside) a Live Activity session, we may store a row keyed by installation id + meet id: optional last drive-minutes (integer), echo/alert/suppression timestamps. Used only to time and de-dupe leave-by APNs. Schema: src/server/db/schema/leave-by-push.ts (leave_by_push_target). No coordinates, email, or name.

Drive-minutes echo for leave-by (non–Live Activity path). POST /api/push/leave-by/echo-drive-eta accepts installation id, meet id, drive-minutes integer, and optional likelyEnRoute — same integer-only pattern as the Live Activity echo. Rate-limited like other push register endpoints. Coordinates stay on device.

Saved-meets ICS export requests. Your browser or app may POST a list of public meet IDs (capped at 50) to /api/calendar/saved. The server looks up public listing fields and returns an ICS attachment. Access logs may still see your IP like any other HTTP request; the body does not carry an installation id.

Editorial pick fields on meets. editorialPick (boolean) and optional editorialBlurb (≤160 chars) on the public meet row — curator copy for the home spotlight rail. Visible on the public site when set; not a visitor identifier.

Anonymous sync on by default. Current builds treat anonymous cloud sync as enabled unless env explicitly sets the feature flag to "false". Data shape unchanged: saved meets, reminders, prefs, inbox, drafts keyed by opaque installation id.

Unchanged commitments worth repeating

• Near me / map distance sorting: approximate coordinates stay in-memory on the device; we do not log your live location to Postgres for sorting.
• Push device records: still no email, name, or IP in the push row.
• Sun / golden hour: pure client math from already-public venue lat/lon — not a new network dependency.
• Orphaned sync rows: if you reset the app or clear site data, server rows keyed to the old installation id still do not auto-expire on a schedule. Inbox rows do (90 days). June did not add an orphan retention window; still on the list for a future report when we ship one.
• Map tiles: still CARTO + OpenStreetMap via MapLibre — not Mapbox, not Google Maps tiles.

What we removed in June

Foreign key on anonymous saved-meet entries

Migration 0030 drops the DB foreign key from anon_saved_meet_entry to the meets table so sync rows can survive meet deletes/recreates without cascading failures. No change to what we store — only referential constraint behavior.

Nothing else material on the render path

April’s deletion of runtime Nominatim geocoding on map/home is still in force. June did not bring that back. No analytics SDK, no ad network, no new render-path third party.

What we added in June

v4.2 — leave-by without Live Activity, ICS export, spotlight (June 2, 26f8558)

• leave_by_push_target (0029) — server state for leave-by APNs when no Live Activity session exists; pairs with /api/push/leave-by/echo-drive-eta.
• POST /api/calendar/saved — on-demand ICS for saved meet IDs; 30 req/min/IP.
• Editorial Spotlight (0028) — editorialPick / editorialBlurb; home spotlight rail; staff-gated in admin.
• Saved-meets week planner — client grouping of your local/synced saved list by day; no new server fields.
• Route preview map on meet detail — same MapLibre + CARTO tile stack as the full-screen map.
• Public meet status history — timeline of operational status changes already stored for the meet; presentation only.

Privacy Policy (June 2)

Material update the same day as v4.2: corrected leave-by wording (alerts without Live Activity) and disclosed the saved-meets ICS download. Accordion history on the Privacy Policy page.

Third parties we currently rely on

Full list as of June 30, 2026. Render path = what loads when a typical visitor browses meets, map, or detail without submitting a form or opting into extra features.

On the render path (unchanged from May unless noted):

• Vercel — hosting, serverless functions, short-lived access logs. No Vercel Analytics / Speed Insights enabled.
• Neon Postgres — meets, organizers, push tokens, sync rows, inbox, live-activity sessions, leave-by push targets, rate-limit buckets, announcements.
• Apple Push Notification service (APNs) — push, Live Activity start/update/end, push-to-start, leave-by alerts.
• Apple App Store — distribution, crash reports (Apple’s policy applies).
• Open-Meteo — weather card, server-proxied (meet coordinates only; optional window summary).
• Catbox — cover image hosting; server-to-server uploads.
• Cloudflare — DNS and edge for detmeets.com.
• OpenStreetMap + CARTO — map basemap tiles via MapLibre, *.basemaps.cartocdn.com. Direct tile fetch from your device; we do not pass installation or sync ids to CARTO.
• GitHub — source + deploy workflow for featured-blog push dispatch.

Off the render path — only when you take a specific action:

• OpenStreetMap Nominatim — /api/address-suggest when you type in submit or the admin meet form; one-shot geocode at organizer publish; not on map/home page load.
• Instagram (instagram.com) — our server fetches public post HTML/images when you use paste-from-link prefill (your IP is not sent to Meta; our server IP is).
• Vercel AI Gateway — when vision prefill runs, caption + flyer image go to the gateway; no vision calls on browse/map/home.
• Apple Maps / Google Maps / Waze — only if you tap an external directions link; we send venue name + address, no device ids.

We do not use:

• Google Analytics or any analytics SDK.
• Meta / TikTok / Twitter / LinkedIn pixels.
• Sentry, LogRocket, FullStory, or session replay.
• Mixpanel, Amplitude, Posthog, Segment.
• Any ad network or data broker.
• Mapbox or Google Maps tiles in production.

Government and legal requests in June

• Law-enforcement requests received: 0
• Subpoenas, search warrants, or court orders received: 0
• National security letters received: 0
• Civil discovery requests received: 0
• Account or content disclosures made: 0
• Takedown notices received: 0
• Takedowns honored: 0

If we receive any of the above in a future month, the next report will say so. If we are ever gagged from saying so, the canary block above will simply not be repeated.

Security in June

• Vulnerability disclosures received from researchers: 0
• Confirmed data breaches: 0
• Confirmed unauthorized access: 0
• ICS export rate limit — POST /api/calendar/saved capped at 30 requests / minute / IP.
• Leave-by echo — same class of per-IP limiter as push registration; body validated (installation id, meet id, drive-minutes 0–600).
• Sync concurrency — server-side advisory locking around saved-state writes to reduce unique-constraint races under fast multi-device tapping.
• Schema export CI guard — prevents accidental drift between Drizzle kit entrypoints.
• Structured server logging — still reportError / reportEvent JSON lines to Vercel function logs only; not shipped to Sentry or any vendor.

If you find a security issue, message @alex.30mm on Instagram.

Numbers (light)

• Posts published in June: 2 (4.2 changelog, this report’s companion ship window; May’s transparency report was dated June 1 but covers May and is counted there).
• iOS app marketing version at end of June: 4.0 (build 21) — unchanged from May; web at 4.2.
• Privacy Policy effective dates in June: June 2 (leave-by without Live Activity; saved-meets ICS export).
• Database migrations applied in June: 3 (0028–0030).
• Notable endpoints added in June: /api/calendar/saved, /api/push/leave-by/echo-drive-eta.
• Render-path third parties added: 0.
• Render-path third parties removed: 0.
• Inbox retention: 90 days (nightly prune) — unchanged.
• Orphan sync retention: still none scheduled.

Closing

May promised the tile-provider commitment and the Live Activity / prefill machinery. June was quieter and more operational: leave-by alerts that work without a Live Activity, an honest ICS download for your saved list, and a clearer Privacy Policy for both — all still with no ads, no analytics SDKs, no new render-path vendors.

If something is wrong, missing, or you want a category tracked next month, message @alex.30mm on Instagram.

Effective: June 30, 2026 · Period covered: June 1 – June 30, 2026 (product baseline 26f8558 and after; no post-26f8558 product commits in June)

Privacy Policy · Terms · May 2026 Transparency Report · Detroit Meets on the App Store