> ## Documentation Index
> Fetch the complete documentation index at: https://docs.twenty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Legal FAQ

> Frequently asked legal questions.

## Data residency and international transfers

<AccordionGroup>
  <Accordion title="In which country and region would our workspace data, attachments, logs, and backups be stored?">
    Twenty Cloud runs on AWS servers located in Frankfurt, Germany.
  </Accordion>

  <Accordion title="Can the hosting region be contractually fixed for our workspace?">
    Hosting region selection will be available starting in 2027, initially for new workspaces. Users will be able to request a region change for an existing workspace at a later date. Alternatively, you can reach out to [our Partners](https://twenty.com/partners/list?categories=HOSTING) to help you set up your instance.
  </Accordion>

  <Accordion title="Which sub-processors may process or access our CRM data, and in which countries are they located?">
    A list of all sub-processors is available in [our Trust Center](https://trust.twenty.com/?tab=subprocessors).
  </Accordion>

  <Accordion title="What safeguards apply to international data transfers?">
    EU Standard Contractual Clauses, together with the UK Addendum and Swiss amendments, apply to international transfers of data outside the EU, including transfers to all sub-processors.
  </Accordion>
</AccordionGroup>

## Data Processing Agreement and legal roles

<AccordionGroup>
  <Accordion title="Where can we find the current Data Processing Agreement?">
    You can generate your signed DPA at https\://{your-domain}/settings/legal/dpa (e.g. [https://getting-started.twenty.com/settings/legal/dpa](https://getting-started.twenty.com/settings/legal/dpa)).
  </Accordion>

  <Accordion title="Does Twenty act as the data processor for merchant and contact information stored in the CRM, while our company remains the data controller?">
    As per our [Privacy Policy](https://twenty.com/privacy-policy), Twenty acts as the data processor for merchant and contact information stored in the CRM, while your company remains the data controller.
  </Accordion>

  <Accordion title="Is CRM content ever used to train Twenty or third-party AI models?">
    CRM content can be used to train AI models depending on sub-processors' Terms and Conditions. Twenty does not have its own AI model — all AI models available on Twenty Cloud are provided by our sub-processors.
  </Accordion>

  <Accordion title="If optional AI processing exists, can it be fully disabled for our workspace?">
    AI can be fully disabled by turning off all AI models in Settings → AI → Models. Additionally, no data is sent to AI unless you actively interact with the AI chat or an AI node in a workflow.
  </Accordion>
</AccordionGroup>

## Security and access controls

<AccordionGroup>
  <Accordion title="Is encryption used in transit and at rest, what are your key-management practices, and how is tenant data isolated?">
    All data is encrypted in transit and at rest. Tenant data is isolated through a schema-per-tenant setup, and encryption keys are periodically rotated.
  </Accordion>

  <Accordion title="Which Twenty personnel or sub-processors may access customer workspaces, for what purposes, and how is access approved and logged?">
    Twenty's engineering and support teams may access customer workspaces to investigate and resolve issues. Workspace owners control this: support access can be disabled at any time in Settings → General → Security, and it stays off until you turn it back on.
  </Accordion>

  <Accordion title="What is your incident-notification process and target notification timeframe following a confirmed security incident affecting our data?">
    In the event of a confirmed personal data breach affecting your data, we will notify you without undue delay and in any event within 48 hours of becoming aware of it. Our notification will include, to the extent known at the time: the nature of the breach, the categories and approximate volume of data and individuals affected, likely consequences, and the remediation and mitigation measures taken or planned. We will provide updates as the investigation progresses.
  </Accordion>
</AccordionGroup>

## Data retention and deletion

<AccordionGroup>
  <Accordion title="When an individual CRM record is deleted, when is it removed from active systems?">
    When a record is deleted, it is first soft-deleted and can still be restored. It is permanently deleted and removed from active systems once the retention period elapses or a user manually destroys it.
  </Accordion>

  <Accordion title="How long are soft-deleted records kept in the system?">
    By default, soft-deleted records are kept for 14 days, after which they are permanently removed from the system. The retention period for soft-deleted records can be changed in Settings → General → Security.
  </Accordion>

  <Accordion title="How long may that record remain in backups or technical logs?">
    A removed record remains in backups for 30 days, after which it is permanently deleted.
  </Accordion>

  <Accordion title="When a workspace is closed or full deletion is requested, what exact timeline applies to production data, attachments, logs, and backups?">
    When a workspace is deleted, its data is removed from live systems within approximately 90 days of service termination, and usually much sooner. Back-up and archival copies are then overwritten or purged within a further 90 days, after which all data is permanently deleted. Throughout both periods the data is isolated from any operational use. On request, we can provide written certification once the purge is complete. See clause 4.9 of your Data Processing Agreement for the full terms.
  </Accordion>

  <Accordion title="During any backup-retention period, is deleted data isolated from operational access and use?">
    Yes, during any backup-retention period, deleted data is isolated from operational use.
  </Accordion>

  <Accordion title="Are any categories of data retained longer for legal, billing, fraud-prevention, security, or audit purposes? If so, which categories and for how long?">
    For more info about data retention, you can request our Data Management and Retention Policy available in [our Trust Center](https://trust.twenty.com/?tab=documents).
  </Accordion>

  <Accordion title="Can Twenty provide written confirmation when a full deletion request has been completed?">
    We acknowledge erasure requests and provide written confirmation once deletion is complete.
  </Accordion>
</AccordionGroup>

## Backups and resilience

<AccordionGroup>
  <Accordion title="What are the backup frequency and retention period?">
    Backups are created continuously with snapshots taken daily, and the retention period is 30 days.
  </Accordion>

  <Accordion title="What are the recovery-point objective and recovery-time objective for Twenty Cloud?">
    RTO and RPO are both 6 hours (as per our DPA).
  </Accordion>

  <Accordion title="What is the process for requesting or performing a restoration?">
    To request a restoration, please reach out to our team via support chat or mail to [contact@twenty.com](mailto:contact@twenty.com).
  </Accordion>

  <Accordion title="Are backups encrypted and stored in the same region as the primary workspace data?">
    All backups are encrypted and stored in geographically separate locations within the same jurisdiction (e.g. within EU for EU data).
  </Accordion>
</AccordionGroup>

## Compliance

<AccordionGroup>
  <Accordion title="Is Twenty GDPR compliant?">
    Yes, Twenty is [GDPR compliant](https://trust.twenty.com/?tab=securityControls\&frameworks=gdpr_v1).
  </Accordion>

  <Accordion title="Is Twenty SOC 2 compliant?">
    Yes, Twenty is [SOC 2 compliant](https://trust.twenty.com/?tab=securityControls\&frameworks=soc2_v1).
  </Accordion>

  <Accordion title="Is Twenty HIPAA compliant?">
    No, Twenty is in the process of becoming HIPAA compliant.
  </Accordion>
</AccordionGroup>

## Licensing

<AccordionGroup>
  <Accordion title="If I change the code to add features only for internal use by my team, do I have to publish those changes?">
    No. Running a modified version for your own team is not distribution, so no publication obligation arises. The AGPL's network clause applies when people outside your organization interact with your modified instance over the network.
  </Accordion>

  <Accordion title="If I create a separate front end and use Twenty as a backend as-is, do I have to publish those changes?">
    No. Your front end is your own, separate work, and talking to Twenty through its APIs does not change that. Since Twenty itself is unmodified, there is nothing to publish.
  </Accordion>

  <Accordion title="If I change the code to add features to re-sell it, do I have to publish those changes?">
    Yes, since you're modifying code to distribute it to others, you're required to publish those changes. If you don't want to publish your changes, you can obtain Organization license.
  </Accordion>
</AccordionGroup>

If you have more questions, please check our [Terms and Conditions](https://twenty.com/terms), [Privacy Policy](https://twenty.com/privacy-policy) and [Trust Center](https://trust.twenty.com/). If your questions are still unanswered, send them to [contact@twenty.com](mailto:contact@twenty.com) or via support chat.