FurnishiTenant isolation
Every tenant table carries a factory ID and a row-level security policy. A query executed in factory A’s session returns zero rows from factory B — verified by test, not by convention.
Home Security & compliance
The whole product is an access-control argument.
Furnishi exists because installation data crosses a company boundary every single day. Security is not a page we added at the end.
Field-level access
Partner-facing screens read from database views that do not contain the identity columns. The data is not hidden late; it is never selected.
Separate admin plane
The platform console is on its own URL with mandatory two-factor and network allow-listing. It is not linked from the product and is not indexed.
Impersonation is logged
When Furnishi support opens a factory workspace, the tenant sees it in their own audit log with the staff member’s name.
Full field audit
Who changed which field, from what value to what value, at what time, from which address.
Data stays in India
Primary and backup storage in an Indian region. No customer personal data is processed outside India.
Backups & recovery
Point-in-time recovery with a 24-hour restore objective, tested on a schedule.
Encryption
TLS 1.3 in transit; encryption at rest on database and object storage. Media inherits the same access rules as the record it hangs off.
Least privilege
Six roles, levels L1 to L3, and approval actions that require a fresh authentication.
Indian regulation
What we have designed against.
- DPDP Act 2023
- The factory is the Data Fiduciary for its customers; Furnishi is the Data Processor. Consent capture, purpose limitation, erasure and grievance redress are built into the customer app and the panel.
- Aadhaar
- Furnishi does not collect or store Aadhaar numbers for customer or partner identity. Section 57 of the Aadhaar Act makes private-party Aadhaar authentication untenable, so identity verification uses mobile OTP and, where required, other officially valid documents.
- GST
- Invoices carry the factory's GSTIN. Where a platform is treated as an e-commerce operator under s.9(5) / s.52, the collection mechanics are configurable — this needs your accountant's confirmation for your specific structure.
- TDS s.194-O
- Relevant where the platform pays partner firms directly. Whether it applies depends on whether Furnishi or the factory is the payer in your arrangement.
- Record retention
- Order records, handover signatures and snag evidence retained for the contracted period, then deleted on schedule.
Not legal adviceThe regulatory notes above describe what the system was designed
against. Your own tax and legal advisers should confirm how each applies to your structure —
particularly the GST and TDS treatment of partner payouts.
Honest status
What we have, and what we do not.
In place today
- Row-level security on every tenant table
- Field-level permission matrix, configurable per factory
- Full audit trail with impersonation logging
- Two-factor on the admin console
- TLS 1.3, encryption at rest
- Indian data residency
- Tested point-in-time recovery
On the roadmap
- SOC 2 Type II — not yet audited
- ISO 27001 — not yet certified
- Customer-managed encryption keys
- SAML SSO (Group plan, in build)
- Penetration test report available under NDA — scheduled, not yet complete
- Bug bounty programme
We would rather tell you nowIf a certification is a hard procurement requirement for
you, say so on the first call. We will tell you where we are and when, rather than discovering
it in a security questionnaire three weeks in.
Send us your security questionnaire.
We will fill it in properly, including the questions where the answer is 'not yet'.