Help Questions
Security and your data
How Tiermark protects what you put in it: a second factor on every sign-in, US hosting, encryption, backups, a hash-linked audit trail, signed answers fixed once signed, and no CUI. Where the full detail and the commitments are.
Updated · Edwards Consulting Group
Put your supplier records in Tiermark knowing how they are kept. Here is what protects them today, in short. The security page has the full list, and Tiermark's commitments about your data are in the privacy notice and the terms. Tiermark holds no security certification and claims none.
Signing in
- A second factor on every account. An authenticator app code or a passkey, never a text message. There is no way to sign in with a password alone.
- Passwords of at least 14 characters, with lower case, upper case, a digit and a symbol.
See Signing in.
Where your data lives
- In Tiermark's own Amazon Web Services account, in the Ohio region (us-east-2), in the United States.
- Encrypted in transit and at rest. The site accepts TLS 1.2 or later, and the records are encrypted with Tiermark's own key.
- Backed up. Every table can be restored to any point in the last 35 days.
Records you can rely on
- An audit trail. What happens in your organization, such as a signature, a share, a change to a risk item or an audit package download, is recorded as an event linked by hash to the one before it, so changing or removing an event breaks the chain.
- A signed answer set is fixed once signed: nothing in Tiermark edits it, and Tiermark refuses to read one whose bytes no longer match its hash. See Answering a request.
- Audit packages are kept in object-locked storage and checked before every download. See Audit packages.
No CUI
Never enter or upload Controlled Unclassified Information (CUI), classified information or export-controlled data. Tiermark checks the text you type, such as questionnaire answers, campaign notes and risk items, for CUI banner and portion markings, and refuses text that carries one. The check cannot catch every way of writing CUI, so keeping it out is yours to do as well.
What other people can see
- Your company's public page shows its SAM.gov registration details, its outside-in grade and its findings, never the evidence behind them. See Your public company page.
- Your signed answers go to the customer who asked, and to any customer you share them with. See Sharing your answers.
- Terry, the assistant in the console, reads the help center and a summary of your own organization's account, and changes nothing in it. See Asking Terry.
Where the commitments are
What Tiermark collects, why, where it lives, who processes it on our behalf, how long it is kept, and how to have it corrected or deleted are in the privacy notice. The terms say what Tiermark is and is not. Read those pages for the commitments themselves; this article does not restate them.
To ask what we hold about you or your company, or to have it corrected or deleted, write to help@tiermark.io. Security questions and vulnerability reports go to security@tiermark.io. Please do not probe Tiermark's systems without written authorization.
Still have a question?
Write to help@tiermark.io and a person will answer.