Trust & Transparency

Security & Data Protection

GharLedger is designed from the ground up to protect sensitive landlord and tenant details. Here is a transparent breakdown of how we secure your data, backed by direct implementation in our codebase.

AES-256-GCM Encryption at Rest

Sensitive Personal Identifiable Information (PII) like Aadhaar numbers, PAN cards, and emergency contact details are encrypted at rest using AES-256-GCM.

How it works: The encryption key is held only in the application server's memory environment and is never written to the database. Losing this key makes the data completely unrecoverable, even from backups.

Enforced TLS & HSTS

All data in transit is encrypted using modern Transport Layer Security (TLS). We enforce HTTPS-only connections at the API level.

How it works: Our backend sets the HTTP Strict Transport Security (HSTS) header to max-age=63072000; includeSubDomains; preload. This ensures browsers refuse to connect over insecure HTTP.

Workspace Isolation

Every database query checking properties, tenancies, bills, or statements enforces strict user isolation. Owners can only interact with data matching their active workspace.

How it works: Every owner endpoint uses our backend isolation helper to verify workspace ownership. Cross-workspace read or write requests return a strict HTTP 403 Forbidden response.

Encrypted Backups & Drills

We perform daily database dumps, encrypted and sent to private Cloudflare R2 containers. The backup bucket is entirely private and does not allow public reads.

How it works: We run regular restore drills. Our tested Recovery Time Objective (RTO) is under 5 minutes for database restoration, minimizing potential downtime.

DPDPA Right-to-Erasure

GharLedger fully aligns with India's Digital Personal Data Protection Act, 2023. We mask Aadhaar numbers to the last 4 digits in all interfaces and log tenant consent timestamps.

How it works: Tapping "Delete my account" triggers a 14-day soft-delete grace period, after which PII is fully anonymized. Financial transaction history is kept for 7 years to comply with statutory tax rules.

Session Controls & Timeouts

Authentication tokens are stored securely in browser cookies configured with SameSite constraints.

How it works: The web console runs an active Session Timeout Guard. If a user is inactive for an extended period, they are automatically logged out, preventing unauthorized access.

Our Honest Trust Posture

We believe in developer-led transparency over marketing fluff. GharLedger does not currently hold a SOC 2 Type II or ISO 27001 certification, nor do we run a formal public bug bounty.

Instead, we focus on rigorous security practices: minimizing PII collection, keeping our entire client-facing surface open for inspection, encrypting sensitive fields, and enforcing strict tenant isolation boundaries.