Essential definitions
The order form identifies the customer, scope, term, and price. Customer content includes data, files, instructions, and prompts submitted by the customer. Output means a result generated with a model or agent. Agent means an automated capability that may perform multiple steps or use tools within an authorized scope.
- User: an individual authorized by the customer to access its organization.
- Integration: a connection to an external service enabled by the customer.
- Gate: a control point that may require review or approval for a supported transition.
- Documentation: technical and usage instructions applicable to the contracted version.
Parties and business use
These terms are proposed between BIK AI Technologies, S.L.U. and the organization identified in an order form. Anyone accepting or signing represents that they have authority to bind that organization. The service is offered to businesses, professionals, and entities rather than as a consumer product.
Documents and priority
The agreement may include an order form, these terms, the DPA, usage policy, applicable documentation, and specific annexes. If they conflict, a signed order and specific terms take priority, followed by the DPA for data-protection matters and then the remaining incorporated documents.
Service and capability status
BIKLABS organizes projects, knowledge, and AI capabilities within the contracted scope. Features identified as preview, alpha, pilot, experimental, or future may change, have different limits, or be withdrawn and must not be used as critical dependencies unless expressly agreed.
Screenshots, roadmaps, and commercial pages explain direction and use cases; they do not independently expand the contracted service or create a commitment to deliver future functionality.
Accounts and administration
The customer controls onboarding, removal, roles, permissions, integrations, and agents in its organization. It must protect credentials, use individual identities where appropriate, and promptly tell us about unauthorized access or loss of control over an account or token.
Customer obligations
The customer must use the service in accordance with law, these terms, and the usage policy; provide lawful instructions; hold the necessary rights in content; keep its administrators current; and reasonably cooperate in investigating an incident, abuse, or claim relating to its organization.
It must also inform its users about AI use where appropriate and must not present a preview capability, output, or automated action as carrying guarantees BIKLABS has not expressly undertaken.
Content, inputs, and outputs
The customer retains the rights it holds in data, documents, instructions, prompts, and other submitted content. It grants BIKLABS only the rights needed to host, process, transmit, and display that content when providing and protecting the service.
Rights in and permitted uses of an output may depend on law, the model used, third-party content, and selected configuration. Outputs may not be unique, and the customer must review whether use infringes rights or breaches obligations.
Third-party models and integrations
The customer may select models, provide keys, or connect third-party services. Their terms, regions, retention, and policies may apply directly. BIKLABS does not control a service selected by the customer; the order form or DPA should identify whether a provider acts as a BIKLABS subprocessor or directly for the customer.
AI, agents, and oversight
Models and agents may generate inaccurate, incomplete, biased, or outdated results and may take action when given tools and permissions. The customer determines the purpose, context, scope, gates, and human review appropriate to the risk.
An output must not be attributed to a person or used as the sole basis for a high-impact decision. The usage policy applies to users, automations, and connected agents.
External actions and reversibility
A tool, API, or integration may create effects in BIKLABS or a third-party system. The customer authorizes those effects when it configures permissions and runs or approves an operation, and must validate recipients, scope, and consequences before enabling sensitive actions.
Not every action can be undone. Gates, logs, and previews reduce risk where available, but do not by themselves create a recoverable copy or guarantee reversal in an external service.
Evaluations, preview, and beta
Trials, pilots, sandboxes, and features without general availability are provided for evaluation and may have different support, retention, limits, or safeguards. They must not process personal data or critical information unless the order form and DPA expressly permit it.
Privacy and security
Where BIKLABS processes personal data for the customer, the DPA defines instructions, measures, assistance, subprocessors, and return or deletion. Each party meets the obligations applicable to it as controller or processor.
We apply technical and organizational measures proportionate to risk. No measure eliminates all risk, and the customer must configure access, data, and integrations consistently with its own assessment.
Fees, taxes, and payment
Prices, billing units, AI consumption, period, taxes, due dates, renewal, and adjustments are set in the applicable order form or purchase screen. No price, credit, refund, or SLA applies unless expressly agreed.
Confidentiality
Each party protects the other's confidential information with reasonable care, uses it only to perform the relationship, and shares it only with personnel or providers who need to know and are subject to appropriate obligations. It excludes information made public without breach, lawfully received, or independently developed.
Intellectual property and feedback
BIK AI Technologies, S.L.U. and its licensors retain rights in BIKLABS, its technology, design, and documentation. Nothing grants the customer ownership of the service. We may use voluntarily supplied feedback to improve the product without publishing customer confidential information.
Suspension and termination
We may limit or suspend access where reasonably necessary to contain a security risk, stop abuse, comply with law, or respond to a material breach. Where feasible, we will give notice and a reasonable opportunity to remediate.
Term, renewal, termination, export, and deletion are defined by the order form and DPA. Ending the agreement does not remove payment, confidentiality, intellectual-property, or other obligations that by nature should survive.
Export and continuity
During the term, the customer may request or use export mechanisms available within the contracted scope. Format, post-termination access period, and migration assistance are defined in the order form; BIKLABS does not guarantee that a third party can import every field, relationship, or history entry.
Availability and liability
Availability, support, and recovery commitments exist only where stated in an order form or SLA. To the extent permitted by law, applicable exclusions, liability caps, and indemnities must be stated in the agreed contract and are not inferred from this information page.
Changes, law, and contact
Accepted terms should state how material changes are notified. The contractual version is governed by the law and jurisdiction in the order form; unless otherwise agreed, Spanish law and its competent courts apply. Questions: admin@biklabs.ai.