What we keep, and who else can see it

• We collect what the exchange needs to work: who you are (an email), which sites you list, and which links changed hands.
• A readable copy of your API key never exists on our side, only a one-way hash.
• Your domain is shared with Ahrefs for a rating and with query.domains for a traffic estimate, and with nobody else for any purpose of ours.
• Other members cannot see who you are until you and they both accept a pairing. After that, they can, for good.
• No ads, no data sales, no analytics or tracking.

Account: email, an internal id, and the profile name and picture GitHub or Google pass along if you use them to sign in.

Sites: domain, URL, title, description, category, the anchors you hope to receive, what you can give in return, Domain Rating with the date it was fetched, and our review decision with its reason.

Pairings: the two sites involved, whether a wider category or DR range was used, each answer, the current state and the timestamps.

Links: the page you reported, the anchor text found, live or missing, position on the page, rel values, and every check we ran with its outcome. Your partner sees this log for the two links between you.

API key: a SHA-256 hash, a short visible prefix, and issue and revocation dates.

Our host additionally keeps standard request logs (IP, user agent, path, time) for a limited period; we do not mine them for member profiles.

• Readable keys. You see the key a single time, at creation, and it is hashed on the spot. We cannot restore a lost one, and a stolen database copy would not expose it.
• Card numbers. Pro payments happen on Stripe's pages; the card never touches our servers. On the Free plan there is no payment data whatsoever.
• Passwords. Sign-in is by emailed link, GitHub or Google.
• Whole web pages. We read a page, keep the result (a draft or a verification record), and drop the document.

It requests only addresses you gave us: your homepage when you list a site, and the page you name when you report a link. It does not roam your site or follow links to other places.

• Identifies as swap-backlinks-bot/1.0 (+https://swapbacklinks.com).
• Ordinary GET requests, twelve-second timeout, few redirects.
• Skips private or internal network addresses, stops at about 1.5 MB, accepts HTML only.
• Rechecks live links after 7 days, after 30 days, then monthly while the swap lasts.

It sees only server-sent HTML. A link added by JavaScript after load may be missed, so keep it in the delivered markup.

Only the following, each as a service provider acting for us.

Resend sends email, so addresses and message bodies pass through it. Supabase stores the data above and runs sign-in. Stripe handles Pro billing. Cloudflare and our hosting provider handle DNS, routing and the application.

When a language model is enabled for drafting, it receives your homepage text with brand name and domain removed, never your domain or URL.

Member data is never sold, rented or handed to anyone beyond this list. Should that change, you would hear first, here and by email.

Anonymity before agreement is the core of the product, so the rules are exact.

Before both accept: a candidate sees your topic, category, DR, wanted anchors and offer, plus the masked top-level domain. Not your domain, URL, email or name.

At mutual acceptance: each side gets the other's domain, URL and email, and we email both. This cannot be reversed, so accept only pairings you mean.

After a link is reported: your partner sees its page, anchor, position, rel and live status at each check, and you see theirs.

Write your description as public text: matched partners can read it.

Beyond that, we disclose data only when legally compelled, and we tell you unless the law forbids it.

Everything is about your own account and swaps: sign-in links, listing received or decided, a pairing waiting, a partner's reply, a link going live or disappearing. No newsletter, no marketing list.

The only recurring message is a digest of sites that suit yours: at most weekly, never empty, never while you have a pairing open. Set it to weekly, fortnightly or paused in your dashboard.

Each email has an unsubscribe link. It stops the digest, pauses your sites, and turns off your API key, without deleting anything. The same link restores it all.

One cookie keeps you signed in; Supabase sets it for this domain only.

We run no analytics: no page-view counters and no tracking pixels. If something breaks, an error report may be sent to our error-monitoring service (Sentry). Before it leaves our servers we remove keys, tokens, cookies, request bodies and email addresses, so it contains the technical error and the page address only.

There are no ad pixels, session recorders or cross-site trackers. The MCP endpoint uses no cookies, only a bearer token.

You do not need to ask us. On the Account page you can download everything we hold about you as a JSON file, and delete your account with one confirmation. Deleting removes your account, sites, pairings, messages, link records and API key straight away, cancels any Pro subscription, and closes swaps in progress so the other side is told. For anything else, such as a correction, write to [email protected]. There is no fee.

Two things deletion cannot do:

• Links already live on other people's websites remain theirs; we can forget them but not remove them.
• Anyone you accepted a pairing with already knows your URL.

Backups expire on their own shortly afterwards.

If we edit this notice, the date moves. Sending data to a new recipient would be posted here and emailed to you before it starts.

Questions, requests or a problem to report: [email protected].

Last updated 21 October 2026.