Portability & Exit

A company earns trust more credibly when customers can understand how to leave.

Design goals

• Clear export paths for customer-controlled content where technically applicable.
• Documented migration paths for domains, sites, data and integrations.
• Reasonable API and format documentation so a customer is not trapped by obscurity.
• Supplier contracts that consider continuity and exit, not only onboarding.
• Separation between authentication, billing, data and product-specific services to reduce unnecessary lock-in.

Telecom and regulated services

Number portability, migrations and termination processes must follow the applicable operational and regulatory frameworks. We will describe exact procedures once the corresponding service is live.

QUARK rule

Convenience is not consent to permanent dependence.