Terms of Use

These Terms cover the commissioned work and the use of the AlefOS technology on which it runs. The signed quotation defines your project. The Customer pays for the agreed services and a right to use AlefOS, not ownership of its technology.

These Terms govern the professional services and use of AlefOS provided by MyBot Ltd, an Israeli limited liability company incorporated in 2021, registration number 516373891, operating from Ashkelon, Israel. The Customer is the person or entity entering into the contract. Its signatory must have authority to commit it; an employee, visitor or end customer does not incur the Customer’s commercial obligations merely by accessing an interface.

The Commercial Agreement is the signed quotation and its agreed specifications, order form or written amendments. It identifies the commissioned project, deliverables, services, fees and conditions. It prevails on commercial matters expressly addressed in it. The DPA prevails for personal data processed on the Customer’s behalf, subject to any mandatory law and the priority of applicable transfer clauses. The Privacy Policy explains processing and does not grant additional commercial rights. A later website price or product description does not amend an accepted order.

The Customer Application is the OS configured or developed under the Customer’s brand using AlefOS Technology. AlefOS Technology means the underlying software, reusable components, interfaces, methods and technical know-how owned by MyBot or its licensors. Customer Materials are the brand and materials supplied by the Customer. Customer Data include its business records, communications and memory derived for it. A Customer-Specific Deliverable is an item expressly identified as assigned to the Customer in a separate written agreement with MyBot Ltd under section 17. Authorized Users are persons granted access within the agreed internal or external audience.

AlefOS is a work OS built around business relationships and the flow of work. MyBot designs, configures, adapts and operates a company-branded OS according to the signed quotation. The project may include interfaces, workflows, a dashboard, MCP access, telephony, messaging, knowledge, contacts, calendars and other agreed capabilities.

Custom work is not restricted to configurations already delivered to another customer. A quotation may commission a new integration or development, with its specifications, prerequisites and delivery conditions. Illustrations on the website explain possibilities; the signed scope determines what MyBot undertakes to supply. An item outside that scope requires an agreed amendment before additional work or charges are committed.

The OS may serve the Customer’s staff and, where included in the project, its own customers or other external users. The Customer remains responsible for its own business offering and the notices and terms it provides to that audience. Providing access to the commissioned interface does not authorize resale of the underlying technology as a standalone product.

The Customer receives the agreed services and a right to use AlefOS. Branding, customization and payment do not transfer ownership or any share of ownership in AlefOS Technology. A separate project involving different development, delivery or ownership arrangements may be agreed in writing with MyBot Ltd, as set out in section 17.

The quotation identifies the interfaces to be delivered: web environment, dashboard, company-branded interfaces and access through compatible AI assistants, according to the project. These may include newly commissioned interfaces or adaptations, rather than only existing screens.

Third-party assistants and platforms remain independently operated and subject to their own terms, privacy practices, technical requirements and availability. Compatibility does not imply endorsement, affiliation or guaranteed marketplace approval. Connecting an assistant authorizes only the access and actions within the user’s permissions; it does not confer unrestricted authority to buy, publish or consult company records.

The user must provide accurate information when creating and using an account. The user is responsible for the confidentiality of credentials, sessions, OAuth authorizations, connected accounts, and devices used.

The user must promptly inform MyBot Ltd of any suspected unauthorized access, compromise, abuse, or fraudulent use. MyBot Ltd may suspend or restrict an account when necessary to protect AlefOS, prevent abuse, comply with the law, investigate an incident, or avoid a security risk.

The Customer appoints its administrators, defines authorized audiences and maintains access rights as people join, change responsibilities or leave. An administrator or “owner” role is an administrative authority, not personal ownership of all company data. Commercial purchases require the Customer’s authority in addition to technical access.

Removing a member’s access and reassigning their work does not automatically delete the company’s professional history. Individual data protection rights remain applicable. Membership in several organizations does not authorize sharing between them.

The company OS is a bespoke project sold under a signed quotation. That quotation separates, as applicable, design and implementation, customization, integrations, technology access, hosting, support, maintenance, usage capacity and third-party charges. It states amounts, currency, applicable taxes, payment schedule and any recurring commitments.

For this OS offer, the number of members does not automatically create seat fees or additional commercial capacity. This does not mean unlimited storage, calls, processing or resources. The agreed package and usage terms define those limits.

Paying for setup or development does not eliminate recurring fees expressly agreed for operation or maintenance. An option shown on the website is not automatically included.

The Commercial Agreement specifies the work stages, Customer prerequisites, delivery milestones, acceptance procedure and the event that starts each charge or recurring service period. Ordering, paying, installing and accepting delivery are distinct steps. Payment alone is not evidence that a commissioned integration is operational.

The Customer supplies the agreed brand assets, domain access, provider authorizations and other prerequisites. A delay, missing prerequisite or change in scope is handled under the agreed project procedure; it does not silently authorize an extra fee or a new sale. If delivery cannot be completed, the parties apply the agreed remedies and mandatory rights. A retry of the same commissioned installation is not a second purchase.

The Customer pays the agreed fees and applicable taxes. One-off work does not renew automatically. Recurring services renew only under the accepted terms. Refunds and withdrawal rights are governed by the Refund Policy, the Commercial Agreement and mandatory law; abuse checks do not remove statutory rights.

The quotation and any usage annex identify the included capabilities, capacity, measurement method and separately priced resources. No new charge results solely from the publication of a website description. Additional capacity or a different measurement scope requires agreed commercial terms.

Where the OS quotation expressly adopts commercial Loops for ChatGPT access through MCP, one eligible reading or retrieval invocation counts as one reading unit, regardless of how many underlying records it examines. A prompt can lead to several invocations. An action unit corresponds to one completed business effect: four separate publications are four effects; three successful effects and one failure without an effect finalize three action units. A technical retry of the same operation is not charged twice. An uncertain result is reconciled separately, without duplicate charging.

Under that usage model, ingestion, transcription intake, background preparation, memory enrichment, web navigation and automatic notifications do not consume commercial Loops. Specialized resources, including telephone service, provider messages, storage or heavy processing, may have separately agreed costs. Processing minutes are not outbound telephone credit.

The usage annex must expressly identify any other chargeable assistant environments and the treatment of failed reading requests. Their treatment is not inferred from the word MCP. Proportionate security and stability controls remain applicable; they do not authorize undisclosed charges.

The user is responsible for the data, calls, messages, contacts, notes, audio, activated professional sources, WhatsApp conversations, or other sources that the user chooses to connect, transmit, process, or exclude in AlefOS.

The user is responsible for informing their own clients, prospects, contacts, employees, contractors, or partners when required by law.

When a tenant imports, connects, transmits or processes third-party data through AlefOS, the tenant represents that it has the right to do so, has informed the relevant persons when required, and holds the necessary authorizations for the connected, transmitted or processed data. The tenant remains responsible for its relationship with clients, prospects, collaborators, suppliers and contacts.

call recording or call assistance rules, consent, electronic communications, commercial messages, marketing, and prospecting;

professional secrecy, regulated sectors, consumer protection, and personal data processing;

United States rules that may apply to calls, SMS, marketing communications, telemarketing, robocalls, autodialing, and consent. AlefOS does not, by merely being provided, constitute a robocall, autodialing, or SMS marketing service.

These responsibilities also apply to the brands, domains, publications and administrator delegations supplied or approved for the project. A technical permission is not, by itself, a lawful basis for prospecting, recording a call or processing sensitive data. The Customer’s obligations do not release MyBot from its own legal or contractual duties.

CallOS processes the calls, audio and related information included in the agreed project and authorized by the Customer. The project may include calling from a web interface, connecting the usual telephone, adding AlefOS to a supported conference, or integrating a PBX, SIP service, telephony provider or mobile service. A new integration can be commissioned under the quotation.

Processing may follow a deliberate transmission or an integration activated in advance for specified flows; a separate click for every imported call is not necessarily required. This does not authorize general monitoring of all communications. The Customer determines the lawful sources and provides any notices and consents required for recording, transcription and communications.

WhatsApp messages, voice notes and live calling are different services whose scope and delivery prerequisites are specified for the project. External or committing WhatsApp messages prepared by AI require human validation before sending. Sending uses the official WhatsApp Business Platform or an authorized provider where enabled, with agreed third-party costs. Configured service notifications, authentication messages and reminders are distinct from AI-generated external actions and do not prove that an underlying task was completed.

GroupOS provides shared professional memory for authorized audiences: instructions, training, meeting notes, field knowledge and other information the Customer chooses to share. Access follows the permissions and group settings for the project.

The publishing user and Customer must have the right to disclose the content, including any personal data, business secrets or protected material. Where the quotation includes publication to an external audience, only the content and audience expressly selected for that publication are exposed. Submitting a form does not itself confer a right to read a group or the company’s history.

ProductOS is the AlefOS business catalog component. It allows products, services, professional offerings, and know-how to be detected, structured, validated, and retrieved.

AlefOS may detect product or service mentions in authorized flows, for example when a user explains a service to a client, proposes a legal service, repairs equipment, installs a charging station, performs plumbing work, or provides another professional service.

These detections may generate mentions, suggestions, or validation missions. The user remains responsible for confirming, correcting, archiving, or deleting proposed products or services before any important use, external publication, or synchronization with a third-party service.

Confirmed products or services may be used within the authorized scope to help retrieve a professional, prepare a record, answer a request, structure a catalog, or feed an authorized product surface or integration when available and validated. AlefOS is not a public marketplace by default.

The Customer’s ProductOS catalog is separate from MyBot’s commercial catalog of AlefOS options and services. The Customer remains the seller or provider of its own offerings. Publishing them does not make it a reseller of AlefOS Technology or make MyBot the seller of those offerings.

AlefOS may generate draft actions, missions, reminders, messages, product records, summaries, analyses, or recommendations. Unless expressly stated otherwise, these outputs are decision-support aids and not final decisions.

The user remains responsible for verifying and validating important actions before relying on them, sending them to a third party, or executing them. Draft → Confirm applies to external or engaging actions, not every internal memory write.

The ability to propose an action is separate from the authority to execute it. Permissions and required confirmations remain applicable when an assistant is used. Automatic internal analysis, memory updates and configured service notifications are not subject to a universal confirmation requirement. A notification or sending status does not prove that the recipient read it or that the underlying business action succeeded.

AlefOS may use artificial intelligence systems and, depending on configuration, inference or transcription providers to extract signals, classify information, generate summaries, prepare actions, structure products, recommend follow-ups, or retrieve context.

AI outputs may be inaccurate, incomplete, outdated, or unsuitable for a particular situation. AlefOS does not provide legal, medical, financial, tax, insurance, employment, engineering, or other certified professional advice. The user must verify outputs before using them in an important decision, professional communication, or action with significant effect.

Relationship inferences are also fallible and must not be treated as verified facts merely because they appear in a customer record. These reservations do not remove MyBot’s own obligations or any expressly agreed service commitments.

It is prohibited to use AlefOS to:

violate applicable law or process data the user has no right to process;

send spam, unlawful messages, automated calls, robocalls, or unsolicited SMS;

import or process illegal, dangerous, defamatory, discriminatory, or abusive content;

process sensitive data without an appropriate legal basis;

publish personal, confidential, or protected data in an AlefOS group without the right or required notice/authorization;

present a product or service in a misleading, unlawful, or non-compliant way;

impersonate a person, access another user's data, bypass security measures, overload, scrape, attack, or disrupt AlefOS;

copy AlefOS structure, tools, prompts, engines, flows, or architecture to build a competing service;

use AlefOS in a regulated sector without verifying that the use is authorized.

Restrictions on copying, reverse engineering or interoperability apply only to the extent permitted by mandatory law. They do not prohibit the external-user access expressly included in the project or the exercise of lawful data export rights. They do not grant a standalone right to distribute AlefOS Technology.

The Customer retains its rights in its data and in the professional memory derived for it, subject to individuals’ and third parties’ rights. MyBot acquires no ownership in that content merely by organizing, processing or hosting it.

MyBot processes business data for the Customer under the DPA and its documented instructions. MyBot separately determines certain purposes relating to its own accounts, billing, commercial relationship, security and legal obligations as explained in the Privacy Policy. Access to a customer file for support remains distinct from administrative handling of a support request. Only the rights necessary for the agreed service and applicable legal obligations are granted; no general right to sell, prospect using, or train general third-party AI models on Customer Data is created.

A bespoke project can connect or adapt third-party services, including telephony, PBX, eSIM, messaging and meeting providers. The quotation identifies the required accounts, authorizations, interfaces, costs and responsibilities. An integration may be newly developed for the project. An example on the website does not guarantee a third party’s approval or waive its technical prerequisites.

Distinguish suppliers engaged by MyBot, services contracted by the Customer and independent AI assistants chosen by users. Customer-contracted services remain subject to their own agreements. Changes or failures outside MyBot’s control are addressed under the project’s agreed conditions; MyBot’s own integration commitments and responsibilities for its subprocessors remain applicable. Ending an AlefOS connection does not transfer ownership of the Customer’s third-party account to MyBot.

The Customer retains its rights in its brand, materials and data. It grants MyBot the limited rights needed to design, configure, host, operate and support the commissioned service.

AlefOS Technology remains the property of MyBot or its licensors. The Customer receives a non-exclusive right to use it through the agreed interfaces, for the contract duration and the authorized internal or external audience. Its branded environment does not give it ownership or any share of ownership in AlefOS, its source code or its common components.

Payment for design, implementation, development or customization does not transfer those rights. Reusable software, methods, workflows and generic improvements remain part of AlefOS Technology; this does not give MyBot ownership of the Customer’s confidential business methods, data or brand. Standalone resale, assignment or sublicensing of the technology is not included in the right of use.

A separate project involving different development, delivery or ownership arrangements may be agreed in a prior written agreement with MyBot Ltd. That agreement identifies the deliverables, financial conditions and rights expressly granted or assigned. Only the rights identified in that agreement are granted; it does not imply a transfer of other AlefOS components. To discuss such a project, contact MyBot Ltd.

These provisions remain subject to mandatory law, including applicable interoperability and data-exit rights.

Feedback may be used to improve AlefOS without compensation, without appropriating Customer Data, brand assets, trade secrets or confidential methods. Feedback is not permission to train general AI models on customer conversations or to publish a customer reference.

Each party protects non-public information reasonably understood to be confidential and uses it only for the contractual relationship. Access is limited to people who need it and are bound to confidentiality. Exceptions concern information lawfully public, already lawfully known without restrictions, independently developed without use of confidential information, or lawfully received from a third party. A legally compelled disclosure is limited to what is required, with advance notice where permitted. Any separate NDA continues to apply. Confidentiality survives termination for as long as the information remains protected.

AlefOS may evolve over time. Features, connectors, tools, limits, models, providers, interfaces, or workflows may be added, modified, restricted, or removed for technical, legal, operational, security, or product reasons.

MyBot Ltd does not guarantee permanent, uninterrupted, or error-free availability.

These evolution rights remain subject to the signed project, its delivery obligations and any agreed support, maintenance or service levels. They do not permit MyBot to remove a paid contractual deliverable without applying the agreed remedies and mandatory rights. A specific availability or response commitment exists only where expressly agreed.

Termination follows the applicable Commercial Agreement. MyBot may restrict or suspend access where necessary to address material breach, non-payment, unlawful use or a material security risk, with an opportunity to remedy where appropriate and reasonably possible. The parties’ accrued rights and mandatory remedies remain applicable.

When the relevant licence or service ends, access to the corresponding AlefOS Technology and dependent interfaces ends. Ownership of the Customer’s brand or deliverables does not provide a perpetual licence to the underlying technology. Removing one member or option is distinct from terminating the company’s service.

The Customer retains its rights in its data, brand, domain and third-party accounts. The agreed exit arrangements identify exportable data and assets, formats, retrieval period, assistance, permitted fees and the treatment of backups. Statutory return, deletion and switching rights remain applicable; technical inconvenience is not a general veto on them. For data processed on behalf of the Customer, return or deletion follows the DPA. Protecting proprietary software does not authorize withholding Customer Data.

Before an AlefOS-operated technical recovery address is closed, the parties organize the agreed transfer of recovery access for accounts belonging to the Customer. Ending the domain’s connection to AlefOS does not delete or transfer ownership of the domain. Continued use of third-party services follows the Customer’s agreements with those providers. Confidentiality, intellectual property, accrued payment obligations and provisions intended to survive remain applicable.

AlefOS is provided, to the fullest extent permitted by law, as is and as available. MyBot Ltd does not guarantee that AlefOS will detect every signal, prevent every omission, identify every business opportunity, produce perfect summaries, or generate error-free results.

AlefOS is a professional assistance system, not a substitute for the user's judgment, professional obligations, or legal responsibilities.

These reservations do not override express commitments in the signed quotation or mandatory guarantees.

To the fullest extent permitted by applicable law, MyBot Ltd is not liable for indirect damages, loss of profit, loss of business, loss of opportunity, loss of data, reputational harm, or claims resulting from misuse of the service, third-party services, inaccurate information provided by the user, or decisions made without appropriate human verification.

Nothing in these Terms limits liability where the law prohibits such limitation.

These limitations apply only within their lawful scope and do not eliminate MyBot’s own duties under the DPA or express commitments for paid services. Specific liability limits apply only where agreed and legally permitted. No general monetary cap is created by these Terms.

To the extent permitted by law, the contracting Customer is responsible for indemnifying MyBot against third-party claims attributable to its unlawful use, breach of these Terms, infringement of third-party rights, or failure to provide required notices or obtain necessary authority. This does not transfer MyBot’s own responsibility to the Customer or impose the Customer’s commercial obligations personally on every employee, visitor or data subject.

These Terms are governed by Israeli law, unless mandatory rules applicable to a consumer, data subject, regulated activity, or mandatory jurisdiction provide otherwise.

Disputes will be submitted to the competent courts of Israel, subject to mandatory jurisdiction rules that cannot be waived.

For any question relating to AlefOS, support, billing, privacy, or these Terms, contact support@alefos.ai.

Material changes to these Terms are communicated with their effective date in accordance with the contract and applicable law. The signed agreement and its written amendments specify the terms governing the project.