Skip to the content

PrivacyWhat reaches us, and what we keep

Bridle is a WordPress plugin. Your conversations, contacts and settings stay in your own WordPress database. We can’t see them. This page covers the few places where data reaches PlugPress.

Last updated 15 November 2026.

The email relay

You forward your support address to your Bridle address (it ends in @bridle.to). Each email then passes through our relay on its way to your site. The relay runs on Cloudflare Email Routing and Cloudflare Workers.

What it receives

Every email sent to your forwarding address: its headers, body and attachments. Attachments can be up to 10 MB each and 25 MB in all.

What it does

It reads the parts of the email and posts them straight to your site. Each post is signed with a secret that only your site and the relay know. It uses no AI, and it reads the email for nothing else.

What it keeps

Only your inbox registration:

  • your site URL
  • your webhook URL
  • the inbox code and its secret
  • a list of each site’s inbox codes, to count them
  • the time deliveries to an inbox started to fail, until one works again
  • a count of emails it had to give up on, for 30 days

An email your site takes is not stored on the relay.

With a licence

Your site also sends its licence key with each registration. The relay asks our account service, which checks the key with Polar. The relay keeps the answer for a day. It uses it only to set how many inboxes you may have.

When your site can’t take an email

The relay keeps the email and tries again for 48 hours. It deletes the email as soon as your site takes it, and after 3 days at the latest. If every try fails, the email is deleted and Bridle tells you that mail was dropped.

We use a kept email only to deliver it to you. It is never forwarded to anyone else.

  • A site can have 200 emails or 200 MB waiting. Past that, new mail is refused back to its sender.
  • An inbox whose site has failed for 14 days is paused. Each new email gets one try. If it fails, the email is refused back to its sender and nothing is kept.

Mail to an address that isn’t an inbox

An email to a Bridle address that no site has registered is refused back to its sender. It is not stored and nobody receives it.

Checking the site is yours

When you add an inbox, the relay calls your site once to check that the request came from it. The call carries the inbox code and a one-time code. It carries nothing about you or your customers.

Logs and limits

The relay keeps short technical logs for up to 7 days: what happened, for which inbox code or site, and when. They hold no sender addresses, no subjects and no email content.

To stop abuse, Cloudflare counts requests to the relay per IP address, for one minute.

How to stop

Remove the forwarding rule at your mail host. Turning off an inbox in Bridle removes its registration from the relay. Deleting the plugin removes them all.

Bridle AI

Bridle AI is optional. It writes drafts and chat answers for sites that haven’t connected their own AI key. It stays off until you turn it on.

When you sign up

We keep your site URL and the email you enter for receipts. We also keep a hash of your site key. The key itself is never stored.

For each answer

We get the same text an AI provider would get:

  • the conversation or chat so far
  • the contact details Bridle holds for that customer
  • your agent instructions and snippets
  • the parts of your knowledge that match the question

What happens to it

We pass it to the model (Claude Haiku, by Anthropic) through Cloudflare AI Gateway, with logging off. Then we send the answer back. We don’t store prompts or answers.

What we keep

  • your site URL
  • your email
  • how many answers your site used each month
  • your packs

That is what we need to count your 100 free answers and your credits.

Payments

Packs are paid through Polar. Polar handles your card. We see the order, never the card.

Your own AI provider

When you connect your own key in WordPress, prompts go straight from your site to that provider, such as Anthropic, OpenAI or Google. They never pass through PlugPress. The provider’s own terms apply.

The same goes for:

  • the decision model you can add under Settings → Sorting (TypeSafe or Cloudflare Workers AI)
  • Cloudflare Turnstile on your chat
  • Gravatar pictures in your Inbox

Licences

Bridle Pro checks its licence and its updates with updates.plugpress.io. It sends your site URL, the licence key and version numbers.

Purchases go through Polar.

This website

bridle.to has no analytics and sets no cookies. Our host keeps short request logs for security.

The waitlist

We store your email, which form you used, the page that sent you (if your browser tells us), your browser’s user agent and the date. We use it to email you at launch. We delete it when you ask.

Stopping abuse

We count sign-ups per visitor with a hash of your IP address. The hash changes every day, and we keep it for a day.

Bot checks

When Cloudflare Turnstile guards the form, it checks your browser for signs of a bot. Cloudflare’s Turnstile privacy addendum applies.

Sub-processors

These companies handle data for the services above.

WhoWhat forWhat they see
CloudflareThe email relay, Bridle AI, TurnstileEmails and AI prompts in transit, emails waiting for a retry, inbox registrations, relay logs, the Bridle AI ledger
AnthropicThe Bridle AI modelPrompts and answers, in transit
PolarPayments for Bridle AI packs and Bridle ProOrders and billing details
SpacefastHosting bridle.to and the waitlistWaitlist entries and request logs

Your choices

Data we hold

Ask for a copy of what we hold about you, or ask us to delete it. Email hello@bridle.to. We answer within 30 days.

Data in your WordPress

Use WordPress’s own privacy tools: Tools → Export Personal Data and Erase Personal Data. They include Bridle’s conversations, messages and attachments.

Data processing agreement

For the relay and Bridle AI, PlugPress handles your customers’ messages for you. Email hello@bridle.to for a data processing agreement.

Changes

When something changes, we update this page and the date at the top. We also note changes that matter in the plugin’s changelog.