Security

How we protect
your data.

TenantFort handles sensitive applicant data — IDs, pay stubs, bank statements, contact information. This page documents the controls in place today and the ones still in progress. Last updated: April 23, 2026.

Data Protection

How applicant and landlord data is encrypted, isolated, and accessed.

Encryption at rest

In place

All applicant data, document files, and database contents are encrypted at rest using AES-256, provided by Supabase (PostgreSQL) and Supabase Storage.

Encryption in transit

In place

TLS 1.2+ enforced on every connection between browsers, the TenantFort application (hosted on Vercel), Supabase, Stripe, Resend, and Anthropic.

Row-level security (RLS)

In place

Each landlord organization's data is isolated at the database row level. RLS policies on every table ensure one organization cannot read another's properties, applicants, documents, leases, or payments.

Signed, time-limited document URLs

In place

Applicant documents in storage are accessed via signed URLs that expire. They are never publicly browsable.

Access Control

How user accounts, roles, and authentication are managed.

Authentication

In place

Account access is gated by Supabase Auth. Passwords are hashed (bcrypt). Session tokens use httpOnly, Secure cookies.

Role-based access control (RBAC)

In place

Within an organization, users have roles (owner, admin, manager, viewer). Each role has scoped permissions for properties, applications, leases, billing, and team management.

Multi-factor authentication (MFA)

In place

TOTP-based MFA enrollment is available to every landlord account from Settings → Security. Enterprise plans can require MFA for the entire organization — un-enrolled users are routed to the enrollment flow on next sign-in and blocked from the dashboard until they complete it.

SSO (Single Sign-On)

In place

SSO via Google Workspace, Okta, Azure AD, or custom SAML is available on the Enterprise tier.

Audit & Monitoring

What is logged, what is reviewed, and what is automatically detected.

Audit trail

In place

Every screening decision is logged with the criteria applied, the timestamp, and the acting user. The audit trail is queryable by the organization.

Document analysis logging

In place

Each AI document review records the model, prompt version, and the structured assessment, attached to the document for review.

Admin action logging

In place

Account-level actions (role changes, key rotations, webhook updates) are written to the audit trail.

Anomaly detection / abuse monitoring

In progress

Manual review of unusual patterns. Automated rate-limiting on public endpoints. Formal anomaly detection is on the roadmap.

Infrastructure

Where the application runs, how it is backed up, and how it is patched.

Hosting

In place

Application hosted on Vercel (US regions, edge network). Database and file storage on Supabase (US regions). Both are SOC 2 Type II audited platforms.

Backups

In place

Database backups are managed by Supabase: daily automated backups with point-in-time recovery available on the Pro tier.

Patch management

In place

Dependencies are monitored for known vulnerabilities. Critical security patches are applied within 7 days of disclosure; high-severity within 30.

SOC 2 Type II

In progress

TenantFort the company is not yet SOC 2 audited. Both Vercel and Supabase, our hosting providers, are SOC 2 Type II audited. We will publish our own SOC 2 attestation when complete.

Penetration testing

In progress

Independent third-party penetration testing is planned ahead of broad enterprise rollout. Currently, we run internal security reviews on every release.

Compliance

The legal frameworks TenantFort is designed to support.

FCRA (US)

In place

Adverse action notices generated by TenantFort include the disclosures required by 15 U.S.C. § 1681 et seq. Landlords using the platform must obtain proper applicant authorization and use the data only for permissible purposes.

PIPEDA (Canada)

In place

Applicant consent is captured for AI document analysis, public records cross-reference, and verification outreach. Cross-border transfer notice is provided. Provincial privacy law obligations (Quebec Law 25, BC PIPA, Alberta PIPA) are reviewed for jurisdictional applicability.

Fair Housing audit trail

In place

Every screening decision logs the exact criteria applied so an organization can demonstrate consistent treatment across applicants for the same property.

Data subject rights

In place

Applicants and tenants can request access, correction, or deletion of their personal data via info@tenantfort.com. Requests are honored within 30 days, subject to legal record-retention obligations.

Subprocessors

Third parties that process applicant or landlord data on our behalf.

SubprocessorPurposeRegionPrivacy
VercelApplication hosting + edge networkUnited StatesPolicy →
SupabasePostgreSQL database, file storage, authenticationUnited States (us-east-1)Policy →
AnthropicClaude API for document analysis and applicant data cross-referenceUnited StatesPolicy →
StripePayments and subscription billingUnited StatesPolicy →
ResendTransactional and verification emailsUnited StatesPolicy →

We do not use paid consumer reporting agencies for credit, criminal background, or eviction history. If you require those reports for your jurisdiction, you must obtain them through a separate provider.

Report a Vulnerability

Found something that looks like a security issue? Tell us.

Email info@tenantfort.com with: a description of the issue, steps to reproduce, and any proof-of-concept. We aim to acknowledge within two business days.

Please do not test against other organizations' data, do not access or modify data that is not yours, and give us a reasonable window to remediate before public disclosure.

We do not currently run a paid bug bounty program, but we publicly credit researchers who report valid issues responsibly (with permission).

Honest about what's not yet done

The items marked "in progress" are real gaps we're actively closing before broad enterprise rollout — primarily SOC 2 Type II attestation, automated anomaly detection, and third-party penetration testing. We'd rather list them than leave you to discover them later. If a specific control is a hard requirement for your deployment, contact us at /contact and we'll tell you where we are honestly.