SwiftlyDPC replaces the spreadsheet of processing activities, the Word templates and the calendar of deadlines that many DPOs keep for each client, with one place per client where the law sits behind every field.
Before: A spreadsheet for each client, with columns of your own
In SwiftlyDPC: Entries made from one template, with an export
Before: Copied by hand from the PDFs
In SwiftlyDPC: Read from the Legal Claims Register by claim ID, with the label and version
Before: A calendar, or memory
In SwiftlyDPC: Counted from the records: licence renewal, DPO notices, reviews and rights requests, with email reminders
Before: Hours counted by hand
In SwiftlyDPC: Clocks that start when the breach is logged, and Form DP3 drafted from the case
Before: Typed into Word
In SwiftlyDPC: Forms DP1, DP2 and DP3 made from the records as PDFs; a person sends them, and the copy is kept
Before: A folder for each
In SwiftlyDPC: One workspace for each, opened from one switcher, walled off from the others
Before: Files gathered from folders
In SwiftlyDPC: The finished file in one download, with an index
Before: Track changes, if it was on
In SwiftlyDPC: A sealed activity log
SwiftlyDPC is an implementation aid, not legal advice. It labels what needs legal verification.
Policies and notices are kept as files, with versions and review dates.
Moving a client's file from spreadsheets and Word templates into SwiftlyDPC.
Still have a question?
Ask us, and a person at Intetrix answers.
Not yet. Entries are made from SwiftlyDPC's templates. Talk to us if you have many to bring, and we will help you set up.
Yes. Keep policies and notices as Word or PDF files in each client's documents, with versions and review dates.
Each client gets its own workspace, opened from one switcher. A client's records are walled off from every other client's.
Still have a question?
Ask us, and a person at Intetrix answers.