Privacy policy
This policy explains how Railbed, LLC ("Railbed", "we" or "us"), handles personal data across the website at https://railbed.com, the merchant dashboard at https://app.railbed.io, the hosted checkout, the API, webhooks, connected AI assistants and the Railbed for Chrome browser extension. We do not sell personal data. Where this policy says "you", it means whichever of the following you are.
Who we are and our role
Railbed deals with three kinds of people, and our role differs for each.
- Merchants use the dashboard and API to accept payments. For merchant account data, Railbed is the controller: we decide what is collected and why.
- Buyers pay a merchant through a Railbed checkout. The merchant is the business you are dealing with and is the controller of your checkout data. Railbed processes that data on the merchant's behalf, under its instructions and these terms. The on-ramp provider that charges your card is a separate controller for the card payment itself.
- Visitors browse https://railbed.com. For what we process about visitors, Railbed is the controller.
If a law uses different labels, such as "business" and "service provider", read the equivalent roles into the above.
What we collect
From merchants
- Business name and logo, and your account email address. You sign in with Google, GitHub or an email code through our sign-in provider; Railbed stores no password.
- Your name and profile photo. When you sign in with Google or GitHub, we copy the name and picture from that account into your profile, unless you have already set your own; you can change or remove them in Settings.
- The Polygon wallet address you give us for payouts, the name of the wallet app it was connected from (if you used Connect a wallet), and the balance we read from the public blockchain to display it. If you save other payout wallets, their addresses, the names you give them and, for networks with their own kind of address (such as Bitcoin), the network.
- Optional settings: a support email address shown to buyers and a checkout brand colour.
- Your business's website address, if you give it, and the brand we read from its public pages: logo, brand colour, fonts and the name the site shows. If you haven't given one, we may find it from your connected Shopify store, your WooCommerce store's address, a checkout's return address or your account email's domain (never a free email provider's). While you first set up your account, the brand read from your website becomes your starting look, which you can change before anything goes live; after that, a brand we read is only suggested until you choose to use it.
- The checkouts and payment links you create, including product names, descriptions and prices.
- API keys, stored only as SHA-256 hashes, and usage records such as when a key was last used.
- Webhook endpoint URLs and their signing secrets, and delivery records for each webhook attempt.
- Records of your use of the dashboard and API, and messages you send us.
- If you turn on two-factor sign-in: the authenticator key, stored encrypted, your recovery codes, stored only as hashes, and when you turned it on and used it. We never show the key or codes again after setup.
- If you connect Slack: the workspace's ID and name, the Slack IDs of the app and of the people who connect their Railbed login, the channels you choose for alerts with their settings, and the app's access tokens, which are stored encrypted. Railbed does not read your channels' messages. Alerts waiting to be sent hold only what the alert shows, and are cleared once sent.
- If you connect an AI assistant: the approved sign-in and client identifiers, business, Test or Live mode, access level, approval and revocation records, and the arguments of changes you prepare for review. The assistant sends the arguments of the tool it uses; Railbed does not request its full conversation history.
From buyers
- The email address you enter at checkout.
- The payment: amount, currency, description or reference, the provider you chose, its status, and the on-chain transaction IDs once it settles.
- Order and customer details supplied by the merchant's integration, such as name, email, phone, shipping and billing addresses, purchased items, store identifiers and fulfilment status.
- The country derived from your IP address, which Smart Routing uses to rank providers.
- When you start a payment, what your browser and connection tell us about you at that moment: your IP address and the country Cloudflare reads from it, the device type and model, the browser and operating system with their versions, and the full browser identification string (up to 400 characters) your browser reports, the first language it asks for, and your time zone. Railbed keeps them with the payment and shows them to the merchant with it, and counts them in the merchant's reports. The merchant's webhooks and API don't carry them, and they are deleted when the merchant deletes you as a customer. A checkout that starts from a merchant's Shopify store keeps the IP address and browser with that checkout, for the merchant's purchase reporting described in Shopify checkout tracking.
You enter your card or wallet details on the provider's page, not ours. Railbed never sees or stores card numbers.
Website and dashboard analytics
- Google Analytics. On railbed.com, railbed.io and the dashboard at https://app.railbed.io, Railbed uses Google Analytics, with Google signals and Google's advertising features (reports on demographics and interests) where consent allows. Google receives the pages you view with their full addresses, including the dashboard's (such as the address of a payment you open), except search terms typed in the dashboard and secrets such as sign-in codes, invitation tokens and keys; your device, browser and screen size; your approximate location, which Google works out from your IP address; how you arrived (the referring site, search engine or campaign link); and how you interact with pages (for example scrolling, clicks such as on sign-up and contact buttons, downloads, searches on our docs, copying code samples and the dashboard features you use). In the dashboard it also receives an opaque user ID derived from your Railbed account, so your visits from different devices count once, with your role and broad facts about the business, such as its main way to sell. Railbed doesn't send Google email addresses, names or phone numbers. Google Analytics' script and most of the data it sends go through a path on our own addresses (railbed.com, railbed.io and https://app.railbed.io), which forwards them to Google with your IP address and the approximate location Cloudflare reads from it: the same details Google gets when your browser contacts it directly.
- Google signals and advertising features. For people signed in to a Google account that allows it, Google links visits across devices and adds demographic and interest reports, which Railbed sees only in aggregate, never who the people are. Where consent allows, Google may set advertising cookies and use this data for its own advertising services, under its terms and privacy policy.
- Google Analytics cookies and your choice. Google Analytics sets
_gaand_ga_QBLW790VRM, which last two years, and, where consent allows, any advertising cookies Google uses. For visitors in the European Economic Area, the UK and Switzerland, all of this starts off until you turn it on; until then Google Analytics sets no cookies and receives only cookieless signals without an identifier, which Google uses to estimate visits. If your browser sends a Global Privacy Control signal, Google Analytics doesn't run until you turn it on. Everywhere else it starts on. You can change your choice at any time: for the website in the cookie policy, and in the dashboard under Settings. Both keep it in a strictly necessaryrb_gacookie. Turning Google Analytics off stops it and removes the Google Analytics cookies already set, on the website and in the dashboard, and from then on our addresses forward nothing to Google for that browser. - Google Tag Manager. On railbed.com and railbed.io, Railbed also loads Google Tag Manager, under the same choice as Google Analytics. It loads through a path on our own addresses, which passes the request to Google with your IP address, browser details and the approximate location Cloudflare reads from your IP address. On the page, Tag Manager is given the pages you view and what you do on them, as our own measurement records them (below), without email addresses or phone numbers. It sets no cookies of its own and holds no tags, so it sends none of this anywhere; a tag added later is listed here before it runs.
- Reddit ads. Railbed advertises on Reddit and measures those ads with the Reddit Pixel and Reddit's Conversions API, under the same choice as Google Analytics. On railbed.com and railbed.io the pixel tells Reddit which pages you view; in the dashboard it runs only on the sign-in and sign-up pages, inside a separate empty page, so it never sees the dashboard's pages, forms or records. Reddit receives the page's address, your browser and device details and IP address, and the ID of the Reddit ad you clicked, if you came from one. When you create an account, and when your business takes its first Test or first Live payment, Railbed's server tells Reddit that it happened, with your email address hashed, an opaque ID derived from your Railbed account, the pixel's browser ID and ad click ID, and the IP address and browser of your latest sign-in (or of the dashboard visit where you turned it on), so Reddit can match it to an ad. It never receives your name, a payment's amount or anything about buyers. The pixel sets
_rdt_uuidand, after an ad click,_rdt_cid, which last 90 days. For visitors in the European Economic Area, the UK and Switzerland, none of this happens until you turn it on; a Global Privacy Control signal or your Off keeps it off, and Off removes the pixel's cookies. Reddit handles this data under its own terms and privacy policy, including for measuring and improving ads. - Our own measurement. Railbed also measures its website, dashboard and hosted checkout itself. It sets no cookies and stores nothing on your device. Pages send us the pages you view with their real addresses (secrets such as sign-in codes, tokens and keys are removed first), the full address of the page that referred you, campaign tags, what you do on the website, in the dashboard and at checkout (including searches, and the checkout or payment a buyer was on), a device class worked out from the window's width, and the country of the connection. Dashboard events also carry your account and business, because you're signed in. Our measurement also records what you type, choose, paste and copy in our forms, except passwords, secrets such as keys and sign-in codes, and card numbers; Google Analytics and Reddit never receive any of it. To count visitors, our server combines your IP address and browser with a secret that changes every day and is deleted after two days, so the result can't follow you from one day to the next, and your IP address isn't stored. This measurement runs whatever you choose for Google Analytics, and also when your browser sends Global Privacy Control, because it uses no cookie, stays with Railbed and is shared with no third party. Raw events are deleted after 90 days; daily totals are kept.
- How you found us. When you create an account, we keep with it where you came from (the referring site or campaign, the ID of the ad you clicked if you came from one, and the first page of our website you visited) and, if Google Analytics was on, Google Analytics' ID for your browser and the Reddit match details described above, so the sign-up and milestones such as your business's first payment can be counted in Google Analytics and Reddit.
- Cloudflare Web Analytics. Cloudflare, which hosts Railbed, counts page views and load times on our website without cookies or identifiers. Visitors in the European Union aren't included.
Shopify checkout tracking
A merchant who sells through a Shopify store can set up its own ad and analytics tags in Railbed: Google Analytics, Google Ads, Google Tag Manager, Meta, TikTok or its own tag code. When it has, and the store's cookie consent allows it, that store's checkout pages on pay.railbed.io (the checkout at pay.railbed.io/s/… and the payment page that follows) load those tags. Before they load, the page copies the tags' cookies from the merchant's store onto pay.railbed.io only (the cookie policy lists them), so the tags recognise the same browser and ad click. The tags receive the checkout's steps, the basket and its value, and the buyer's contact and address details for matching the purchase to an ad (Meta's, Google's and TikTok's tags hash them before sending). Once the payment is paid, Railbed's server reports the purchase to the services the merchant connected (Meta's Conversions API, TikTok's Events API, Google Analytics, and a postback address the merchant chooses), with the buyer's contact details hashed and, where a service uses them, the checkout's IP address and browser and the ad click and campaign details captured on the store. The merchant chooses these services and is the controller for this data; each service handles it under its own policies. Test-mode checkouts load none of this, and Railbed's other checkout pages load no third-party analytics or ad tags.
From the Railbed for Chrome extension
Railbed for Chrome is a browser extension for merchants. It reads a web page only when you open it on that page, with its toolbar icon, its keyboard shortcut or its right-click menu, and only that page.
- The page you open it on. The extension reads the page's text on your computer to find a selected price, email addresses and Railbed payment, order and customer numbers. It sends Railbed only those email addresses and numbers, with your key, to look them up in your own account. It doesn't send, store or keep the page's text, its address or anything else on it. Looking an email address up doesn't add it to your account; like any API request, the look-up is in the request records described under "From everyone".
- Payment links you make with it. The amount, currency, description and buyer email address you enter, as for any payment link you create.
- Sign-in. When you approve the extension in the dashboard, Railbed creates a Test key and, if you choose, a Live key for it, named for the extension in Developers, and records the approval as it does for AI agents.
- On your computer. The extension keeps the business you signed in to, its keys, the payment links you made with it until each is paid or ends, your alert setting and the last currency you used, in Chrome's storage on your computer. Chrome doesn't sync them.
The extension doesn't measure how you use it, shows no ads, and sends nothing to anyone but Railbed. Railbed's use of information received through the extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements: we use it only to provide the extension's features, never sell it, never use it for advertising or to decide creditworthiness, and never let people read it except with your agreement, for security, or to comply with the law.
From everyone
- IP addresses and request details, used transiently for security and rate limiting, and processed in request logs by our hosting provider.
- Emails you send to any of our addresses.
How we use it
We use personal data to:
- run the service: create accounts, sign merchants in, publish checkouts, create and track payments, deliver USDC to the right wallet and send webhooks
- route each buyer to a suitable provider, using the amount and the buyer's country
- show merchants who started each payment (device, browser, language, time zone, country and IP address) and count them in their reports, so they can recognise their buyers and spot unusual payments
- pass a buyer's email address to our payment infrastructure partner and to the chosen on-ramp provider, because they need it to create the payment and send receipts
- keep the service secure: detect abuse, enforce rate limits, verify signatures, investigate incidents
- enforce our terms of service and acceptable use policy
- run Railbed for Chrome: look up the payments, orders and customers named on the page you open it on, create the payment links you ask for, and tell you when one is paid
- answer support, privacy and legal enquiries
- understand how people find and use Railbed, and improve the website, the docs, the dashboard and the checkout
- on behalf of merchants who sell through Shopify and set it up, report checkout steps and purchases to their ad and analytics services
- meet legal obligations, including tax, accounting, sanctions and anti-money-laundering requirements, and respond to lawful requests from authorities
- send merchants service messages about their account, such as security notices and changes to these terms
Where a data-protection law asks us to name a lawful basis, we rely on performance of a contract (providing the service to merchants and, on their behalf, to buyers), our legitimate interests (security, abuse prevention, running and improving the service, defending legal claims), compliance with legal obligations, and consent where we ask for it, such as for Google Analytics and the Reddit Pixel in the European Economic Area, the UK and Switzerland. We do not use personal data for profiling that has legal effects on you. How Google and Reddit may use analytics and ad data for advertising is described in Website and dashboard analytics.
Who we share it with
We share personal data only with the parties needed to provide the service, by category:
- Cloud hosting and security. Cloudflare hosts the service, screens traffic and processes request logs.
- Brand matching. To read a business's brand from its website, Railbed either reads the site's public pages itself or asks context.dev, which receives the website address and reads the same public pages. It receives no other account or buyer data.
- Fonts. When a checkout uses a Google font, Railbed fetches the font files from Google Fonts and serves them from its own servers, so buyers' browsers never contact Google for them and Google receives no data about buyers.
- Sign-in. WorkOS runs merchant sign-in and receives your email address, name and sign-in details; Google or GitHub take part when you sign in with them.
- Email delivery. Resend sends Railbed's own account emails (for example payout wallet changes and payments that need a decision) and receives the recipient's email address and the email's content, plus delivery results such as bounces.
- Wallet connection. When you choose Connect a wallet in the dashboard, your browser contacts WalletConnect (Reown) to list wallets and relay the connection, and Coinbase if you use Base Account. They receive your wallet address and technical connection data under their own privacy policies. Railbed sends them nothing else and asks for no signature or transaction.
- Payment infrastructure providers. Our payment infrastructure partner receives the payment amount, the buyer's email address and the merchant's payout wallet address to create the forwarding address and deliver the funds.
- Licensed on-ramp providers. The provider a buyer chooses receives the buyer's email address and the payment details. It collects card and identity information directly from the buyer under its own privacy policy.
- Analytics. Google receives the Google Analytics data described in Website and dashboard analytics and handles it under its own terms and privacy policy, including, where consent allows, for its advertising services.
- Advertising. Reddit receives the Reddit Pixel and Conversions API data described in Website and dashboard analytics and handles it under its own terms and privacy policy.
- Merchants' ad and analytics services. On a merchant's Shopify checkout with tracking set up, the services the merchant chose receive the data described in Shopify checkout tracking.
- Public blockchain RPC providers. We query the Polygon network to read wallet balances and confirm settlements. Only wallet addresses and transaction IDs are involved.
- Merchants. Each merchant receives the checkout data of its own buyers: email address, amount, reference and status, and in the dashboard the device, browser, language, time zone, country and IP address each payment was started from.
- Slack. If you connect Slack, Slack (Salesforce) receives what Railbed posts there at your request: payment alerts, daily reports, account notices and payment links, which can include a buyer's name, email and what they bought if the channel's settings show them, and the replies to your commands. Everyone who can see the channel, including guests, can read them. Slack handles them under its own terms and privacy policy.
- AI assistants you connect. At your request, a connected assistant and its provider receive the results of the tools it calls within the business, mode and access you approved. Depending on the task, results may include payment and settlement records, order items, customer contact/address details, checkout links, and webhook delivery outcomes. Public documentation tools return public information only. Account tools do not return API keys, signing secrets, provider credentials, private staff notes or webhook receiver query values. Your assistant provider handles returned information under its own terms, privacy policy and account settings.
- Professional advisers and authorities. Lawyers, accountants and auditors under confidentiality, and regulators, courts or law enforcement where the law requires or allows it.
- A successor. If Railbed, LLC is involved in a merger, acquisition or sale of assets, personal data may transfer to the successor under this policy.
We do not sell personal data, and we do not share it with data brokers.
The dedicated Railbed Reporting plugin returns a narrower set: the approved business and mode, a profile identifier and optional display name, payment and order IDs, times, payment method and reported settlement amounts, payment statuses, order numbers/states/totals, the connection's name and state, and webhook endpoint IDs and delivery outcomes. It omits buyer payment links, customer contact/address details, free-form payment descriptions/references, merchant metadata, webhook receiver URLs and payout destinations. It does not prepare business changes. Public reporting documentation requires no sign-in. Reporting access and limits.
You can disconnect an MCP assistant in Developers → AI assistants. Its next account request is refused and unconfirmed proposals are canceled. Disconnecting does not recall results already sent to the assistant, erase the provider's copies or reverse a change already executing. Browser-based WebMCP tools use the signed-in page's session and are available only while that page offers them. See the MCP guide for the access and review controls.
Public blockchain data
Settled payments are recorded on the Polygon blockchain: the forwarding address, the merchant's wallet address, the amount and the transaction ID. That record is public, permanent and outside anyone's control, including ours. It contains no names or email addresses. A wallet address can still be linked to a person by anyone who knows the connection. Deletion requests cannot remove data from the blockchain.
Cookies and local storage
The website and the dashboard use Google Analytics cookies while Google Analytics is on, and the Reddit Pixel's cookies under the same choice, as described above. The dashboard also uses a strictly necessary session cookie, a strictly necessary cookie that keeps your Google Analytics choice, a referral cookie when you arrive through a partner's referral link, and browser storage keys for your settings. Railbed's own measurement uses no cookies anywhere. Checkout pages set no cookies, except a merchant's Shopify checkout with tracking set up, which carries that merchant's ad and analytics cookies as described above. The cookie policy lists each item and lets you change your choice. Railbed for Chrome sets no cookies; it keeps its sign-in, keys and settings in Chrome's extension storage on your computer, as described above.
International transfers
Railbed runs on a global network, and our providers and partners operate in various countries. Your personal data may therefore be processed in countries other than your own, including countries whose data-protection laws differ from yours. Where the law requires it, we rely on appropriate safeguards for those transfers, such as contractual clauses approved for the purpose, and you can ask privacy@railbed.com for more information about them.
Retention
We keep merchant account data while the account is open. After an account is closed, we keep what is needed for legal, tax, accounting, fraud-prevention and dispute purposes, and delete or anonymise the rest. Payment records are kept on the same basis, because merchants, providers and authorities may need them for disputes and compliance well after the payment. Request logs are held by our hosting provider under its own retention rules. Our own analytics events are deleted after 90 days, leaving only daily totals; where an account came from, and its Google Analytics ID, stay with the account. Google Analytics keeps event-level data for at most 14 months. A brand read from a website is kept for 30 days so it can be reused, then deleted, unless you use it. Data on the public blockchain is permanent and is not held by us.
When you disconnect Slack, or remove the app in Slack, Railbed deletes the workspace's connection, its people, channels and unsent alerts at once; our database provider's point-in-time recovery can restore deleted rows for up to 30 days, after which they are gone. Sent alerts have no stored content; we keep only delivery records for up to 7 days. Messages already posted in Slack stay in Slack under your workspace's own retention settings.
Railbed for Chrome's data on your computer stays until you sign out or remove the extension; signing out deletes its keys from Chrome. To stop the keys working, revoke them in Developers. Look-ups through the extension leave only Railbed's usual request and key usage records.
MCP approval records remain while their connection is active. Proposed changes expire after 15 minutes; their input is cleared when execution begins, on cancellation or by scheduled expiry cleanup. Minimal operation receipts are scheduled for deletion after 90 days. Disconnected or expired unapproved connections are also removed by bounded cleanup after 90 days, once no retained operation requires them. The MCP server does not log raw tool request or result bodies. Information already returned to an assistant follows that provider's separate retention and deletion controls.
Security
We protect personal data with HTTPS everywhere, provider-managed sign-in, encrypted sessions, hashed API keys, signed webhooks, verified payment notifications, rate limiting and access controls. Connected MCP assistants use resource-bound OAuth credentials and current business-role checks. The security page describes these in more detail. No system is perfectly secure, and you should keep your sign-in, keys and wallet safe.
Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you and receive a copy
- correct data that is inaccurate or incomplete
- delete your data, subject to the retention needs above and the limits of public blockchains
- receive your data in a portable format
- object to, or ask us to restrict, certain processing
- withdraw consent where processing is based on consent
- complain to a data protection authority
To exercise a right, write to privacy@railbed.com. We may need to verify your identity before acting, and we will respond within the time the law allows. We do not discriminate against anyone for exercising their rights.
If you are a buyer, the merchant you paid is the controller of your checkout data, so contact the merchant first. You can also write to us, and we will help or pass the request to the merchant as appropriate. Requests about your card payment or identity check go to the provider that charged you.
Children
The service is for businesses and adults. We do not knowingly collect personal data from anyone under 18. If you believe a child has provided data to us, contact privacy@railbed.com and we will delete it.
Changes
We may update this policy. The date at the top shows the latest version. For material changes we will notify merchants at their account email address or in the dashboard before the change takes effect.
Contact
Privacy questions and data requests: privacy@railbed.com. Other questions: see the contact page.