Privacy Policy

Last updated: August 17, 2026

This policy describes what RadiusRoute collects when vendors run neighborhood campaigns and neighbors join them. Stripe also processes payment data under Stripe's privacy policy.

What we collect

• Vendors: email, password (handled by Supabase Auth), optional website URL, Stripe Connect account ids, and SaaS billing customer/subscription ids.
• Neighbors (on join): name, address, phone and/or email, geocoded coordinates, and the amount charged. We also store hashed join-attempt IPs for rate limiting (not the raw IP).
• Payments: PaymentIntent ids and charge ids from Stripe. Neighbor name, address, phone, email, and coordinates are copied onto Stripe PaymentIntent metadata so a webhook can recover the join if the browser never finishes.
• Out-of-range join attempts (name, address, contact) are stored so the vendor can see who tried to join outside the neighborhood.

Who sees neighbor details

After a neighbor pays, the vendor can see that neighbor's name, phone, email, and address on the campaign page — including while the campaign is still Filling — so they can plan and run the route. RadiusRoute staff may access the same records to operate the product and debug payments. We do not sell neighbor lists.

How we use data

• Run campaigns, joins, settle-down refunds, and cancellations.
• Send join, settle, cancel, and account emails (via Resend).
• Bill vendors for the RadiusRoute subscription (via Stripe).
• Prevent abuse (Turnstile, join rate limits, radius checks).

Processors

We use Supabase (auth and database), Stripe (Connect charges and vendor billing), Mapbox (address lookup), Cloudflare Turnstile (join captcha), and Resend (email). Each processes data only to provide that service.

Retention

Campaign and join records stay for as long as the vendor account exists so settlements and refunds can be audited. You can email us to request deletion where we are not required to keep a payment trail.

Contact

Privacy questions: hello@radiusroute.com.