Privacy Policy

1. Controller and contact

Shape is the controller of personal data processed in connection with the Service, except where we process data solely on behalf of an organization under a separate agreement. Privacy questions and data-subject requests may be sent through our contact page.

2. Data we collect

2.1 Account data

Authentication is provided by Clerk. Clerk stores your email, password credentials, session cookies, and sends verification and password-reset messages. Shape stores a linked user record in Postgres (Neon) with your Shape user id, email, optional display name, clerkId, billing fields, credit balances, and consent flags (telemetryOptIn, marketingEmailOptIn). We do not store your password. GitHub or GitLab sign-in is completed through Clerk OAuth; we receive the email and profile identifiers Clerk provides.

2.2 Billing data

For paid plans we process subscription tier, credit balances, invoices, and limited payment metadata through Stripe. We do not store full payment card numbers on Shape servers. Stripe acts as an independent payment processor under its own privacy policy.

2.3 AI and usage data

When you use Shape Cloud AI, we process prompts, selected context you choose to include, model selections, conversation history stored for your account, token counts, and related metering needed for delivery, billing, abuse prevention, and support. Aggregate usage metrics power your dashboard.

2.4 Device and security signals

To protect accounts we may process a stable device identifier from the desktop app, IP address, user agent, approximate location derived from IP, and recent login or step-up verification events. These signals are used for fraud prevention and security, not advertising.

2.5 Cookies and website analytics

Necessary cookies: Clerk session cookies required to sign in. Optional analytics: if you accept analytics in the cookie banner (necessary only, or accept analytics), the website records first-party product events in our Postgres analytics tables (page path, event name, not chat contents) and enables Sentry performance traces. Analytics stay off until you accept. We do not set advertising cookies. Product emails are not a cookie; they use the checkbox on sign-up and the dashboard marketing toggle.

2.6 Diagnostics (Sentry) and desktop telemetry

Desktop, website, and API errors are sent to one Sentry project with tags source=desktop|website|api, a shared release/commit, authenticated Shape user id (not passwords), request/trace ids, OS/runtime/browser, feature or action, and when an AI call fails: provider, model, operation, and status. We upload source maps so Sentry can show the shipped code. Automatic capture does not include repository contents, secrets, tokens, or full conversations. Optional desktop product telemetry (app launches, feature usage) is off by default and follows Settings → Data Control; it never includes chat text or source files. Error reporting can run without optional telemetry so crashes remain diagnosable.

2.7 Report a problem and linked chats

"Report a problem" uses our own form and submits through Sentry User Feedback. It includes your description, category, current page/feature, app version/release, platform, nearby diagnostic context, and the nearest Sentry event/trace id if one exists. Reports do not call an AI model or consume credits. On desktop only, you may optionally pick a chat from the current project; that chat is redacted (secrets/emails/home paths stripped, length-capped) and attached only if you select it. Other chats, files, and tokens are never attached. Sentry AI payload capture is not enabled for this product.

3. How we use data

We use personal data to:

• Provide, operate, secure, and improve the Service
• Authenticate users, prevent abuse, and enforce our Terms and EULA
• Process payments, credits, and invoices
• Deliver AI features through our proxy and model providers
• Communicate service, security, and (where permitted) product messages
• Comply with law and respond to lawful requests

Legal bases may include contract performance, legitimate interests (security, product improvement with safeguards), consent (where required for cookies or optional telemetry), and legal obligation.

4. AI providers and training

Shape Cloud AI routes requests through Shape's servers to model providers via OpenRouter and similar infrastructure. Prompts and context you submit are processed by those providers to generate outputs. Provider policies apply to data they process. We do not sell your content. Unless you explicitly opt in to a training or improvement program described in the Service, we do not use your Content to train foundation models for general third-party use.

5. Sharing and sub-processors

We share personal data with vendors that help us run the Service, under contractual obligations appropriate to the processing. Current categories include:

• Hosting and database (Neon)
• Authentication, session cookies, and verification email (Clerk)
• Payments (Stripe)
• Crash diagnostics, traces, and user problem reports (Sentry)
• Marketing email preference if you opt in. The choice is stored. Marketing mail is not sent.
• Contact-form delivery (Resend), when you submit the contact form
• AI inference routing and model providers (OpenRouter and underlying providers)
• Marketing banners, blog, and in-app feature cards (Sanity), when configured
• Public documentation on this website. Docs pages do not receive your account, chats, or source.

We may disclose data if required by law, to protect rights and safety, or in connection with a merger, acquisition, or asset sale, subject to appropriate safeguards.

6. Retention

We retain account and billing records while your account is active and as needed for tax and fraud prevention. Clerk retains auth logs per its retention settings. Sentry events follow our Sentry project retention. Conversation history stays on your device unless you use Shape Cloud AI (prompts are processed to generate outputs) or you explicitly attach a chat to a problem report. When you delete your account we delete or anonymize Shape Postgres personal data, typically within 30 days, except where law requires retention. You must also delete or request deletion of your Clerk account data through account deletion in the dashboard.

7. Security

We implement administrative, technical, and organizational measures designed to protect personal data, including encryption in transit, access controls, and build attestation for official Shape Cloud AI clients. No method of transmission or storage is fully secure, and we cannot guarantee absolute security.

8. International transfers

We may process data in the United States and other countries where we or our processors operate. Where required, we use appropriate transfer mechanisms such as standard contractual clauses.

9. Your rights

Depending on your location, you may have rights to access, correct, delete, restrict, or export personal data, to object to certain processing, and to withdraw consent where processing is consent-based. You may also lodge a complaint with a supervisory authority. To exercise rights, use dashboard account controls where available or contact us through the contact page. We may need to verify your identity before fulfilling a request.

California residents may have additional rights under the CCPA/CPRA, including the right to know, delete, and correct personal information, and to opt out of "sale" or "sharing" as defined by those laws. We do not sell personal information for money. If our analytics practices are considered "sharing" for cross-context behavioral advertising in your jurisdiction, you can reject analytics cookies and contact us to exercise opt-out rights.

10. Children

The Service is not directed to children under 13 (or the higher age required in your jurisdiction). We do not knowingly collect personal data from children. If you believe a child has provided data, contact us and we will take appropriate steps to delete it.

11. Changes

We may update this Policy from time to time. We will revise the date above and, for material changes, provide additional notice through the Service or by email where appropriate. Continued use after changes become effective constitutes acceptance of the updated Policy.

12. Related documents

Please also review our Terms of Service and End User License Agreement.