Data ownership and control
What stays in the customer estate and what railbase.app needs to operate the contract.
Updated
Ordinary Suite records, files, approvals and audit history live in the customer's private Railbase estate. Vault is the primary single-file NoSQL data store; uploaded file storage uses the configured customer storage destination.
railbase.app stores only the account, legal-company verification, billing, entitlement, release, installation-health and support information needed to operate the commercial relationship and managed distribution path. The Privacy Policy describes those categories and retention rules.
A screening-data outage is an availability incident, not a detected sanctions match. It does not by itself cancel or revoke a current paid-period entitlement. Railbase continues signed licence validation through a heartbeat whose rolling window is no longer than 24 hours; a confirmed hit follows the separate suspension and review process described in the Terms.
Ending a subscription
Ending a Product stops renewal and, after the applicable term and grace rules, stops entitled Suite operation. It does not silently delete the customer's stored records. Export, retention and deletion duties remain subject to the Product agreement, Order and customer's own data-governance policy.
Portability
The customer controls backup copies of its Vault and configured file storage. Restore procedures, secrets and encryption keys must be maintained in the customer runbook. Account data held by railbase.app can be exported through the Account lifecycle controls described in the Privacy Policy.
FAQ
Can Railbase use our operating data to train a public model?
Not by default. AI use follows the provider and policy configured in the private estate and the applicable agreements. See AI privacy.
Does non-renewal hold our records hostage?
No. The Product entitlement ends, but stored records remain in the customer environment for the customer to govern and export.