Security
Controls, stated plainly.
How Terriv handles access, connections and your documents, control by control.
Controls ledger
Eleven controls. The ones agreed with each brokerage rather than fixed by us carry a label.
- Transaction scope A person reaches only the transactions their role covers, rather than the whole office by default.
- Roles Permissions by role, set by the brokerage rather than by us.
- Decision record Every confirmation carries the account that made it and the time it was made, so a reviewed date traces back to a person.
- Broker control of connected systems Which systems Terriv reads, and for how long, is set by the broker under written terms and revocable by the broker. Per brokerage
- Required-document policy The list of documents a transaction requires differs by state, by association form set and by office. It is agreed with each brokerage rather than fixed by us. Per brokerage
- Export, retention and deletion What is kept, for how long, where it sits, and how it is deleted on request is agreed in writing before any file is shared. Nothing of yours moves before that is signed. Per brokerage
- Email and phone connections Email and phone systems are read under written terms, switched on per brokerage and revocable by the broker.
- CRM and transaction platforms Terriv connects to the transaction and CRM systems a brokerage already runs, scoped with the broker under written terms.
Implemented: live in the product today. Per brokerage: set with each brokerage during setup.
These are the same three questions the home page answers in its What runs today band, asked in the same order, so the two pages can be checked against each other. As of today no control on this page carries the Implemented label.
Access levels
There are three levels. Each sees only what its role requires, and one of the three is deliberately empty.
- Agents An agent reaches the files they are on and nothing else, including after hours.
- Brokers and authorized staff Broker-level access covers the whole office. Which staff carry it is decided by the brokerage, and broker-level controls are not delegated below the broker. Per brokerage
- Consumers There is no consumer surface. Nothing reaches a client from Terriv, and client communication stays where it is today.
Human oversight
Terriv's output is reviewable and attributable: a proposed date points back at the sentence it came from, and a confirmation carries the account that made it and the time it was made.
What is already fixed is the boundary. Nothing unconfirmed drives client communication, and nothing reaches a client from Terriv at all. Software that reads documents will sometimes miss a date or misread a clause, so a quiet list is never a guarantee that the file is clean, and Terriv is not a substitute for your own review.
What we do not claim
Terriv holds no third-party security certification and claims none. Architecture and data-handling documentation is available for review during demo and pilot discussions, and questions from IT contacts or E and O carriers are answered directly.
There is no penetration test report, no audit, and no compliance badge to show you, because none has been done. If a control matters to your brokerage, ask about it before a pilot rather than after, and you will get a straight answer.
Security questions answered before a demo.
Bring your IT contact. We answer your questions first, then show the product running on sample data.