Website import

When you give your website address, Privacyboard reads your public pages to prefill your workspace. You check everything before it is saved. Nothing is added to your records without your confirmation.

#What it reads

• The page metadata: title, description and social sharing tags.
• Structured data that describes your organisation, when your site publishes it.
• A privacy contact email, when your pages publish one explicitly.
• The addresses of the scripts your page loads, to recognise tools such as analytics, chat or payments.
• A few public response details that reveal your hosting.
• Public records of your domain, to recognise email and other providers.

#What it never does

• It does not log in to your accounts or connect to your tools.
• It does not use AI to guess legal or security facts. Country of establishment, security practices and legal roles are never guessed.
• It only opens public HTTPS pages, and only when you ask.
• Only the suggestions you accept are saved to your workspace.

#After the import

• Detected company details are shown for you to edit.
• Detected tools are suggestions: remove the ones that are wrong, add the ones that are missing.
• Existing answers are never overwritten by a new import.
• Vendor details are filled from the catalog where the tool is known, and marked as suggestions until you confirm them.

#If the import finds nothing

Some sites block automated readers or load most of their content with scripts. Continue manually: a company name is enough to start, and you can add vendors from the catalog by hand.

#The cookie banner has its own scan

The site check of the cookie banner is a separate, deeper check of what your pages load before and after a visitor chooses.

#FAQ

#Is my website data sent to a third party?

The import is made by Privacyboard itself when you ask for it. Logos and icons are served from Privacyboard, not fetched from outside services by your visitors.

#Can I run the import again later?

Yes. Existing fields are preserved and only missing information is suggested.

#Why was a tool not detected?

Tools loaded after a visitor interacts, or added through a tag manager, are not visible in the page code. Add them from the catalog.