> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/data-residency-information.md). # Data Residency Information An overview of Solink regional data differences (North America and EU). Solink supports data residency by region, allowing your to choose where your data is stored based on geographic location and compliance needs. This article explains how data residency works in Solink, what choices are available, and a few important limitations to be aware of before selecting a region. *** ## Choosing a Data Residency Region When setting up Solink, you can select a **data residency region**. This determines where video footage, metadata, and other user data are stored and processed. Regions are typically aligned to geographic areas (for example, North America or Europe) to help you meet local regulatory, privacy, or operational requirements. If you require your organization to have data residency in multiple regions, each region must be set up separately. *** ## Important Things to Know Before You Choose Before selecting a data residency region, please review the following carefully. ### 1. Locations Cannot Move Between Regions Once a **location** is created in a specific data residency region, it **cannot be moved to another region** later. If you need locations in multiple regions, they must be created separately in each region from the start. ### 2. Pricing May Vary by Region Solink pricing can differ depending on the selected data residency region. Pricing differences may be influenced by factors such as infrastructure costs, regulatory requirements, or local market conditions. Your Solink sales representative can confirm pricing for your chosen region(s). ### 3. Separate Logins Are Required for Each Region Each data residency region operates as a **separate environment**. This means: * A single login is not permitted across multiple regions * Users must log in separately for each region * User accounts, permissions, and settings are managed independently per region *** ## Need Help Choosing a Region? If you’re unsure which data residency region is right for your organization—or if you operate across multiple regions—contact your Solink sales representative before onboarding. They can help you plan your setup to avoid future limitations. --- # 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://help.solink.com/docs/install-connect-and-integrate/data-residency-information.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.