Terms of service
General service terms and usage conditions.
Legal center
The documents behind the decision.
Use the published terms and privacy policy for general information. Confirm account-specific data, support, billing, export, and managed-delivery commitments in the agreement you actually sign.
Published documents
Start with the canonical pages.
These pages are the public reference points. An order form, invoice, dashboard agreement, or signed contract may add account-specific terms.
Privacy policy
Public information about privacy and data handling.
Pricing
Current public offers and starting prices. Exact scope belongs in a proposal or order form.
Security
Implemented security controls, limitations, disclosure contact, and production checks.
Reliability
Runtime safeguards and the backup, restore, incident, and support items to confirm.
Trust center
A concise separation of verified platform capability and customer-specific assurance.
Before purchase
Put the important promises in writing.
Do not rely on a feature page to define commercial or legal commitments. Confirm the items that matter to your workload in the applicable agreement.
Commercial terms
- Exact deliverables, exclusions, acceptance criteria, and timeline
- Price, taxes, payment method, renewal, and cancellation
- Refund, upgrade, downgrade, overage, and support terms
- Who owns implementation, testing, deployment, and maintenance
Data and operations
- Controller and processor roles, DPA, subprocessors, and residency
- Retention, deletion, export, backup, restore, and incident process
- Security or compliance requirements for the intended data
- Uptime, escalation, response, and recovery commitments
IP and portability
Separate product capability from contractual rights.
Spala has real export surfaces, but technical output and legal ownership are different questions.
| Question | Current product fact | What to confirm |
|---|---|---|
| Can project data be exported? | Export routes support JSON and CSV data surfaces. | Which data is included, when export is available, and retention after cancellation. |
| Can a runtime be packaged? | Spala can produce packaged runtime ZIP output. | What the package includes, hosting responsibility, secrets, support, and deployment rights. |
| Is Spala open source? | No. The main Spala product is not currently open source. | License terms for any delivered runtime, SDK, or managed implementation. |
| Does export guarantee no lock-in? | No. Export capability does not prove an easy migration to every platform. | Migration scope, target compatibility, data transfer, replacement services, and assistance. |
Need a DPA, subprocessor list, custom support terms, or managed-build scope? Ask for the current account-specific document before putting sensitive data into production.
Make the agreement match the workload.
Tell Spala what data, reliability, support, export, and delivery terms your application requires before you purchase.