Disclaimer
Last updated: September 2, 2026
DeepSpace is a developer platform and SDK for building real-time collaborative apps. This page sets out important limitations of the service that are not separate legal terms but that you should understand before relying on the platform.
AI-generated content
Code, copy, schemas, audio, images, and other output produced by AI features in the SDK or in apps built on it is generated by large-language models or other AI systems. It can be confidently wrong.
Treat AI output as a starting point. Review, test, and verify it before deploying to production, before publishing, and before relying on it for anything important.
- AI output may contain bugs, security vulnerabilities, or insecure defaults.
- AI output may include patterns or text that resemble third-party content; you are responsible for ensuring it does not infringe.
- AI output may misuse APIs, hallucinate functions, or include outdated practices.
- AI features depend on third-party model providers. Their availability, behavior, and pricing change over time, and may change without notice.
- We do not currently set provider-specific opt-out headers on outbound AI traffic. Each provider treats prompts and outputs according to its standard API default, which for most providers in this list excludes use for model training but may allow short-term retention for safety, abuse monitoring, or service quality. Treat anything you send through an AI feature as visible to that provider on its standard API terms.
- The SDK's scaffolded AI chat feature, by default, saves each turn of a conversation — your messages, the assistant's replies, and any tool calls the assistant makes — into the app's database, and gives the assistant tools to create, update, and delete records on your behalf, bounded by your role-based permissions inside the app. App developers can narrow this default. If you are using an app whose AI assistant feels like it has too much reach, ask the developer of that app what they have configured.
Apps built on the platform
Apps shipped on the DeepSpace platform are operated by the developers who deployed them, not by DeepSpace. We provide the infrastructure (authentication, storage, deploys, payments, integrations), but the design, behavior, accuracy, and quality of each app are the responsibility of the developer who built it.
If you sign in to an app at a *.app.space subdomain or at a custom domain attached through us, the developer of that app determines what the app does with your data, subject to that developer's own privacy policy and terms.
Shared files inside an app
Each app's data is private to that app; there is no platform-wide store that other apps can read. However, files an app places in its shared, app-wide file area are served without authentication, so anyone who has a file's URL can retrieve it. Developers are required by our Terms to keep personal and private content out of that area and to tell their users when an upload will be publicly retrievable. If you use an app, treat anything it publishes as a shared file as not private.
Beta and preview features
- DeepSpace is in beta. SDK APIs, schemas, defaults, integration availability, pricing, and quotas can change as the platform evolves. Backwards-incompatible SDK changes are possible until we reach a stable major version; pin your SDK version in production.
- Features marked beta, preview, experimental, or alpha may change, break, or be removed at any time.
- We will provide commercially reasonable notice of material changes that affect paying developers, except where shorter notice is required for security, legal, or regulatory reasons.
No professional advice
Nothing produced by the SDK, the AI features, or any app built on the platform is intended to be medical, legal, financial, accounting, tax, mental-health, immigration, or other professional advice. If a developer builds an app in one of those domains, end-users should consult a qualified professional, and the developer should make that clear inside the app.
Third-party services
The platform integrates with third-party services, including model providers, OAuth providers, payment processors, voice and audio providers, and domain registrars. Their availability, accuracy, and terms are outside our control. An outage or change on their side may affect features that depend on them, and your use of those services through us is also subject to their own terms.
Payments
Payments inside apps are processed through Stripe. We are the merchant of record for those payments, but we are not a bank, do not lend money, and do not act as an escrow agent. Funds in transit are held briefly through Stripe before being paid out to the responsible developer or refunded.
Custom domains and hosted source repositories
When you purchase a domain through us, we register it on your behalf at Cloudflare Registrar or Porkbun, holding the registration under a platform account with DeepSpace as the registrant of record. The lifecycle of the domain — registration, renewal, transfer-out, and any registry- or registrar-level outage — depends on those providers and on the registry rules for the relevant top-level domain. Once a domain has been registered with the registry the registration is non-refundable, and domains that lapse for non-payment may be suspended or released by the registry. The full registrant-on-record arrangement is set out in Terms §8.
When DeepSpace hosts your app's source repository, the repository lives on the platform's own Cloudflare infrastructure — not on GitHub or any other third-party code host — and we hold it on your behalf. A hosted repository is not a substitute for your own backups; we may impose creation and deletion quotas, and we may delete repositories that become inactive after reasonable notice. The full arrangement is set out in Terms §9.
No warranty of fitness for any particular purpose
The service is general-purpose infrastructure. We make no claim that it is suitable for any specific use, including high-stakes, regulated, life-safety, or mission-critical workloads. You decide whether DeepSpace is the right place to run your app, and you accept the operational risk of that decision.
Security
- We follow reasonable industry practices, but no platform is perfectly secure. We are pursuing a SOC 2 Type II examination but have not yet received a SOC 2 or ISO 27001 report.
- Do not send us regulated personal data (including cardholder data, healthcare data, or government identity documents) through any channel other than the payment integration described in the Terms.
Privacy requests
To access, export, or delete the personal data we hold about you, or to report a concern about how your data has been handled, contact privacy@deep.space. We verify requests before acting on them, and complete verified deletion requests within 30 days, except where we are required to retain information by law or by a written agreement with you.
Security concerns
If you have a security or vulnerability concern, reach out to security@deep.space. We appreciate responsible disclosure.