Privacy Policy

What we collect

We may collect account details such as your name, email address, company information, and authentication data when you sign up or are invited to use Dassie.

We also collect product usage information, including workspace activity, feature interactions, device and browser information, log data, and diagnostics that help us operate and improve the service.

If you contact us, participate in support conversations, or submit forms, we may collect the contents of those communications and any information you choose to provide.

How we use data

We use collected information to provide the service, authenticate users, maintain accounts, deliver requested features, and support collaboration within customer workspaces.

Information may also be used to monitor performance, troubleshoot issues, secure the platform, prevent abuse, analyze product usage, and guide improvements to the product and user experience.

Where permitted by law, we may use contact information to send important operational notices, service updates, and other communications related to your account or use of Dassie.

AI processing

Dassie sends customer content, including code excerpts, ticket text, commit messages, and Slack threads you choose to connect, to large-language- model providers in order to generate standups, answer questions, and produce the summaries you see in the product.

For Dassie Apps, AI helps with conversations, drafting and building requested changes, responding to your answers, and updating sketches. We send relevant messages, conversation history, requests, answers, notes and app information, including plans and sketch descriptions, to Vercel AI Gateway and the AI providers it selects. These services use models from Anthropic, OpenAI and Z.ai. The model's creator and the provider running it may differ. We also send conversation text directly to OpenAI to generate or update chat titles.

If you choose Eco for a chat, its messages and the context Dassie adds to them are sent directly to GreenPT instead, which runs open models. If GreenPT cannot answer, that message is sent to Vercel AI Gateway and answered as it would be without Eco. Turning Eco off returns that chat to the services above.

The AI service used depends on the task. Some requests go through Vercel AI Gateway, while others go directly to an AI provider, including OpenAI for chat titles. Anthropic does not train its models on data sent through its API. If you supply your own Anthropic or OpenAI key under the BYOK option on paid plans, AI requests are sent directly using your key and are subject to that provider's terms.

We do not use customer content to train models, and we do not share customer content with third parties for advertising or marketing.

Subprocessors

We rely on a small number of trusted infrastructure providers to operate Dassie. Each is bound by a data processing agreement appropriate to its role.

• Supabase, primary database, authentication, realtime updates, and queue infrastructure.

• Vercel, application hosting, serverless compute, request logging, and AI Gateway processing and routing to AI inference providers.

• Anthropic, large-language-model processing for standups, summaries, and chat.

• OpenAI, AI processing, including direct generation and updating of chat titles. OpenAI models are also used through Vercel AI Gateway. OpenAI processing is not limited to workspaces that supply their own key.

• GreenPT, AI processing for chats where you choose Eco, sent directly rather than through AI Gateway. When GreenPT cannot answer, the message goes through AI Gateway instead.

• Resend, sending authentication emails, including the destination email address and the sign-in link or code in the email content.

AI Gateway also supports our use of Z.ai models for drafting changes. The provider that runs a model can differ from the model's creator and is selected through Gateway routing.

• Stripe, payment processing, subscription management, and billing communications.

• PostHog, product analytics and error tracking.

• GitHub, Linear, and Slack, only when you choose to connect them. We read the data you authorize through their APIs and store it only as needed to render Dassie's views.

We may add or change subprocessors as the product evolves. Material changes will be reflected on this page.

Payments

Payments are processed by Stripe. When you subscribe to a paid plan, your card details are submitted directly to Stripe and are not stored on Dassie's servers. Dassie keeps a Stripe customer reference and subscription metadata. If you add business details on the Billing page, Dassie also stores your business's legal name, registration and tax numbers, billing address and billing email, and shares them with Stripe so they appear on your invoices and invoices reach the right inbox. Only the people who manage billing for your team can see or change them.

Stripe's privacy practices are described at stripe.com/privacy.

Data sharing beyond subprocessors

We do not sell personal information. Beyond the subprocessors listed above, information may be disclosed only when required to comply with applicable law, enforce our terms, protect the rights or safety of users and others, or as part of a corporate transaction such as a merger, financing, or sale of assets.

Retention

Account data (your name, email, workspace memberships) is retained for the life of your account and for up to 30 days after account deletion to allow recovery.

Generated content (standups, summaries, chat history) is retained while your workspace is active and is deleted within 30 days of workspace deletion.

Integration data (commits, tickets, messages we read from connected services) is retained only as long as needed to render the views you actively use; superseded data is purged on an ongoing basis.

Logs and diagnostics are retained for up to 90 days for security and debugging.

Billing records are retained for up to seven years to satisfy tax and accounting obligations.

Security

We use administrative, technical, and organizational measures designed to protect information against unauthorized access, disclosure, alteration, or destruction. Customer content is encrypted in transit and at rest. BYOK keys, when supplied, are encrypted at the application layer before storage. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

Your choices

Depending on your location and applicable law, you may have the right to access, correct, delete, or restrict the use of your personal information, or to object to certain processing activities.

You may also choose not to provide certain information, although doing so may limit the functionality of the service. If you would like to exercise privacy rights or make a request about your information, contact us using the details below.

Contact

For privacy questions, requests, or concerns, contact C craig@maatskappy.co.

We may update this Privacy Policy from time to time. When we do, we will revise the last-updated date on this page so the current policy is visible in the product and repository.