devguard: Your Compliance Platform
PlatformSolutionsFrameworksDevelopersPricing
Sign inStart for free
devguard

One workspace for your whole ISMS: Swiss-hosted, one control set, mapped to every framework you run.

All systems operational
Product
PlatformFeaturesSolutionsFrameworksPricing
Developers
API & CLIIntegrationsDocumentationChangelogSwiss hosting
Company
AboutBlogCompare
© 2026 devguard AG. All rights reserved.
Terms of servicePrivacy policySite noticeTrust centerLLM info
Swiss Made Software
Book a conversationStart for free
Privacy

Every processing activity,
accounted for.

Keep the record of processing activities for the nFADP and the GDPR in the workspace where your vendors and risks already live. devguard shows which transfers abroad have a safeguard, which activities need a DPIA and which data subject requests are due, from what you record.

Start for freeBook a conversation
++++
app.devguard.ch / privacy
5 activities
Transfers abroad
Transfers with a safeguard
3/4
have a safeguard
Adequate01
Safeguarded02
No safeguard01
ActivityRoleTransfersDPIA
Payroll and HR administrationControllerNoneNot needed
RecruitingControllerSafeguardedOpen
Applicant scoringControllerSafeguardedDone
NewsletterControllerNo safeguardNot needed
Hosting for customersProcessorAdequateNot needed
Every framework
ISO/IEC 27001ISO/IEC 27002SOC 2SOC 1GDPRHIPAAPCI DSS v4.0.1NIST CSF 2.0EU AI ActNIS2 DirectiveDORAOWASPISO/IEC 42001CIS ControlsCloud Controls MatrixISO/IEC 27017 & 27018ISO/IEC 27701ISO 9001ISO 14001ISO 45001Swiss nFADP
ISO/IEC 27001ISO/IEC 27002SOC 2SOC 1GDPRHIPAAPCI DSS v4.0.1NIST CSF 2.0EU AI ActNIS2 DirectiveDORAOWASPISO/IEC 42001CIS ControlsCloud Controls MatrixISO/IEC 27017 & 27018ISO/IEC 27701ISO 9001ISO 14001ISO 45001Swiss nFADP
ISO/IEC 27001ISO/IEC 27002SOC 2SOC 1GDPRHIPAAPCI DSS v4.0.1NIST CSF 2.0EU AI ActNIS2 DirectiveDORAOWASPISO/IEC 42001CIS ControlsCloud Controls MatrixISO/IEC 27017 & 27018ISO/IEC 27701ISO 9001ISO 14001ISO 45001Swiss nFADP
ISO/IEC 27001ISO/IEC 27002SOC 2SOC 1GDPRHIPAAPCI DSS v4.0.1NIST CSF 2.0EU AI ActNIS2 DirectiveDORAOWASPISO/IEC 42001CIS ControlsCloud Controls MatrixISO/IEC 27017 & 27018ISO/IEC 27701ISO 9001ISO 14001ISO 45001Swiss nFADP
  • ISO/IEC 27001
  • ISO/IEC 27002
  • SOC 2
  • SOC 1
  • GDPR
  • HIPAA
  • PCI DSS v4.0.1
  • NIST CSF 2.0
  • EU AI Act
  • NIS2 Directive
  • DORA
  • OWASP
  • ISO/IEC 42001
  • CIS Controls
  • Cloud Controls Matrix
  • ISO/IEC 27017 & 27018
  • ISO/IEC 27701
  • ISO 9001
  • ISO 14001
  • ISO 45001
  • Swiss nFADP
How it works

Record, derive, assess.

You record each activity once; the transfers, the assessments and what is still open follow from the records behind it.

01

Record each activity

Start from common activities such as payroll, recruiting and customer support, or add your own. Each activity names its purpose, its categories of people and data, its lawful basis, its retention period and the vendors that receive the data.

02

See where the data goes

devguard checks each vendor’s processing countries and transfer mechanism against the Swiss list or the EU adequacy decisions, whichever apply to you, both dated. A transfer without a safeguard shows at once, and one that rests on standard contractual clauses asks for a transfer impact assessment.

03

Assess what needs it

Tick the DPIA screening criteria on an activity, and devguard says whether a DPIA is required or worth checking. Rate its risks for the persons concerned and file the DPIA from the built-in template; the finished record keeps the risks as they stood.

Prior consultation is not forgotten

While a risk for the persons concerned stays high, the activity says so until a finished DPIA records the consultation. Accepting the risk does not clear it.

Why it’s built this way

Built so nothing is recorded twice.

Four choices behind how the privacy register works here, each one something you can check, not an adjective.

01

Each fact is recorded once

An activity is an asset and a recipient is a vendor, so the owner, the retention period and the vendor’s DPA are kept where they already are, not copied into a separate privacy tool.

02

Transfers are derived, not typed

A transfer’s status follows from the vendor’s countries and safeguard, checked against dated adequacy lists, so a change on the vendor shows on every activity that uses it.

03

Findings say what to do next

Missing safeguards, DPIAs, transfer impact assessments, DPAs and retention periods are listed in one place, the most serious first, each linked to where it is fixed.

04

Requests arrive with a due date

A data subject request is a submission with a response time, and your website’s server can file it through an API key that serves that one form and nothing else.

Swiss-hosted, yours to export.

Hosted in Switzerland by default, in German and English, with on-premise possible. Your data and evidence are yours and exportable in full at any time, with no lock-in.

See the full feature comparison

One module of the platform

Where privacy connects.

Privacy reads the rest of the workspace: the vendors that receive the data, the risks rated for the people concerned, the processes that hold DPIAs and requests, and the reports you hand an auditor.

AWAWSReviewed
CFCloudflareReviewed
StStripe

Vendors

Record where each vendor processes data and the safeguard it relies on.

2.0SCORE

Risks

Rate DPIA risks for the persons concerned in your one risk register.

Vehicle check · monthly
Warning triangle1
Headlights and signalsok
Defibrillator battery>80%
Submitted 07:42

Processes

DPIAs, transfer impact assessments and data subject requests as dated submissions.

86%
Shared with
JDAKMR+3

Reports

Print the record of processing activities as a PDF.

FAQ

The questions evaluators ask.

Does devguard decide whether my processing is lawful?

No. The privacy register shows what follows from what you recorded and from the adequacy lists as of the date it names. It is not legal advice, and the assessment stays with you.

Which laws does it cover?

The Swiss nFADP and the GDPR. The frameworks you adopt decide which adequacy list applies: the Swiss list, the EU decisions, or both.

Can I print the record of processing activities?

Yes. The report prints the controller record and the shorter processor record as a PDF, with the legal basis and the date of the adequacy lists on its cover.

Can our website send data subject requests in?

Yes. Create a key on your request process and let your web server file each request through the API. It arrives as a submission with its due date. The key belongs on your server, and it can read that one form and file to it, nothing else.

Where’s the data hosted, and can I export it?

Swiss-hosted by default, in German and English, with on-premise possible. The register prints as a PDF and the API returns it as JSON; your data is yours, so there’s no lock-in.

Keep every processing activity accounted for.

Record each activity once, link its vendors, and see which transfers, assessments and requests still need you, before an authority or an auditor asks.

Start for freeBook a conversation