# Technical Architecture

Signet utilizes a unique, privacy-preserving architecture that separates session data from personal identity.

#### The Ephemeral Session

Traditional analytics rely on cookies that persist on a user's device for days or months. Signet uses a temporal session model. When a user visits your site, we generate a session hash based on the request data and a daily rotating salt.

This hash allows us to link a sequence of page views into a single logical session, enabling you to see the user's journey through your funnel. However, because the salt rotates every 24 hours, this hash is ephemeral. A visitor returning the next day is seen as a new session. This makes it mathematically impossible to create a long-term profile of a specific individual, ensuring privacy is preserved at the cryptographic level.

#### The Anonymization Pipeline

Our data ingestion pipeline follows a strict verify-process-discard protocol:

1. **Ingest:** The request hits our edge network.
2. **Verify:** We validate the origin and project ID.
3. **Anonymize:** We derive the geographic location (Country/Region) from the IP address in memory.
4. **Discard:** The raw IP address is immediately discarded. It is never written to a disk or database.
5. **Store:** Only the aggregated, anonymized behavioral data is committed to our encrypted storage.

#### Edge-First Delivery

Speed is a feature. The Signet script is served via a global Content Delivery Network, ensuring low-latency loading regardless of where your users are located. The script loads asynchronously, guaranteeing it never blocks your main thread or delays the First Contentful Paint.


---

# 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.signtoken.vip/1.-overview/technical-architecture.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.