Skip to content
Draft. Not legal advice. Not yet in force.This text describes what the product does today and has not been reviewed by a lawyer. It names no company, registered address or contact person because none has been supplied. Items marked [To be supplied] are open decisions. Do not rely on it, and do not announce the service publicly until it has been reviewed and completed.
Draft · Data retention

Data retention

How long things are kept, and what happens when the time is up. The figures below are what the product does today. See also Privacy.

1. Paper files: 180 days after the conference ends

WhenBy default, 180 days after the conference’s last day. A conference on a paid plan keeps its files for at least 365 days. The deletion date is calculated from the conference’s current end date and plan, so moving the end date moves the deletion date.
WarningThe chairs are emailed 30 days and 7 days before, so they can export what they need.
HowDeletion is run by a platform administrator pressing a button (a dry run first, then the real run). It is not scheduled, so files may remain for a while after the date. A file is deleted only once it is at least 7 days past its due date.
What is deletedThe paper files (every version). The paper’s record is kept and shown as expired.
Cannot be undoneDeleted files are gone. There is no backup of paper files.

2. Withdrawn papers

A paper withdrawn by its author keeps its number, its place in the conference’s count, and its file until the same retention date as every other paper. [To be supplied: whether a withdrawing author may ask for earlier deletion of the file]

3. Uploads that were never submitted

A file uploaded but never attached to a submission is kept for at most one day in a holding area; the storage provider deletes it automatically, and the retention run removes any left over.

4. Everything else

The product has no automatic deletion today for the following. Each needs a decision:

  • Paper records (title, abstract, authors, keywords): [To be supplied: retention period]
  • Reviews and decisions: [To be supplied: retention period]
  • The audit trail (who did what, including every file download): [To be supplied: retention period]
  • The email log (which email was sent to whom and whether it was delivered): [To be supplied: retention period]
  • Conference applications and any identity document: [To be supplied: retention period]
  • Accounts: no self-service deletion exists; [To be supplied: closure process and what is kept after it]
  • Server logs and error reports at the hosting and monitoring providers: [To be supplied: period, from those providers’ settings]

5. What staff can and cannot see

Plansphere staff screens never show papers, reviews or decisions, and the database rules refuse staff accounts access to them. Staff can see applications (including identity documents), plans, usage totals and audit summaries. [To be supplied: policy on administrative access to the database itself]