Last updated: 16 May 2026
These Terms describe the basic rules for using TraceProof, including the website, platform, verification pages, APIs, Protected Messaging workflows, and browser extensions such as TraceProof Protect.
Using TraceProof
- You may use TraceProof only for lawful business, operational, or verification purposes.
- You must have authority to create or manage the organisations, agents, credentials, operators, sender identities, traces, proofs, templates, and verification workflows you configure.
- You are responsible for the accuracy of the information your organisation declares through TraceProof, including company details, declared purposes, action summaries, sender identities, and protected-message context.
- You must keep account credentials, operator access, API credentials, OAuth clients, private access codes, and administrative access secure.
Protected Messaging and browser extensions
- TraceProof Protect helps approved operators add TraceProof verification to Gmail drafts and similar approved workflows.
- The extension does not send email on its own. The operator remains responsible for reviewing and sending any email from Gmail or another messaging system.
- The extension may insert a TraceProof block, public reference, and verification URL into the draft, depending on the approved profile, purpose, and template.
- For private protected messages, the operator is responsible for sharing any private access code through an appropriate separate channel.
- Organisations are responsible for ensuring that operators, sender identities, templates, and purposes are authorised and appropriate for their use case.
Verification and responsibility
- TraceProof provides verification tooling, message-fingerprint checks, integrity checks, and verification pages. It does not make the underlying business action automatically safe, valid, lawful, or approved.
- Declared interaction context is provided by the organisation that creates the trace or proof and should be reviewed accordingly.
- Recipients should independently check the TraceProof reference before trusting or acting on sensitive contact.
- No valid proof should be treated as a warning sign, but TraceProof is not a replacement for legal, financial, security, or operational judgement.
Prohibited use
- Do not use TraceProof to impersonate another organisation, mislead recipients, issue false declarations, or create verification records for unauthorised communications.
- Do not attempt to bypass access controls, abuse verification endpoints, interfere with the platform, reverse engineer restricted systems, or test production security controls without written permission.
- Do not upload, transmit, or certify content that is unlawful, harmful, infringing, or outside your authority to use.
Plans, limits, and availability
- Paid features, usage limits, subscriptions, and production access follow the plan, agreement, or subscription assigned to your organisation.
- Developer or test environments must not be presented as production verification.
- We may update, improve, suspend, or discontinue features over time, including where needed for security, reliability, compliance, or abuse prevention.
Data and privacy
Use of TraceProof is also governed by the TraceProof Privacy Policy. The extension-specific privacy page is available at TraceProof Protect Privacy.
Liability
TraceProof is provided as a verification and trust-support tool. To the maximum extent permitted by law, TraceProof is not liable for losses caused by misuse, incorrect declarations, unauthorised operators, recipient decisions, third-party messaging systems, outages outside our control, or actions taken without appropriate independent checks.
Questions
For commercial, legal, or platform questions, contact [email protected].