> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/organization-settings/ai-privacy-and-data-retention.md). # AI Privacy & Data Retention This page explains what data Luciq's AI capabilities use, how long it is retained, and the security standards behind it. For general, per-product data retention, see [License Entitlements and Restrictions](/organization-settings/billing/license-entitlements-and-restrictions.md). For the full list of third parties, see [Sub-processors](/organization-settings/others/sub-processors.md). For PII controls and data deletion, see [GDPR](/organization-settings/gdpr.md). {% hint style="info" %} **The short version** * AI capabilities are **opt-in and off by default**. * We only process the **non-PII technical data you choose to send**. * AI-derived data is retained for the **same period as the data it is based on, nothing more**. * Your data is **never used to train any AI model**. {% endhint %} ## What data do AI capabilities use? Only the non-PII technical and diagnostic data you choose to send for a given function, for example a crash stack trace, masked logs, or a bug description. AI capabilities are opt-in and off by default, so if you do not enable them, none of your data is processed by any AI service. Luciq does not need or capture your end users' personal or telecommunications data to operate; we capture technical data and product-engagement signals (such as screen visits or taps), under your control. ## How long is AI data retained? ### In Luciq Any AI output shown in your dashboard (a suggested fix, a summary, an issue grouping) is stored alongside the data it is derived from and follows the **same retention period as that data type**, as defined by your plan in [License Entitlements and Restrictions](/organization-settings/billing/license-entitlements-and-restrictions.md). Enabling AI does not extend retention: an insight derived from a crash follows your Crash Reporting retention, an output derived from a bug follows your Bug Reporting retention, and so on. It is not deleted until that window elapses or you request deletion. ### At our AI providers To produce a result, the relevant non-PII data is sent to an AI model provider, processed, and the result is returned. At this layer the data is **automatically and permanently deleted within no more than 30 days** (retained only transiently for the providers' abuse and safety monitoring) and is **never used to train or improve any model**. The AI model providers we use are themselves SOC 2 Type II certified. See [Sub-processors](/organization-settings/others/sub-processors.md). ### Isolated compute (code-fix generation) Capabilities that generate a code fix run inside a dedicated, isolated compute sandbox that is created on demand and **permanently destroyed the moment the task completes**. Your code and the context used are never written to persistent storage and are never co-located with another customer's workload. There is **no retention at this layer**. ## Is the retention period configurable or fixed? * **In Luciq:** retention is set by your plan and agreement, and Enterprise plans are configured to match your requirements (through your contract and account team). Data retention can also be extended on request. * **At our AI providers:** the processing window is fixed and short by the providers' published terms. ## Do you use our data to train AI models? No. Our AI model providers do not use data submitted through their APIs to train or improve their models, and Luciq does not opt in to any data-sharing or training programs. ## How do I delete data or control PII? You control what personal data is captured through masking and the Luciq APIs, and you can remove a specific end user's data on demand with the Delete User API. See [GDPR](/organization-settings/gdpr.md) for details. ## The security standards behind it Luciq is built for enterprise security and audited independently. These certifications and controls apply across the platform, including the AI capabilities. | Standard | Status | | ------------- | ---------------------------------------------------- | | SOC 2 Type II | Certified | | ISO 27001 | Certified | | GDPR | Compliant; [DPA](https://www.luciq.ai/dpa) available | | HIPAA | Compliant; BAA available | | Encryption | At rest and in transit | {% hint style="info" %} For a security review, a custom questionnaire, or copies of our reports, contact your Luciq account team or . {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.luciq.ai/organization-settings/ai-privacy-and-data-retention.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.