Privacy policy

Last updated

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.

If a law uses different labels, such as "business" and "service provider", read the equivalent roles into the above.

What we collect

From merchants

From buyers

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

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 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

How we use it

We use personal data to:

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:

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:

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.