Privacy & Security

Security Model

  • Administrator-only. The feature lives entirely inside the Joomla back end. Nothing is added to your public website, and it does not run in the SP Page Builder front-end editor.
  • Permission-aware. Generating a page requires the same login, CSRF token and page-edit rights Joomla already enforces for editing that page normally (core.edit / core.edit.own plus the page-owner check).
  • One outbound destination. Only your prompt and the bundled SP Page Builder layout guide are sent, and only to the AI provider you configured. No other page content, database rows, file paths or Joomla credentials leave the server.
  • No key of its own. The plugin reads SP Page Builder's stored API key at request time and never writes or copies it.
  • Fails safe. If anything unexpected happens while the feature loads, the SP Page Builder editor keeps working normally; at worst the button does not appear that time.
  • GPL-2.0-or-later, like every Joomla extension — the source is readable and auditable.