Terms of Service
Rules for the Continuum Memory API, SDK integrations and developer console.
Last updated: 10 October 2026
1. Agreement and service
These Terms govern Syntarus's hosted Continuum Memory API, developer console and related integrations (“Service”). By using it you accept these Terms and the Privacy Policy. A signed enterprise agreement takes precedence for matters it expressly covers.
Continuum stores and retrieves application-provided context. It is not your agent's answer model, CRM, payment processor or action-authorisation system. You remain responsible for your application and its decisions.
2. Accounts, projects and credentials
You must be legally able to enter this agreement and authorised to act for any organisation you represent. The Service is not directed to children; users must be at least 13 or the higher minimum age required by law. Keep sign-in accounts, API keys, delegated tokens and webhook secrets secure. You are responsible for activity under your credentials and reporting suspected compromise.
Onboarding is project-first: sign in, create a named project, then create a scoped key. Keep keys server-side or in a suitable secret store, never public repositories or browser bundles. Assign required scopes only, revoke compromised credentials and map customer/user/agent namespaces correctly. Do not access another customer's project.
3. Content and permissions
You retain ownership of submitted content. You grant Syntarus the limited permission needed to store, index, process, retrieve and deliver it and derived context to operate the Service, including configured provider processing and necessary recovery/retention described in the Privacy Policy.
You must have the rights, notices, consent or other lawful basis needed to submit and process end-user information. Do not ingest credentials or unauthorised confidential content. Confirm processing terms and suitability before submitting sensitive or regulated content. You are responsible for your end-user notices and requests.
4. API lifecycle rules
- Accepted is not completed: writes and deletion jobs can return receipts before processing finishes. Poll the event or verify the completion webhook; handle failures explicitly.
- Retries: use supported stable idempotency keys for the same operation, bounded backoff and timeout handling. Do not repeatedly write just to force visibility.
- Scope: use consistent project, user and optional agent identifiers. Key revocation does not erase content.
- Modes: choose direct, document or model-enabled ingestion for your workflow. Extraction/graph processing can add time, source-token use and provider dependency.
- Consequential actions: inspect sources and freshness, then verify authoritative balances, permissions and current business state before acting.
5. Plans, limits and billing
Published prices and allowances appear on the pricing page and in the console; purchased capacity and enterprise terms follow your order or agreement. Project, request, source-token, memory and other applicable limits are separate. A write allowance is not unlimited extraction tokens, storage or provider usage.
Handle rate-limit and quota responses rather than bypassing them. Price, taxes, cycle, renewal, refund and any overage terms must be disclosed in the applicable purchase terms. These Terms do not introduce new credit multipliers, change your plan or authorise undisclosed overage charges. The free sandbox has no uptime SLA.
6. Acceptable use
Do not violate law or others' rights; ingest or disclose information without authority; impersonate others; expose credentials; evade quotas or scope checks; conduct unauthorised security testing; distribute malware; or disrupt shared infrastructure. Follow third-party integration terms.
We may limit/suspend access for abuse, security risk, unpaid agreed charges or legal obligations. Where reasonably possible we provide notice and a way to resolve the issue. Coordinated security reports: [email protected].
7. Availability and accuracy
General hosted access does not promise uninterrupted availability, fixed latency, perfect recall or error-free state resolution. Formal SLAs, certifications, residency guarantees and recovery commitments require explicit agreement. Model, network and infrastructure providers can affect processing. Benchmarks apply to stated test configurations, not every customer workflow.
Keep authoritative records, suitable fallbacks and recovery/export procedures. Short conversations can remain in your existing context window; choose memory infrastructure for the actual workload.
8. Data controls and termination
Use supported export/deletion controls and verify asynchronous receipts. Memory deletion, end-user purge, project/account closure and backup expiry are distinct operations. Retention settings do not guarantee removal of all source job payloads or operational records. See the Privacy Policy and contact us for broader closure or legal deletion requests.
You can stop using the Service or request closure at [email protected]. We may suspend/terminate access for breaches, security or legal requirements, subject to contract and law. Ownership, accrued payment duties and provisions that naturally survive remain effective.
9. Warranties and liability
Except obligations that cannot be excluded by law or are expressly agreed in writing, the Service is provided “as is” and “as available”, without warranties of merchantability, fitness for purpose, accuracy or non-infringement. Verify important outputs; this is not qualified professional advice.
To the maximum extent permitted by law, Syntarus is not liable for indirect, incidental, special, consequential or punitive damages, including loss of profits, goodwill or business interruption. Unless a signed agreement provides otherwise, aggregate liability relating to the Service is limited to the greater of the amount you paid Syntarus in the preceding twelve months or INR 1,000. Mandatory statutory rights and liabilities are unaffected.
10. Indemnity and law
To the extent permitted by law, you agree to defend and hold Syntarus harmless from third-party claims arising from unlawful content, misuse or violation of these Terms. These Terms are governed by Indian law; disputes are subject to courts in India, subject to mandatory law and any signed agreement.
11. Changes and contact
Material changes will be announced through the console or email at least 14 days before taking effect where applicable, except changes required sooner for law/security. We identify the revision date. Continued use after applicable changes take effect constitutes acceptance, subject to law and signed agreements.
Questions about service, privacy, terms or enterprise agreements: [email protected].