> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/introducing-dope.swg/quick-start-guide/create-a-dope.swg-account.md).

# Create a dope.swg Account

## Create a tenant using Google or O365

After accessing [fly.dope.security](https://fly.dope.security/), select Google or O365, depending on which corporate email you use:

![](/files/lzd3JBchWLbel3YJjycA)

You will authenticate using your corporate email/password and two-factor authentication (if enabled). The dope.console is automatically single sign on without any configuration

{% hint style="warning" %}
Personal Gmail or Outlook does not work. You must use a corporate Microsoft or Google account
{% endhint %}

## Choose Data Residency Region

We offer a variety of regions to store your [transaction records](#user-content-fn-1)[^1] and will only upload the records to the region you choose. Data is automatically deleted (time-to-live) with a maximum of 30 days (typically less).

{% hint style="info" %}
Learn more about our policies through our [Data Processing Agreement](https://dope.security/legal/dpa)
{% endhint %}

![](/files/RBslFnqVtdz52LK9q4Dl)

Customers can choose one of the of the following locations:

<img src="/files/IHZHiRMGGHcqo6yuf9ng" alt="" data-size="line"> USA

<img src="/files/JggR1YqaME5l4dVjXwwK" alt="" data-size="line"> Germany

<img src="/files/FrIzNHEyDvpb6rhyJFum" alt="" data-size="line"> Bahrain

<img src="/files/IKv00tDAKJNbnwcJ5QUV" alt="" data-size="line"> Singapore

<img src="/files/vf2EeJUiPYHYqhKKlNO6" alt="" data-size="line"> Australia

<img src="/files/3pGu4OB25w0C4kil8pbh" alt="" data-size="line"> Brazil

No Storage - With no storage enabled, data will be sent to your SIEM to help satisfy data-residency laws (e.g. KVKK in Turkey).

#### What other data do we store?

We collect customer user information (device name, username/email, user groups, IP addresses) for administrators to configure policy and monitor endpoints. This is stored in an Active-Active multi-region global database to support failover, disaster recovery, and performance.

Unlike other SWG products the dope.endpoint enforces policy and inspects all content with an on-device proxy — including SSL decryption. The output is analytics/reporting data records that include the user, URL, timestamp, size, and policy result. Customer web traffic never transits our cloud, it remains in the safezone of your endpoint.

#### Agree to Our [EULA](https://dope.security/legal/eula)

[^1]: Logs of all websites, internet requests, including URL, User, Device, etc.


---

# 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://inflight.dope.security/introducing-dope.swg/quick-start-guide/create-a-dope.swg-account.md?ask=<question>&goal=<endgoal>
```

`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.
