# Privacy Policy

This Privacy Policy explains how we collect, use, and protect your personal information.\
Like all [GitBook](/api-reference.md) websites, Burla.dev is subject to the [GitBook Privacy-Policy](https://policies.gitbook.com/privacy-and-security/statement) in addition to the following privacy-policy stated below.

#### **Additional information we collect:**

* **Name**: Collected on login through the Google OAuth consent screen.
* **Email Address**: Collected on login through the Google OAuth consent screen.

#### **How We Use Your Information**

* To manage your account and provide identity access management services.
* To send (very occasional, unsubscribable) updates related to our services.

#### **Data Storage and Security**

* Your information is encrypted at rest, in a private database hosted on Google Cloud.
  * This is the only place this information is stored.
* Our database is securely configured and not exposed to the public.
* We take appropriate measures to ensure the confidentiality and protection of your data.

#### **Sharing of Information**

* We do not sell, share, or disclose your information to any third parties, except as required by law.

#### **Your Rights**

* You have the right to contact us anytime to have any and all personal information (Name, Email address) permanently deleted from our systems.

#### **Contact Us**

If you have any questions or concerns about this Privacy Policy, please contact **<jake@burla.dev>**

**Last Updated:** 5/25/25


---

# Agent Instructions: 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:

```
GET https://docs.burla.dev/website-privacy-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.