Regions and data retention
Learn more about where and how we store the identification data of your visitors.
Regions
When creating your Fingerprint workspace, you can choose the region in which your data will be stored. Pick the one that best suits your infrastructure, latency, and regulatory compliance requirements. Your data never leaves the chosen region. Once chosen, your workspace region cannot be changed.
Fingerprint supports the following regions. The Global (US) region is used by default.
Region | Server location | Code identifier | Base API URL |
---|---|---|---|
Global (US) | Northern Virginia, USA | us (default, can be omitted) | https://api.fpjs.io |
EU | Frankfurt, Germany | eu | https://eu.api.fpjs.io |
Asia | Mumbai, India | ap | https://ap.api.fpjs.io |
Specifying region for the JavaScript agent
If you choose a non-default region (EU or Asia), you need to specify it when initializing the JavaScript agent. See the JavaScript agent Reference > region
for more details.
<script>
const fpPromise = import('https://fpjscdn.net/v3/<<browserToken>>')
.then(FingerprintJS => FingerprintJS.load({
// Specify `region` as `eu` or `ap` if you don't use the default region
+ region: 'eu'
}));
</script>
import FingerprintJS from '@fingerprintjs/fingerprintjs-pro'
const fpPromise = FingerprintJS.load({
apiKey: '<<browserToken>>',
// Specify `region` as `eu` or `ap` if you don't use the default region
+ region: 'eu'
})
Specifying region for the Server API
If you choose a non-default region (EU or Asia), you need to use a corresponding base API URL (eu.api.fpjs.io
or ap.api.fpjs.io
) when interacting with Fingerprint Server API. See the Server API Reference for more details.
curl --request GET \
- --url https://api.fpjs.io/events/YOUR_REQUEST_ID \
+ --url https://eu.api.fpjs.io/events/YOUR_REQUEST_ID \
--header 'Auth-API-Key: YOUR_API_KEY' \
--header 'accept: application/json'
curl --request GET \
- --url https://api.fpjs.io/events/YOUR_REQUEST_ID \
+ --url https://ap.api.fpjs.io/events/YOUR_REQUEST_ID \
--header 'Auth-API-Key: YOUR_API_KEY' \
--header 'accept: application/json'
Data retention
For most plans, visit history is available through the Server API for the past 30 days. For Enterprise plans, the data is kept for 90 days or longer depending on the enterprise contract.
If you need to store data for longer than your plan allows or prefer a custom storage solution, you can use Webhooks. Webhooks allow you to automatically receive each identification response at your custom server endpoint and save them in your database.
Data deletion
As a data processor that complies with several Data Processing Addendums (i.e., GDPR, CCPA, etc) Fingerprint, upon request from a data controller, will delete information belonging to a browser or a device. Please contact support for more information.
Updated about 9 hours ago