What we collect, how we protect it, and who sees it.
This page is for IT, procurement and anyone reviewing Laneo. It covers the data we handle, encryption, access, the audit trail, retention and the providers we use.
Laneo- Hosted in the United States
- Encrypted in transit and at rest
- Data separate per property
- Every lookup and change logged
- Residents · sendPlate, state, name, email, unit
- Guests · sendPlate, state, visit time
- Stripe · card paymentsFull card details stay with Stripe
- Property team · seesPermits, visits, reports, audit trail
- Enforcement partner · seesWhether a plate is valid, and why
Data we handle
We collect what parking needs and nothing more. Analytics never include plate numbers, names, emails or card data.
| Data | From | Why | Who sees it |
|---|---|---|---|
| License plate and state | Residents, guests | The plate is the permit or pass | The property, its enforcement partner |
| Name and email | Residents, guests | Account, receipts and support | The property |
| Unit number | Residents, the property | Permit slots and free guest hours | The property |
| Guest visit times | Guests, hosts | Passes, limits and rules | The host, the property |
| Payment status, last four digits | Stripe | Receipts and refunds | The payer, the property |
| Lookups, photos and notes | Enforcement partners | Audit trail and violation log | The property, the partner |
- Sell personal data
- Send text messages
- Track phone location
- Put plates or names in analytics
Encryption
In transit
Every connection to Laneo uses TLS, for residents, guests, property teams and partners.
At rest
The database, files and backups are encrypted at rest, and sensitive fields are encrypted again by Laneo.
Secrets
Keys and passwords live in our hosting providers’ secret stores, never in code.
Access controls
Each property’s data is kept separate, and every person signs in with a role that decides what they can see and do.
- Resident
- Their own vehicles, guests, billing and receipts.
- Guest
- Their own pass and receipt. No account needed.
- Property admin
- Their property’s residents, permits, rules, visits and reports.
- Portfolio admin
- Properties in their portfolio, as set by your company.
- Enforcement partner
- Plate lookups and the violation log for properties that invited them. Towing partners see only valid or not valid.
- Laneo support
- Customer data only to help with a request, with access logged.
Single sign-on for your company accounts is available as an add-on. Laneo staff access customer data only to support you, and that access is logged.
Audit trail
Plate lookups, permit changes, rule changes and refunds are recorded with who did it and when. Property teams can review their own trail.
- 11:42 PMTest TowingLooked up TST-4821 · not valid
- 6:15 PMProperty adminChanged overnight window to 10 PM to 6 AM
- 2:03 PMResident, Unit 000Swapped plate TST-1234 to TST-5678
- 11:20 AMLaneo supportViewed Unit 000 billing for a refund request
- 9:02 AMProperty adminIssued a refund for a guest pass
Retention and deletion
Plate data has an expiry
Plate and lookup records are deleted on a schedule set out in the privacy notice. Deletion runs automatically.
When a resident moves out
Their permits end on the move-out date, and their data follows the same schedule.
When a property leaves Laneo
We return the property’s data on request, then delete it under the data processing agreement.
Personal requests
Residents and guests can ask to see or delete their data by writing to privacy@getlaneo.com.
Infrastructure and providers
These are the main providers that process data for Laneo. The full sub-processor list is in the security pack.
| Provider | What it does for Laneo | Data it handles |
|---|---|---|
| Fly.io | Hosting for the Laneo API and background jobs, in Virginia, United States | All customer data, in transit and in queues |
| Neon | Database and backups, on Amazon Web Services in Virginia, United States | All customer data |
| Stripe | Card payments for residents and guests | Card details, payment status |
| Cloudflare | DNS for Laneo’s domains | Domain name lookups, no customer data |
| Vercel | Hosting for the Laneo web app and the public website | Requests to the web app, website visits and form submissions |
| Resend | Sending email from the website, like demo confirmations and support receipts | Names, email addresses and messages from website forms |
| Google Workspace | Email for support, billing and privacy requests | Messages you send us |
Card payments. Residents and guests pay through Stripe. Laneo never sees or stores full card numbers; we keep the last four digits and the payment status.
Requests and reports
Privacy requests
See, correct or delete personal data.
privacy@getlaneo.comSecurity reports
Found a vulnerability? Tell us privately.
security@getlaneo.comBilling
Invoices, receipts and refunds.
billing@getlaneo.com
Request the security pack
Everything most security reviews ask for, in one place.
- Data processing agreement
- Completed security questionnaire
- Sub-processor list
- Privacy notice and retention schedule
Questions from reviewers
Where is our data stored?
In the United States. The database runs on Neon in Amazon Web Services data centers in Virginia, and the Laneo API runs on Fly.io in Virginia. The web app is served by Vercel.
Can we use our own data processing agreement?
Yes. Send it with your request and we’ll review it, or use ours from the security pack.
Who at Laneo can see our data?
Only people who need it to support you. Their access is limited by role and logged in the audit trail.
Do you sell or share data with advertisers?
No. Data is shared only with your property team, your enforcement partner and the providers listed on this page.
How do we report a security issue?
Write to security@getlaneo.com. Please don’t share details publicly until we’ve had a chance to fix it.