Skip to the page
LotPost

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.

POST /api/seat/signin Once, when you sign in inside LotPost. Pressing Activate on your dashboard does the same job from the dashboard itself, through /api/seat/connect, and LotPost sends nothing for it.
email The email you use for your LotPost account.
password Your LotPost password, checked and not kept by LotPost. The extension keeps the seat token the server answers with, never the password.
POST /api/seat/signout Only when you press Sign out, so the seat token stops working on our server too.

An empty body. The request carries the seat token it is signing out, and nothing else.

GET /api/licence On a timer, and when the panel opens, to ask whether this seat is still live.

No body at all. The request carries your seat's token so we know which seat is asking, and nothing else.

POST /api/events Once per posting, so a seat can be metered against its plan.
target The word facebook or the word kijiji. Nothing else is accepted.
ts When it happened.
outcome published, failed or aborted.
eventId A random identifier, so that if the request has to be retried the same posting is not counted twice.
POST /api/diag Only when you press Send diagnostics. Never on its own.
items At most 100 error records, each one a time, a short code and a message of at most 500 characters. These are LotPost's own error messages about what went wrong, kept on your computer until you choose to send them.
GET + PUT /api/lots When the panel reads your lot's settings, and when you save one. These are the same settings /app shows, so a lot reads the same in every browser.
name The name you gave the lot.
settings Where your car list comes from (the feed address you entered, or the name of the file you picked, and the format that reads it), your city and postal code, the listing template, the pace and limits LotPost posts at, quiet hours, and whether you post as a profile or a Page, with that account's name. These are stored on our server with your account. The car list itself is not: LotPost reads it in your browser.
rev A version number, so a save made from an older copy is refused rather than overwriting a newer one.
POST /api/studio/sources Only when you choose to send a photo to the Studio and confirm. The Studio's mark finder and mark remover, /api/studio/detect-marks and /api/studio/inpaint, carry the photo the same way, for that one edit.
the photo The picture itself, up to 8 MB. It is stored on our server so the Studio can work on it, and the photo and everything made from it are deleted after 30 days. When an edit needs an AI model, the photo is sent to Replicate, the service that runs the model.
POST /api/studio/jobs When you start an edit on a photo already in the Studio. The panel then asks /api/studio/jobs for its progress and fetches the finished file, and reads /api/studio for the list of scenes and their prices; those carry no body.
sourceIds Which uploaded photo to work on.
preset Which background you chose.
branded Whether to use your dealership's colour, and brandHex, that colour.
watermark Whether the result carries the footer.
key A random identifier, so a retried request is not charged twice.

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.

POST /api/auth/signup Once, when you open an account.
type Dealership or salesperson.
name Your name. You can change it later on /app.
dealershipName The dealership's name, if you give one.
email Where we send your sign-in and password-reset mail.
password Kept only as a one-way hash, never as the password.
invite An invite code, if someone gave you one.
POST /api/me/avatar Only when you add a profile photo. Removing it on /app (DELETE /api/me/avatar) deletes it from our server.
the photo The picture itself, up to 512 KB, shrunk to 256 pixels and stored until you remove it.
POST /api/lots/preview While you edit a lot on /app, to show what a change would do before you save it.

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.

Railway Runs our server and its database, where everything stored above lives.
Replicate Runs the AI model behind a Studio edit. It receives the photo for that edit.
Brevo Sends our email, such as your sign-in and password-reset mail. It receives your email address and the message.
Stripe Will take payment. Billing is not switched on yet; when it is, your card is typed into Stripe's own page and LotPost never sees the number.
Cloudflare Serves this website, so it handles each visit the way any web host does.

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.

storage Keeps your inventory, drafts and settings in this browser. The unlimited variant is there because a large lot with photos outgrows the small default.
tabs Opens the marketplace tab it is filling and notices when that page finishes loading.
scripting Types into the marketplace form, and reads the inventory page you point it at.
alarms Picks a paused job back up at the right time, instead of holding a timer open.
notifications Tells you a run finished or stopped.
downloads Saves a file to your computer when you ask for one.
geolocation Fills in your town. When your lot has no town yet, and whenever you press Use my location, Chrome gives LotPost this computer's rough position and LotPost picks the nearest town from its own built-in list. The position itself is never sent to us; the town goes into your lot settings, which are stored as described above.
sidePanel The panel LotPost runs in.
host access facebook.com/marketplace and kijiji.ca, the only two sites LotPost may read or type into without asking you first.
optional host access Your own inventory site, requested one site at a time, by you, when you connect your inventory. Chrome asks before it is granted and you can take it back.

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 sia@kavalsia.com 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 Drive
Angus, Ontario L0M 1B4
Canada
Ontario Corporation Number 1000576319

sia@kavalsia.com