# Hosting, maintenance and renewal policy Draft templates only. Professional legal review under applicable Israeli law is required before binding use. These documents are not legally approved. Draft version: 2026-11-10 / draft-4 Service allocation for development, managed hosting, existing websites and maintenance-only arrangements. ## 1. Development, hosting and maintenance choices The quotation may provide development-only delivery, development with an external host, hosting managed by BTNXIO, deployment to customer-owned hosting, use of a customer-owned domain, domain registration assistance or ongoing domain administration. It may instead cover hosting or maintenance of an existing site, migration to BTNXIO, migration away from BTNXIO, maintenance alone, or a custom combination. Each chosen service has its own responsibilities and charges. Developing a website does not require buying BTNXIO hosting or domain management, and maintaining an existing site does not imply responsibility for all pre-existing defects. ## 2. Defined service period and renewal Starter, Business and Advanced include initial setup and the first 12 months of the website service defined in the quotation. For an agreed launch the period starts on the customer-approved launch date. For delivery-only or maintenance-only work, the quotation identifies any service included and its commencement event; BTNXIO hosting is not a compulsory purchase. Renewal for the three fixed packages is ₪150 for another 12 months, only with express customer approval. There is no automatic renewal or charging. The renewal proposal identifies its exact services and any separate infrastructure/domain costs. Custom terms are individual. ## 3. Annual minor changes after handover or launch After handover or launch, each 12-month service period includes one consolidated round of minor content changes and focused adjustments to the existing website. There is no fixed minute or hour allowance; scope is agreed in advance. New development, extra pages, new systems and redesign are not automatically included. Attributable defect fixes are separate. This annual allowance is distinct from development-stage adjustments. Any additional paid work requires a quotation and prior approval; statutory rights remain unaffected. ## 4. Service schedule and existing sites The schedule names the host/account owner, environments, domain responsibilities, included tasks, permitted access and separate supplier charges. For an existing site, the initial review records its stack, known limitations, licences, external accounts and available backups before work is accepted. Hosting or a maintenance engagement does not automatically include a rebuild, repair of every legacy issue, content editing or unlimited incident support. ## 5. Proposed operational commitments — only if adopted For a managed service, the proposed schedule allocates monitoring, update approval/testing, backups and restore checks to a named responsible party. Backup frequency, retention, storage location, restore scope, support hours, contact channels and any incident/recovery targets must be expressly adopted for that service before they are treated as commitments. Without that adoption no fixed backup schedule, uptime percentage, response time or disaster-recovery objective is promised. Hosting management alone does not establish that a backup exists. ## 6. Infrastructure and domain renewal Hosting capacity, provider terms and availability depend on the selected infrastructure. Domains have their own registration periods and account-holder duties. The schedule states who receives expiry notices and who authorizes/pays each renewal. The ₪150 website-service renewal is not represented as automatically covering domain registration, paid plugins, external email, bandwidth or all supplier subscriptions. Necessary third-party costs are disclosed before commitment. ## 7. Updates, access and security Updates and integration changes follow the agreed maintenance scope and approval path. Material changes should be assessed against compatibility, licensing and rollback needs before application. Each party maintains appropriate protection for its own accounts; access is limited to what the task needs and removed when no longer justified. The service does not guarantee that no vulnerability, supplier outage or unauthorized act will occur. Personal-data access is covered by an applicable processing appendix and lawful instructions. ## 8. Incidents and proportionate suspension A reported incident is assessed according to actual access, responsibility and severity. The parties coordinate containment and required notices without promising an unapproved service level. A real security threat, unlawful use or material failure to meet agreed obligations may justify proportionate restriction, with explanation and notice where lawful and practicable. A payment dispute does not justify destroying data, disabling unrelated customer-owned services or refusing a lawful handover. ## 9. End of service, export and deletion The service ending date and customer instructions are documented. Before the managed service ends, the parties identify exportable files/data, account ownership, destination, technical migration work and any lawful retention obligations. Website takedown is distinct from erasure. No automated deletion promise or indefinite storage guarantee is made; deletion/return arrangements must identify who performs the action, what happens to backups and how completion is documented. ## 10. Handover and migration The customer may request delivery or migration to another provider. Identity and authority are checked and the parties record the destination, files/data to export, access rights, dependencies, backup responsibility and a transition plan before changes. Reasonable technical work beyond included handover may be separately quoted, but migration must not be obstructed improperly, nor may unrelated customer property or credentials be withheld as leverage. Shared credentials and other customers’ data are never handed over. Domain transfers remain subject to registrar rules, authentication and legitimate locks. Accounts are separated where feasible; credentials are passed through an agreed secure channel and no deletion is automatic. ## 11. Cancellation, refunds and early takedown A customer may request cancellation, early takedown or non-renewal by contacting btnxio@gmail.com, without limiting any additional cancellation channel required by law. The request, authority and relevant work stage are recorded. Refunds and any lawful charge are assessed under the specific agreement and applicable Israeli law, considering work actually performed and authorized third-party commitments where legally relevant. Neither the deposit nor all payments are categorically non-refundable. Takedown alone does not automatically determine a refund, and declining renewal creates no automatic new annual charge. Statutory cancellation rights, remedies for defects or breach, and mandatory disclosure duties prevail over inconsistent wording. ## Related drafts - [Service terms and development agreement](en-service-agreement.md) - [Website ownership and transfer policy](en-ownership-transfer.md) - [Payment, cancellation and refund policy](en-payment-cancellation.md) - [Conditional data processing appendix](en-data-processing-appendix.md)