Security & data handling

Your data, treated like it's ours to lose.

Our software runs real portfolios and messages real residents every day. That's a responsibility we engineered for from the start — here's exactly how.

Your system of record stays yours

LeaseRails reads and writes to your property management software — it doesn't replace it or hoard a copy. Prospects, leases, and charges live where they always have. Walk away, and your data is already home.

Sends fail closed

If an opt-out list or safety check can't be verified, automated messaging stops — it never guesses. A resident who texts STOP is honored across every channel, automated and human alike.

Least data, least access

We keep only the operational state the product needs to run — queues, opt-out lists, message logs. Per-user accounts, no shared passwords, access revocable per person.

In practice

Production hardening, not promises.

  • Encrypted in transit, everywhere
    HTTPS across every page and API call, with strict transport security (HSTS), a content-security policy, and clickjacking / MIME-sniffing protections on every response.
  • Nightly off-site backups
    Every operational store is backed up automatically each night to independent cloud storage, encrypted at rest — and the backup job alerts us if it ever isn't configured or fails.
  • Monitored automation
    A dead-man watchdog alerts us if scheduled jobs stop running, and every run writes a health record we review. Silence is treated as an incident, not a relief.
  • No double-sends, by design
    Every automated message must atomically claim its recipient first, with a hard one-per-day cap per person — so a retry, overlap, or crash can't text anyone twice.
  • Guarded writes
    Money-touching actions are idempotent and re-verified against live data before they land — a duplicate click can't create a duplicate charge, and rent guardrails re-check the source of truth, including local rent-cap rules.
  • Licensed access, clean exit
    Software is licensed per client with individual team accounts. If an engagement ends, outbound automation stops — and your records are still sitting in your own system.
Straight talk

Small company. Conservative engineering.

We're not going to wave an enterprise compliance badge we haven't earned. What we will do is show our work: how sync behaves, what we store, what happens on failure, and how messaging stays compliant. If your team wants to review any of it before we integrate, we'll walk you through — gladly.

Questions welcome

Security review, data-flow walkthrough, or integration vetting — we'll get on a call with your team and answer everything, in plain English.

Book a call
Book a Call