Railbase

Refund Policy

Version: 1.8 Effective date: 18 August 2026

This Refund Policy explains how Silkway Tech LLC, a Wyoming limited liability company with a mailing address at 5830 E 2nd St, Ste 7000 #30294, Casper, WY 82609, USA ("Company", "we", "us"), handles refunds for purchases made through railbase.app — Product and Suite subscriptions, Product Plan changes, and any other paid offerings (the "Service"). It supplements the Terms of Service; if this policy and the Terms conflict, the Terms control.

1. All sales are final

Except where required by applicable law or expressly stated in this policy, fees are non-refundable. There are no refunds or credits for:

  • partial subscription periods, including after cancellation mid-period;
  • unused users, roles, company capacity, quotas, Product functionality, or included Components;
  • downgrades between Basic, Pro, and Max Product Plans;
  • trials that converted to paid subscriptions;
  • dissatisfaction with features that are accurately described on the Product page or documentation;
  • incompatibility with your own environment, infrastructure, or third-party services, since Railbase is self-hosted software that you are responsible for operating.

Business purchases only. The Service is sold to businesses and organizations, not consumers. To the extent permitted by law, statutory consumer withdrawal or "cooling-off" rights do not apply to purchases under the Terms of Service.

2. Try before you buy

Because refunds are limited, we make evaluation free:

  • the Railbase Core is free of charge — after creating an authenticated B2B Account and completing effective company KYC (including optional provider-managed full KYB/KYC only while that control is enabled), you can download, install, and evaluate it on your own infrastructure before spending anything;
  • a Product may offer a trial or guided demonstration only where its Product page or checkout expressly says so. The absence of such an offer does not create a trial right.

Please review the Product description, Product Plan composition, documentation, and any expressly offered evaluation before subscribing.

3. When we do refund

We will refund a charge where:

  • the refund is required by applicable law;
  • the charge was a billing error on our side — for example, a duplicate charge for the same subscription period, or a charge after a correctly submitted cancellation took effect;
  • we discontinue a paid Product or the Service during a period you have already paid for, in which case we refund the unused portion of that period pro rata.

We may, at our sole discretion and without creating any precedent or obligation, issue a goodwill refund or credit in other cases.

4. Effect of a refund on your licence

Components are licence-gated at execution. A full payment reversal, chargeback, or clawback revokes the Product entitlement source associated with the reversed subscription. A partial refund or credit note does not by itself change the Product Plan, Product composition, or access. If a Component included in the affected Product is also supplied by another active Product for the same company, removing one entitlement source does not remove the other; that Component continues under the remaining source's effective rights. Your self-hosted data is not deleted by revocation — it stays in your Vault and may become usable again after a later valid entitlement — but continued Component execution requires at least one active licence source.

Stripe invoice and credit-note documents remain the payment documents of record. railbase.app records refunds and credit notes as immutable negative adjustments allocated across the original invoice's products and taxes. A voided credit note is recorded as a positive reversal; neither event erases the original invoice.

5. Chargebacks

If you believe a charge is wrong, contact us first at support@railbase.app — most billing issues are resolved faster that way than through a card dispute. A chargeback on a valid charge is treated as a material breach: the associated Product and Component entitlements may be revoked and the Account may be suspended pending resolution.

6. Sanctions and compliance holds

Where refunding funds would violate or risk violating sanctions, export-control, or other applicable law — for example, following a positive sanctions-screening result or prohibited destination decision — we freeze movement and open a restricted-funds case instead of issuing an ordinary refund. Once the adverse decision is actually detected, the related server-side access is suspended in the detecting request or sweep, bundle grants stop, and future renewals are stopped without an automatic refund or credit for the suspended period. Missing, inactive, or stale sanctions data alone is not such a positive result: it closes new transaction boundaries but does not itself revoke the current paid-period entitlement or create a refund. A pending, on-hold, resubmission or rejected result from optional enhanced KYB/KYC may likewise suspend distribution or execution while that control is enabled, but does not by itself create a refund, credit or release of funds. A VPN/country-conflict hold before collection is not a charge or refund event.

For money already received, the Company records the amount as a restricted-funds liability pending classification; preserves the tax component; records the payment, screening and decision evidence; contacts Stripe where applicable; determines whether a filing is required; and records the authority, report and custody references in its operator case. Blocked property is not refunded or transferred without an applicable general or specific licence, regulator order, or other legal authorization. A false-positive/no-blocking-interest refund requires a documented legal determination and goes only to the original payment method. We do not use credits, another card, another bank account, an affiliate, or an alternative recipient to route around a restriction. A payment provider's hold, refund capability, or own reporting does not by itself establish that a transfer is lawful or discharge our obligations.

Customer support cannot override this process or promise a date for release. Where law restricts disclosure, the response may state only that the transaction is under compliance review. The detailed classification, regulator filing, Stripe reference, custody record and decision rationale remain in the operator-only case file for the legally required retention period.

7. How to request a refund

Email support@railbase.app from the Account email used for the purchase, with the invoice or receipt identifier, the Product and Product Plan concerned, and the reason for the request. We respond to refund requests within a reasonable period. Approved refunds are issued to the original payment method through our payment provider (Stripe); depending on your bank, the funds typically appear within 5–10 business days.

8. Changes

We may update this policy prospectively. The version in effect at the time of your purchase applies to that purchase. Material changes will be posted here with a new effective date.

9. Contact

Silkway Tech LLC — 5830 E 2nd St, Ste 7000 #30294, Casper, WY 82609, USA · support@railbase.app