There is no single period that is right for every contract. How long a signed record must be kept depends on the document, your business and the law that applies, so Formspring never deletes a completed record unless your workspace has set a duration for it. Ask your legal adviser what applies to you.
What is kept for how long
| Kind of record | Default | What happens |
|---|---|---|
| Draft that was never sent | 90 days after it was created | Removed, with its files. |
| Request that ended without every signature (declined, voided or expired) | 365 days after it ended | Removed. |
| Request that can still be signed | Never removed | Kept while it is open. |
| Completed record and its evidence | Kept until your workspace sets a duration | Not removed automatically until you do. |
The defaults apply until the workspace saves its own policy. The request page shows which kind of record it is, whether the workspace has set its own periods, and the date it is scheduled for deletion, if any.
Setting your periods
A workspace administrator (the signing:settings permission) sets separate durations for drafts, unfinished requests and completed records. There is no screen for this yet: set or read the periods through the API (GET and PUT /api/v1/signing/retention, token ability signing:settings), or ask Formspring support. Changing a period changes when the next sweep removes things; it does not change a record that is on hold.
Legal holds
A hold keeps one request out of every deletion until someone releases it. Only an administrator can place or release one. A hold needs a reason and a review date, and both are written to the request's history. A review date that passes only flags the hold; it never releases it. A recipient or a client cannot place a hold, so a hold cannot be used by a client to avoid deletion without review. There is no screen for holds yet: place, list and release them through the API (POST /api/v1/signing-requests/{id}/holds, GET the same path, and POST .../holds/{hold}/release, token ability signing:settings), or ask Formspring support.
What deletion does and does not do
- A purge removes the request, its recipients and with them every link and verification code, its history and its stored files. What was removed is noted in an audit record that holds no document content.
- Completed content is never edited in the name of erasure. If a request to erase personal data conflicts with a retention duty, the record is kept under the hold or the policy and the outcome is reported to the person asking, plainly.
- Erasing a contact unlinks the contact from the recipient and does not delete the signed record.
- Deleting a response does not delete a signed request made from it. The signed request stays available by its own reference until its own retention date.
- Backups follow their own expiry. A record removed on schedule can remain in a backup until that backup expires.
- A recipient can download their copy before a scheduled deletion. A copy somebody already downloaded cannot be recalled.
Records you hold stay downloadable if you move to a plan without signing, until their retention date.
