[DCT-Berinyuy]

Summary

Listings stored the seller's exact GPS position and showed it as a map pin to every user. This rounds listing coordinates to 2 decimals (about 1.1 km) in the database, so Play's "shares precise location with other users" answer can honestly be No. This is a database-only change, so no app rebuild is needed.

Closes #

Changes

• supabase/migrations/20261020000000_coarse_listing_location.sql:
  • public.coarsen_listing_location() trigger function (search_path = '').
  • BEFORE INSERT OR UPDATE OF latitude, longitude trigger on public.listings.
  • One-time backfill of existing rows. Idempotent.
• Meetup coordinates are unchanged: they are user-chosen public spots, already rounded to 3 decimals by the app.
• bookbridge-rust-core/tests/listing_location_tests.rs: insert and update rounding, nulls preserved, migration re-run rounds existing precise rows.
• Website privacy policy now discloses the approximate (about 1 km) listing location.
• CHANGELOG Unreleased entry.

Test plan

• cargo fmt (touched files) and cargo clippy pass
• cargo test: the new DB tests skip locally (no local Postgres) and run in CI only
• Migration is idempotent; the re-run is covered by a test (CI)
• Distance sort on Home is computed client-side, so it still works at about 1 km precision.

Checklist

• Targets dev, not main
• No secrets, keys, or personal data in code, logs, or screenshots
• User input is validated; new tables have RLS policies (no new tables)
• User-facing strings added to both EN and FR ARB files (no app strings changed)
• Docs updated if behavior changed

Screenshots

N/A

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
book-bridge	Ready	Preview	Oct 6, 2026 10:44pm UTC