Security
Call data is sensitive. These are the controls actually built into Farminghub Call Analyzer today — we'd rather describe real safeguards than recite slogans.
Tenant isolation enforced in the database
Every organization’s rows are separated with PostgreSQL row-level security, enforced for the application itself — not just filtered in application code. Cross-organization access is part of our automated test suite.
Encrypted transport
Browser, app and API traffic runs over TLS.
Credential hygiene
Passwords are stored only as strong one-way hashes. Device and API credentials are shown once at issue, stored hashed, and can be rotated or revoked individually. Sign-in attempts are throttled.
Role separation
Admin, manager and agent roles are enforced server-side, and platform operations live in a separate realm with mandatory MFA. No organization role can delete call history.
No third-party call capture
The Android app reads the phone’s own call log and, on supported devices, imports recordings the built-in dialer made. It contains no audio-capture or accessibility-based recording code.
Audit trail
Administrative and data-affecting actions are written to an audit log with actor, action and time — kept free of message content and personal call notes.
Farminghub Call Analyzer implements technical controls designed to support our customers' obligations under India's data-protection law. Questions or a disclosure to report? Contact us.