Privacy Policy

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.

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.

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.

We use Anthropic as our default AI provider. 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.

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, and request logging.
• Anthropic — large-language-model processing for standups, summaries, and chat.
• OpenAI — optional, only when a workspace supplies its own OpenAI key under the BYOK option.
• 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 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 receives only a Stripe customer reference, subscription metadata, and the billing email you provide.

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

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.

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.

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.

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.

For privacy questions, requests, or concerns, contact 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.