Technical and documentary compliance

Backed by evidence

Understand how your product handles compliance. Compare requirements, documentation and code, then act on the gaps.

Private by default. You choose what to share.

What we review

Requirements, evidence and a clear scope.

Applicable requirements

Identify the data protection and consent requirements relevant to your product, users and markets.

Documentation and code

Compare privacy notices, consent flows, data handling, third-party services and retention practices with the submitted code.

Gaps and next steps

Understand observed support, gaps, possible gaps and missing evidence. Each finding explains what to review next.

Evidence you can explain

Make compliance findings actionable.

See which requirements are supported, where gaps appear and which conclusions need more evidence. Findings connect documentation and code to concrete next steps.

Read our own report
  1. 01

    Findings and next steps

    Priorities, reasoning and recommended actions.

  2. 02

    Evidence

    Findings linked to the materials reviewed.

  3. 03

    Scope and limitations

    A clear distinction between what is observed and what remains unverified.

How it works

From compliance evidence to dated results.

  1. Describe your application

    Tell us about your product, its users, markets and data practices.

  2. Share the evidence

    Share the code, privacy notices, terms and documentation of consent, data flows, third parties and retention through your private application.

  3. Review your results

    Receive a compliance report with supporting evidence, gaps, limitations and next steps. Its certificate records the assessed version and dated results.

Our own certificate

We use Promethia too.

We use Promethia to assess our own compliance practices. Our product, our evidence, our findings.

Browse public certificates

Our own assessment is pending.

Only certificates published by their owners appear in the public directory.

Before you start

A few things to know.

What does the team need to share?

Share your source code through GitHub Actions, as a ZIP file of up to 25 MiB. The Delivery keys section of your application provides the setup instructions. Exclude passwords, secret keys and customer data.

Does this guarantee legal compliance?

It provides technical and documentary evidence within the agreed scope. It does not guarantee legal compliance or replace legal advice. Missing operational evidence and unresolved applicability are stated in the report.

What does the certificate represent?

It records the compliance assessment findings for an identified version, date and scope, including gaps and limitations. A completed assessment can still contain unresolved issues.

What can I publish?

The certificate is intended for display on your website or application. Source code and supporting application materials remain private.

Your next step

Start with your application.

Request a compliance assessment

Already have an account? Sign in