Meet compliance requirements
What leaves your server, where AI requests are processed, how the product key is stored and how to keep content recoverable. Use the table to find the answer your security or legal team asks for.
| I want to ... | Use | Needs |
|---|---|---|
| list every outbound connection and where AI runs | Firewall and data residency | Nothing |
| review permissions, output filtering and the editor's routes | Security | Nothing |
| back up builder pages and restore them | Back up and restore your builder pages | Drush or your hosting backups |
Which should I use
Start with firewall and data residency when a firewall blocks the editor, or when someone asks what data leaves the site. Security covers who can do what inside the site. Backup and restore matters before every major update.
What's next?
Accessibility and findability for inclusive sites to continue exploring DXPR Builder.
In this section
- Firewall and data residency: Every DXPR host the module contacts, what each request carries, the EU-only AI model and air-gapped operation
- Security: Permissions, output filtering and the AJAX routes the editor uses
- Backup and restore: What to back up and how to restore builder content
Something wrong or missing on this page?
Report it
or edit the page.