Effective Date: June 12, 2026 · Version: 2.0
This Customer Agreement governs the terms under which Mirava acts as your service provider to manage regional pricing on your behalf across the platforms you connect (the Apple App Store, Google Play Store and, when supported, Stripe). It forms part of, and should be read together with, our Terms of Service.
Where this Agreement describes how connected credentials are stored, protected and deleted, those statements are the binding commitments in force for connected accounts — not a claim that any particular credential is already stored. You decide what to connect and when, and you can revoke access at any time.
Mirava acts solely as your service provider and agent. Every action Mirava takes on a platform is authorized by, and attributable to, you. You remain the principal and the party responsible for the pricing changes made through the service, and you can revoke access at any time.
2.1 Mirava acts solely as your Service Provider and agent in connecting to the Platforms and managing your regional pricing. Mirava does not act as an independent principal and does not make pricing decisions in its own right. Every action Mirava takes on a Platform is authorized by, and attributable to, you.
2.2 You remain the principal and the responsible party for all activity Mirava performs on your behalf, including all pricing changes, and remain bound by your own agreements with each Platform (the Apple Developer Program License Agreement, the Google Play Developer Distribution Agreement, and Stripe’s agreements, as applicable).
2.3 Mirava uses the Platform Credentials only on your behalf and only in accordance with the applicable Platform terms. Mirava will not use a Service Provider relationship to submit applications to the App Store or to use TestFlight on your behalf (the express carve-outs in section 2.9 of the Apple Developer Program License Agreement), and does not perform those actions.
3.1 Your use of Mirava with respect to Apple is subject to terms at least as restrictive of, and as protective of, Apple as those in the Apple Developer Program License Agreement. Your obligations to Apple flow through to Mirava’s handling of your Apple Platform Credentials and Apple-directed actions.
3.2 Mirava will safeguard the Platform Credentials: encrypted at rest, isolated to your organization, with least-privilege scopes, rotation support, instant revocation, and deletion on disconnect and on account closure. These commitments are described in further detail on our Security page.
3.3 Mirava will not transfer or sub-share your Platform Credentials to any further third party except subprocessors strictly necessary to provide the service (for example, the cloud infrastructure that will host the encrypted store), each bound by obligations no less protective than these.
4.1 For Google Play, you authorize Mirava to manage pricing and monetization on your behalf. Mirava’s authorization and actions are limited to pricing and monetization management and do not extend to publishing applications on your behalf.
5.1 You may authorize Auto-Pilot, under which Mirava executes pricing changes according to the policy, guardrails, and limits you configure, including on a schedule and without a separate confirmation for each change.
5.2 By enabling Auto-Pilot, you pre-authorize those changes and acknowledge that each automated change is made on your behalf and remains your responsibility, to the same extent as if you had made it directly.
5.3 Mirava executes the policy you configure; you are responsible for the policy you set and the pricing outcomes that result. To the maximum extent permitted by law, Mirava is not liable for pricing outcomes arising from a policy you authorized, save for Mirava’s own failure to operate the service as described. You can revoke Auto-Pilot and disconnect at any time.
6.1 You may revoke Mirava’s access and disconnect any Platform at any time. On revocation Mirava stops acting on that connection, and the associated Platform Credentials are deleted when you disconnect and when your account is closed. Revoking access does not revert pricing changes already made on your behalf; it stops Mirava from making further changes for that connection.
6.2 Mirava will maintain an audit trail of actions taken on your behalf (the action, the time, the Platform), providing accountability and supporting your visibility into, and responsibility for, those actions.
7.1 When Mirava supports Stripe under an agent-only or Standard-Connect direct-charges posture, Mirava acts on your own Stripe account and is not the merchant of record. You remain the merchant of record and retain ownership of your catalog, settlement, refunds, chargebacks, and disputes.
7.2 If Mirava ever offers a posture in which it is the merchant of record, that posture requires different, explicit terms and is not covered by this section. This section must not be construed to make Mirava the merchant of record.
This Agreement is presented to and accepted by you in-product, and your acceptance is recorded together with the version and the time. If this Agreement materially changes, you will be asked to re-accept the current version before continuing to use connected features.
This Customer Agreement should be read together with the documents that govern your use of Mirava and how we handle your data:
Last updated: June 12, 2026 · Version 2.0