RailXBack to RailX

Privacy

Last updated September 9, 2026

RailX collects the information needed to run accounts, projects, API access, and trade-planning services. RailX does not hold customer funds, private keys, or wallet signing authority.

Information RailX receives

  • Account information such as your name, email address, profile image, user identifier, and organization membership.
  • Project and API information such as project names, API-key metadata, permissions, usage totals, and request diagnostics. RailX stores verifiers for API keys, not recoverable key secrets.
  • Product inputs such as public wallet addresses, asset symbols, amounts, policy settings, and unsigned transaction data needed to create and retrieve trade plans.
  • Billing references and subscription state from Stripe. Payment card details are collected and processed by Stripe, not RailX.

Google sign-in

When you choose Google sign-in, RailX receives your basic Google account profile, email address, and account identifier through Clerk. RailX uses this information only to create, secure, and operate your RailX account. RailX does not receive your Google password, request access to Google Workspace data, or use Google user data to train AI or machine-learning models.

How RailX uses information

RailX uses this information to authenticate users, keep projects separated, enforce permissions and usage limits, produce requested trade plans, process subscriptions, prevent abuse, troubleshoot failures, and improve the reliability of the service.

RailX does not sell personal information. RailX shares information with service providers only when needed to operate the product, including Clerk for identity, Neon for database hosting, Stripe for billing, Vercel for application hosting, and market, routing, or blockchain infrastructure used to answer a request.

Retention and security

RailX retains account, project, billing, plan, usage, and diagnostic records for as long as they are needed to operate the service, satisfy security requirements, or meet applicable obligations. Short-lived operational records are removed on scheduled retention windows. RailX limits logs to approved diagnostic fields and does not intentionally place secrets or raw request bodies in request logs.

Your choices

You may ask to access, correct, or delete personal information tied to your RailX account. Some records may need to be retained for security, fraud prevention, billing, or legal reasons.

Contact

For privacy questions or account-data requests, email railxdev@gmail.com.