Welcome Lot help
Privacy Policy
What information the current service uses, who can see it and how to contact us about your data.
Effective 2026-11-13 · Version 2026-11-13-llc-1
You are using our test site. Test payments do not charge real money or authorize real parking.
Operated by Welcome Lot LLC.
Mailing address: 233 Broad St, Ste 13A, Bridgewater, MA 02324.
Who this notice covers
This notice describes Welcome Lot’s website, owner and attendant accounts, parking payments and support. It covers drivers, operators, attendants and business contacts. The service is operated by Welcome Lot LLC, using the Welcome Lot name. The business mailing address is shown above.
The parking operator also uses information to provide parking and manage its property. Stripe handles payment and payout services under its own terms and privacy policy. Ask the operator about any separate cameras, enforcement systems or records it uses; Welcome Lot does not currently operate plate-reading cameras.
Information used by the service
- Accounts and businesses: email, account identifiers, authentication records, owner name, business name, optional phone, account settings and business contact/support notes.
- Operator agreement records: the business and account identifiers, business name, signer’s name and verified email, authority and agreement confirmations, acceptance time, and the exact accepted documents and version. This records which terms the operator explicitly accepted. Viewing a public policy page does not collect an acceptance.
- Lots and teams: lot name and address, instructions, schedules, prices, invited email addresses, assigned lots, roles and invitation/access history.
- Parking purchases: plate and issuing region, selected lot and parking period, amounts and fees, payment status, time, payment-provider references and private pass/recovery identifiers. A parking record can reveal where a vehicle was expected to park.
- Driver agreement records for live purchases: the order reference, selected lot and parking offer, amounts, parking period, agreement version and acceptance time. We keep the exact policy text linked to that version. This step does not require a driver account or collect an additional email address, IP address or browser fingerprint. Practice payments do not create these records.
- Communications: messages you send to support and the information needed to deliver account confirmations, resets and invitations. An operator supplies an attendant’s email when inviting them.
- Technical information: request and error records, browser/device details and network information handled by our hosting and authentication providers. The app also uses hashed request counters to reduce abuse and stores referral labels supplied in lot or signup links.
Enter card and bank details only into Stripe’s payment or onboarding screens. Welcome Lot’s application database does not store full card numbers, card security codes or full bank credentials. Stripe may provide account status and limited payment information to the operator and authorized platform staff.
You can optionally request an email receipt before paying. The receipt checkbox starts unchecked. We save your choice and selected email with that purchase and share the email with Stripe so it can send the payment receipt. We do not display that email in public passes, plate lookup or operator sales reports. You can pay without requesting a receipt. This choice does not subscribe you to marketing. Separate marketing choices remain a practice-only feature, and marketing delivery is not enabled. Entering an email in Stripe checkout is not consent to Welcome Lot or operator marketing. Text-message receipts are not currently offered.
How information is used
We use information to create and secure accounts, connect owners with their attendants, display parking offers, process and reconcile purchases, issue and check passes, produce sales reports, help with support and refunds, investigate misuse and meet applicable legal or accounting obligations.
A driver does not need a Welcome Lot account to pay. A plate and issuing region let authorized lot staff check the parking payment. We do not sell personal information or use advertising pixels for targeted advertising in this version of the service.
Public pages and private links
A lot’s public payment link and QR sign show its name, location, instructions, parking offer and operator name. Do not put private personal details into public lot instructions.
A parking-pass link is private but does not require a login. Anyone holding that link can view its parking details and status. Confirmation, reset and attendant-invitation links can also give access to an account or assignment. Keep those links private; use the public lot QR to invite customers to pay.
Browser storage, cookies and tracking choices
We use browser storage for sign-in sessions, pending invitations and recovery of recent parking purchases. This can include a plate, issuing region and a private recovery key. Recent saved payments stay on that browser until its site data is cleared; clearing browser data does not delete the server’s payment records.
Cloudflare, Supabase, Stripe and other providers may use cookies or similar technologies for their services, security and fraud prevention. Blocking storage can prevent saved sign-in or payment recovery. Save your private pass before clearing site data, and avoid using a shared device for private accounts.
This version has no optional advertising tracking. It does not separately respond to a browser’s Do Not Track signal. We do not sell or share information for cross-context behavioral advertising regardless of that signal. Any future optional analytics or marketing changes must be reviewed and disclosed before activation.
Keeping information and handling requests
We keep information while it is needed to provide the service and address payment, security, accounting, legal and dispute obligations. Retention depends on the record: account and assignment details support active access; parking and payment records support passes and payment questions; agreement records document the terms accepted; support messages document the request and resolution.
We review these needs when an account closes, when handling a privacy request, and after the pilot. Information no longer needed is deleted or de-identified where permitted. Reviews and eligible removals are manual; there is no general automatic deletion timer. We may retain necessary transaction or agreement evidence for an unresolved dispute or applicable legal obligation, with access restricted to those who need it.
You may contact support@welcomelot.com to request access, correction or deletion, or to ask about your choices. We will verify the request using an appropriate, limited method and explain any information that must be retained. Available rights and response deadlines depend on applicable law.
Removing an attendant assignment stops access but does not erase the business’s audit history. Account closure may require separate handling of related parking and payment records. Provider backups and records kept by Stripe or the operator can follow separate retention requirements. Do not send passwords, full card numbers or private account links with a request.
Security, children and changes
The app uses HTTPS, sign-in and role/lot access checks, private credentials and request limits. No online service can guarantee absolute security. Contact support promptly about suspected unauthorized access or a disclosed private link.
The service is not directed to children under 13. If you believe a child has provided personal information, contact us so we can investigate and handle it appropriately.
The effective date and version appear above. We will communicate material changes where required and review our operating procedures when the service or use of information changes.