Privacy & External Services
Document the optional WordPress AI Client and DeepL data paths and no-telemetry boundary.
mcLogiora contains no analytics, telemetry, tracking pixels, or beacon requests. It has no mcLogiora server in the request path.
When an external request happens
Only after the site owner enables suggestions, chooses and configures a provider, and clicks an action. Page loads, activation, editor opening, visitor traffic, manual translation, and scanning do not send content to a provider.
Only the single field requested is sent. A title suggestion sends the title, not the post body or the rest of the site.
WordPress AI Client
WordPress AI Client handles provider discovery, connectivity, credentials, model selection, and the provider request through WordPress Core's supported Connectors/provider infrastructure. mcLogiora does not store or receive those provider credentials and does not expose direct OpenAI, Anthropic, or Gemini settings.
DeepL
DeepL remains a separate dedicated translation service where supported. A DeepL API key is stored in the site's options table when configured in mcLogiora, or can be supplied through MCLOGIORA_DEEPL_API_KEY. DeepL requests happen only after an explicit suggestion action. DeepL has no model selection.
Suggestions are reviewable and never auto-publish. Manual translation requires none of these services.