Question 1

Does Audulate make me GDPR compliant?

Accepted Answer

Audulate gives you the tools, evidence, and guidance to achieve and demonstrate GDPR compliance — but compliance itself is your responsibility. We make it dramatically easier by surfacing gaps, automating workflows, and generating audit-ready evidence.

Question 2

How long does setup take?

Accepted Answer

Most teams are up and running in under 5 minutes. Add your website URL, invite your team, and optionally connect your GitHub repository — the platform starts scanning immediately. For best results, add page hints under Settings → Websites to tell the scanner exactly where your privacy policy, cookie policy, and DSR pages live. No code changes required.

Question 3

Do you store my website data?

Accepted Answer

We store scan results, findings, and evidence records in our EU-hosted database. We do not store full copies of your web pages. Scan data is retained according to your plan's retention window and is deleted when you close your account.

Question 4

What happens when a regulation changes?

Accepted Answer

Our Regulation Watcher monitors official sources — EDPB, ICO, FTC, HHS, IAPP, and PCI SSC. When a relevant change occurs, we update our rule engine and notify affected tenants with a plain-language summary and recommended actions. NIST sources will be added when SOC 2 scanning ships.

Question 5

Can I use this without a dedicated DPO?

Accepted Answer

Absolutely. Audulate is designed to be usable by developers, product managers, and founders — not just legal experts. The AI layer explains every finding in plain language and provides step-by-step remediation guidance.

Question 6

Is my data processed in the EU?

Accepted Answer

Yes. All data is stored and processed in EU-based infrastructure. We do not transfer personal data outside the EU/UK. Our own compliance posture is available on request.

Question 7

How does GitHub PR scanning work?

Accepted Answer

You install our GitHub App on your repository. On every pull request, we analyse the diff for GDPR-relevant patterns: PII leaks, insecure logging, hardcoded secrets, and missing consent checks. Findings are posted as PR comments so developers can fix issues before merging.

Question 8

Do you support mobile apps (iOS / Android)?

Accepted Answer

Yes, for the parts that matter most today. Your mobile source code (Swift, Kotlin, React Native, Flutter) goes through the same PR scanner as your backend — PII leaks, insecure logging, hardcoded secrets, missing consent gating. Your privacy policy is analysed via the URL on your App Store / Play Store listing (Art. 13/14 completeness, DSR contact, ICO registration). And the GDPR operating system — RoPA, DSRs, vendor DPAs, breach response, cookies & consent — is framework-agnostic, so it works the same whether you ship a website or an app. What is not yet supported: static analysis of the compiled .apk / .ipa, and scraping of App Store Data Safety / Privacy Nutrition Labels — both on our roadmap. Tell us if you need them and we will prioritise.

Question 9

How often does the scanner run?

Accepted Answer

Free plans run manual scans only — you trigger them yourself. Growth plans include weekly automatic scans (every Monday at 09:00 UTC). Enterprise plans scan daily. You can always trigger a manual scan on any plan. Scan history and findings are retained for 30 days (Free), 60 days (Growth), or 2 years (Enterprise).

Question 10

What support is included?

Accepted Answer

Free plans get community support via our documentation and GitHub Discussions. Growth plans include email support with a 24-hour SLA. Enterprise plans get a dedicated Customer Success Manager and a contractual SLA.

We're real people.
We reply within 24 hours.

Send us a message

Response times

Office

Start your free trial and explore on your own.

We're real people. We reply within 24 hours.

Send us a message

Response times

Office

Start your free trial and explore on your own.

We're real people.
We reply within 24 hours.