> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/accounts-and-security/overleaf-data-processors.md). # Overleaf data processors Overleaf may engage the entities listed below to assist it in connection with its products and services, including to provide hosting and infrastructure services and customer and technical support and which may therefore involve the processing of personal data. Where you are an institution or organization, and we are processing that personal data as your “processor” (as defined in the GDPR), such entities will be considered “subprocessors”. | Third Party Service Provider Name | Location | Function | | --------------------------------- | -------- | ---------------------- | | Algolia | US | Data processing | | Amazon Web Services | US | Hosting | | Anthropic | US | Data processing | | BugSnag | US | Application operations | | Customer.io | US | User communication | | FrontApp | US | Support | | Google Cloud Platform | US | Hosting | | GrowthBook | US | Application operations | | Heroku | US | Hosting | | Kount Inc | US | Payment processing | | MailChimp | US | Service messages | | MongoDB Atlas | US | Hosting | | OpenAI | US | Data processing | | PayPal | US | Payment processing | | Recurly | US | Payment processing | | Redis | US | Application operations | | SendGrid | US | Service emails | | Sentry | US | Application operations | | SheerID | US | User verification | | Stripe | US | Payment processing | As part of a global organization, various Overleaf group companies may also be involved in connection with the development and delivery of its products and services, including as customer contracting entities and service providers, namely: Digital Science UK Ltd (UK), Digital Science & Research Solutions Ltd (UK), Digital Science & Research SRL (Romania), DS Digital Science GmbH (Germany), Digital Science & Research Solutions Inc (US), ThinqLab Ltd (UK) and Writefull BV (Netherlands). Please refer to [our Privacy Policy](https://www.overleaf.com/legal#Privacy) or the data processing terms\* we have agreed with you, as applicable, for further information. Not all service providers will be used for every user. \*Note to organizations: if we do not already have a data processing agreement in place with you, one can be executed by following [this link](https://eu.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=a9bf6ead-e5f9-4809-be36-c1728a19c07e\&env=eu\&acct=db2a35aa-12e2-4017-b74a-bb8e4a1d199e\&v=2). To receive notifications when this page is updated, please [subscribe here](http://eepurl.com/hAG6ir). Date: May 2026 --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.overleaf.com/accounts-and-security/overleaf-data-processors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.