# Multi-region support for Canada
Redox supports multi-region data exchange with Canadian organizations. With this type of integration, we process healthcare data in the U.S. but store it in Canada. This allows Canadian organizations to exchange healthcare data via Redox without requiring patient consent. But keep in mind that all configuration settings are stored in the U.S.
> **Canadian PHI**
>
> We store data for customer-managed operations (e.g., translation sets, filters, config modifiers) in the U.S. with the same safeguards as PHI data. Given that Redox configuration data is housed in the U.S., though, it might not be appropriate to include Canadian patients’ PHI in any of these settings. Please consult with your legal counsel before inputting any PHI originating in Canada.
First, [find out what this means for allow-listing](/security/allow-listing-for-redox). Then, check out the details below.
## Domain names
Whenever you make a web request to Redox from Canada, you must use URLs with the `.ca` region specified. For example:
- `https.ca.redoxengine.com`
- `api.ca.redoxengine.com`
- `blob.ca.redoxengine.com`
- `webhooks.ca.redoxengine.com`
- `sftp.ca.redoxengine.com`
## Redox dashboard
The Redox dashboard has a few differences for multi-region Redox organizations, specifically on the Developer and Logs pages.
> **For users who belong to multiple Redox organizations**
>
> If you belong to more than one Redox organization, you’ll only see the extra Region fields in multi-region organizations.
#### Developer page
On the Sources and the Destinations tabs, there’s an extra field to designate the region of any source or destination.
*Source region field*
*Destination region field*
This also means that there’s an extra Region field whenever you’re creating or editing existing sources and destinations.
*Region field in the source wizard*
*Region field in the destination wizard*
> **For multi-region organizations**
>
> The source you use designates which region an API request comes from. As best practice for security, though, we recommend using a unique OAuth API key for sources in each region.
>
> You can designate the region the API key name (e.g., `Production API key — U.S.`).
#### Logs page
When you’re searching for logs, there’s an extra Region filter for you to use. This narrows down the log results to logs only sent or received in the designated region.
*Region filter for logs*