---
title: "Privacy and external services"
description: "Exactly what leaves your server, what never does, and how to run the plugin with no outbound request at all."
url: "https://maksut.net/price-anchor/docs/privacy-and-external-services/"
language: "en-US"
datePublished: "2026-08-02T00:35:16+00:00"
dateModified: "2026-10-10T08:40:00+00:00"
---

# Privacy and external services

## What the plugin sends

Price Anchor can contact an external exchange-rate service when an automatic provider is selected and a scheduled or manual rate refresh runs. These requests originate from the store server, never from a visitor’s browser.

They contain:

- the requested base/store currency code;
- the source-currency codes;
- ordinary HTTP connection metadata, such as the server’s IP address.

## What is never sent

- Product prices and product data
- Orders and order contents
- Customer data
- WordPress user data

There is no usage analytics, no tracking pixel, no advertising request and no customer-side third-party script anywhere in the free plugin. Nothing is loaded into your storefront from another domain.

## The services

### Frankfurter

The default automatic provider. A public exchange-rate API requiring no account or API key.

- Service and API information: [frankfurter.dev](https://frankfurter.dev/)
- API privacy information: [frankfurter.dev/#faq](https://frankfurter.dev/#faq)

### TCMB

Available for stores whose WooCommerce currency is TRY. Price Anchor retrieves the Central Bank of the Republic of Türkiye’s published daily exchange-rate XML.

- Service: [tcmb.gov.tr/kurlar/today.xml](https://www.tcmb.gov.tr/kurlar/today.xml)

## Running with zero outbound requests

Choose the **Manual** provider. Price Anchor then makes no automatic rate request of any kind. You enter rates yourself and everything else — validation, markup, rounding, sync, order stamping — behaves identically.

## Credentials

Pro’s optional commercial provider uses your own API key. It is encrypted at rest with a key derived from the site’s WordPress salts, and is never written to logs, status reports or notification emails. Secret reads never migrate or rewrite stored values; legacy plaintext fails closed rather than being silently upgraded in place.

## Logging and personal data

Security-relevant boundary decisions are logged as stable action, capability, route and object identifiers. Nonces, cookies, authorization headers and request bodies are deliberately excluded, and context values are scalar-only, redacted and bounded. The log records that a decision happened, not the payload behind it.

## Uninstall

See [Uninstall and data](https://maksut.net/price-anchor/docs/uninstall-and-data/). Order records are never removed, under any setting.