Overview

Truestamp keeps its support and contact channels small and public. General help goes to [email protected], and security vulnerabilities go to [email protected] under a responsible disclosure program that is also published in machine-readable form at /.well-known/security.txt. The public support page at www.truestamp.com/support gathers everything in one place: the email channels, embedded feedback, roadmap, and changelog panels, a searchable knowledge base browser, and links to self-serve resources such as the API documentation and the home-page FAQ. None of these pages require an account or sign-in.

How do I contact Truestamp support?

Email [email protected]. The support page states that the team responds within 24 hours. The same address is listed on the support page at www.truestamp.com/support, which is public and needs no sign-in. For background on the product itself before writing in, start with what Truestamp is.

Where do I send feedback, or follow the roadmap and changelog?

The support page hosts three embedded panels, each opening in a popup on the page itself so no separate account is needed:

• Feedback: suggest features, vote on ideas, and report issues. The page notes that every post is read by the team.
• Roadmap: see what is being worked on now, what is planned next, and what is under consideration.
• Changelog: recent releases and product updates, with a subscribe option to keep up with what just shipped.

Can I browse the Truestamp knowledge base?

Yes. The support page has a built-in Knowledge Base browser at www.truestamp.com/support#knowledge. It lets you search the concepts behind Truestamp, filter them by domain or tag, read a concept in place, and follow the links between related concepts (its prerequisites, related reading, and which other concepts reference the one you are viewing) to explore how everything fits together. It is the same knowledge base that answers questions in the in-app AI chat assistant, here in a browse-and-read form.

No sign-in is required, and what you can see is scoped to who you are: a signed-out visitor sees the public concepts, and signing in surfaces additional concepts written for members. Searching, filtering, and following a link all stay on the support page.

How do I report a security vulnerability?

Email [email protected]. Truestamp runs a responsible disclosure program: the security page asks reporters to send vulnerabilities to that address and commits to working with them to address issues promptly. The same contact is published two more ways so automated tooling and researchers can find it: on the support page’s “Security Issues” card, and in the machine-readable disclosure file at www.truestamp.com/.well-known/security.txt. Use the security address only for vulnerabilities; general questions belong at [email protected].

What is the security.txt file?

/.well-known/security.txt is a plain-text vulnerability disclosure file served at the standard well-known location defined by RFC 9116, so security researchers and scanners can discover the right contact without guessing. Truestamp’s file declares:

• Contact: mailto:[email protected]
• Policy: https://www.truestamp.com/security (the disclosure policy page)
• Canonical: https://www.truestamp.com/.well-known/security.txt
• Preferred-Languages: en
• Expires: a date roughly one year in the future, regenerated on every request so the file never goes stale

What does the security page cover?

The public security page at www.truestamp.com/security summarizes Truestamp’s security posture for a general audience: the cryptographic foundations (SHA-256 hashing, Ed25519 signatures with a published signing public key, Merkle trees, and tamper-evident ledger records that stay verifiable even after you redact your submitted data), data protection practices (hash-only storage, TLS in transit, revocable API keys, role-based access), infrastructure and operational security, and the transparency model in which every timestamp can be independently verified offline. It closes with the vulnerability-reporting instructions described above. For the precise statement of the cryptographic guarantees themselves, see what Truestamp proves.

Where can I find self-serve help?

Before emailing support, three public resources answer most questions:

• The Knowledge Base browser at www.truestamp.com/support#knowledge: search and read the concepts behind Truestamp and follow the links between them.
• API documentation at www.truestamp.com/api: guides for the REST and GraphQL APIs, including interactive documentation and code examples.
• The FAQ on the home page at www.truestamp.com/#faq: quick answers to the most common questions about timestamping and verification.

For checking a proof you already hold, the walkthrough in verify a proof covers the public verification page. For the terms of service, privacy policy, and other legal documents, see legal documents.

Citations

1. RFC 9116: A File Format to Aid in Security Vulnerability Disclosure. Defines the /.well-known/security.txt location and the Contact, Expires, Preferred-Languages, Canonical, and Policy fields Truestamp’s file uses.