# Website ownership and transfer 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 Account control, customer deliverables and a reasonable transition between hosting or maintenance providers. ## 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. Deliverables, source code and licences After full payment, rights in customer-specific deliverables and their permitted use are governed by the approved quotation and agreement. The deliverable list states whether source repositories, design files, build output and documentation are transferred or licensed and in which formats. Customer-provided content remains subject to its existing ownership. Pre-existing code, reusable components, tools, know-how, open-source packages, third-party assets and proprietary infrastructure are distinguished from customer-specific work and are not automatically assigned. Necessary permitted use of retained components must be licensed with the deliverable; third-party licence restrictions and non-transferable subscriptions are disclosed. No rights beyond those lawfully held are promised. ## 3. Customer-owned domains and accounts Where feasible the customer is the registered domain holder and controls the registrar recovery address and billing account. BTNXIO can be given delegated technical access without becoming the owner. Customer-owned hosting remains under customer control even when BTNXIO performs development or maintenance. The quotation records access, permitted changes, support boundaries and who pays suppliers; a development purchase does not bind the customer to BTNXIO hosting. ## 4. BTNXIO-managed registration or hosting If BTNXIO assists with registration or manages an account, the registrant, beneficial customer, administrative contact, renewal payer and authorization are recorded. Customer-specific accounts should be separated from shared operational accounts where feasible. Management does not by itself transfer ownership to the provider. Shared infrastructure can remain with its owner while the customer receives the agreed export, necessary permitted-use rights and transition assistance. ## 5. Source, content and portable delivery The agreed delivery inventory identifies repository/source, build files, design files, content, media, documentation, environment-variable names and dependencies. Secrets are not embedded in delivered code. Export formats and limitations are explained for databases or proprietary platforms. Ownership of a custom deliverable is distinguished from access to a non-transferable commercial account or an external platform; essential licence restrictions are disclosed before approval. ## 6. 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. ## 7. Migration work and legitimate charges Migration can require environment preparation, dependency changes, DNS coordination, testing, data conversion and service reconfiguration. Work not included in the approved delivery may be separately priced and requires approval before charging. The provider must not use an invented migration penalty, arbitrary lock or unrelated debt to obstruct a lawful transfer. Genuine registrar locks or supplier restrictions are explained and addressed through the relevant provider rather than bypassed. ## 8. Credentials, data and termination record Handover uses verified recipients and secure account transfer, invitation or credential rotation. It excludes other customers’ data, shared master credentials and private provider keys; customer-specific replacements may be required. The record identifies exported data, retained licences, access removed, third-party billing and outstanding work. Any required deletion or return is confirmed according to the agreement and law, with backup limitations disclosed. Neither early takedown nor non-renewal automatically deletes the customer’s files. ## 9. Governing law, disputes and mandatory rights The proposed governing law is Israeli law, subject to mandatory rules that apply to the parties or transaction. The parties should first exchange the relevant facts and attempt a practical resolution, without delaying urgent relief or expiry of legal rights. No compulsory arbitration, exclusive distant forum or waiver of access to a competent court is imposed by this draft. A dispute provision in a signed agreement operates only to the extent lawful, and nothing limits rights or liability that cannot lawfully be excluded. ## Related drafts - [Service terms and development agreement](en-service-agreement.md) - [Quotation and work order](en-quotation-work-order.md) - [Hosting, maintenance and renewal policy](en-hosting-maintenance.md) - [Customer delivery and acceptance record](en-customer-acceptance.md)