For compliance officers
Know which version applies, and who has signed it.
Every legal document keeps a public history with clear effective dates. Every customer DPA shows its version, its signer and its status, and nothing is published without a person's approval.
- v3.1Draft
- v3.0Current
- v2.1Historical
Changes from v2.1 to v3.0, section 7.2
The Processor shall notify the Controller of a Personal Data Breach without undue delay and in any event within 72 48 hours of becoming aware of it, and shall provide the information listed in Annex III.
Control what is in force
Publishing a document and making it effective are separate decisions. Customers always see which version applies today.
- Publication and effective datesPublish v4.3 today and make it effective on 1 November. Until then, v4.2 stays marked as current.
- Text comparison between versionsAdditions and removals are highlighted in the text. If text can't be read from an uploaded PDF, the comparison says so instead of showing no changes.
- Every version stays publicAnyone can read and download any published version as a PDF, without an account.
- A person approvesEach trust center decides whether administrators may approve their own drafts. Automated uploads can never approve or publish.
Self-approval is off for this trust center. Another administrator must approve.
| Approved by | Sam Rivera |
|---|---|
| Published | 16 Oct 2026 |
| Effective | 1 Nov 2026 Upcoming |
| Notify subscribers | Yes |
The right person signs, and the record shows it
Your customer's legal team manages the agreement. The person with authority signs it. Those can be different people.
- Legal administrators prepareThey prefill the organization's details and choose who signs, or sign themselves.
- Signers check and acceptThe signer can correct any field, reviews the regenerated agreement, and explicitly accepts both the terms and their authority to sign.
- Evidence you can retrieveThe signed PDF is kept with the submitted values, template version, acceptance wording, verified email and timestamps.
Signed PDFs are designed to carry a platform seal and a trusted timestamp. These are not a personal certificate signature by the signer.
- Started a DPA v3.0 workflow
- Prefilled company details
- Chose Jamie Chen as signer
- Changed the registered address
- Reviewed the updated preview
- Accepted 20 Oct 2026, 14:12 UTC
Signed DPA v3.0 is now current. The v2.1 copy signed in March remains on file.
Re-signing with deadlines everyone can see
When a new DPA version needs fresh signatures, mark it as mandatory and set a deadline. Each customer's status is visible to your team and theirs.
| Customer | Product | Status | Deadline |
|---|---|---|---|
| Northstar Studio Ltd. | SecureMailMerge | Current v3.0 | Signed 20 Oct |
| Lakeside Analytics GmbH | SecureMailMerge | Pending re-signing | 15 Dec 2026 |
| Fernwood Clinics Ltd. | MailMerge Insights | Overdue | 30 Sep 2026 |
| Harbor & Pine LLP | SecureMailMerge | Archived | None |
- Required notices are separateCustomer legal administrators receive the re-signing notice even if they never subscribed to document updates.
- Reminders to both sidesPending signatures remind the signer and the legal administrators on a schedule you can turn off.
- One live workflow at a timeStarting a new workflow disables earlier signing links for that customer. Their history is kept.
Overdue is a status, not a cancellation. After the deadline, the previously signed agreement stays on file and visible. What you do next is your decision.
Compliance questions
Does SimpleTrustCenter make us GDPR compliant?
No tool can do that on its own. SimpleTrustCenter publishes your documents, tracks versions and collects signatures. The content of your agreements and how you meet your obligations remain your responsibility.
What kind of electronic signature is this?
The signer verifies their email, reviews the completed agreement and explicitly accepts. The final PDF is designed to carry a platform seal and trusted timestamp. It is not a qualified signature made with the signer's own certificate.
What happens to earlier signed copies?
Each customer has one current signed DPA per product. When they sign a new version, it replaces the current one and every earlier signed copy stays in the history.
Can a customer opt out of re-signing notices?
No. Optional document updates and required signing notices are separate. Unsubscribing from updates does not stop a required notice.
What if we archive a customer?
Their access to that trust center is closed and new signing is blocked, but their signed agreements and history are kept.
Walk through a re-signing cycle
We will show you a mandatory replacement from publication to the new signature.