Descant is operated by Autonomy. This policy explains how we handle information when you visit our website, contact us, request access or use Descant.
Information we collect
Account and billing information. When you create or use an account, we process your account and profile information, sign-in and linked-account details, authentication and session records, organization membership and settings. We also process usage records, charges, payment references and limited payment-method details to operate the service, secure accounts and provide billing records.
Waiting list. If you requested an invite before open signup, we collected your email address to manage the waiting list and contact you about access. We store it in Descant and with our email delivery provider, Resend. We also sent an internal notification so we could handle your request.
Messages you send us. When you use the contact form, we collect your name, your work email, your company if you give it, the subject you pick, and your message. We use these to answer you. The contact form does not save your message in a Descant application database. Your message is processed and retained in the email systems used to deliver and answer it. Privacy requests go to our privacy mailbox. You can request deletion through our privacy contact form or by emailing [email protected].
Demo bookings. If you book a demo, the Google Calendar appointment page we embed collects your name, email address and the time you choose, so we can meet you.
Information collected automatically. Like most websites, our hosting and content-delivery providers record standard technical data such as IP address, browser type, and request timestamps. We use this only to operate and secure the site. We use Cloudflare Turnstile to protect our forms from automated submissions. Verification includes the challenge response and, when available, the connecting IP address. Our website also loads Cloudflare Web Analytics for website-usage and performance measurement. This site does not set advertising or cross-site tracking cookies. See our Cookie Policy for the browser storage we use.
We also compare homepage headlines using aggregate counts of headline views and Get started, case-study or benchmark clicks. These test records contain the experiment, version and action, with no visitor identifier or form contents, and are retained for up to three months. We use the totals to improve the website.
How we use your information
- Create and operate your account and provide the Descant service you request.
- Process payments and provide usage and billing records.
- Communicate with you about your account, your requests and Descant.
- Operate, maintain, and secure this website and the service.
- Comply with legal obligations.
We rely on your consent and our legitimate interest in running and securing Descant as the bases for this processing. You can withdraw consent at any time by contacting us.
Customer code and the Descant service
When you connect a repository to the Descant service, we process the content needed to do the work you ask for: repository contents such as code and configuration, issue and pull-request text, and the settings you choose for the repository. We use this content to plan, implement, verify, review and deliver the work you authorize, to keep the working records that support it, and for optional features you enable as described below — never for advertising or profiling, and never to train models.
Session insights. If session analysis is enabled, Descant uses AI to analyze your organization’s session data and produce insights about engineering output and spend. Your organization owner can turn this off in Data & privacy settings. Opting out prevents new analysis and clears stored insight artifacts through the analysis cleanup process. It does not delete the underlying run records.
AI model providers
Descant uses Anthropic, OpenAI and Google (Gemini API) to perform autonomous software engineering work. Model inference for that work can also run on Amazon Web Services. We send these providers the repository context and task instructions needed for that work, which can include code, diffs, issue and pull-request text, and model conversation context.
AI providers may retain API inputs and outputs under their applicable service terms, including for abuse prevention and legal obligations. Retention depends on the provider, model and feature used. End-to-end zero data retention is not currently available for Descant.
API inputs and outputs are not used to train the providers’ models. Each provider is bound by a data-processing agreement. Our subprocessor list describes each provider’s role.
Data retention
We keep waiting-list information for as long as needed to manage access to Descant, and a reasonable period afterward, then delete it. You can ask us to delete it sooner.
For the Descant service: run history, model conversation records and event logs become eligible for routine deletion after 365 days. Working-context checkpoints, session insights and in-app notifications become eligible after 90 days. Cleanup is subject to the run being safely terminal and to the scheduled deletion process. Usage and billing records are retained for as long as financial and legal obligations require.
Closing an organization stops its work and starts its data-handling process. Deletion or anonymization is completed through our erasure process. We retain records required for financial, legal and erasure-audit obligations; a shared user account may remain while it is used by another organization. Automated database backups are kept for seven days; a final snapshot taken if a database cluster is retired has no automatic expiry. Learnings the service commits to your own repository live in your repository and remain under your control.
The same is true of everything the service publishes to your repository: its commits, pull requests, issues, and comments, and its pull-request reviews. Descant adds no personal identifiers of its own to them, but text written in your issues is carried into them as written: an issue's title can become a pull request's title, and its description can be quoted in the pull request. An erasure request does not remove what was published; it is yours to manage in your repository. Someone with write access to it can edit a pull request's or an issue's title and description and delete a comment; ask a repository administrator to delete an issue; and rewriting the repository's history removes a commit from it, though cached or forked copies may need your git host to purge them. Ask your git host's support for anything you cannot edit or delete there, such as a submitted review.
Your rights
Depending on where you live, you may have the right to access, correct, delete, or object to our use of your personal information, and to withdraw consent. To exercise any of these, email us at [email protected]. We will respond within the timeframe required by applicable law.
International transfers
We and our service providers may process your information in countries other than your own, including the United States. Where required, we use appropriate safeguards for these transfers.
Children
This site is intended for professional use and is not directed to children. We do not knowingly collect personal information from children.
Changes to this policy
We may update this policy as the product evolves. When we do, we will revise the “Last updated” date above.
Contact us
Questions about this policy or your information? Email [email protected]. Descant is a product of Autonomy — meetautonomy.com.