What LeaseLab stores
Your account and the workspace you create. Your properties, units, leases, and the tenant names and contact details you enter. Rent amounts, monthly obligations, and the payments, reminders and adjustments you record. The files you import, and the maintenance emails you forward, including their attachments.
Alongside that, LeaseLab keeps operational records — identifiers for each request and each background job — so support can trace a problem you report. Those records hold identifiers and outcomes, not the contents of your documents or emails.
How email forwarding works
Your workspace has its own intake address. Mail sent to it is stored and turned into a work order. That is the entire mechanism.
By default, you never connect your mailbox, and you never give LeaseLab a password — LeaseLab only ever sees what you forward, or what a tenant sends to that address directly. If you would rather have messages pulled in automatically, the account owner can instead connect a dedicated mailbox as a separate, opt-in step: the credentials are encrypted and never shown again, and LeaseLab only ever reads that mailbox — it never sends, moves, or deletes anything in it.
Which workspace a message belongs to is decided purely by the address it was sent to. Who it came from, and what it says, never changes that — which is what keeps one landlord’s mail out of another landlord’s workspace.
How AI is used
Three places: reading structure out of a spreadsheet or lease document you import, suggesting a category and priority for a maintenance request, and helping organise inbound messages.
AI never writes to your records on its own. Imported rows are shown to you first and only saved when you confirm them. A maintenance suggestion sits alongside the work order as a read-only note; the work order itself came from the email, not from the model.
That means a wrong suggestion changes nothing on its own — it is advice you can ignore. You still set the work order’s own priority, add notes, reassign it, and close it, and those are what the product acts on. The suggestion itself is not editable today; if one is misleading, tell us and we will look at it.
How you correct a mistake
Everything you can enter, you can also correct. A payment recorded in error can be reversed; an obligation can be waived; a work order can be re-assigned or closed.
Corrections are added on top rather than erasing what was there — the history shows both the original entry and the correction, with when each happened. That is deliberate: when you are looking back at a disagreement about rent months later, a record you can trust is worth more than a tidy one.
Your workspace is separate
Every piece of data belongs to exactly one workspace, and every request is checked against your membership of that workspace before it can read or write anything. There is no shared pool and no cross-workspace view for customers.
Card details
Stripe is LeaseLab’s payment rail for periodic settlements. Your card number is entered on Stripe’s own hosted page and never reaches LeaseLab. What LeaseLab knows is whether a settlement payment succeeded, failed, or is not yet set up.
Getting a copy of your data, or having it deleted
Email support@leaselab.io. There is no self-service export or delete button today, and rather than pretend otherwise: a person handles these requests.
Cancelling does not delete anything, and your workspace never becomes read-only because of a billing or payment outcome — access is not tied to billing status.
Who to contact
Support, privacy questions, and security reports all go to support@leaselab.io. It is one monitored mailbox rather than three, which is the honest description of how a small operation works.