#096Guide4 min

Understand Hackaiz’s role in a GDPR effort

Use observed technical evidence about your website to support privacy work, while keeping legal assessment and organizational responsibilities with qualified people.

Hackaiz team · updated 21/11/2026

Illustration: a professional files evidence folders.
Illustration: a professional files evidence folders. Illustrative photo, not a screenshot.

01What the GDPR check actually observes

Hackaiz contributes technical observations to a GDPR effort; it does not certify compliance or replace legal advice. The GDPR check screen reviews what a visitor receives from a website: trackers, cookies, and accessible legal pages. It lists External services contacted and provides evidence beside the individual checks. These observations help a developer and a privacy lead discuss concrete behavior rather than relying only on what a configuration was intended to do.

The screen includes checks such as Trackers only after consent, Cookies set before consent, Reachable privacy policy, and Retention period stated. For example, an analytics service loaded on the initial page can warrant investigation of consent settings. A policy page that names no retention period can warrant a content review. These are different types of evidence: detecting text on a page does not establish that the organization follows it, and observing one page load does not describe every visitor journey.

02Prepare an authorized review

Website ownership proof is mandatory before the review, even though the checks read visitor-facing content. In Connect, establish domain control using the DNS TXT record at _hackaiz or the HTTPS file at /.well-known/hackaiz-verification.txt with the verification value supplied by Hackaiz. If your site is managed through an AI builder, you can ask that project’s assistant to create the required file. Do not treat knowing a public URL as permission to analyze someone else’s service.

Once the domain is verified, open GDPR check, enter the intended website address, and use Check compliance. That is the button’s label, not a promise of a legal compliance verdict. Make sure the address identifies the environment you mean to examine. The review consumes credits. Reading an existing result and launching a new check are different activities; a previous report cannot establish what changed after its date.

  1. 1Prove control of the website domain using the supported verification method.
  2. 2Open GDPR check and enter the correct site address.
  3. 3Start Check compliance and read the evidence for each returned point.
  4. 4Share technical findings with the person responsible for privacy decisions.

03Separate an observation from a legal conclusion

The privacy screen uses No issue found, Issue found, Needs review, and Not assessable for individual checks. These review statuses are not a GDPR certification scale. Not assessable means you lack a usable conclusion for that point, not that it passed. For instance, a site whose text is assembled in the browser may prevent the review from confirming a legal page from the server response. Inspect the actual website and involve its maintainer rather than assuming a missing observation proves a missing policy.

The Score of the technical points checked is explicitly indicative. Neither a high score nor an empty list of external services demonstrates that all processing is lawful. The review cannot replace your organization’s inventory of personal data, choice of legal bases, assessment of processors and transfers, retention practice, or handling of individual requests. Use it to identify questions and technical corrections, then have the appropriate privacy or legal professional assess the wider obligations.

04Keep evidence and validate the resulting work

The result offers Download report (PDF), an action plan, and a Privacy policy draft area with Generate the draft. Draft generation consumes credits and uses observed information; it is not a ready-to-publish legal opinion. Check the real organization name, purposes, recipients, retention periods, and contact details before using any draft. A technically reachable privacy policy can still be inaccurate or incomplete. Do not publish text simply because a tool produced it.

For your own evidence folder, retain the target address, report date, relevant observations, decisions, and subsequent verification. Organize access so reports do not circulate more widely than necessary. When a finding requires a code change, apply your normal review process. Any Hackaiz GitHub fix is a draft pull request requiring human review and approval, never an automatic merge. After the approved change is deployed, repeat the relevant authorized checks and explain what remains outside their scope. Technical evidence supports accountability; it does not confer compliance status.

Frequently asked questions

Was this article helpful?

Related articles