Skip to content

Who opened your data?Now there’s a witness.

Every time a company touches your data, Saksi seals a fingerprint of that record on a public chain. Your phone can check it, so nobody, not even an insider, can quietly rewrite the story.

  • Hash only on chain
  • No wallet for citizens
  • Fingerprint 0x3fa2c41b…09e19c1d

The problem

Your access log lives in the company’s own database. Any insider can edit a row. You would never know.

Access log · Contoh Lending Co.DB only
21 NOV 09:12 · R.0408
READ · OPS-12
21 NOV 10:47 · R.0409
UPDATE · OPS-03
21 NOV 11:30 · R.0410
READ · CS-07
21 NOV 13:58 · R.0411
EXPORT · RISK-02
21 NOV 14:03 · R.0412
OPENED YOUR FILE
WHO
Contoh Lending Co.
DID
READ
WHY
Debt collection
BASIS
Legitimate interest
FINGERPRINT
none · database only

WASSHARED WITH THIRD PARTY

Nobody but the insider saw that.

  1. RECORD: A company opens your file. It has to write down who opened it, what they did and why.
  2. SEAL: Only a fingerprint goes on chain. Your data stays on their server. The chain gets a hash, sealed by the company’s registered wallet.
  3. VERIFY: Your phone recomputes it. Same fingerprint as the chain. Match. Checked in your browser, not on our server.
  4. EDIT: An insider rewrites the log. One field, quietly, straight in the database. Nobody touches the chain.
  5. ALTERED: Your phone flags it. The chain still holds the original fingerprint. The edited record no longer matches it.

One record. One fingerprint. Checked by you.

A company opens your file.

It has to write down who opened it, what they did and why.

  • WHOContoh Lending Co.
  • DIDSHARED WITH THIRD PARTY
  • WHYDebt collection

Only a fingerprint goes on chain.

Your data stays on their server. The chain gets a hash, sealed by the company’s registered wallet.

  • FINGERPRINT0x3fa2…9c1d
  • BLOCK#7,123,242
  • SEALED21 Nov 14:03 WIB

Your phone recomputes it.

Same fingerprint as the chain. Match. Checked in your browser, not on our server.

  • VERIFIEDBy your phone
  • MATCH1.8 S

Edit the database. The chain remembers.

An insider rewrites the log.

One field, quietly, straight in the database. Nobody touches the chain.

    Database says
    WHOContoh Lending Co.
    DIDSHARED WITH THIRD PARTY
    WHYDebt collection
    BASISLegitimate interest
    Chain sealed
    WHOContoh Lending Co.
    DIDSHARED WITH THIRD PARTY
    WHYDebt collection
    BASISLegitimate interest
    MatchAltered · 1 field changed after sealing

    Your phone flags it.

    The chain still holds the original fingerprint. The edited record no longer matches it.

    • ALTEREDDID changed
    • SEALED0x3fa2…9c1d
    • NOW0x7be0…41a6

    A breach starts a clock. The chain keeps the time.

    UU PDP Art. 46 gives a company 72 hours to report a breach. The notice is sealed with its own block time, and the contract compares it with the declared discovery time.

    Left of the 72-hour windowExample notice · synthetic data

    On timeSealed at 53.5 H of 72 H · 18.5 H to spare · computed by the contract

    Don’t trust us. Check it yourself.

    Paste a fingerprint or a transaction, or scan a receipt QR. Your browser reads the chain from a public node and recomputes the fingerprint itself. Switch the node, read the raw log, open it on the block explorer.

    0x3fa2c41b7e0d…5b1e09e19c1d

    Match

    This record matches the chain.

    1.8s

    Verified by your phone · not by our server

    Saksi proves

    • The record has not been changed since it was sealed.
    • When the chain received it: the chain clock, not the company’s.
    • Which registered company wallet sealed it.
    • Whether a breach notice was sealed inside 72 hours.

    Saksi does not prove

    • That every access was recorded, only the ones logged.
    • That the access was lawful or the stated reason is true.
    • The real discovery time of a breach.
    • That notifications were actually sent to people.
    • Three people. A company (the controller) records each access from its registered wallet. A citizen gets a receipt and checks it on their phone. A regulator sees on-time or late breach notices and altered rows, without asking the company for access.

    • Checking is reading, and reading a public chain is free. Your phone asks a public RPC node and recomputes the fingerprint itself. Only the company signs, because only the company makes claims.

    • A normal log lives in the company’s own database, so whoever can write to it can rewrite it. Saksi seals a fingerprint of each entry on a public chain the moment it is written. If someone changes the row later, the fingerprint no longer matches.

    • It does not prove that the access was lawful, that the stated reason is true, or that every access was recorded. It proves three things: the record has not changed since it was sealed, when it was sealed, and which registered wallet sealed it.

    • A fingerprint of the record and a keyed pseudonym (HMAC) in place of your identity, plus a salted hash of the purpose, the access type, the legal-basis code and the time. No names, no ID numbers, no record contents. The readable details stay on the company’s server.

    • The company (the controller) signs every record in its own wallet, so it pays the gas: one small transaction per access. Saksi’s server never holds a key and pays nothing. The demo runs on the Sepolia testnet, where gas costs no real money. Batching many records into one transaction (Merkle) and moving to an L2 are on the roadmap, not built.

    • Then there is no receipt, and Saksi cannot invent one. We state that limit openly. What Saksi does is make recorded history impossible to quietly rewrite, and make a breach notice that never arrives show up as late.

    • The breach notice is sealed with its own block time. The contract compares that time with the declared discovery time. On time or late is computed by code, not claimed in a PDF.

    • This is a hackathon demo with synthetic data only. A public testnet gives judges real, checkable transactions without anyone spending real money. The contracts and the in-browser verifier are ordinary EVM code; moving to mainnet or an L2 is a roadmap step we have not taken.

    • It explains a receipt in plain language and drafts the Art. 46 breach notice. It never decides. MATCH, ALTERED, on time and late are always computed by code and the contract, and every AI output is labelled with its model.