Rules for using SPLime

Agreement

Operator and acceptance

The SPLime hosted service is operated by Iastrebov Kirill as an individual operating the SPLime project. No incorporated SPLime company currently exists. In these Terms, "SPLime," "the Service," "we" and "us" refer to that hosted project and its operator unless the context refers to separately licensed code.

By creating an account or using the hosted Service, you agree to these Terms. You must be at least 18 years old and legally capable of accepting them. The Service is intended for developers, researchers, professionals and business users. If you act for an organization, you confirm that you have authority to bind it.

If you do not agree, do not use the hosted Service. These Terms do not waive any mandatory right or protection that applicable law does not allow you to waive.

Different legal layers

Open-source framework and hosted Service

The spl repository/package is made available under the Apache License, Version 2.0, as stated in its package metadata and accompanying LICENSE and NOTICE files. That licence governs use, modification and distribution of the code it covers. Read the framework licence file and the authoritative Apache License 2.0 text.

These Terms do not replace, restate or modify the Apache licence. The hosted SPLime Service, Console, server operation, accounts, SPLime branding, website and managed features are governed by these Terms. A repository, plugin, component, document, logo or asset without an explicit licence is not automatically licensed under Apache-2.0 merely because it interoperates with the framework.

Access

Accounts and security

• Provide accurate account and profile information and keep it reasonably current.
• Use the account only for yourself or people you are authorized to represent. Configure team roles, Library grants, invitations and credential scopes carefully.
• Protect identity-provider credentials, Console sessions, user and Machine tokens, daemon master tokens, provider keys and recovery material. Do not place secrets in source, notebooks, URLs, logs or support messages.
• Notify splime.project@gmail.com promptly if an account, token, Worker or target may be compromised, and revoke or rotate affected credentials where possible.
• You are responsible for Workers, execution targets and authorized users connected through your account, including their environments, permissions and external-system access.

SPLime may require reauthentication, limit credential scopes, revoke a compromised session or credential, or temporarily restrict access when reasonably needed to protect the Service or its users.

Ownership

Your code, data and other content

You retain ownership of your code, data, Functions, Pipelines, Adapters, notebooks, definitions, inputs, outputs, artifacts and other content. SPLime does not claim ownership of that content.

You grant SPLime a limited, worldwide, non-exclusive licence to host, cache, copy, transmit, format, reproduce and execute your content only as necessary to provide, maintain and secure the operations you choose. This licence ends when the content is deleted from the Service, except for copies retained temporarily in backups or as necessary for audit, security, shared-resource integrity, legal obligations or claims.

Publishing or sharing a resource grants access only according to the Library visibility, team role, invitation, token and access settings you select. You must have all rights needed to submit, share, execute and licence the content and dependencies involved, including third-party code, data, models, packages and external services.

User-controlled code

Execution and Adapter risks

SPLime coordinates execution; user code and custom Adapters run on selected local or remote Workers. Depending on their code and permissions, they can consume CPU, memory, storage or network capacity; read or modify files; call external services; create costs; expose data; and produce repeatable or non-repeatable side effects.

Runs can fail because of source, dependencies, environment differences, permissions, data, connectivity, target state, timeouts or external systems. Native and virtual- environment execution is not a security sandbox. A Docker boundary depends on its mounts, network and host configuration.

You must review source, target, runtime, Adapters, dependencies, inputs, telemetry and likely side effects before execution. Keep independent backups and use least privilege. Stop, cancel, timeout or retry is not an undo operation and does not guarantee reversal of an external side effect. A retry can execute code again; SPLime does not promise exactly-once execution.

Managed assistance

AI features require review

Managed AI is a separate explicit action. Review the proposed transfer and exclusions before sending source or context. AI output can be incomplete, insecure, biased, incompatible, outdated or wrong. Treat it as an editable draft, inspect it for secrets and licensing issues, and test it in an appropriate isolated environment.

The current implemented operations return proposals or explanations. They do not automatically write, publish or execute code. A later user action using ordinary product controls may do so, and that action remains the user's responsibility. Provider terms and the managed-AI disclosures in the Privacy Policy also apply.

Prohibited conduct

Acceptable use

You must not use the Service to:

• create, distribute or operate malware, destructive payloads or credential-stealing tools;
• access an account, Worker, system, network or data without authorization, or help another person do so;
• steal, expose, trade or misuse credentials, tokens, secrets or personal data;
• abuse Workers, provider resources or third-party infrastructure, including through denial-of-service, unauthorized cryptomining or avoidable resource exhaustion;
• conduct unlawful surveillance or process personal data without a lawful right to do so;
• infringe intellectual-property, privacy, confidentiality or other rights;
• bypass or probe security, quotas, rate limits, access restrictions, grant checks or provider safeguards except for an authorized, responsibly conducted security test;
• deceive users about an execution, result, identity, payment, entitlement or AI output, or intentionally cause unlawful or material harm; or
• upload, share or execute code, data or dependencies you are not authorized to use.

Active development

Pre-release Service

SPLime is under active development. Alpha, preview, Early Access and other pre-release features may be incomplete, unavailable, defective or changed in incompatible ways. Data models, routes, interfaces and behavior may change as the project matures.

Any compatibility commitment applies only where it is specifically documented for a stated release or contract. These Terms do not create a service-level agreement, uptime commitment, support response time or promise that a preview becomes generally available.

Coming Soon

Paid plans and Early Access are not yet a purchase

Paid plans and Early Access are currently marked Coming Soon. Recording interest, reserving an offer or requesting access is not a purchase or subscription. The present flow does not take payment, create a recurring charge, automatically renew, collect payment-card details or guarantee access, availability, a price or a promotion.

Before any future paid contract is formed, applicable plan terms, price, billing period, taxes, provider, cancellation, renewal and refund information will be presented for review. Mandatory consumer rights will be preserved. Current reservations may expire or be withdrawn and do not require SPLime to launch a particular plan or feature.

Operations

Availability, changes, suspension and termination

SPLime may maintain, repair or change the Service, retire an unsafe or obsolete feature, impose reasonable technical limits, or interrupt availability for security, dependency, infrastructure or operational reasons. Where practicable, material changes affecting active users will be communicated through the site, Console or account contact.

Access may be suspended or limited when reasonably necessary to investigate a security incident, protect another user or Worker, comply with law, prevent abuse, or address a material breach of these Terms. An account may be terminated for a material or repeated breach after appropriate notice where circumstances permit. Nothing here creates an unrestricted right to remove a paid service or overrides a mandatory notice, remedy, refund or consumer protection.

You may stop using the Service and request account or content action by contacting splime.project@gmail.com. Some records may remain as described in the Privacy Policy.

External dependencies

Third-party services and licences

Identity providers, AI providers, packages, container images, operating systems, notebooks, user infrastructure, Workers, databases and external APIs may be supplied by third parties. Their availability, security, licences, charges, terms and privacy practices are separate from SPLime's.

You are responsible for reviewing third-party terms and licence obligations that apply to your environment and content. SPLime is not responsible for a third party's service, except to the extent applicable law makes responsibility non-excludable.

No operational guarantee

Warranties

To the maximum extent permitted by applicable law, the hosted Service and pre-release features are provided on an "as available" basis. SPLime does not guarantee that they will be uninterrupted, secure, error-free, compatible with every environment, or fit for a particular purpose, or that a result, artifact, analysis or AI output is accurate.

You must maintain appropriate backups, validate outputs and security, and test critical workflows before relying on them. This section does not exclude a warranty or remedy that applicable law does not allow to be excluded.

Limits

Liability

To the maximum extent permitted by applicable law, SPLime is not liable for indirect, incidental, special, exemplary or consequential loss, or for lost profits, revenue, business, opportunity, goodwill or data, arising from use of or inability to use the Service. This limitation applies only where and to the extent the law permits it.

Nothing in these Terms excludes or limits liability that cannot legally be excluded or limited, including any mandatory liability for fraud, deliberate misconduct, death or personal injury where applicable law so provides. No arbitrary monetary liability cap is stated because no formal governing jurisdiction or approved cap has been selected.

Professional and business use

Limited business indemnity

If you use the Service as a professional or business user, and only to the extent permitted by applicable law, you will defend and indemnify Iastrebov Kirill against a third-party claim caused by your unlawful content, your infringement of that third party's rights, or your deliberate material violation of the Acceptable Use section.

This section does not apply to a consumer where applicable law prohibits it, does not cover a claim caused by SPLime's own conduct, and does not override non-waivable rights or defenses.

Interim clause

Applicable law and disputes

These Terms are governed by the law that applies under the relevant conflict-of-law, consumer and mandatory rules. They do not select an exclusive country, governing law, court or arbitration forum. Any mandatory local or consumer right, remedy and venue is preserved.

Before starting formal proceedings, please contact splime.project@gmail.com and describe the issue so an informal resolution can be attempted. This does not prevent either party from seeking urgent relief or using a complaint or court process available under applicable law.

A formal governing-law and forum clause may be proposed in a future Terms update after an operating company and jurisdiction are selected. It will not apply retroactively in a way that removes mandatory rights.