DebugInit
Control your data, deployment choices and transition path.
DebugInit defines ownership, portability, source rights, exports, documentation and transition assistance before implementation begins.
Public claims must match implemented controls and verified operational evidence.
Overview
This page is for procurement and legal, deciding what happens to your data, your configuration and your systems if you stop working with us.
The position is set before implementation rather than negotiated at exit: you retain rights to your business data, configuration and metadata are exportable in open formats, and transition assistance is defined in the agreement rather than left to goodwill.
Capabilities
Business-data ownership
Configuration and metadata export
Open data formats and documented APIs
Deployment artifacts by engagement model
Source and customization rights
Model and provider portability
Transition support and knowledge transfer
Clear exclusions for third-party components
Evidence and documentation
Each item below is published here when it exists, with its scope, its date and who produced it. Nothing on this list is claimed today.
- pendingArchitecture and data-flow notes
- pendingPolicies, with their scope and review dates
- pendingThird-party test and audit summaries
- pendingSubprocessor list, with location and purpose
- pendingCompleted security questionnaires
- pendingService status and incident history
Shared responsibility
Where the boundary sits. Agreed before an engagement rather than discovered during one.
| Area | DebugInit | You |
|---|---|---|
| Business data | Stored, exportable, deletable on request | Classification, retention policy and lawful basis |
| Configuration | Exportable in documented formats | The decisions it represents |
| Source and customisations | Rights set per engagement model | Reviewing those terms before signature |
| Transition | Documented procedure and assistance | Naming a receiving party and a date |
Scroll the table sideways to see every column.
Procurement information
Deployment options, support terms, ownership and exit rights, data location, subcontractors and contract documents are provided during evaluation, scoped to the engagement you are considering.
Where your review requires evidence we cannot yet provide, we will say so in writing rather than answer around it. That is a more useful basis for a decision than a confident questionnaire.
Bring your review to us
Send the architecture question, the security questionnaire or the procurement constraint you have to satisfy, and we will answer against what is actually implemented.