Uwawp What data Ariadne sends outside your site, and under exactly what conditions.
The short version
Ariadne’s own matching — tag overlap, category overlap, and title similarity — runs entirely on your own server. No external service, no account, and no API key are needed to get a genuinely good related-posts engine. Two optional pieces load an external resource, and only ever under the specific conditions below.
Google Fonts
Ariadne’s own Dashboard, Settings, and Post Status admin screens load one typeface (DM Sans) from Google’s font CDN to render the plugin’s branded admin UI. This happens only on those three admin screens, only for a logged-in administrator — never on your site’s public-facing pages, and never for a visitor.
Separately, if you’re on a Pro or Pro+ plan and choose one of the curated Google Fonts for your Related Posts card styling in the Customizer, that one font family is also requested from the same CDN on your site’s frontend. In both cases, only the standard browser request information (like IP address and user agent) reaches Google — nothing else.
Voyage AI Pro / Pro+
If you’re on a Pro or Pro+ plan and have entered your own Voyage AI API key, Ariadne sends each post’s title and body text to the Voyage AI API once — when that post is saved, and only if its content has actually changed — to compute the semantic-matching signal. This is entirely opt-in: no key means no calls. It also uses your own Voyage AI account and key, never one shared by or routed through Ariadne or Uwawp.
What never leaves your site
Tag overlap, category overlap, title similarity, and local text (BM25) scoring are all computed directly on your own server, with no account and no API key required for any of it. This is the complete Free plan — a fully-functioning related-posts engine entirely on its own.