# HTTPS Proxies

VGS HTTPS Proxy sits in front of your backend and filters sensitive data out of incoming requests. By configuring the filtering rules (aka [routes](https://docs.verygoodsecurity.com/vault/inbound-connection#what-does-it-allow-you-to-do)) via the VGS Dashboard, you ensure that sensitive data never hits your systems. Instead of storing the sensitive data, you store VGS-provided [aliases](https://www.verygoodsecurity.com/blog/posts/tokenization-vs-encryption-vs-aliasing-how-to-truly-minimize-compliance/).

When the time comes to use the data — for example to charge a credit card via a payment processor — the data is again passed through the VGS HTTPS Proxy on its way to a payment gateway or other 3rd party, and VGS substitutes the aliased data in transit with the original value.

![http-proxy](https://2096104711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUreALQAfVnRMQEz110rC%2Fuploads%2Fgit-blob-19a7aee2d1309e836fbdd62e70d5ae010ed56999%2Fhttp-proxy.png?alt=media)

## Configuring the HTTPS Proxy

VGS HTTPS Proxy processes big variety of data types and 3rd party processors, check [Operations Examples](https://docs.verygoodsecurity.com/vault/operations#operations-examples) for detailed examples.

To make sure your sensitive data is fully secured use one of [VGS Collect](https://docs.verygoodsecurity.com/vault/developer-tools/vgs-collect) solutions for web and mobile apps.

Essential steps to integrate with VGS HTTPS Proxy are described in our [Getting Started Guide](https://docs.verygoodsecurity.com/vault/developer-tools/vgs-collect/js/index).

## Inbound and Outbound Routes Definition

The difference between the inbound and outbound routes is that Inbound Routes utilize a reverse proxy, and can therefore be accessed by third parties (such as a website or app), and the Outbound Routes utilize an HTTPS forward proxy, which sits between your server and third parties. Both tools can be used in conjunction for accepting and sending requests using a secure data infrastructure.

### Integration Examples

See [Integration Templates](https://docs.verygoodsecurity.com/vault/http-proxy/integration-templates) and [Example Integrations](https://docs.verygoodsecurity.com/vault/example-integrations).


---

# 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.verygoodsecurity.com/vault/http-proxy.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.