Infrastructure & Continuity
Ownership, backups, and migration rights
Ask AI to explain
Get a quick, plain-language summary of this page without all the jargon.
Effective date: July 3, 2026
Provider: Ziteox (“Ziteox”, “we”, “us”, “our”)
1. Purpose
This Infrastructure Ownership & Continuity Agreement defines asset ownership, infrastructure responsibilities, access rights, backup policies, and business continuity procedures for services provided by Ziteox.
This agreement exists to ensure transparency, reduce dependency risks, and provide clear handover procedures when required.
2. Asset Ownership
2.1 Domain Ownership
Clients always retain full ownership of their domain names.
Ziteox does not claim ownership of client domains. We may manage DNS configuration or domain-related technical setup only when authorized by the client.
Clients may update DNS settings or transfer domains to another provider at any time.
2.2 Website & Code Ownership
Unless otherwise specified in a separate written agreement, ownership of the delivered website codebase transfers to the client (or the client’s authorized project manager) once all outstanding project invoices are fully paid.
Ziteox retains ownership of:
- Internal management tools
- Deployment systems
- Automation workflows
- Client portals and dashboards
- Proprietary operational infrastructure
2.3 Third-Party Services
Infrastructure and service delivery may rely on external third-party providers, including but not limited to hosting, storage, CDN, databases, email delivery, analytics, and monitoring services.
A current list of providers used by Ziteox is maintained in our Subprocessors document within the Legal section of our website.
All third-party services remain the property and responsibility of their respective providers.
3. Infrastructure Architecture
Modern web applications often operate across multiple specialized infrastructure providers rather than a single hosting provider.
Depending on project requirements, infrastructure may include:
- Application hosting
- File/media storage
- Database systems
- CDN / content delivery
- Email delivery services
- DNS management
- Monitoring and logging
This distributed architecture improves:
- Performance
- Reliability
- Scalability
- Security
- Fault isolation
Failure in one infrastructure layer does not necessarily impact the entire system.
4. Access & Visibility
Ziteox provides clients or authorized project managers with appropriate access to project-related information through available tools, reports, or support channels.
Access may include:
- Project status
- Hosting/resource usage
- Billing information
- Backup availability
- Export requests
- Deployment status
Access scope may vary depending on the service package.
5. Backup & Recovery Policy
5.1 Backups
For eligible hosted services, Ziteox maintains regular backups where technically applicable.
Standard backup policy:
- Backup frequency: Daily or scheduled based on project needs
- Minimum retention period: 14 days
Some systems may use provider-level backups managed by third-party infrastructure vendors.
5.2 Recovery
In case of data corruption, deployment failure, or service disruption, Ziteox will attempt restoration using the latest stable backup.
Recovery time depends on:
- Incident severity
- Provider availability
- System complexity
Recovery timelines are not guaranteed unless explicitly defined in a separate SLA.
6. Vendor Lock-In Policy
Ziteox does not intentionally create vendor lock-in.
Clients may migrate away from Ziteox at any time, subject to payment settlement and applicable contractual obligations.
Upon request, clients may receive:
- Website code export
- Database export (where applicable)
- Backup files
- Migration documentation
- DNS transition guidance
Migration assistance beyond standard exports may incur additional fees.
7. Business Continuity
Ziteox is committed to long-term service continuity.
To reduce dependency on any single individual, operational processes are designed around:
- Documentation
- Backup systems
- Infrastructure records
- Export procedures
- Operational workflows
This helps ensure project continuity even during unexpected disruptions.
8. Service Handover & Exit Plan
If Ziteox becomes unable to provide services for 30 consecutive days without prior notice, clients or authorized project managers may request a handover of accessible project assets.
Where technically possible, handover may include:
- Latest available project files
- Exported data
- Backup files
- Migration-related documentation
This allows another technical provider to continue operations if necessary.
9. Security & Maintenance
Ziteox follows industry-standard security practices appropriate to project scope.
Security measures may include:
- Dependency updates
- Security patches
- Access control
- Secret management
- Monitoring and logging
- Backup verification
No infrastructure can guarantee absolute security.
Ziteox continuously works to reduce risks and respond to incidents as efficiently as possible.
10. Third-Party Service Disclaimer
Ziteox builds and manages infrastructure on top of third-party providers listed in our Subprocessors document.
While we carefully select reliable providers, service availability may partially depend on those providers.
Ziteox is not liable for outages, service interruptions, or failures caused directly by third-party systems outside our reasonable control.
This includes, but is not limited to:
- Hosting outages
- DNS failures
- CDN downtime
- Cloud provider incidents
- Email service outages
- Force majeure events
11. Acceptance
By purchasing or using hosting, infrastructure, maintenance, or development services from Ziteox, the client acknowledges and accepts this agreement.