This is the formal policy for how RVA Wallet is developed, tested and released to production, ensuring compliance with Apple App Store, Google Play, MoonPay and KuCoin requirements.
Applies to: RVA Wallet mobile apps and backend wallet services
The purpose of this Release Policy is to ensure that every change to RVA Wallet is delivered in a controlled, auditable and secure manner. It defines how code moves from development to production, how we minimise risk during each release and how we coordinate changes that affect third party partners and app stores.
This policy covers RVA Wallet mobile applications for iOS and Android, the RVA Wallet backend services that support those applications, and integrations between RVA Wallet and certain third party services, including MoonPay for on and off ramp flows and KuCoin connectivity where applicable.
Security is the primary consideration. Changes affecting auth or payments are reviewed and validated against security findings before production.
Designed to comply with Apple App Store, Google Play, MoonPay and KuCoin requirements regarding data handling and disclosures.
We follow a predictable cadence, grouping non-urgent changes. Emergency fixes use a separate accelerated process.
Releases are monitored for error rates and user impact. If regression occurs, we pause or rollback immediately.
| Release Type | Description | Typical Contents | Approval Level |
|---|---|---|---|
Major release | Large scale update (new modules, networks, major UX). | New features, redesigns, reg updates. | Product, security & engineering leadership. |
Minor release | Regular incremental update. | Feature improvements, non-breaking API changes. | Product owner & engineering lead. |
Patch or hotfix | Targeted update to fix a critical issue. | Security fixes, crash fixes, urgent updates. | Engineering lead & security sign-off. |
RVA uses semantic versioning (major.minor.patch). Public store versions are aligned with these types and kept consistent between iOS, Android and backend where possible.
Code changes move through a series of controlled environments before reaching production. All changes are first developed and tested in non-production environments isolated from live user data.
A staging environment is used to validate release candidates using builds that closely match the production configuration. Only release candidates that have passed defined quality gates are promoted to production.
Automated unit tests and integration tests
Manual QA on supported OS versions & devices
Security checks on auth, keys & payments
App Store & Google Play policy verification
Regression testing of MoonPay & KuCoin flows
iOS submissions via App Store Connect align with App Review Guidelines. Metadata, privacy labels, and permissions are kept consistent with actual app behavior.
Android releases use staged rollouts to reach a small percentage of users first, identifying issues early before full deployment.
Store listings are reviewed for accuracy. Data sharing disclosures are updated consistent with latest Apple and Google rules.
MoonPay provides regulated on/off ramp services. Changes to flows are tested in non-production first. API keys are rotated securely.
Releases affecting trading or price feeds are planned to avoid impact. We monitor API usage and respect maintenance windows.
We use phased rollout features to initially expose new versions to a subset of users, expanding only if no material issues are detected.
Each release is observed for error rates, crash reports, backend latency, and success rates for third-party flows.
If monitoring indicates a serious regression, security issue, or loss of functionality, RVA pauses the rollout or submits a corrective update immediately.
If a critical vulnerability or security incident is identified, RVA initiates an emergency release. The issue is triaged and risk-assessed by security and engineering teams. A minimal, targeted fix is developed to resolve the issue without introducing new changes.
Normal quality gates are followed with priority given to security validation. Accelerated submission flows available through Apple and Google are used where appropriate. Backend fixes can be deployed directly to production after non-production testing.
RVA is committed to transparency. Release notes describe main user-facing changes. Material changes to privacy or data processing are disclosed via in-app messaging. Extended service disruptions are communicated via official status channels.
This policy is owned by RVA technology leadership and reviewed annually. Each release is logged with a unique ID, date, environment, changes, and approvals.
Last updated: 21st November 2025