Privacy notice
BadgePark UK · Updated 19 November 2026
Who is responsible
George Smith trading as BadgePark, based in the United Kingdom, is the operator responsible for the personal data described here.
For privacy questions or to exercise your data rights, email badgepark+privacy@gmail.com. For account, app or billing support, email badgepark+support@gmail.com.
Data and why we use it
- Email address, sign-in credentials and display name: to provide and secure your optional account. Supabase handles authentication; passwords are not shown to BadgePark staff.
- Saved car parks, private notes, contribution history and Scout points: to provide the account features you request. Private notes are not public.
- Optional profile photos: resized on your device, then saved privately in Supabase for your account. They are not sent to the sign reader or displayed on the public map. You can remove your photo in your account; account deletion removes it too.
- Purchase and subscription identifiers, status and expiry: to provide Pro access and prevent billing errors. Stripe processes payment details; BadgePark does not store full card numbers.
- Town/postcode searches and location, when you allow it: to find nearby parking or place a contribution. Coordinates and search terms are sent to postcodes.io and OpenStreetMap’s Nominatim/Overpass services. We do not track your location in the background. A selected search can remain in the page URL and browser history.
- Selected sign photos: sent through Lovable’s AI gateway to Google Gemini to read the rules and check for visible faces or readable vehicle plates before public storage. Rejected photos are not saved in the public bucket. AI checks can make mistakes; crop tightly to the sign and do not include personal information. Approved photos and parking rules are public. Issue reports contain the parking location and selected reason, not your account identity, and are reviewed by the BadgePark owner.
Our UK GDPR legal bases are performance of a contract for account and Pro features; legitimate interests in operating, securing and improving the community guide; legal obligations for required billing records; and consent where required for optional device access. Device permission can be withdrawn in your browser settings. We do not ask you to upload a Blue Badge or medical information.
Cookies, device storage and permissions
BadgePark uses browser storage for your sign-in session, parking timer, the 24-hour confirmation limit and, for Pro users, offline favourites. Its installed app caches public app files. These support requested features, not advertising. Offline favourites are cleared on sign-out and account deletion. Stripe may use cookies and storage for payment security and checkout; see Stripe’s privacy policy.
Location and camera access are requested only after an explanation and your choice to continue. You can decline and search by postcode; uploading a photo is optional. Permissions are separate from accepting these terms.
Visitor analytics
For every visitor, Lovable records page visits, clicks on buttons and links, where visitors came from, country, browser, operating system and device type, time on page, page-load speed and errors. Page visits, time on page, page speed and errors are recorded for every visitor, without cookies and without identifying anyone.
This analytics uses no cookies, stores nothing on your device, does not keep IP addresses and does not identify visitors. Detailed data is kept for 90 days and daily summaries for a year.
Lovable collects this data for us. Lovable’s privacy policy explains how it handles it.
Other services and international transfers
Supabase hosts accounts and data; Stripe handles payments; Lovable and Google process sign-reading requests. OpenStreetMap supplies maps and discovery, and postcodes.io provides postcode lookup. Map tile providers receive the map area requested and ordinary connection data. Google Fonts receives connection data when fonts load; selecting Google Maps directions opens Google’s service. These providers have their own privacy notices.
Some providers may process data outside the UK. Where required, we use UK adequacy regulations or appropriate contractual safeguards. Provider hosting locations and transfer arrangements must be confirmed by the operator before launch.
Retention and deleting your account
Account data is kept while your account remains open. Delete Account in your account page cancels active subscriptions and removes your auth account, profile, saved spots, private notes, personal verification history and app payment-access records. Anonymous public parking signs, rules and aggregate verification counts remain for the community; they are not linked to your account.
Stripe may retain invoices and transaction records where required for tax, fraud prevention or legal claims. Deletion is not an automatic refund. Backup expiry and statutory retention schedules must be confirmed by the operator before launch.
Your rights and complaints
Under UK GDPR, you may request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests. Rights may be limited by legal obligations. You can withdraw consent without affecting earlier lawful processing. Contact the operator using the privacy contact above; we normally respond within one month.
You may complain to the UK Information Commissioner’s Office at ico.org.uk. This notice and the operator’s arrangements should be reviewed before public launch.