This notice applies whenever you arrive at a SpitShake signing page through an identity-bound link — one that includes a signed handoff token from the sending organization after they have verified your identity through a third-party identity verification service (for example, Stripe Identity).Documentation Index
Fetch the complete documentation index at: https://docs.spitshake.io/llms.txt
Use this file to discover all available pages before exploring further.
SpitShake’s role
SpitShake is an execution engine, not an identity provider. The organization that sent you here — the tenant whose brand appears at the top of this page — is solely responsible for determining who you are and for the accuracy of any identity attributes they show you during signing, including the “verified name” that will be applied to signature and initial fields on your behalf.What we received, and what we did not
Where this session was initiated after an identity check performed by a third-party verifier such as Stripe Identity, SpitShake received only a cryptographically signed handoff token asserting that a verification occurred. We did not inspect your government-issued ID. We did not capture biometric data from you. We did not independently confirm your identity. We verify three things about the handoff token: that it is authentically signed by the sending organization’s key, that it has not expired, and that it is addressed to this session. We then bind it — together with the document hash and a trusted timestamp from an RFC 3161 time-stamping authority — into this signature’s tamper-evident audit record. We do not warrant the correctness of the underlying identity claim. That remains the representation of the sending organization and the identity verifier they chose.Disputes about identity verification
If you believe a third-party identity verifier (such as Stripe Identity) returned incorrect information about you, please contact that verifier directly under their own terms of service. The sending organization may also be able to help resolve the issue since they are the verifier’s direct customer. For disputes about how SpitShake handled the handoff token itself — for example, if you believe a token was accepted after expiration or without a valid signature — contact us at security@spitshake.io.Service provided by IVERIFI, LLC d/b/a SpitShake (a Connecticut limited liability company wholly owned by ADS CORP). Last updated: 2026-04-19.