The commitments we will put in writing.
Including the unflattering ones.
You are about to hand a vendor marketing material your firm has not published yet. Before you do, you should know what the service is permitted to do with it, who may process it, where the firm's authority remains, and which diligence requirements the company cannot currently satisfy. The commitments below are bounded by our Terms and Privacy Policy. Where those documents preserve operational or legal discretion—retention included—we say that rather than invent a cleaner promise for this page.
Seven boundaries a buyer should test against our public terms.
A trust page that only lists reassurance is still a marketing page. The boundaries below are drawn from our Terms and Privacy Policy, which control where this summary and those documents differ. Product behavior and security posture still belong in diligence; a public paragraph is not a substitute for current documentation.
Current certification posture, stated without implication.
TIMEWrit does not currently hold SOC 2 Type II or ISO 27001. If either is mandatory before a vendor can process firm content, do not seek an exception on the strength of this page. Ask for current documentation and compare it with your firm’s diligence standard before submitting content.
Certification language should be documentary, not decorative. This page does not ask you to infer a control environment from design language or a logo. Ask for the current security posture and subprocessor list; measure the answer against your own vendor requirements before content is submitted.
Ask us directly for our current security posture and subprocessor list
A conflict worth weighing.
TIMEWrit is built by a small team with a commercial interest in serving firms that want to publish more of their best thinking. That incentive should never decide whether a piece is acceptable. Our public terms place reviewing, approving, revising, publishing, retaining, and supervising content with the firm. You should weigh our commercial incentive against that written boundary when you read anything on this site, including this sentence.
We are also early. A firm buying from an early company accepts a different risk profile from one buying from an established vendor. Evaluate the product against the workup, contractual limits, current support model, and diligence evidence available now—not against a maturity we have not earned.
Diligence questions are welcome before an application.
If something on this page would fail your review, we would rather hear it now than after your committee has spent a cycle on it.