Security
Last updated 7 September 2026
This page states plainly what Ghost Tenant actually does to protect your data — not a generic checklist, only things that are true today. If something changes, this page gets updated, not left stale.
Encryption
Every connection to Ghost Tenant — the website, the dashboard, the admin panel — is HTTPS only, enforced site-wide with HSTS, so a browser will refuse to fall back to an unencrypted connection once it's visited once. Your house's data is stored in Supabase's managed Postgres database, encrypted at rest with AES-256 and in transit with TLS — this is Supabase's own infrastructure-level guarantee, always on, not something we configure or could accidentally leave off.
Payments
All payments are handled by Stripe. Your card details are entered directly with Stripe and are never seen, transmitted through, or stored on our own servers at any point — Ghost Tenant only ever holds a reference token Stripe gives us back, never the card number itself.
Passwords
No password — yours, a landlord's, or a staff member's — is ever stored in plain text. Every password is salted and hashed (scrypt) before it touches the database, so even direct database access never reveals a usable password.
Backups — real, and actually tested
The database is backed up automatically every day. Unlike a lot of products that just assume their backups would work if they were ever needed, we've actually run a real restore: a live backup was restored to a genuinely separate project and checked row-for-row against production to confirm it was byte-for-byte accurate, then the throwaway copy was deleted. Every photo, PDF, and other file your house generates (condition reports, damage logs, deposit evidence) is separately synced daily to an independent backup location, so a fault in one system can't take out both the record and the evidence at once.
Access controls
Every table in our database enforces row-level security, so data access is restricted at the database layer itself, not just by application code that could have a bug in it. Staff and admin accounts require two-factor authentication, and every destructive admin action — removing a house, changing another admin's access — requires the acting owner to re-enter their own password first, logged in a permanent audit trail.
Your rights over your own data
You can request a full export of everything we hold about you, or ask for it to be permanently deleted, at any time — this is a real, working process, not just a policy statement. See our Privacy Policy for exactly how, and what happens to shared house records versus your own.
Found a vulnerability?
We take reports seriously and will respond properly, not just file it away. Email security@ghosttenantai.com with what you found and how to reproduce it. Please don't access, modify, or delete anyone else's data while investigating — a proof of concept describing what you found is enough. We won't pursue legal action against a good-faith report made this way.
Technical details for automated scanners: /.well-known/security.txt.