What LotPost knows about you
Most policies describe categories. This one names the fields. Every one is listed below. Your car list is not among them, and a car photo reaches us only when you send it to the Studio yourself.
Updated 2 October 2026 The extension and this site
The short version
- Your inventory stays on your computer. The car list, the drafts and your marketplace logins are read and kept in this browser and are never uploaded to us. A photo leaves only when you send it to the Studio, and the Studio deletes it after 30 days.
- We count postings, not cars. To know a seat is being used we record which marketplace, when and whether it worked. Nothing about the car.
- Nothing is sold or advertised against. Five named services do work for us, hosting, email, payments and the Studio's AI edits, and each sees only what that work needs. Visitor counting on this site is switched off, and if it is ever switched on it waits for your yes.
What stays on your computer
LotPost reads your inventory from your own website and keeps it in this browser's own storage. It stays there until you remove the extension or clear it yourself. That includes every car and its details, every photo, every listing draft LotPost prepares, your settings and field mappings, and the record of what you have posted.
LotPost fills the marketplace form in a tab you are already signed into. It does not hold your Facebook or Kijiji password, and it cannot: it types into the page the same way you would, in your own signed-in browser. No car is ever posted from our server.
Everything that leaves it
Every request goes to your own LotPost account server, and they are all here: first the ones the extension makes, then the ones your account page at /app makes. Where a request carries fields, the fields listed are its whole body, and that is enforced rather than promised: the server rejects any field it was not told to expect, so a future version cannot quietly add one to this list without the list changing too. A photo is the one body that is not a list of fields; it is the picture itself.
An empty body. The request carries the seat token it is signing out, and nothing else.
No body at all. The request carries your seat's token so we know which seat is asking, and nothing else.
Your account page at /app signs you in, resets or changes your password and changes your name with exactly the fields you type into it. Beyond those, it makes these, and only when you use it. The Studio's own page makes the same Studio requests as above.
The same settings as /api/lots above. Nothing is written: the server answers and forgets.
LotPost reads two other kinds of page and neither one sends us anything: your own inventory feed, at the address you gave it, and the marketplace page it is filling. Everything it learns from those stays on your computer.
What we never ask for
These are not fields we choose not to read. There is no field for them, and a request carrying one is rejected before it is looked at.
- A VIN, a stock number, a price, a mileage or a title status.
- A listing URL or the text of a listing. A photo only when you send it to the Studio yourself, as above.
- A buyer, a message, a lead or anyone's contact details.
- Your Facebook or Kijiji password, or anything from those accounts.
- Your browsing on any other site. LotPost reads two marketplace addresses and whichever inventory site you point it at yourself.
Who else handles it
Five services do work for LotPost. Each one is given only what its job needs, and we sell your data to none of them, or to anyone.
Counting visits to this site
This website has room for three visitor-counting tools: Google Analytics, the Meta Pixel and Cloudflare Web Analytics. All three are switched off today. The site loads none of them and sends them nothing.
If we switch one on, it still waits for you. A small bar asks "Count this visit?" and nothing loads until you press Allow. With your yes, the tools we switched on see the page you are on, the ad or link that brought you here (the utm tags in the address), and at most five moments: a page view, a click on a sign-up button, a click on the extension download, starting sign-up and finishing it. Each tool also collects what its own script collects: Google Analytics and the Meta Pixel set cookies in your browser and see your browser and rough location, and Cloudflare Web Analytics sets no cookie. Your yes covers only the tools the bar named. If we switch on another one later, you are asked again before it loads.
To say no, press No thanks; this browser remembers it and you are not asked again. If your browser sends Global Privacy Control or Do Not Track, we take that as no and never ask. To be asked again, clear this site's data in your browser. The extension never loads any of these tools.
The permissions Chrome shows you
Chrome lists these when you install. Here is what each one is actually for.
Deleting all of it
Removing the extension deletes everything it kept on your computer, because all of it lives in this browser's own storage and goes with it.
On our side we hold your account details, your lot settings, any Studio photos from the last 30 days, your profile photo if you added one, and the posting counts described above. Studio photos delete themselves after 30 days, and you can remove your profile photo yourself on /app. For everything else there is no delete button yet: write to [email protected] and a person deletes the account and everything held for it.
Who to write to
LotPost is made by Kavalsia Inc., an Ontario corporation. Write to us about anything on this page, including deleting your account, and a person will answer.
Kavalsia Inc.
312 Greenwood DriveAngus, Ontario L0M 1B4
Canada
Ontario Corporation Number 1000576319