# Apeari: external services and privacy

Apeari makes no analytics or licensing requests. With the Apeari service explicitly enabled, AI requests go to apeari.com for computation and billing against a verified domain. No background installation reporting is performed. The Apeari.com link opens only when clicked. Fonts and editor assets are bundled locally.

AI is disabled by default. After an administrator configures a provider, explicitly consents and submits an AI request, WordPress sends it to the selected service:

* Apeari hosted AI: https://apeari.com/v1/lite/edits
  Provides restricted Gutenberg edit proposals and draft content using OpenAI on the server. Requires an Apeari account, Lite token and paid service credits; local functionality is not locked by credits. A useful answer without changes may also consume credits.
  Terms and data processing agreement: https://apeari.com/regulamin
  Privacy: https://apeari.com/polityka-prywatnosci
* OpenAI: https://api.openai.com/v1/responses
  Terms: https://openai.com/policies/services-agreement/
  Privacy: https://openai.com/policies/privacy-policy/
* Anthropic: https://api.anthropic.com/v1/messages
  Terms: https://www.anthropic.com/legal/commercial-terms
  Privacy: https://www.anthropic.com/legal/privacy

Editing requests include your instruction, up to six recent conversation messages, and necessary context from the selected page's blocks, such as text, attributes and supported styles. Image title and alt text may be included. Image files are not sent to AI. URLs explicitly typed or inserted into your message are part of that message and may be sent. Draft-generation requests include your brief, language, sequence number and previous generated titles. Do not include confidential or personal data that you are not authorized to share. The site owner must determine the applicable legal basis and document the selected provider's processing terms.

For Apeari hosted AI, results are retained by the service for up to 30 days for retries, independently of the local retention below; billing records follow the service privacy policy. Lite sends no theme files, image files, executable code or provider keys. Hosted operations are validated against an allowlist on both the API and WordPress sides. Disabling the separate service consent stops new calls. Account and service data erasure requests go to the contact in the service privacy policy.

Apeari domain verification is initiated by the administrator and uses a single-use proof valid for 15 minutes. The service calls the fixed WordPress /apeari/v1/ownership REST endpoint over HTTPS to verify website control. This route exposes no editing functionality and requires the temporary proof secret. Multisite proof generation requires a superadministrator.

API keys and installation tokens are encrypted in the WordPress database using keys derived from WordPress salts and used only by the server. When migrating from a local Apeari PRO installation, configured keys and model IDs may be copied into separate Apeari settings; AI remains disabled until consent and provider selection. No existing page or theme draft is migrated.

Each conversation message expires seven days after it is saved. Refreshing a session or adding another message does not extend older messages' expiry. Expired messages are excluded from editor sessions, restored history, undo/redo snapshots, AI context and personal data exports. Legacy messages without a trustworthy timestamp are discarded when upgrading to 1.0.2. Generation-job metadata expires seven days after the last generation step or status change; merely viewing the job does not extend it. Private editor sessions expire after two hours of inactivity. Physical deletion of expired metadata is performed by WordPress scheduled cleanup; scheduled tasks require visits or a configured system cron. sessionStorage stores only a session identifier per browser tab. A local per-user preference remembers dismissal of the optional PRO introduction. History is offered through an optional load-history button. Settings > Apeari can erase the current user's stored editor data on the current site. WordPress personal data exporters and erasers include Apeari records across all sites in a multisite network, with pagination. User removal clears that site's private editor data; network user deletion clears it across sites. Generated drafts are ordinary WordPress posts governed by the site's retention policy.

Uninstall removes Apeari settings, secrets, history and scheduled cleanup. It leaves pages, posts, media and Apeari PRO data intact. Provider-side retention is governed by the provider's terms.

