Rail.Open workspace
The public collection

04 / Data

Data handling notice

Information used by the workspace, session storage, and the limits of demonstration records.

3 min readEdition 1.0Reviewed

Information used by the workspace

The access form uses an operator ID and passphrase to request a session. A payment instruction uses a destination, amount, currency, and reference. The workspace displays available balance information, confirmation references, and activity associated with the active wallet.

Use demonstration identifiers and test instructions. The current demonstration does not request card numbers, bank credentials, identity documents, or contact details.

Session information

The browser stores an essential session cookie after successful access. It lets the service recognize subsequent workspace requests and is not exposed to page scripts. Signing out removes that browser session cookie. A session can also expire or be rejected by the connected service.

This frontend does not currently include advertising trackers or marketing analytics integrations. Cookies and technical request information used by the hosting service may be subject to that service’s own practices.

Demonstration records

Local demonstration accounts, balances, approvals, and activity are temporary. A server restart can clear them. They are test records and should not be relied on as a durable account history, receipt, or financial statement.

Do not put confidential information in operator IDs or payment references. Those values can appear in the workspace and its activity list.

Connected services

When configured, a connected service receives account and payment requests needed to operate the workspace. Its retention periods, account-management process, and privacy obligations must be established separately. This notice does not claim a retention policy or deletion process for a service that has not been configured and assessed.

Scope of this notice

This notice describes information handled by the current interface. It does not describe the handling of real card payments or regulated financial accounts. Before enabling a production service, its applicable privacy information must be provided to the people using it.