BTNXIODocument drafts
Document drafts for professional review
Website notices, privacy, accessibility, service and payment policies, ownership, and project documents. All are drafts requiring legal review.
Draft templates only. Professional legal review under applicable Israeli law is required before binding use. These documents are not legally approved.
01Website terms of use
Terms for browsing btnxio.com and contacting BTNXIO. Project services require a separate approved agreement.
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
1. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
2. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
3. Operator and contracting parties
BTNXIO — Build The Next Experience is the name of an independent digital development activity. As of this draft, the activity has not yet been formally registered as a business; the brand is not represented as an incorporated company. The individual or entity contracting as provider and the customer are identified in the individual quotation and agreement. The business website is btnxio.com and the contact address is btnxio@gmail.com. No registration number, registered office or tax classification is represented by this draft.
4. Website purpose and information
The website presents development services, indicative package scope, approved package prices, potential integrations and interactive design demonstrations. It has no direct checkout. Catalog entries describe capabilities, not configured services included in every package. Portfolio entries, if added, identify their status; demonstrations are not client results. Published information is general and does not replace a project specification, professional advice or a signed quotation.
5. Inquiries and formation of a contract
Sending a form or email is an inquiry, not an order, reservation, acceptance of a quotation or authorization to charge. BTNXIO reviews requirements and provides an individual quotation and relevant terms. The customer expressly approves those documents before payment. A form confirmation means that the email provider accepted the inquiry for processing; it is not approval of a project or proof of delivery to an inbox. No marketing subscription is created.
6. Permitted use
Visitors may browse, use the demonstrations, follow links and submit genuine inquiries using information they are authorized to provide. Reasonable personal or internal evaluation of the published material is permitted. Use must respect other visitors, privacy, intellectual property and applicable law. Visitors should not submit passwords, identification documents, confidential customer lists or unnecessary sensitive data.
7. Prohibited use and protection
Do not impersonate another person, send spam, inject malicious content, attempt unauthorized access, interfere with availability, bypass verification or rate limits, or collect personal information without authority. Security concerns can be reported to btnxio@gmail.com without exploiting them or disclosing other people’s data. Proportionate access restrictions may protect the service; they do not restrict lawful complaints or statutory rights.
8. Intellectual property
The brand presentation, original interface, code and written material are protected according to their applicable ownership and licences. Browsing does not transfer ownership or authorize redistribution, misleading use of the BTNXIO name, removal of notices or sale of website assets. Third-party icons, fonts and software retain their own licences. Customer project ownership is determined by the separate agreement, not these browsing terms.
9. External links and demonstrations
A link or provider name is supplied for context and is not an endorsement, guarantee of availability or statement of partnership. External sites control their content, privacy terms, accounts and charges. The Design Lab previews this website in a same-origin frame; a demonstration does not activate an external commercial integration. Evaluate an external service before giving it information or purchasing it.
10. Accuracy, availability and liability
Reasonable efforts are made to keep the information usable and accurate. Corrections, maintenance, browser differences and third-party failures can affect operation. The site does not promise uninterrupted service, a particular search ranking or a business result. Any limitation operates only as permitted by law; it does not exclude liability that cannot lawfully be excluded, excuse misleading representations or limit remedies under a separately approved service agreement.
11. Updates and contact
A revised browsing draft is identified by its version and date. Changes apply prospectively subject to law and do not unilaterally rewrite an existing signed order. For questions, corrections, privacy or accessibility requests contact btnxio@gmail.com. The applicable privacy, storage and accessibility notices are available in this document area.
12. 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.
02Privacy policy
How the BTNXIO business website processes inquiries and technical information. This draft describes the inspected implementation, not a certification of legal compliance.
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
1. Operator and contracting parties
BTNXIO — Build The Next Experience is the name of an independent digital development activity. As of this draft, the activity has not yet been formally registered as a business; the brand is not represented as an incorporated company. The individual or entity contracting as provider and the customer are identified in the individual quotation and agreement. The business website is btnxio.com and the contact address is btnxio@gmail.com. No registration number, registered office or tax classification is represented by this draft.
2. Information supplied in an inquiry
Name and email are required to use the inquiry form. Phone, package, service, preferred working method, estimated budget and project description are optional; a selected capability and language may accompany the inquiry. Providing information is voluntary, not a statutory obligation. Without name/email the form cannot process the inquiry; you may instead contact us by email and provide the details necessary for a response. Do not include confidential or sensitive information unrelated to the request, payment-card details or account credentials.
3. Technical and security information
A request includes an IP address supplied by the hosting context, request metadata and verification tokens. The security workflow derives keyed hashes from normalized email, IP and inquiry content and uses random operation identifiers, state and timestamps to limit abuse and repeated delivery. These are pseudonymous identifiers, not anonymous data. The rate-limit store does not contain the raw inquiry, name, email or IP. Hosting infrastructure may separately process request/security logs; their exact fields and account-level retention are not established by the application code.
4. Purposes and limits on use
Inquiry details are used to review requirements, communicate with the sender, prepare a quotation and retain appropriate correspondence about the request or an ensuing agreement. Technical information supports secure operation, bot checks, temporary quotas and duplicate prevention. The form does not enrol the sender in marketing, create a customer portal or make an automated eligibility decision about a project. No analytics, advertising pixels or cross-site marketing scripts are installed in the reviewed site. New purposes require the notice and legal basis appropriate to the change.
5. Processing and email recipients
The prepared production architecture uses a Netlify Function for submission handling, Resend for plain-text email delivery, Upstash Redis for temporary abuse-control records and Cloudflare Turnstile for bot verification. Inquiry email is addressed to btnxio@gmail.com and uses the authenticated sender contact@btnxio.com, with the visitor’s address as Reply-To. The Gmail mailbox, email provider and persons authorized to handle inquiries can process the message and delivery metadata. Provider acceptance is not proof of inbox receipt. BTNXIO has no public inquiry database or CRM in this implementation.
6. Verification, browser preferences and embedded content
In live mode Turnstile loads a Cloudflare script and verification frame. Cloudflare receives technical browser/network signals and a verification challenge; the server checks the token, origin-related hostname and action. The site stores theme and language preferences in localStorage and does not persist inquiry contents there or in sessionStorage. Fonts are served from local website assets. The Design Lab uses a same-origin site preview, not a third-party social feed. The capability catalog describes potential integrations; it does not itself activate them. Security storage and provider-side behavior are detailed in the cookies and tracking draft.
7. International processing and disclosures
The named infrastructure, verification and email providers may process information outside Israel, depending on their service arrangements and the selected account region. No particular country, exclusive Israeli hosting or international certification is promised. Transfers and provider engagement must follow applicable Israeli privacy rules and suitable contractual safeguards. Information may also be disclosed where required by law, a competent authority or a lawful defence of rights, limited to what is relevant. Information is not sold through the reviewed inquiry workflow.
8. Actual temporary storage and other retention
Accepted inquiries count toward rolling email and IP limits for 24 hours and one hour respectively. Expired entries are removed when checked and shared keys expire according to their remaining entries; the end of a counting window does not guarantee immediate deletion of every associated identifier. Verification-attempt counters expire after one minute; accepted-content duplicate pointers expire after five minutes. Operation receipts and uncertain reservations use expiries of approximately 48 hours; some retry aliases receive a fresh bounded expiry, and cleanup may include a short technical margin. These limits apply to security records, not the original email. No universal automatic deletion period is implemented for Gmail correspondence, provider delivery logs, hosting logs or backups. Those records are retained as needed for the inquiry, agreed services, lawful recordkeeping or disputes, subject to applicable law and approved provider/operational arrangements. No indefinite retention or fixed mailbox deletion promise is made.
9. Security and confidentiality
The implementation separates server credentials from browser code, validates form inputs, limits payloads, uses a honeypot and server-side bot verification, and uses atomic shared rate limits and idempotent delivery handling. User text is sent as plain text rather than interpolated HTML. The handler does not intentionally log raw inquiry bodies; infrastructure/provider logging is separate. Access should be limited to authorized persons for the stated purpose. These safeguards reduce risk but do not guarantee absolute confidentiality or freedom from incidents. Please report suspected exposure through the contact email without sending further sensitive material.
10. Access, correction and personal-information requests
Israeli privacy law provides rights of access and correction subject to its conditions and exceptions. To request access, correction, deletion where legally available, or information about handling your inquiry, email btnxio@gmail.com and describe the request. Proportionate identity verification may be necessary; do not send an identity document unless a suitable secure method has been agreed. Requests are considered under applicable law, including lawful retention obligations and rights of others; deletion is not an unconditional right over every record. No invented universal response deadline or automatic self-service deletion facility is represented. You may also approach the competent authority or exercise other legal remedies.
11. Minors, client projects and changes
The inquiry service is intended for people able to enter the relevant business arrangement. A minor should involve a parent or guardian where needed, and unnecessary information about children should not be submitted. For a customer website, the customer’s own privacy notice and any applicable processing appendix govern its separate processing activities; this notice does not automatically describe every client system. Material changes to this website’s processing will be reflected in a dated notice and, where required, appropriate additional information or permission. Privacy contact: btnxio@gmail.com.
03Cookies, storage and tracking policy
The storage and third-party activity present in the reviewed website, distinguished from optional future marketing tools.
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
1. Scope
This notice covers btnxio.com and the browser features used by its reviewed React application. A cookie and browser localStorage are different mechanisms; both can retain information on a device. Server-side Redis records are not browser cookies. A catalog entry for an analytics or social platform is not evidence that its script is installed.
2. Theme and language preferences
The application reads and writes btnxio-theme and btnxio-language in localStorage to remember the selected experience and language across navigation/reload. No application expiry is set, so the preferences can remain until removed by the visitor, browser or device settings. If storage is blocked the application falls back to its defaults. Inquiry contents and credentials are not persisted in these keys, and no sessionStorage workflow was found in the reviewed code.
3. Security and Turnstile
The live contact page loads Cloudflare Turnstile and verifies its response on the server. This involves technical device/browser and network processing for abuse prevention. The reviewed application does not itself set a first-party tracking cookie. Whether provider-side security cookies or optional cf_clearance pre-clearance are used depends on the live Cloudflare/hosting settings, which the repository alone cannot establish. This notice does not describe those account settings as enabled or verified. Security protection is not an advertising permission.
4. Analytics, advertisements and external content
No Google Analytics, Tag Manager, Clarity, Meta/TikTok pixels, advertising SDK or third-party social feed is installed in the reviewed website. Fonts are hosted locally. The live Design Lab frame uses this same website. External profile, map or provider links take a visitor to another service only when followed; that service may use its own storage. Actual third-party content or tracking added to a client project requires its own disclosure and appropriate controls.
5. Controls and consent
Visitors can change the theme/language in the interface or remove site storage through browser settings; deleting preferences does not delete email correspondence held by the business. Browser restrictions on third-party scripts may prevent verification, in which case email contact remains available. There is no cookie consent manager, analytics opt-in banner or marketing preference center in this implementation. Optional tracking must not be activated before the applicable legal basis and, where required, prior consent controls have been implemented.
6. Changes and questions
Storage or provider changes require review of this dated notice and the privacy policy. Questions about the current application can be sent to btnxio@gmail.com. No setting in this notice claims to block a provider’s independent infrastructure logs or to erase information already sent to another service.
04Accessibility statement
Accessibility features, verified testing scope and current limitations of the BTNXIO website. This is a draft statement, not a compliance certificate.
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
1. Approach and scope
BTNXIO works to make its Hebrew/English website usable across screen sizes and input methods, including all eight design experiences. The website uses readable HTML for its main content rather than a canvas-only interface. Accessibility requirements for customer projects are specified individually; displaying this statement does not certify any client website.
2. Navigation and keyboard
The reviewed implementation includes semantic page headings, a skip link, labeled navigation, visible keyboard focus and mobile menu controls. Menus can be closed with Escape and focus is restored. Native disclosure elements expose expanded state. Contact feedback uses a modal dialog with associated title/description, focus trapping, Escape handling and restoration to Submit. Standard Tab and Shift+Tab can be used to move through controls; essential actions are not hover-only.
3. Forms, language and presentation
Form controls have associated labels; name/email are required and phone is optional. Field errors are connected to controls, input is retained on failure, and status feedback distinguishes uncertainty from confirmed acceptance. Hebrew uses RTL and English LTR, with mixed-direction values isolated where appropriate. Responsive layouts, local language-aware fonts, text wrapping and reduced-motion preferences are implemented. Theme selection can offer a different reading presentation, but is not a substitute for fixing a barrier.
4. Verified local test evidence
Local QA dated 10 November 2026 records Chromium and Firefox checks across eight experiences and both languages. Contact layout coverage included 320×568 through 1920×1080 and intermediate widths, keyboard/modal interactions, validation and overflow checks. Zoom-related checks simulated viewport/DPR factors of 80%, 100%, 125% and 150%; native browser zoom menus were not operated. Provider responses and the verification widget were mocked for these checks. Selected rendered screenshots were inspected. These are development tests, not an independent accessibility audit or certification.
5. Known limitations
A comprehensive screen-reader audit, real-device coverage, native zoom-menu verification and the live third-party Turnstile interface have not been established by the reviewed QA. WebKit testing was not completed on the local host. Downloaded Markdown may require an appropriate reader, and client-added content or external sites may have separate barriers. No complete WCAG, Israeli Standard 5568 or legal-compliance claim is made. Legal applicability, required arrangements and any exemption must be determined for the actual operator and service; none is assumed here.
6. Reporting a barrier and receiving assistance
For an accessibility issue, email btnxio@gmail.com with the page address, language/theme, action attempted and an optional description of browser or assistive technology. Please avoid unnecessary medical information or personal documents. If the verification widget or form prevents contact, use the direct email link. Requests can include an alternative accessible format or channel; availability is considered individually without inventing a response-time guarantee. No coordinator name or telephone number is represented.
7. Maintenance of this statement
This statement identifies the reviewed version and evidence rather than guaranteeing permanent absence of barriers. Relevant changes, reported barriers and further audit findings should be reflected in a dated revision. Accessibility contact remains btnxio@gmail.com.
05Service terms and development agreement
Proposed agreement for a specifically approved development or digital-service project. The quotation and specification identify the actual transaction.
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
1. Operator and contracting parties
BTNXIO — Build The Next Experience is the name of an independent digital development activity. As of this draft, the activity has not yet been formally registered as a business; the brand is not represented as an incorporated company. The individual or entity contracting as provider and the customer are identified in the individual quotation and agreement. The business website is btnxio.com and the contact address is btnxio@gmail.com. No registration number, registered office or tax classification is represented by this draft.
2. Definitions and document order
Provider means the person or entity identified as BTNXIO’s contracting provider in the accepted quotation. Customer means the identified purchaser and its authorized representative. Project means the expressly listed work; deliverables are the agreed outputs; third-party services are independently supplied infrastructure, software or accounts. Mandatory law prevails. Subject to it, the signed quotation and specification control project-specific scope, followed by the accepted agreement and relevant appendices. Website descriptions do not expand the approved work or override statutory rights.
3. Quotation, authority and approval
An inquiry starts a discussion only. Before payment the parties approve the quotation, specification, relevant service terms and the identity of the authorized approver. Email or another agreed written method can record explicit acceptance of an identifiable version. A different scope, additional service or material change requires recorded approval of its price and effect on milestones before that work starts. Silence, viewing a preview or submitting this website’s form is not acceptance.
4. Scope and exclusions
The specification identifies page count, languages, design direction, components, supported screen/browser targets, integrations, content entry, SEO work, accessibility scope, tests and handover formats. The selected package page limit applies; actual pages are listed within it. A capability is included only if expressly listed. Payment systems, accounts, automation, AI, advanced security, legal advice, copywriting and licensed assets are not inferred from a package name. A general description does not create unlimited project scope or support, or guarantee a commercial result. Development-stage adjustments follow the chosen working method within the specification.
5. 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.
6. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
7. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
8. Price and payment
The fixed package prices are Starter: ₪700; Business: ₪1,200; Advanced: ₪3,000. Custom work is individually quoted. The approved total and any applicable tax are stated before acceptance or payment. The payment model is 50% before development begins and 50% before publication or final handover. The customer receives an opportunity to review the agreed deliverables before the balance becomes due. The deposit is part of the price, not an automatically forfeitable penalty. Additional scope and third-party purchases require separate approval.
9. Customer materials and cooperation
The customer supplies accurate content, contact details, media, approvals and authorized access in the agreed format, and is responsible for having rights and lawful grounds to use supplied materials and personal information. The provider may identify a technical or apparent rights issue and seek clarification rather than publish it. The customer appoints a coordinating contact and provides clear feedback according to the selected working method. Missing materials, late approvals or unavailable external accounts may change the schedule; their effect is documented rather than converted into automatic acceptance.
10. Milestones, design and development
Work is organized into requirements, specification, design review, development, testing, customer review and handover/publication as applicable. Dates and dependencies are agreed for the particular project; the website does not guarantee a universal delivery time. Approval of a design version fixes the agreed direction, not a waiver of defects or statutory remedies. Material changes after approval are assessed for scope, cost and schedule. Development previews may contain test content and must not be mistaken for an authorized public launch.
11. Testing, review and acceptance
Testing follows the agreed acceptance criteria and representative environments. The provider supplies a reviewable version and a list of known limitations or open items; the customer checks the agreed functions and supplies consolidated, specific feedback. Attributable defects are distinguished from new requirements. Approval is recorded by version and authorized person, with any outstanding work and responsibility identified. Access to a preview, partial use or lapse of time alone does not create a blanket waiver.
12. Publication or development-only handover
Publication requires explicit customer launch approval, the agreed final payment and the necessary lawful account access. Alternatively, development-only work is delivered in the agreed format without requiring BTNXIO hosting. The delivery record identifies files, configuration instructions, account control, dependencies and exclusions. Public activation of payments, analytics or other integrations requires the necessary real accounts, permissions and approved configuration; a test demonstration is not presented as operational.
13. 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.
14. 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.
15. 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.
16. Domains and third-party accounts
Customer-controlled domain registration and separate customer accounts are preferred where feasible. The quotation records the registrant, payer, administrative permissions and responsibility for expiry notices and renewals. Registrar and hosting charges, paid plugins, usage-based APIs and subscriptions require approval and are separate unless expressly included. Provider limitations, licence restrictions and commercial-account prerequisites are disclosed; the provider does not guarantee another supplier’s continuity, pricing or approval decisions.
17. Maintenance, backups and security allocation
Only agreed maintenance is included. The parties identify responsibility for software updates, content changes, monitoring, backups, restoration, account administration and security incidents in the service schedule. A backup must not be assumed merely because hosting is managed. Any proposed backup frequency, retention, response target or recovery objective becomes a commitment only when expressly approved; no uptime percentage or response-time guarantee is supplied by this draft. Each party protects the accounts and systems under its control and cooperates in addressing attributable incidents.
18. Confidentiality and data protection
Non-public project information is used only for the agreed work, authorized administration or a lawful requirement. Access is limited according to role; credentials are shared through an agreed secure channel, not public forms or source repositories. Information already lawfully public, independently developed or lawfully obtained is not treated as another party’s confidential disclosure. A legally compelled disclosure is limited and communicated where permitted. If the provider processes personal information on the customer’s behalf, the conditional processing appendix must be adopted with the actual categories, instructions and suppliers before that access begins.
19. Incident cooperation and interruption
A suspected incident should be reported through the agreed contact without exposing additional secrets. The parties coordinate proportionate containment, preservation of relevant evidence, responsibility and legally required notifications. Urgent protective restriction may be appropriate for a real security threat or unlawful use; other suspensions require proportionate handling and notice where lawful and practicable. A dispute does not authorize destructive deletion, misuse of credentials or withholding unrelated customer property.
20. 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.
21. 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.
22. Responsibility and remedies
Each party is responsible for its obligations, representations and conduct under applicable law. The provider does not guarantee search rankings, sales, uninterrupted third-party systems or absolute security, but remains accountable for attributable breach and duties that cannot be excluded. This draft imposes no blanket exclusion or invented monetary liability cap. Agreed exclusions do not excuse a defect within the approved scope, misleading conduct, unlawful information handling or mandatory consumer remedies.
23. 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.
24. Notices, changes and survival
Service notices are sent through the contact channels recorded in the quotation, with btnxio@gmail.com as the business contact. Material amendments require explicit recorded approval, not a silent website update. Ownership/licensing, confidentiality, lawful payment reconciliation, data-return obligations and mandatory rights continue as applicable after termination. No public draft becomes a signed agreement merely because it is displayed or downloaded.
06Payment, cancellation and refund policy
Payment stages and stage-specific cancellation handling, subject to the individual agreement and mandatory Israeli law.
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
1. Price and payment
The fixed package prices are Starter: ₪700; Business: ₪1,200; Advanced: ₪3,000. Custom work is individually quoted. The approved total and any applicable tax are stated before acceptance or payment. The payment model is 50% before development begins and 50% before publication or final handover. The customer receives an opportunity to review the agreed deliverables before the balance becomes due. The deposit is part of the price, not an automatically forfeitable penalty. Additional scope and third-party purchases require separate approval.
2. Before payment and changes of scope
The quotation and relevant terms are supplied for review and expressly approved before requesting the deposit. They identify deliverables, exclusions, total payment, tax treatment applicable to that transaction and third-party costs. No checkout or payment-card collection is offered by this website. Scope changes require a separate approved price and milestone effect; additional work is not silently charged against the original package.
3. Cancellation before development
Before development begins, the customer may notify the provider that the project will not proceed. The parties confirm whether any authorized specification work or third-party purchase has actually occurred and reconcile payment under the applicable cancellation rules. A deposit is not automatically lost merely because it was paid; any lawful deduction must have a legal or contractual basis and a clear explanation. An unapproved purchase is not simply passed on to the customer.
4. Cancellation during development
On a cancellation request during work, further avoidable work and commitments are assessed for stopping, and the completed work, paid sums, approved external commitments and usable deliverables are documented. The settlement follows the agreement and mandatory law; this policy fixes no universal refund percentage or cancellation fee. Delivery or licence rights in paid work and legitimate restrictions on incomplete materials are addressed expressly rather than assumed.
5. After review, delivery or publication
Customer review precedes the final payment milestone. Later cancellation requests are assessed by the nature of the service, the approved deliverables and applicable law. Acceptance does not extinguish claims for attributable defects, non-conformity or breach. The provider may first assess and propose agreed correction where appropriate, without delaying a statutory remedy or requiring a blanket waiver as a condition of assistance.
6. Early removal of a hosted website
The customer can request that a hosted website be taken offline before the service period ends. Authority, affected domains, timing, backups and transition needs are confirmed before action. Takedown is not the same as cancellation of development, deletion of data or transfer of a domain. It does not by itself establish or remove a refund entitlement. No automatic deletion is performed, and remaining obligations and statutory rights are assessed separately.
7. Non-renewal and external subscriptions
Renewal of fixed-package annual services requires explicit approval; declining it does not authorize a new annual charge. Before expiry the parties can arrange export, transfer or an agreed end to the managed service. Domain and supplier subscriptions are separate arrangements: cancelling BTNXIO work does not automatically cancel them. The account holder must approve and complete supplier cancellation where necessary, subject to the supplier’s terms and mandatory rights. No refund from an independent supplier is guaranteed.
8. 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.
9. Consumer rights and reconciliation
Whether a transaction is a consumer transaction, distance sale, ongoing service or individually commissioned work depends on its actual facts. Those classifications are not decided merely by using a website or the word Custom. All legally required disclosures, channels, time limits and remedies apply where relevant, including special rules where applicable. Refund handling identifies the amount, reason and lawful deductions in a written reconciliation; this draft invents no processing deadline or blanket exception for custom development.
10. 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.
07Hosting, maintenance and renewal policy
Service allocation for development, managed hosting, existing websites and maintenance-only arrangements.
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
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.
08Website ownership and transfer policy
Account control, customer deliverables and a reasonable transition between hosting or maintenance providers.
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
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.
09Quotation and work order
Reusable quotation terms with a project schedule for the particular customer. It becomes an order only through explicit approval of the completed documents.
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
1. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
2. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
3. Operator and contracting parties
BTNXIO — Build The Next Experience is the name of an independent digital development activity. As of this draft, the activity has not yet been formally registered as a business; the brand is not represented as an incorporated company. The individual or entity contracting as provider and the customer are identified in the individual quotation and agreement. The business website is btnxio.com and the contact address is btnxio@gmail.com. No registration number, registered office or tax classification is represented by this draft.
4. Proposed project and incorporation
The project schedule identifies the customer, authorized representative, project objective, selected package and specification version. The quotation incorporates only the identified service agreement and appendices supplied for review. Its proposed validity period and any dependencies are recorded for this transaction; no universal expiry or delivery deadline is invented. A partial schedule or inquiry is not authorization to begin chargeable development.
5. Scope and deliverable inventory
The agreed inventory specifies pages/sections, languages, chosen design, components, integrations, supplied content and delivery formats. It lists each included task and exclusion, including account setup, content production, licensed assets, testing, SEO and accessibility work. Unlisted platform features, ongoing operations and out-of-scope changes are not silently included. The customer can compare the inventory with the approved specification before acceptance.
6. Price and payment
The fixed package prices are Starter: ₪700; Business: ₪1,200; Advanced: ₪3,000. Custom work is individually quoted. The approved total and any applicable tax are stated before acceptance or payment. The payment model is 50% before development begins and 50% before publication or final handover. The customer receives an opportunity to review the agreed deliverables before the balance becomes due. The deposit is part of the price, not an automatically forfeitable penalty. Additional scope and third-party purchases require separate approval.
7. Milestones and customer inputs
The project schedule records expected stages, materials/access required from each party, review/approval points and dependencies on third-party accounts. A proposed timeline is confirmed for the individual scope and changes when dependencies or approved work change, by recorded agreement. The customer supplies coordinated feedback; the provider identifies the effect of a requested addition before implementing and charging for it.
8. 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.
9. 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.
10. 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.
11. 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.
12. External costs and service choices
The schedule states who owns and pays each domain, hosting account, plugin, email service and usage-based API. It records included allowances, separate charges and limits, where relevant, without implying that all provider costs are covered by the package or renewal fee. Customer-owned hosting and development-only delivery remain available. No external purchase or subscription is authorized by silence.
13. 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.
14. Acceptance and work authorization
The customer confirms the quotation/specification versions, total payable, scope, exclusions, payment stages, service choices, cancellation terms and relevant appendices by the agreed written method. The approval record identifies the person, authority and date. Development begins after that approval and receipt of the agreed deposit and necessary inputs. A signature on an incomplete template, merely downloading it, or a form confirmation is not treated as agreement to unstated terms.
Individual project schedule
These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template.
- Selected working method A/B/C, in-scope adjustments, agreed method changes and customer approval
- Provider legal identity, customer legal name and authorized contacts
- Quotation number, date, version and approval record
- Project description, selected package and specification reference
- Approved total, applicable taxes, deposit and final payment
- Milestones, dependencies and customer review stages
- Hosting, domain, maintenance and third-party cost choices
- Source delivery, licences, data export and migration arrangements
- Exclusions, open items and express customer approval
10Project specification appendix
A reusable specification structure for defining a project before development, including testable delivery and acceptance criteria.
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
1. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
2. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
3. Purpose, pages and content structure
The appendix defines the project objective and intended audiences, then records each page, route, section and primary action. Each item has a content owner, language coverage and acceptance outcome. Navigation hierarchy, legal/contact links, empty states and error/not-found behavior are identified. The Starter one-page limit, Business maximum of 5 pages or Advanced maximum of 10 pages applies; Custom page count is recorded individually. The actual sitemap and content responsibilities are listed within that scope, without unlimited content entry.
4. Features, forms and interactions
For each feature the specification describes inputs, required/optional fields, validation, state changes, outputs, error handling and responsible service. Forms identify recipients, consent/disclosure needs, spam controls and the distinction between accepted processing and completed delivery. Search, filtering, accounts, commerce, bookings and AI appear only if expressly selected. Test modes must be clearly identified and must not impersonate live integrations.
5. Design, languages and responsive behavior
The agreed design direction, brand assets, components and review version are recorded. Hebrew and English or other selected languages have content responsibility, RTL/LTR direction, appropriate typography and mixed-direction handling. The project defines representative mobile/tablet/desktop widths and browser targets, touch behavior and reduced-motion requirements. BTNXIO’s eight showcase experiences do not mean that every customer project includes eight complete designs.
6. Integrations and infrastructure
Each chosen provider has an identified account holder, required permissions, allowed data flows, commercial prerequisites, fees and test/live activation conditions. Client-side public settings are separated from private server credentials. Hosting/deployment, custom domain, HTTPS and access requirements are recorded for the chosen model. No API availability, payment approval or supplier subscription is assumed.
7. Content, accessibility and search scope
The customer supplies or approves lawful content, media, translations and project-specific legal notices according to the responsibility inventory. Accessibility tasks and testing, including keyboard/forms, headings, text alternatives and any specialist audit, are expressly scoped; legal certification is not inferred. SEO tasks can include semantic markup, metadata, sitemap, robots rules, internal links and image work, without a ranking or indexing guarantee.
8. Acceptance tests and defect classification
The test inventory identifies actions, environments, expected outcomes and evidence for the agreed pages/features, responsive/RTL behavior, links, forms, failures and delivery. Attributable defects are distinguished from omitted customer content, third-party restrictions and new requirements. Critical open issues and any accepted limitations are recorded explicitly; a passing build alone is not acceptance. No performance score, full browser coverage or legal compliance is asserted without a corresponding test.
9. Delivery requirements and change control
The appendix lists source/build/design files, export formats, documentation, account handover and any agreed training. It identifies excluded infrastructure and licences and the conditions for publication or delivery to customer hosting. Proposed changes are logged with their scope, cost, dependency and approval impact; only an expressly accepted revision changes the specification. Customer launch approval is separate from design approval and from the final payment record.
Individual project schedule
These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template.
- Selected A/B/C method, development adjustments reviewed and separate post-handover annual round
- Project and quotation identifiers; approved specification version
- Page/feature inventory, languages and content owner for each item
- Supported environments, integrations and acceptance test inventory
- Delivery formats, dependencies, exclusions and approvals
11Website delivery and launch approval
A record of the exact version and customer authorization for publication or handover; it does not itself publish, charge or delete anything.
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
1. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
2. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
3. Version and deliverables reviewed
This record applies only to the identified release and agreed deliverable inventory. It identifies the quotation/specification and the preview or handover materials reviewed by the authorized customer representative. A later unreviewed change is not covered by the earlier approval. The record contains no passwords, private keys or unnecessary personal documents.
4. Testing and outstanding items
The parties record completed tests, supplied content, known restrictions and any remaining defect with its effect, responsible party and agreed handling. A critical issue is not silently represented as resolved. An express decision to launch with a stated limitation does not waive rights concerning unrelated or undisclosed defects or mandatory legal protections.
5. Final review and payment
The customer has a meaningful opportunity to review the agreed version before the final 50% payment milestone. The payment record states the approved total, amounts already received and balance confirmation. Receipt of payment alone is not authorization to change DNS, publish confidential material or enable a chargeable external service. Statutory cancellation and defect remedies remain separate.
6. Express launch or handover authorization
The approval identifies whether it authorizes publication on the named domain/host or development-only handover to the customer. It records the authorized person, scope of action, agreed timing and any conditions. Accounts, live integrations and legal/content approvals needed for publication are checked against the schedule. No actual launch is inferred from a contact form or unsigned draft.
7. 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.
8. Handover evidence and later corrections
The record identifies delivered files, documentation, account invitations, safe credential-handover method and the support/maintenance arrangement that begins. Acknowledgment confirms receipt of listed items only, not unrestricted assignment of third-party licences. Later corrections and approvals are attached as dated records without altering the earlier evidence or removing statutory rights.
Individual project schedule
These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template.
- Selected A/B/C method, development adjustments reviewed and separate post-handover annual round
- Customer/approver identity and authority; project and quotation
- Release identifier, review URL and test record
- Accepted limitations, open defects and agreed correction plan
- Final payment confirmation, approved host/domain and launch event
- Approval method, signature/evidence and date
12Customer delivery and acceptance record
Reusable evidence of delivered items, customer checks, agreed corrections and final acceptance for the specified project.
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
1. Package scope and equal quality
Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval.
2. Development-stage working method
Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round.
3. Identity and reference documents
Acceptance is recorded by an authorized person for the identified customer, project, quotation and specification version. The date, review method and exact release or delivered archive are identified. The record does not substitute for a missing quotation or invent approval by a person whose authority has not been verified.
4. Delivered inventory and access
The inventory lists pages, features, languages, media/content, source or build files where agreed, documents, licences and account control actually delivered. Each item can be marked received, not applicable or outstanding with an explanation specific to the project. Passwords and private keys are transferred separately through an agreed secure method, not written into this public template or a widely shared record.
5. Customer review and defects
The customer records the agreed checks and any mismatch with the specification. Outstanding issues identify severity, affected function, responsibility and the agreed correction or further review. New feature requests are distinguished from attributable defects. Acceptance may be conditional on identified corrections; silence or the existence of this record is not proof that all work is defect-free.
6. Payment and publication status
The record distinguishes customer review, final payment, launch authorization and actual publication or handover. The final 50% is due before the agreed publication or final delivery, after the customer review opportunity. It records confirmation of the balance and actual event without enabling an automatic charge. If publication is outside the provider’s scope, the handover destination and customer responsibilities are recorded instead.
7. Support, ownership and remaining obligations
The record references the applicable ownership/licence schedule, start of any defined service period, minor-change allowance and maintenance scope. It identifies any remaining document, migration work, supplier charge or access removal and who is responsible. Receipt does not assign pre-existing tools or non-transferable licences, waive statutory rights or consume the defect-correction obligation as a minor-change round.
8. Express acceptance record
The authorized customer records acceptance, conditional acceptance or a reasoned refusal against the identified deliverables. The method and evidence of approval are retained with the project documents. Any later revised acceptance is dated and linked to the correction record. This template alone is not a signature, a blanket release or an authorization to publish unapproved information.
Individual project schedule
These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template.
- Selected A/B/C method, development adjustments reviewed and separate post-handover annual round
- Customer, authorized reviewer and reviewed version
- Delivered inventory, accounts and documentation
- Review results, open issues, agreed remedies and responsibility
- Final payment, approval date and publication/handover evidence
13Conditional data processing appendix
Applies only when expressly adopted for a project in which BTNXIO processes personal information on the customer’s behalf. It is not automatically part of every website build.
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
1. Conditional application and roles
Before access begins, the parties identify the actual processing and decide whether this appendix applies. For processing performed solely on documented customer instructions, the customer determines the purposes and authorized uses and the provider performs only the agreed operations. Each party remains separately responsible for processing it determines for its own lawful purposes, such as its own business correspondence. Legal roles depend on actual facts; this draft does not assume GDPR applicability, a statutory role or an exemption for every arrangement.
2. Instructions, scope and minimization
The processing schedule identifies data subjects, data categories and sensitivity, systems, permitted operations, duration and locations. Access is limited to the least information and permissions reasonably needed. Production information is not copied into public previews or test systems without a lawful, expressly agreed basis and safeguards. The provider does not sell data, use it for unrelated marketing or train unrelated AI systems on it. An instruction that appears unlawful is raised with the customer and the affected processing is not continued blindly.
3. Confidentiality and access authorization
Persons with access are authorized for their role, informed of confidentiality/security duties and restricted to the permitted work. Authentication, credential handling, account separation and access revocation follow the approved schedule and applicable duties. Shared root credentials are avoided where feasible; secrets are not placed in source control, public tickets or contact forms. Access that is no longer required is removed and documented.
4. Security measures and oversight
The parties document safeguards appropriate to the data and risks, including permissions, secure communications, system updates, logging boundaries, backups where agreed and incident handling. Where applicable, their arrangement addresses the Israeli Privacy Protection (Data Security) Regulations, including relevant outsourcing requirements, rather than relying on this appendix’s title as proof of compliance. Evidence and proportionate reviews are coordinated to permit oversight while protecting other customers, security details and lawful confidentiality.
5. Subprocessors and international access
The approved schedule names the actual hosting, email, database, verification or other suppliers with access to project data, their roles and relevant locations or transfer arrangements. New or changed processing suppliers follow the agreed notification/approval procedure and applicable law before access; the provider imposes suitable confidentiality and security duties. The providers used by BTNXIO’s own inquiry form are not automatically approved for every client project. No particular country, certification or transfer safeguard is asserted without evidence.
6. Incidents and cooperation
The provider informs the customer of an incident affecting entrusted information without undue delay after becoming aware, supplies available relevant facts and updates, and cooperates in containment, evidence preservation and remediation. The schedule allocates responsibility for legally required notices to authorities and affected people; it does not postpone a mandatory duty. No unapproved fixed number of hours, absolute detection promise or transfer of all legal responsibility to the customer is imposed.
7. Rights requests and legal disclosures
The provider forwards requests relating to customer-controlled information through the agreed contact and assists within the lawful instructions and actual technical capability. It does not independently decide the customer’s purposes or make an unauthorized disclosure to a requester. Identity verification, response responsibility and any costs for separately scoped assistance are agreed without limiting mandatory rights. Legally compelled disclosures are limited and notified to the customer where permitted.
8. End of processing, return and deletion
At the agreed end, the parties arrange export/return or deletion of the entrusted information and revocation of access, subject to applicable retention duties. The plan identifies copies, backups, supplier limitations, completion evidence and any data lawfully retained with restricted further use. No automatic erasure, immediate deletion from every backup or unlimited retention is presumed. The provider documents the performed return/deletion and any lawful exception rather than declaring completion without verification.
9. Activation and precedence
This appendix becomes part of the individual agreement only through explicit adoption of its processing schedule by authorized parties before the relevant access. It supplements, rather than replaces, applicable privacy/security duties. If an instruction or general service clause conflicts with mandatory law, the law prevails and the parties document a lawful adjustment. The customer’s own notice to data subjects remains a separate responsibility according to the actual roles.
Individual project schedule
These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template.
- Parties, roles, project and processing duration
- Data subjects, data categories, sensitivity and permitted operations
- Systems, access roles, locations and approved subprocessors
- Security measures, reporting arrangements and review evidence
- Return/deletion, legal retention and backup treatment