Features

What PiloSuite Does, in Detail

One workspace per company, with everything that belongs to data protection documentation. Every object has an owner, a dated state and, wherever there is a deadline, a reminder before it. This page describes what is in the application today – nothing that is merely planned.

1. Profile and Requirements

It starts with questions about the company: country, size, sector, what is processed, whether employees, customers, patients or applicants are affected, whether vendors are used, whether a website, a newsletter or video surveillance is part of it. From the answers PiloSuite computes, with the rule pack for Germany or Austria, what typically applies.

  • Every result names its reason and its legal reference. Not “you must”, but “based on your answers, the following typically applies … (Art. 30 GDPR)”.
  • Required and recommended are kept apart. The overview shows both, but not in one pot.
  • What does not apply is stated explicitly. “Based on your answers you do not need a data protection officer, because …” is worth more to a small company than another requirement – and is exactly what it would otherwise pay an adviser to establish.
  • Four ways forward per requirement: upload an existing document, start a draft by Pilo, mark the requirement as not applicable with a reason, or defer it with a date. “Not applicable, because we do not run a newsletter” is documentation, not a gap.
  • The plan for the first thirty days. The requirements as a short plan by risk and dependency instead of a list of forty items. Progress is shown against the plan; the full list stays one click away.
  • Impact assessment screening with result and justification.

2. Bringing in What You Have

The strongest first impression is your own material, suddenly organised. You upload a folder, individual files or an exported Confluence space – Word, PDF, Excel, text, images. PiloSuite recognises what a document is, reads out date and author, maps it to the matching requirement, flags duplicates and anything untouched for more than a year.

Whatever comes in gets the state Imported – needs review. The provenance stays visible on every document: where it came from, when, uploaded by whom.

3. The Registers

Processing activities
The record in the controller's and the processor's view, with a completeness indicator per entry and links to vendors, measures, documents and retention rules. Around 30 templates for typical activities as a starting point.
Vendors
Who processes on your behalf, with the status of the processor agreement and, for seats outside the EU, the safeguard for the transfer. The roughly 50 most common tools are prepared.
Technical and organisational measures
Around 60 measures with status and evidence upload. What is implemented, what is not, what does not apply – with a date.
Retention rules
Retention tables for Germany and Austria, assigned to the processing activities.
People
Who holds which role in the documentation, what each person is responsible for, and what has to be reassigned when someone leaves.

4. Documents, Responsibility, Approval

Every document passes through states: draft, in review, approved, due for re-review, withdrawn. Every version has a date, an author and a provenance. An approved version is never changed again; the next one is a new version.

  • Responsibility on every object: an owner is mandatory; a deputy, a reviewer and an approver are optional. When someone leaves, everything that person owns has to be reassigned before the leaver flow can close.
  • Approval through a link. The reviewer – your external data protection officer, say – needs no account. They receive a link, see the documents to review in one place, comment, approve or reject, and receive the approved PDF by e-mail. How many approvals a document needs is set by the company.
  • Skeletons for the usual documents: website privacy notice, notices for customers and for employees, processor agreement, confidentiality commitment (in Austria with the data secrecy duty under § 6 DSG), internal policy. Skeletons, not reviewed legal texts: review and approval rest with your adviser.
  • No word processor. Writing happens in Word. The new version is uploaded and goes through review like any other.

5. Periodic Review

The reason PiloSuite exists. Every document, every register and the contacts area too has a review cycle – annual, for instance. On top come triggers on change: a new vendor, a new processing activity, a change of data protection officer.

  • A reminder before the deadline to the owner, escalation when nothing happens.
  • Confirmation “reviewed, still valid” or a new version – both with date and name.
  • The review history per object, visible at any time and included in the evidence.
  • Tasks, reminders and a notification centre in the application; e-mails contain no content, only the note that something is waiting.

6. Incidents and Data Subject Requests

Data Breaches

A form filled in within two minutes; the 72-hour clock starts with the moment of discovery. A checklist for the first hours, escalation to the designated people, skeletons for the notification to the authority and the information to those affected, an entry in the incident register – even when no notification turned out to be necessary.

Data Subject Requests

Access, rectification, erasure, objection: recorded with receipt and deadline, with a reference instead of the person's name. Skeletons for the response, a reminder before the month runs out, an entry in the request register. The search in your own systems stays with you – PiloSuite does not have them.

The descriptions of incidents and requests are stored encrypted field by field with the application key; they are the most sensitive free text in the system.

7. Data Intake and Deletion Dates

A problem every company has and almost none has under control: an employee receives a file with personal data for a specific, temporary purpose – the Excel export to test an import, the customer list for a migration, the application documents. The file lands in Downloads, gets copied into a project, stays as an attachment in the mailbox, and stays.

  • Only the fact that the file exists is recorded – purpose, origin, locations, owner – never its content.
  • A proposed deletion date for every purpose; extended only with a reason and a new date.
  • Deleted by checklist across every declared location, with confirmation; overdue deletions sit on the dashboard next to the other open items.
  • Pilo creates an entry from a pasted e-mail: sender, purpose, attachment, proposed deletion.

8. Contacts and Emergency Card

The data protection officer with every channel, deputy, appointment, publication and notification to the authority; management, IT, vendors, lawyer, insurer; the supervisory authority assigned by seat. Plus the check whether a data protection officer has to be appointed at all – with the reason.

From these records the emergency card is generated: one page for the first hour after a suspected data breach. Whom to call in which order, with numbers; what not to do. Generated, not written: when a contact changes, the card changes, and a generation date makes the old copy on the wall recognisable as outdated. A QR code opens the incident report directly on a phone.

9. Website and Cookies

This is about your website. A questionnaire records what it does – hosting, contact form, newsletter, analytics, embedded content, shop, payment, chat. From that comes the draft of the matching sections of your privacy notice, which your adviser reviews and approves like any other document. As evidence, the consent tool in use, the contract with it, a screenshot of its settings and the date of the last check are recorded – with their own review cycle.

What PiloSuite does not do: scan your website, show a banner, manage consent. It documents what you have set up.

10. Evidence, Audit Mode, Read-only Link

  • Audit mode: the approved state at a glance – registers, documents, approvals with names and dates, review history, incident and request registers, open items with their reasons, the rule-pack version in force. As a structured PDF with a table of contents and as a ZIP of the files, with a generation timestamp.
  • Read-only link: the same evidence for an auditor, an authority or a client asking a due-diligence question. Time-limited, revocable at any time, scoped to what you select – everything, or only registers and approvals without incident detail. Every access is logged; all issued links appear in a list with their last access.
  • Immutable approvals and a chained log: what was approved stays as it was; the audit log is chained so that a later change to an entry stands out.

11. Exports and Hand-over Package

Documents as PDF and DOCX, registers as XLSX, the deletion log – at any time. And the hand-over package as one ZIP: every approved document as PDF with name and date, every register as Excel, the approval and review history as a report, a JSON file for machines, an index. Included in every tier, available at once and for 30 days after a cancellation. Then the workspace's database is deleted and the deletion confirmed by e-mail.

12. Pilo, the Assistant

Pilo is switched on per workspace, deliberately. He helps where reading and sorting cost time:

  • Recognising imported material and mapping it to the requirements.
  • Writing first drafts from the profile and the skeleton – always marked Draft – not reviewed, in the export too. A draft never enters the evidence before a person has reviewed and approved it.
  • Explaining why a requirement applies to this company – with the reference.
  • Preparing a review: what has changed since the last version, what the reviewer should look at.
  • Creating an intake record from a pasted e-mail; answering questions about the state of the workspace.

Pilo receives only what the published rule allows for the task at hand. Names the application knows are replaced by codes before sending, e-mail addresses and phone numbers removed; data subject requests are never sent. The model runs on Amazon Bedrock inside the European Union and does not train on your inputs. Every workspace has a monthly allowance; once it is used up, Pilo pauses until next month and everything else keeps running. Text generated by Pilo carries a machine-readable marking in documents, as Art. 50 of the AI Act requires.

Pilo speaks in the first person only when addressed as the assistant. A deadline is a deadline of the application, not an opinion of Pilo's.

13. Accounts, Roles, Languages

Roles
Owner, administrator, editor, contributor, viewer and guest reviewer. Privileged roles sign in with a second factor.
Workspaces
One workspace per company with its own database; up to three in the Business tier.
Languages
Interface in German and English, switchable per person.
Countries
Rule packs for Germany and Austria, with references to the GDPR, the BDSG and the DSG.
Billing
Annual invoice from Austria, reverse charge for German companies with a VAT ID, reminder 60 days before expiry; payment status visible on the account.
Help from the provider
The provider sees your workspace only when you grant access for a limited time – read-only, with a banner and an end time, logged.

What is missing from this page does not exist yet. An “as of date” reconstruction in audit mode, tracking of staff instruction, client portfolios for advisory firms and Switzerland are on the plan, but not in the application. We write nothing in the present tense that is still to come.

View the Demo Request a Trial