Cloud Deployment

Managed tracio.ai cloud: EU/US region selection, AES-256 encryption, Redis caching, and nginx proxy setup

Overview

tracio.ai is a fully managed cloud platform. All visitor data is processed in our secure cloud infrastructure with AES-256 encryption at rest and TLS 1.3 in transit. We never share your data with third parties. Choose between EU and US data residency to meet your compliance requirements.

Getting started takes minutes: create an account, get your API key, install the client SDK, and start identifying visitors. Our cloud handles scaling, redundancy, security patches, and infrastructure management.

How It Works

Your application integrates with tracio.ai through two touchpoints: a client-side JavaScript SDK and a server-side API.

Browser (JS SDK)  ──▶  tracio.ai Cloud  ──▶  Your Server (webhooks)
                  ◀──  (identification)
1. SDK collects signals → sends encrypted to tracio.ai cloud
2. Cloud processes and returns: visitorId, confidence, signals
3. Optionally, tracio.ai sends webhook events to your server

Data Flow

1. The browser SDK collects signals and encrypts them with AES-256-GCM.
2. The encrypted payload is sent to the tracio.ai cloud API.
3. The server processes signals and returns the identification result.
4. Your server can verify results via the Server API using the requestId.
5. Optionally, tracio.ai sends webhook events to your configured endpoint.

Getting Started

Create an account at dashboard.tracio.ai, choose your data region, and get your API keys:

1. Sign up at dashboard.tracio.ai
2. Choose data region: EU (Frankfurt) or US (Virginia)
3. Copy your API Key (public, for the JS SDK) and API Secret (private, for server-side calls)
4. Install the SDK and start identifying visitors

Webhooks

Configure webhooks in the dashboard to receive real-time notifications when visitors are identified. Webhooks are sent as POST requests with HMAC-signed payloads.

Configure your webhook endpoint in Dashboard → Settings → Webhooks.

Data Regions

Rate Limits

Security

• All data encrypted at rest (AES-256) and in transit (TLS 1.3)
• Use your API Secret only server-side, never expose it to the browser
• Webhook payloads are HMAC-signed for verification
• Rotate API keys periodically via the dashboard