Prompt
Should I store signed documents and audit logs in my system?
Latest observation
Nov 11, 2026
OpenAI APIWeb search: off
Yes — if your system handles contracts, approvals, regulated workflows, or any action that needs non-repudiation or traceability, you should store both:
1) Signed documents
Store the final signed version of the document, along with:
- signer identity
- signature timestamp
- signature method
- document/version hash
- certificate or verification data if applicable
This helps prove what was signed and when.
2) Audit logs
Store audit events for important actions such as:
- document creation/update
- viewing/downloading sensitive documents
- signing/declining
- permission changes
- login/logout and admin actions
Audit logs are useful for:
- compliance
- troubleshooting
- security investigations
- proving process integrity
Good practice
- Keep signed docs and audit logs immutable or append-only
- Restrict access tightly
- Encrypt sensitive data at rest and in transit
- Use retention policies based on legal/regulatory needs
- Separate audit logs from application logs
Important note
If you’re dealing with legal signatures, the exact storage requirements may depend on your jurisdiction and compliance regime, so you may want legal/security review.
If you want, I can also suggest a minimal data model for storing signed documents and audit trails.