Legal

Privacy Policy

Effective date: March 14, 2026

Overview

This Privacy Policy explains how Spatial ("we", "our", or "us") collects, uses, stores, and shares information when you use our website, desktop application, web dashboard, APIs, and related services (collectively, the "Service").

Spatial is an AI-native coding platform. Some data stays on your device, some data is stored on our systems to provide hosted features, and some data is sent to third-party AI providers or integrations when you ask the Service to use them. This policy describes those flows at a practical level.

Information we collect

Account and profile information

When you create or manage an account, we collect information such as your email address, display name, avatar, account identifiers, authentication method, email verification status, and basic account metadata. If you sign in with GitHub or another provider we also receive the profile information that provider makes available to us.

Billing and transaction information

Billing and credit purchases are handled through Polar and its payment partners. We do not store your full card number. We do store and receive transaction-related data such as Polar customer IDs, order IDs, balance history, billing events, and receipts so we can manage your paid account access and balance.

Session, project, and workspace data

Depending on the feature you use, we may store project names, session metadata, conversation history, prompts, assistant responses, attachments, tool-call records, model selections, usage records, and memories created during a session. We may also collect or review conversation data for service quality, LLM correctness evaluation, observability, debugging, abuse prevention, and support. This is necessary for features such as hosted session continuity, usage accounting, feedback review, and restoring prior work.

The desktop application also stores data locally on your device, including local session transcripts, project metadata, attachments, preferences, and related app state. Local data remains under the control of the device and operating-system account where the app is installed unless you use hosted or sync-related features that transmit it to us or third parties.

Code context sent to AI providers

When you use AI features, relevant code, prompts, files, selections, attachments, tool outputs, and other context you provide may be transmitted to one or more third-party AI model providers to generate a response. The exact payload depends on the feature, the selected model, and the context you choose to include.

API keys, secrets, and integrations

If you create Spatial API keys, we store those keys in hashed form and only show you a prefix after creation. If you choose to bring your own provider credentials or connect integrations, we may store encrypted secrets, OAuth access tokens, refresh tokens, token expiry information, and limited account or project metadata needed to keep those integrations working.

Usage, diagnostics, and security data

We collect operational data such as IP address, request timestamps, browser or client metadata, token counts, feature interactions, session counts, account balance changes, device or browser fingerprint signals, and other security or abuse indicators. We use this information to run the Service, enforce plan limits, prevent spam and abuse, diagnose incidents, and measure reliability. We do not use IP addresses or device fingerprints for advertising or cross-site tracking.

Feedback and support communications

If you send us support requests, bug reports, or product feedback, we collect the information you include. If you submit in-product session feedback, we may store recent message content and tool-call context that you chose to send with that feedback.

Cookies and local storage

We use essential cookies and similar storage technologies to keep you signed in, remember security state, and persist preferences such as theme, locale, and similar settings. The desktop app and web client may also use local storage for UI preferences and lightweight client identifiers.

How we use your information

  • To create accounts, authenticate users, and secure the Service
  • To provide coding sessions, project history, memory features, and other core product functionality
  • To route model requests, integrations, and tool calls that you ask us to run
  • To process billing, manage balances, detect fraud, and handle customer support
  • To monitor usage, enforce plan and rate limits, and investigate reliability or abuse issues
  • To improve the Service using aggregated analytics, product diagnostics, and user feedback
  • To comply with legal obligations and protect users, our business, and the public

How we use code, prompts, and AI session content

We use session and workspace content primarily to provide the features you request, such as generating responses, restoring session history, tracking usage, processing feedback you submit, and keeping the Service reliable and secure.

We do not sell your personal information, code, prompts, or session content to third parties, and we do not use that information for third-party advertising or marketing. We also do not use your code, prompts, or private session content to train our own foundation models. We may, however, use de-identified usage patterns, operational metrics, and voluntarily submitted feedback to improve the product.

Third-party AI providers may apply their own retention and data-use rules to the content sent to them. Their policies, not ours, govern how they handle that data once it reaches their systems.

Third-party AI providers and service providers

Every LLM request necessarily runs through a model provider. That provider's own privacy policy and data-handling terms still apply to the request, and the provider may collect, retain, review, or otherwise process conversation data under its own rules. These may include providers such as Anthropic, OpenAI, Google, Meta, Mistral, xAI, DeepSeek, and OpenRouter, as well as billing, authentication, hosting, and infrastructure providers such as Polar, GitHub, and similar service providers that help us operate the Service.

If you connect optional integrations, such as deployment or project management services, we also process the credentials and metadata needed to maintain those connections. We recommend reviewing the terms and privacy policies of every provider you choose to use through Spatial.

In the desktop app, Anthropic-backed Claude models and OpenAI-backed models may run through their corresponding managed local runners, such as Claude Code CLI or Codex CLI, rather than the default hosted Spatial runtime. When that happens, the runner or provider may maintain its own conversation history or account-side logs. We do not control, own, or take responsibility for those runner-managed histories, and we do not collect those separate provider-side histories beyond any local app state or metadata needed to operate the app itself. Review Anthropic's privacy policy and OpenAI's privacy policy for those flows.

Data sharing

We share information only in the following circumstances:

  • AI providers and integrations when you use a model, tool, or connected third-party service
  • Payment and infrastructure providers that help us operate billing, hosting, authentication, email, and security
  • At your direction when you ask us to connect, transmit, export, or share information
  • Legal and safety reasons if required by law, court order, or to protect rights, safety, and the integrity of the Service
  • Business transfers in connection with a merger, acquisition, financing, or sale of assets

Data retention

We keep personal data for as long as reasonably necessary to provide the Service, maintain account history, meet legal and financial obligations, resolve disputes, and enforce our agreements.

In practice, retention varies by data type. Account records, billing records, API key metadata, and integration records may be retained while your account is active and for a period afterward as required for legal, tax, fraud-prevention, and accounting purposes. Session content, memories, and usage records may remain available until you delete them, delete your account, or they are removed under our retention practices.

Standard operational logs are generally retained for up to 90 days unless a longer period is needed for security investigations, dispute resolution, or legal compliance. Locally stored data in the desktop app remains on your device until removed by you, the app, or the operating system.

Security

We use reasonable technical and organizational safeguards designed to protect data, including encryption in transit, access controls, and encryption or hashing for certain sensitive credentials and secrets. No system is perfectly secure, and we cannot guarantee absolute security.

International transfers

We and our service providers may process information in the United States and other countries where we or our providers operate. Those countries may have data-protection laws that differ from the laws in your jurisdiction.

Your choices and rights

Depending on where you live, you may have the right to access, correct, delete, or request a copy of certain personal data, or to object to or restrict some processing. You may also be able to disconnect integrations, revoke API keys, delete sessions, or delete your account directly through the product.

If you are in the EEA, UK, or another jurisdiction with similar rights, you may request deletion of your account and associated personal data by emailing support@prismos.dev. We will handle those requests in accordance with applicable law, including GDPR where it applies. In some cases, we may retain limited information where required for legal obligations, security, fraud prevention, dispute resolution, or the establishment, exercise, or defense of legal claims.

To make a privacy request, contact us at support@prismos.dev. We may need to verify your identity before acting on a request.

GDPR requests

Where GDPR applies, we facilitate data subject rights requests, including requests for access, correction, deletion, restriction, objection, and portability. Requests should be sent in writing to support@prismos.dev.

We document GDPR-related requests and aim to respond within the time required by applicable law. If we cannot fully comply with a deletion request, we will explain the basis for the refusal or limitation where required.

California and similar U.S. privacy disclosures

We do not sell personal information and we do not share personal information for cross-context behavioral advertising. We collect and use personal information only for the business and commercial purposes described in this policy.

Children's privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will take appropriate steps to delete it.

Changes to this policy

We may update this Privacy Policy from time to time as the Service evolves or legal requirements change. If we make material changes, we will provide notice through the Service, by email, or by another reasonable method. The effective date at the top of this page shows when this version took effect.

Contact

Questions about this Privacy Policy or our data practices can be sent to legal@prismos.dev. Requests for account deletion or other privacy-rights requests should be sent to support@prismos.dev.