# Store signed agreements where you can't edit them.

> Store signed agreements and clickwrap evidence only in your own database and you are the sole keeper. See what an independent, tamper-evident record adds.

Source: https://esigncomply.com/why/third-party-record

Why a third party keeps the record

You're signing people up in an app you built, and the acceptance lands in your own database. That makes you a party to the agreement and the only keeper of the evidence. Keep vibe coding the app. Let someone who is not a party keep the record.

[Get started](https://esigncomply.com/signup) · [How sealing works](https://esigncomply.com/product/evidence)

## A row in your own table is your word about your own agreement

You can change the row. So can anyone with database access, a bug, or a migration. And you cannot show that nobody did.

What you have today

### One row, written by you

public.acceptances · 1 row

One row of a home-built acceptances table, with its columns

| id | user_id | terms_version | accepted | accepted_at | ip |
| --- | --- | --- | --- | --- | --- |
| 4812 | user_7c1d | v3 | true | 2026-11-21 15:03:20+00 | 203.0.113.24 |

psql

```
update public.acceptances
set terms_version = 'v3',
    accepted_at = '2026-11-21 15:03:20+00'
where user_id = 'user_7c1d';
-- UPDATE 1
```

- The row above is either the original or the result of this statement. Nothing in the table says which.
- A teammate, a contractor, or anyone holding a service-role key can run it.
- So can a backfill, a column migration, or a restore from last week's backup.

rec_Z4m8 · sealed at signing

### One record, kept by us

- `events[]`: Every step of the ceremony as the signer's browser reported it, in order, each with Esign Comply's server time.
- `documents[]`: Version dv_3kT9 of your terms and the SHA-256 hash of its exact text.
- **intent**: The control, its exact label, the button text, its state when the page loaded, and whether a real user event changed it.
- `record_hash`: A salted SHA-256 over all of the above. Change one character and the hash changes.
- **receipt**: Our ES256 signature over that hash, the record ID and ledger entry 18244.
- **timestamp**: An RFC 3161 token from an outside authority over the same hash.
- **checkpoint**: The ledger entry sits under a signed checkpoint and a public anchor.

**You're a party to the agreement. The keeper of the record shouldn't be.**

Adding a hash column or an audit table does not change this. You compute the hash, you store it, and you can compute it again after an edit. A record kept by someone who is not a party, sealed at the moment of signing, is different in kind.

## What Esign Comply keeps for each signature

Five things for every completed signing act. Each one is held outside your database.

1. **Events from the signer's browser**

   The SDK reports each step straight from the signer's browser to Esign Comply: the documents presented, the notice, the assent and the signing act. They do not pass through your server on the way.

2. **The exact document version**

   You register each version of a document through the API. Every record pins the version by its SHA-256 hash, so the text the signer was given is fixed.

3. **A signed receipt**

   Esign Comply signs a receipt over the record hash with ES256 keys you do not hold. The receipt names the record, its hash and its place in the ledger.

4. **An outside timestamp**

   An RFC 3161 timestamp authority outside Esign Comply issues a token over the record hash. The time comes from neither your clock nor ours.

5. **A place in the ledger**

   Each record is an entry in a hash-chained, append-only ledger for your domain, covered by a signed checkpoint each minute and a public anchor each hour.

[How each step makes the record tamper-evident](https://esigncomply.com/why/immutable-record)

## What you get back

Your table stays. It gains two columns, and you gain three things you can hand to someone else.

Your migration

```
alter table public.acceptances
  add column esc_record_id text,  -- rec_Z4m8
  add column esc_receipt   text;  -- the signed receipt
```

Signed receipt

### Store it in your table

`complete()` returns the receipt in the browser, and your server gets it again when it confirms the record. Save it next to the record ID. It ties your row to the sealed record.

PDF, per record

### Evidence report

A readable account of one signature: the parties, each document with its hash, the method, the exact label and button text, our server time for every event, and the integrity details.

ZIP, verifies offline

### Evidence package

The record, the receipt, the timestamp token, the ledger proof, the exact document bytes and the public keys. Anyone you give it to runs the open-source verifier, with no account and no network.

In the browser

### Public verification page

A page where the holder of a receipt, a document or a package checks it against the seal. [Open the verification page](https://esigncomply.com/verify).

You can also have us email the signer a copy at the time of signing, and request a certificate, a dated and sealed statement about a record, for $20.

## A customer says they never agreed to the auto-renewal

A customer bought your annual plan last November. This November the renewal charge goes through. They write to support, then to their card issuer: they never agreed to auto-renew. Now someone outside your company is going to look at what you have.

`public.acceptances`

### With a row in your own table

- You export the row: a user ID, `accepted = true`, and a time from your own server.
- You attach the terms page as it reads today, or the commit you believe was live that day.
- You say nobody edited the row. You have no way to show it.
- Every item comes from you, the party that wants the charge to stand.

rec_Z4m8 · evidence report and package

### With the sealed record

- You download the evidence report. It names the exact version of the terms by hash, prints the notice, the checkbox label and the button text, and lists each event with our server time: renewal terms presented, renewal consent given, final act received.
- The record holds the renewal terms as your page showed them, and the state of the renewal consent box: unchecked when the page loaded, then changed by the signer's own click.
- You hand over the evidence package. The other side runs the open-source verifier offline and sees the record match its seal, its signature and its outside timestamp.
- Every item was kept by someone who is not a party, and none of it has changed since the minute it was sealed.

That is what the record is for. It lets you show what was presented, what the signer did, when, and that nothing changed since.

## You still vibe code the whole product

None of this takes the interface away from you. There is no hosted signing page. Your AI tool builds every screen, and the record sits behind the signing moment.

Yours

### What you build

- The signing page, the checkbox and the button.
- Upload, the PDF viewer, field placement and the signed PDF.
- Invitation emails, signer links, the dashboard, teams and billing.

[Build your own DocuSign-style app](https://esigncomply.com/build)

Ours

### What we supply

- One prompt with the rules for your flow, for the AI tool you already use.
- A headless SDK that reports the ceremony from the signer's browser.
- The sealed record and everything on this page that comes back from it.

[Generate a prompt](https://esigncomply.com/product/prompt-generator)

Start

### Seal a test record today

The Free plan includes 10 live signatures a month and a full test mode, with no card. Starter is $200 per year for2,000 live signature events.

[Read the quickstart](https://esigncomply.com/docs/quickstart) · [See pricing](https://esigncomply.com/pricing)

## More on why not to DIY the record

- The main argument

  **[Vibe code the interface, not the record](https://esigncomply.com/why)**

  What to build with your AI tool, and the two parts to hand off.

  Read it

- What goes wrong

  **[7 things AI coding tools get wrong](https://esigncomply.com/learn/vibe-coded-esignature-mistakes)**

  Pre-checked boxes, vague notices, links to terms that change, and four more, each as code with the fix.

  Read it

- How it works

  **[How the record stays tamper-evident](https://esigncomply.com/why/immutable-record)**

  Hash, chain, signature, outside timestamp, Merkle checkpoints and offline verification, step by step.

  Read it

## Questions about where to store signed agreements

### Why should a third party keep the record of a signed agreement?

Because you are a party to the agreement. A record that only you hold, in a database you can edit, is your own statement about your own deal. A record kept by someone who is not a party, sealed at the moment of signing, lets you show what was presented, what the signer did, when, and that nothing changed since.

### What does Esign Comply store for each signature?

The ceremony events reported straight from the signer's browser, the exact document version by hash, a receipt signed with ES256 keys you do not hold, an outside RFC 3161 timestamp, and an entry in a hash-chained, append-only ledger with signed checkpoints and a public anchor.

[Evidence and verification](https://esigncomply.com/product/evidence)

### Do I still keep my own acceptances table?

Yes. Keep your table and add two columns: the record ID and the signed receipt. Your app keeps reading its own table, and the receipt ties each row to the sealed record held by Esign Comply.

[Read the quickstart](https://esigncomply.com/docs/quickstart)

### What can I give someone who questions an acceptance?

The evidence report PDF for a readable account, and the evidence package for anyone who wants to check it. The package is a ZIP that verifies offline with the open-source esigncomply-verify tool, with no account and no call to Esign Comply.

[How the record stays tamper-evident](https://esigncomply.com/why/immutable-record)

### Does Esign Comply host the signing page?

No. You build every signing screen in your own app with your own AI coding tool. The headless browser SDK attaches to your checkbox and button and reports the ceremony to Esign Comply. You own the interface, and the record is kept outside it.

[Build your own signing app](https://esigncomply.com/build)

## Be a party to the agreement. Let us keep the record.

[Get started](https://esigncomply.com/signup) · [Documentation](https://esigncomply.com/docs)

Free plan: 10 live signatures a month and a full test mode. No card required.

---

Every page on esigncomply.com has a Markdown version at the same URL plus `.md` (the home page is `https://esigncomply.com/index.md`). https://esigncomply.com/llms.txt lists them.
