LOTWELL.

Privacy policy

Effective October 12, 2026

Lotwell is an app for parking at homeowner associations and other shared properties. It is provided by Lotwell LLC ("Lotwell", "we"). Its idea is in its first line: everyone can tell whether a car belongs, and nobody learns who anyone is. This policy says what that means for your data.

Who uses Lotwell

A property's board sets Lotwell up and decides its rules. Owners and their renters register their vehicles and issue visitor passes. Front gate staff check stalls. Guests receive a visitor pass and do not need the app.

What we collect, and why

What we do not collect

Who can see what

Services we use

These process data for us, under their own privacy and security commitments, which are at least as protective as this policy:

We share data with no one else, except where the law requires it.

Guests' Wallet passes

A guest who adds a visitor pass to Apple Wallet lets their phone register with our server so the pass can update if it ends early. We keep that registration, which does not identify the guest, for 30 days after the pass last changed.

The guest's page

A visitor pass comes with a link to a page that shows the stall, the times, directions, and the last three characters of the guest's plate. The page needs no account and sets no cookies. It holds no name, no unit, and nothing about the resident. A guest can tell the resident from the page that they have arrived or left, or ask for more time; those taps are kept on the pass, with the time, and shown to the resident. The link stops working a day after the pass ends. To keep the pages from being guessed at, we count failed attempts against the network address they come from, as a one-way hash, for a day. Directions open in Apple Maps or Google Maps on the guest's own phone, under those services' privacy policies.

Tags and placards scanned without the app

A car's tag and a stall's placard open a page on any phone. The tag page lets a neighbour send the car's owner one of a few fixed sentences, such as "has its lights on". We store which sentence was picked and when, against the vehicle, and show it to the owner; we store nothing about who sent it. The owner never learns who scanned the tag, and the sender never learns whose car it is, not even that it is registered. An owner can turn these messages off per vehicle. The placard page shows what kind of stall it is and, for shared stalls, whether it is free; it never shows a name, a unit, or a plate. A guest can check their pass code against the stall; the answer names a stall and nothing else.

Tows

When a board member asks a tow company to remove a car from a stall, we make a page for the company that shows the stall, the plate the board member read off the car, the time the tow may go ahead, and where to meet. It holds no name and no unit. The link is sent to the company's dispatch address, and to the company's Towbook account where the property has linked one; it stops working when the ticket closes, and the plate is removed from the ticket a day later. The household the stall belongs to is told through the app and can answer once; the other board members are told by notification and by email to their sign-in address. The record of the request, the answer, and the outcome is kept with the property's enforcement notes, without names.

Live Activities, widgets, and Siri

On iPhone, a visitor pass, a move-your-car event, a car at a charger, or a board patrol can appear on the Lock Screen and in the Dynamic Island while it is happening, and a widget can show what is next. What appears is a stall label, a time, and a count, never a name or a unit. To keep those current, your phone gives our server a token for each one, alongside the notification token it already has; the tokens identify the phone, not you, and are dropped when the activity ends. If you ask Siri to issue a pass or to check your stall, the request is handled by the app on your phone the same way a tap would be; nothing about it goes to Apple beyond what Siri needs to understand the words. You can turn Live Activities off for Lotwell in your phone's Settings at any time.

Where the stalls are

The board may survey a parking area with the camera: walking it, marking each bay, and saving where the bays are. What is saved is the stalls' positions on the map and, for an area, a scene: ARKit's record of the fixed shapes the camera saw there, a few megabytes of geometry with no pictures in it, by which a board member's phone can later find its place to the centimetre and name the stall in front of it. Positions and scenes are the property's data, kept with it and deleted with it. The camera's pictures are never saved or sent, during a survey or a patrol.

How long data is kept

Deleting your data

In the app, open Settings and tap Delete account. The app shows exactly what will be deleted first. Your sign-in, your link to the property, and your notification tokens are deleted at once. If you were the last account on your unit, its vehicles and open passes are deleted too. Records the property keeps, such as past passes and notes, stay but no longer point to you.

You can also turn notifications off at any time in your phone's Settings, and remove a vehicle or end a pass in the app. To ask about your data or have it deleted another way, email support@lotwell.app.

Security

Data is encrypted in transit and at rest. Plates are encrypted again on top of that. The app cannot read the database directly: every request goes through our server, which checks who is asking.

Children

Lotwell is for property residents and staff, and is not directed at children under 13.

Changes

If this policy changes, the new version is posted here with a new date. A significant change is announced in the app.

Contact

Lotwell LLC, support@lotwell.app

Apple, Apple Maps, Apple Wallet, and Sign in with Apple are trademarks of Apple Inc., registered in the U.S. and other countries.