Privacy
Last updated: November 20, 2026. This covers the Ropeline website, its update emails, Ropeline Pro purchases, the online dashboard, the Ropeline plugin, Ropeline Pro, the Ropeline Network, Ropeline Proof (Agent Receipts), the Ropeline app for Stripe and Ropeline for Shopify.
Who runs Ropeline
Ropeline is built and run by Sparsh H. in Atlanta, Georgia, USA. Contact: hello@getropeline.com.
For security and legal reviews
The short version, in one place. Each point is covered in full further down this page.
- Who processes data for us: Cloudflare (hosting, Workers, D1, Email Service and Web Analytics), Stripe (payments) and Trybe (which creators' videos lead to sales).
- Who Ropeline Pro contacts straight from your site: Have I Been Pwned (only the first 5 characters of a SHA-1 hash of a password, when one is set or changed, and at most once every 30 days at login), and an AI agent operator's public keys, only when a request arrives signed by that operator. If you turn on the "prove you're human" check, the plugin also uses Cloudflare Turnstile.
- What Ropeline Pro sends us: once a day, its key, the website's address, Pro's version and, on a WooCommerce store, one number: paid orders in the last 30 days (store plans are sized by orders). Also the IP addresses of bots it stopped and what each did, kept for 7 days. If you turn on the online dashboard, hourly totals: numbers only.
- What it never sends us: passwords, card numbers, customers' names, emails or orders, or page contents.
- Ropeline for any website: tries are counted under a scrambled copy of each visitor's address for 2 hours. An address is kept as it is only when it reaches a block line, for 7 days. Emails sent with signups are checked against the list of throwaway services and not kept.
- Legal basis: network and information security, a legitimate interest under the GDPR (Recital 49).
Need something else for your review? Email hello@getropeline.com.
What we collect
- If you ask for update emails: your email address, the "I run" answer you pick, and the time you signed up.
- If you ask to upgrade: your email address, your website's address, the plan you picked, and the time you asked.
- When you download the plugin: a count of downloads per day. Nothing about you.
- If your website uses Ropeline for any website (its
/v1/checkAPI): for each login, signup, checkout or form post your server asks about, we count the tries under a scrambled copy of the visitor's address (hashed with your key and website), kept for 2 hours. A visitor's address is kept as it is only when it reaches a block line, as your site's report to the shared list, for 7 days. An email address sent with a signup is checked against the list of throwaway services and not kept. - If you ask for a free week of Ropeline Pro: your email address, the plan, and (when you start from your WordPress settings) that page's address, kept with a scrambled copy of the link we email you until the link runs out, 24 hours later. When you open the link, your key is made and kept like a paid plan's (your email address and plan, and a scrambled copy of the key).
- If you also ask for a setup call: your store's address and whether card testing is happening, kept with the link the same way. When you open the link, they and your email address go to our own inbox (hello@getropeline.com), so we can email you to set a time, and our database keeps them for 30 days. After that it keeps only that a call was asked for, to count how many are left.
- If you buy Ropeline Pro: your email address, your plan, and the IDs Stripe gives your checkout, customer record and subscription. Stripe handles the payment; we never see or store your card number. To keep free trials to one per customer, we also keep a scrambled (hashed) copy of the code Stripe gives your card (its "fingerprint", which is not the card number and can't be turned back into one). See Stripe's privacy policy.
- If you start a checkout, tick Stripe's box to hear from us, and leave without finishing: when the checkout expires 2 hours later, Stripe gives us your email address and a link back to it, and we email you that link once. We keep only a scrambled (hashed) copy of the address, so we never send it twice.
- If you sign in to the online dashboard: a cookie holding a random sign-in code, for 30 days or until you sign out. We store only a scrambled (SHA-256) copy of the code.
- Visit counts. To know how many people visit, this site uses Cloudflare Web Analytics, which counts page views without cookies and without following you across other sites. It sees the page you opened, the site that sent you, your browser type and your country.
- If you use the free store check (/check): the address you type. We look at that store's public pages, keep the result for an hour so it isn't looked at again ("Check again" can refresh it after 5 minutes), and count checks per day. Nothing about who asked is kept, and usernames we see are counted, never stored.
- If you use the free AI agent check (/agents): the same as the store check. It looks at three public addresses on that store and keeps the result for an hour. The agent verify API checks the request details your server sends and keeps none of them, only a count per day. An AI agent operator that lists itself in our agent registry gives us its domain and the name it chooses, which we show publicly.
- If your store uses Agent Receipts (Ropeline Proof, /proof): for each purchase by a verified AI agent, the receipt: the store's address, the agent's signature and its operator's public key, and the order as the store sends it (its number, total, currency, items and payment ID; never the shopper's name, email, address or card). Receipts are kept for 540 days, the longest the card networks give a shopper to dispute, then deleted. If the store also uses the checkout rules, the shopper's IP address, email and card fingerprint arrive with each checkout and are kept only as scrambled (hashed) copies, unique to that store, for a day, to count failed payments. Each checkout's decision and each payment's outcome also go on the store's decision log, kept for 90 days: the order's number and total, the agent's operator and the decision, never anything about the shopper (not even the scrambled copies). After 90 days an entry is deleted; only the newest entry's number and fingerprint (hash) stay, so the log's chain carries on. If a store sets an address for attack alerts, we keep the address and its secret until the store removes them or sets another; an alert says when an attack started and how many payments failed, never anything about a shopper. Anyone handed a receipt can check it at /proof; checking one keeps nothing about the receipt.
- If your store installs the Ropeline app for Stripe: your Stripe account's ID, whether you linked a Ropeline key, and your failed payments for 2 days (when, the amount, the decline code, and a scrambled code that tells one card from another, made from the card's fingerprint or its brand, last 4 digits and expiry; never card numbers or shopper details), to spot card testing. When a disputed payment has an Agent Receipt, the app adds that receipt to the dispute in your Stripe account. Uninstalling the app deletes what we kept about your account.
- If your store installs Ropeline for Shopify: your shop's myshopify.com address, its Shopify access token (encrypted), your settings, and for each order Ropeline screens its order number, risk rating and the reasons, for 90 days, to show you on the app's page. To spot repeats, it keeps for 2 days keyed hashes of each order's connection (IP address), email, phone, shipping address and card, made with a secret key so they can't be turned back into those details. Signups that look fake are kept as their customer number and the reasons, for 30 days. We don't keep shoppers' names, emails, phone numbers or addresses: the blocklist the checkout guard uses is kept in your store's own Shopify data, where you can see and change it. When Ropeline sees a card-testing attack, it emails your store's contact address once, without keeping it. Uninstalling stops the app and deletes its Shopify access at once, and when Shopify asks (48 hours later) we delete everything about your store; we also act on Shopify's requests to delete a shopper's data.
- Sales from creators' videos. To see which creators' videos and links lead to sales, our pages load Trybe's pixel from track.getropeline.com. It isn't loaded on the checkout, welcome, free-week, dashboard or report pages, or for visitors in the EU, Iceland, Liechtenstein, Norway, the UK or Switzerland. It sets a cookie named
ugc_vid_followed by our Trybe store number, holding a random visitor code, for 365 days. With that code, Trybe records the pages you view, the site that sent you, any campaign or creator code in the link, and your browser type and screen size. When you start a plan or free trial through our checkout, our server tells Trybe your subscription's ID and the creator's share (one month of your plan's price, up to $20), with that visitor code, within the hour, then forgets the code (after 7 days if Trybe can't be reached). Never your email, name or card. You can delete or block the cookie; the site works the same without it. See Trybe's privacy policy. - Nothing else. Apart from the sign-in cookie and Trybe's, this site sets no cookies and runs no ads. Fonts are served from our own site. The checkout page loads Stripe's payment form, which Stripe runs under its own policy.
Why
To email you about new versions and big updates, and, if you buy Ropeline Pro, to run your plan: your key, the sign-in links you ask for, up to two emails during the free trial (one 2 days in if no website uses your key yet, with the install steps, and one 3 days before the first charge, with what Ropeline stopped and what you'll be charged), for a free week the link to get your key and one email 2 days before the week ends, receipts and renewals. If you ticked the box at checkout and left without finishing, one email with the link back to your checkout. We won't send anything else and we never sell or rent your email.
Where it's kept
Signups and upgrade requests are stored with Cloudflare, which hosts this site. Cloudflare also handles the network traffic for the site, as any web host does.
How long
Until you unsubscribe or ask us to remove it. Upgrade requests that don't become a plan are deleted after 12 months. If you become a customer, the customer policy takes over.
Your choices
Every update email has an unsubscribe link. To see, correct or delete what we hold about you, email hello@getropeline.com and we'll do it within 30 days.
The Ropeline plugin
The Ropeline plugin runs on websites that install it. Those websites, not Ropeline, decide to use it and are responsible for telling their visitors. The plugin suggests wording for each site's own privacy policy.
What the plugin stores, on the website's own server:
- A log of what it stopped or watched: the visitor's IP address, the time, which form, and a short reason. For failed logins, the reason includes the username that was tried. The log is deleted after 30 days.
- Counters and lockouts, which expire within a day.
- A cookie named
ropeline_device_followed by a user number, set when someone logs in. It holds a timestamp and a signature and lasts a year. It lets a person keep logging in from that browser if their account is ever under attack. - If a visitor passes the optional "prove you're human" check, a cookie named
ropeline_humanthat holds a timestamp and a signature and lasts one hour.
What the plugin sends elsewhere:
- Cloudflare Turnstile, only if the website owner turns on the "prove you're human" check and a blocked visitor chooses to use it. The check loads from Cloudflare in the visitor's browser, and the website sends the resulting one-time token to Cloudflare to confirm it. See Cloudflare's Turnstile privacy addendum.
- Ropeline: nothing. Only the separate Ropeline Pro add-on contacts us; see below.
Ropeline Pro and the Ropeline Network
Ropeline Pro checks its key with our server once a day, sending the key, the website's address, a one-off random number (so our signed answer can't be reused), Ropeline Pro's version and, on a WooCommerce store, how many paid orders it took in the last 30 days (a single number, because store plans are sized by orders). Once a month Pro also checks its own files against the list we signed when we released it, and the daily check says whether they matched and how many didn't (never the files themselves). We keep the latest of each for each website. While the key is live, Pro also connects the website to the Ropeline Network, described below.
What Pro sends to others:
- Have I Been Pwned (haveibeenpwned.com), when someone sets or changes a password, and at most once every 30 days at login. Only the first 5 characters of a one-way scramble (SHA-1 hash) of the password are sent. That isn't enough to work out the password or even the full scramble.
- AI agent operators (such as OpenAI at chatgpt.com), only when a request arrives signed by one of them. Pro downloads that operator's public keys to check the signature. Nothing about the website's visitors is sent.
What we keep about the customer: the email address and plan for each key, so we can send receipts and renewals. The key is emailed to the customer once, when it's made, and the page shown after checkout can show it for its first day. After that we keep only a scrambled (SHA-256) copy of each key, never the key itself. A "Lost your key?" sign-in link is kept the same way, as a scrambled copy, and works once, for 30 minutes; the one in a free-trial email works once, for 3 days. Emails are sent through Cloudflare Email Service.
What each website sends us: its key, its address (for example shop.example.com), and the IP addresses of bots it stopped, with IPv6 addresses cut down to the network block (/64), and what each bot did: a failed-login lockout, card testing, a fake signup, a forged AI-agent signature or form spam. Never names, emails, usernames, passwords, orders, payment details or page contents.
The online dashboard (only if the website's owner turns it on): once an hour, Ropeline Pro sends the website's address, its name and its totals: bots stopped and watched per door this week, AI agents verified and fakes caught, card fees saved, whether learning mode or an attack is on, and the Ropeline, WordPress and WooCommerce versions. Numbers only: never visitors' addresses, usernames, customer details or orders. We keep the latest copy for each website, and each day's last totals for 100 days, so a report can cover up to 12 weeks. Anyone with the key can see them at getropeline.com/dashboard. The key's owner can also make a link that opens one website's report (the same numbers, nothing else) without signing in, for a client; we store only a scrambled (SHA-256) copy of the link, and it stops when the owner turns it off or the plan ends. An agency can put its name on its reports; we keep that name with the key. Turning the dashboard off in the website's settings stops the sending; email us to have the copies deleted.
What we keep: the reported addresses and what they did, deleted after 7 days. We also keep each member website's address, its public key and the network it registered from, for as long as it uses the plan.
What we share: member websites receive the list of addresses that websites on at least three different networks reported in the last day. Each website uses it to give those addresses fewer tries; nobody is blocked outright because of the list alone.
Why: to protect websites and their customers from automated attacks. Under the GDPR, network and information security is a legitimate interest (Recital 49).
Where: on Cloudflare's network (Workers and D1).
Leaving: a website leaves by removing its key, or when its plan ends. Its reports age out within 7 days. To have the rest deleted, email us.
Questions or removal requests: hello@getropeline.com. If you believe your address was listed by mistake, email us and we'll remove it.
Kids
Ropeline is a business product and isn't meant for children under 13. We don't knowingly collect their information.
Changes
If this policy changes, we'll update the date above. Big changes will be emailed to people who signed up for updates first.