When the customer says "I never approved that"
This is the expensive argument in print: ten thousand labels are already run, and the customer says "that was not the colour", "that was not the quantity", "I never saw this". What actually happened is lost in the WhatsApp history; the email thread is scattered. Making that moment provable is the reason BaskıGATE exists.
Four layers
Each layer closes the gap the one before it leaves open.
1 · The approval certificate
On one page: the artwork exactly as it was put forward for approval, the complete order details, each decision item by item, the name of the person who approved, the time and the IP address — and the exact warning text that was on screen at the moment of approval. "I never saw that warning" is not available.
2 · The copy in the customer’s own inbox
The moment they approve, a summary of the decision and the file fingerprints land in their own inbox. The same record therefore sits in the other side’s archive too — not tied to your server.
3 · A tamper-evident record chain
Every event carries the hash of the one before it, and its own hash is computed from its own fields. Changing the contents of a row breaks its hash; slipping a row in between breaks the chain. Either one becomes visible.
4 · The chain tip, held off-site
The tip of the chain is copied off the server every day: to the owner’s inbox and to a backup store at a provider other than your host. That the records existed on that date is then written down in places you cannot change.
What gets presented to the court
- Print the approval certificate. One click from the job page, saved as a PDF. Readable, intelligible, one page.
- Download the record export. The job’s entire event chain, the hash algorithm, and which fields were used in which order to compute it, are all written inside the JSON file.
- Hand over the verifier with it. A single-file, independent script. It runs without connecting to BaskıGATE, to us, or to the internet; it computes the integrity of the records on its own.
- Show the external copies. The daily digest of the chain tip sits, with its date, in the owner’s inbox and in the off-site store. If you use qualified timestamping, the tokens verify with standard tools as well.
Where the limit is
Article 199 of the Turkish Code of Civil Procedure treats electronic data as a document; it is submitted to the court and the judge weighs it freely. But this record is not a deed: under the second paragraph of Article 205, a secure electronic signature is required for it to have the force of a deed.
So what you are holding is strong evidence that the other side remains free to rebut. Copying the chain tip off-site every day answers much of the "you keep the records yourself, you could have written them later" objection; those copies cost nothing to run and are on by default.
One step beyond that is timestamping: a certificate authority signs the tip of the chain. The timestamping servers of international authorities (DigiCert, Sectigo) are free and the system supports them. The strongest footing under Turkish law is a qualified timestamp from a licensed provider under Law no. 5070; that one is paid. The protocol is the same, so moving between them is a single settings change.
Overstating this would not help you. Your contracts and your evidence strategy need to be discussed with your lawyer; this page is not legal advice.
Put your approvals on the record
BaskıGATE is being developed together with pilot print shops. Pilot shops use the product free of charge, set their own priorities directly, and steer what gets built next.