Audit trail
An append-only, timestamped record of every event in a contract's lifecycle: creation, sharing, opening, field filling, signing. Akitle stores this as a document under HMK art. 199.
An audit trail is an append-only, timestamped recording of every event from a contract's creation through signing and archiving. In Akitle, every contract maintains a record of: creation, sending to parties, the renter opening the link, field filling, signing, PDF sealing.
Each record carries metadata: event type, event time (UTC), the IP address from which the event occurred, browser information (User-Agent), and user identity. These records are not stored in a blockchain or Merkle tree, but in an immutable (append-only) data structure — they cannot be added after the fact or deleted.
From an evidentiary standpoint, the audit trail strengthens the contract's status as a 'document' under HMK art. 199. If a counterparty claims 'I never opened this contract', 'I never signed', or 'I wasn't aware of the terms' in a dispute, the audit trail provides technical data refuting that claim. When and from which device the contract was opened and signed is shown by concrete record.
Once signed, Akitle computes and stores the PDF's cryptographic hash (SHA-256). This hash lets a court technically verify whether the file was tampered with afterward. Audit-trail data is retained for 10 years under TBK art. 146.
Other names
Audit log · Activity log · Olay günlüğü
Related resources
Send your first contract today
Opening an account is free. An example template is ready — no need to wait for your own document to try it.