Service Availability, Provider Changes & Migration Policy
Provider-neutral rules for service continuity, provider replacement, migration and retirement.
1. Provider-Neutral Architecture
X2 may use independent providers for distribution, storage, payments, verification, analytics, rights infrastructure, social integrations, cloud infrastructure, communications and other functions. Providers are service components or adapters and do not define customer ownership or X2 identity.
2. Canonical X2 Data
X2 may maintain canonical internal records for catalog, rights, identifiers, metadata, delivery state, verification state, reporting and other operational information independently of any single provider.
3. Provider Changes
X2 may add, replace, remove or reconfigure providers for reliability, security, cost, performance, geographic coverage, compliance, scalability or product development.
4. No Ownership Transfer
Changing a provider does not transfer ownership of customer content, masters, compositions, publishing rights, catalog records or customer identity.
5. Migration
Where appropriate, X2 may migrate metadata, files, delivery routing, reporting connections, credentials or service configuration between provider components.
6. Service Continuity
X2 aims to maintain reasonable continuity, but migrations may cause delays, synchronization differences, status changes, reporting gaps or temporarily limited functionality.
7. Emergency Changes
Accelerated provider changes may occur after security incidents, outages, provider termination, legal restrictions, sanctions, urgent compliance risk or material infrastructure failure.
8. Distribution Migration
During distribution migration, canonical catalog records should remain in X2, identifiers should be preserved where appropriate, duplicate deliveries should be avoided and provider-specific takedown or redelivery procedures may be required.
9. Payment Provider Migration
A new financial provider may require renewed KYC or KYB, beneficiary verification, new payout methods, acceptance of provider terms or different currency support. Accrued eligible entitlement does not disappear solely because X2 changes financial providers.
10. Rights and Analytics Migration
Rights history should remain distinct from technical provider changes. Analytics from different sources may use different definitions and may not be directly comparable across provider changes.
11. API Versioning
X2 may introduce new API versions and deprecate old versions. Material breaking changes may receive reasonable notice where practicable.
12. Service Retirement
X2 may retire a feature where provider support ends, technology becomes obsolete, legal requirements change, usage no longer justifies operation or replacement functionality is available, subject to contractual obligations.
13. Migration Does Not Rewrite History
Technical migration must not silently alter rights ownership, historical shares, financial history or verification history.
14. Customer Action
Some migrations may require reconnection, renewed OAuth authorization, updated payout information, acceptance of new provider terms or review of migrated data.
15. No Implied SLA
General X2 access does not create an implied guaranteed service-level agreement. Enterprise services may have separate written availability commitments.