Help & Support

Pactbound creates tamper-evident evidence bundles for professional handoffs: client transitions, credential transfers, vendor offboardings, and any situation where you need a clear, unambiguous record that both parties agreed to. Every handoff is cryptographically sealed and anchored to the Hedera Consensus Service (a public ledger) so the record exists independently of Pactbound. Even if Pactbound ceased to exist, your evidence bundles would remain verifiable.

1. Click New Handoff from your dashboard and choose a template (or start from scratch).
2. Add your recipient's email address. They do not need a Pactbound account to receive or acknowledge a handoff.
3. Attach files, documents, or screenshots: anything you want included in the evidence record. Each file is SHA-256 hashed on your device before upload.
4. Add any known issues or disclosures. This step protects you: it creates a record that the recipient was informed of existing problems before taking over.
5. Optionally add credentials. These are encrypted on your device before being stored. The recipient reveals them using a view-limited link.
6. Review and send. The recipient gets an email with a link to review, acknowledge, and sign off. Once they do, the entire bundle is anchored on-chain.

No. Recipients receive a secure link by email. They can review files, read disclosures, reveal credentials (within the view limit), and submit their acknowledgment without creating an account. If they want to send their own handoffs in the future, they can sign up: but it's never required to receive one.

Yes. You can add multiple recipients with different roles: primary recipient, CC, or witness. Each recipient receives their own email notification. All acknowledgments are recorded independently in the audit trail.

No: and this is by design. Once a handoff is sent, its contents are sealed. Any modification would invalidate the cryptographic hash and break the evidence chain. If circumstances change, you can create an amendment: a new handoff that references and supersedes the original: or revoke the original and create a replacement. Both actions are recorded in the audit trail.

A disclosure is a formal record of a known issue you're informing the recipient about before they take over. For example: a server that needs a license renewal, a firewall with a known configuration issue, or a client with unpaid invoices. Disclosures protect you: they create an immutable record that the recipient was informed. If a dispute arises later, "you never told me about that" is not a viable argument when the disclosure is timestamped and on-chain.

Setting an expiration date means the handoff must be acknowledged before that date, or it expires automatically. Expired handoffs are no longer actionable but their records remain intact. This is useful when a transition has a hard deadline: for example, a contract end date.

Yes, if the handoff has not yet been acknowledged. Revocation is recorded in the audit trail and on-chain: it does not erase the record, it adds to it. The recipient will no longer be able to acknowledge a revoked handoff. Use revocation when circumstances change and the original handoff is no longer accurate.

Each credential has a maximum number of times it can be revealed: you set this when creating the handoff (1, 2, 3, 5, or 10 views). Once the limit is reached, the credential value is permanently destroyed and cannot be recovered by anyone, including Pactbound support. This ensures that credentials are not left indefinitely accessible after the handoff is complete.

Before sending, Pactbound checks your credential passwords against the Have I Been Pwned database: a public registry of credentials exposed in known data breaches. This check uses a k-anonymity model: only the first 5 characters of a SHA-1 hash of the password are sent to the API. The actual password never leaves your device. If a breach is found, the credential is flagged so the recipient knows to rotate it immediately.

TOTP (Time-based One-Time Password) is the seed used by authenticator apps like Google Authenticator or Authy to generate 2FA codes. Including the TOTP seed in a credential transfer means the recipient can immediately set up 2FA on their authenticator app without needing to go through an account recovery process. The TOTP seed is stored with the same encryption as the password: it is never stored or transmitted in plaintext.

A topic ID (formatted as 0.0.xxxxxxx) is the address on the Hedera Consensus Service where Pactbound's on-chain records are stored. Each organization has its own topic. Every completed handoff results in a message being submitted to that topic containing the bundle hash and a timestamp. You can view all messages on a topic publicly using HashScan.

Yes. You can cancel your subscription at any time from Settings → Billing. Your plan remains active until the end of the current billing period. After that, your account moves to the free tier: your existing handoffs and evidence bundles remain accessible and verifiable.

Canceling doesn't delete anything — see the question above. Your account moves to the free tier and your handoffs, evidence bundles, and audit trail stay accessible and independently verifiable. If you want the account itself deleted, that's a separate step from Settings → Organization: accounts with no completed handoffs are deleted immediately, and accounts with completed handoffs can't be self-service deleted because those evidence records are retained permanently — email support@pactbound.com to discuss closure options. On-chain records on the Hedera ledger are permanent regardless: they cannot be deleted and remain independently verifiable forever.

All fees are non-refundable except where required by applicable law. If you believe you were charged in error, contact support@pactbound.com within 14 days and we will review the situation.

Pactbound uses passwordless magic link authentication: there is no password to lose. Go to the sign-in page, enter your email address, and click the link in the email you receive. If you no longer have access to that email address, contact support@pactbound.com with proof of account ownership.

No. Credential values are encrypted on your device before upload using a split-key scheme. Pactbound holds one half of the encryption key; the other half is only accessible through the recipient's acknowledgment flow. Neither half alone can decrypt the credential. Handoff file content is encrypted at rest. Pactbound support can view metadata (handoff titles, statuses, timestamps) for account support purposes, but cannot read file contents or credential values.