Know the current protection boundary before you test.
This notice describes the Founding Tester security posture without claiming controls that have not been deployed and verified.
1. Transport and access
TERA Signature is deployed over HTTPS. Founding Tester and administrative workflows use controlled access mechanisms, including private tester links and short-lived administrative verification codes. Users remain responsible for protecting their own devices, email accounts, access links, codes, and downloaded copies.
2. Workflow evidence
The service records evidence needed to operate and inspect the signing workflow, which may include document fingerprints, participant roles, invitations, access events, signing actions, timestamps, completion state, evidence seals, request identifiers, and tester-program telemetry. Evidence of a workflow is not a blanket guarantee of legal validity, civil identity, or authorization.
3. Hosting and infrastructure boundary
TERA Signature currently relies on third-party infrastructure providers for portions of hosting, email, storage, networking, or service operation. Those providers may process information as necessary to provide infrastructure services, subject to their applicable controls and TeraSystemsAI’s service configuration.
Current limitation: the Founding Tester service does not claim that documents are protected by provider-resistant end-to-end encryption or confidential-computing isolation. Do not assume that possession of the hosting infrastructure is cryptographically insufficient to access all service data unless TeraSystemsAI explicitly states that a stronger architecture has been deployed and verified.
4. Data minimization and AI use
TeraSystemsAI’s corporate Privacy Policy states that it collects information reasonably needed to operate the business, deliver services, protect systems, and meet legal obligations; that it does not sell personal information; and that confidential customer content is not used to train general-purpose AI models unless expressly authorized in writing. The Founding Tester program is governed by that policy.
5. Retention and deletion
Tester records, workflow evidence, operational logs, and documents may have different retention needs. Deletion requests are evaluated under the Privacy Policy and any applicable agreement. Some records may need to be retained for security, evidence integrity, contractual, tax, dispute-resolution, or legal reasons.
6. Security development direction
TeraSystemsAI is continuing to strengthen document confidentiality, key management, access boundaries, monitoring, and provider-resistance. Future controls are not represented as active until deployed and verified.
7. Security reporting
If you identify a suspected vulnerability or security incident, do not exploit it or access data that is not yours. Report it responsibly to security@terasystems.ai. Suspected impersonation or fraud may be reported to admin@terasystems.ai.
8. Related documents
TeraSystemsAI Privacy Policy · TeraSystemsAI Terms of Use · TERA Signature Founding Tester Terms & Disclosure