Arelvia Studio

Privacy

Data we use

VersionPact uses non-identifying consumer aliases, one public migration source, old and target version labels, a sunset deadline, an evidence standard, bounded readiness declarations, hashed capability tokens, workspace entitlement identifiers, and minimal recovery records to operate and secure one API sunset room. Stripe processes Checkout and payment details; VersionPact receives only the verified entitlement data needed to create and recover the workspace.

Data that is not permitted

Do not enter names, email addresses, customer records, API keys, authorization headers, private endpoints, traffic logs, secrets, or regulated personal information.

Purpose

We use the permitted data only to operate VersionPact, secure access, support the product, and maintain a minimal operational record.

Retention and access

VersionPact retains the purchased workspace and its immutable readiness record to provide and recover access, preserve declaration integrity, secure and troubleshoot the service, resolve payment disputes, and meet legal obligations. The current product does not provide self-service deletion or a configurable retention period. Users should not submit data they cannot permit Arelvia Studio and its infrastructure providers to retain for those purposes.

Sharing

We do not sell participant data. We share data only with service providers needed to operate VersionPact, or when required by law.

Policy approved 2026-08-30.

← Back