Trust
Subprocessors
Infrastructure
Where the platform runs.
Amazon Web Services
Compute for the exam gateway and API, enforcement fleet, and artifact storage. Runs the WireGuard tunnel termination, DNS filtering and nftables enforcement.
- Data category
- Exam session telemetry, DNS decision logs, integrity reports, customer account data
- Region
- us-east-1
Microsoft Azure
Control-plane services (session, admin, auth, billing, partner), managed Redis for live session state, blob storage for session-log archives and database backups, and the database host running Postgres, Temporal and ClickHouse.
- Data category
- Exam session telemetry, integrity reports, customer account data, session log archives
- Region
- eastus
Cloudflare
Edge data plane. Per-exam durable objects, key-value store for join-code routing, and the queue that receives session telemetry, plus TLS termination for the gateway relay.
- Data category
- Exam session telemetry, join codes, organisation identifiers
- Region
- Global edge network; no jurisdiction restriction is currently configured
Vercel
Hosting for aiseptor.com. The proctor dashboard and exam infrastructure do not run here.
- Data category
- Website visitor IP address and coarse geolocation
- Region
- Not pinned
GitHub
Source control, CI, and distribution of the candidate agent installer. Candidates download the agent directly from a public release repository.
- Data category
- Candidate IP address at the moment of installer download
- Region
- United States
Application services
Third parties the product calls during or around an exam session.
Resend
Transactional email: exam invitations to candidates, one-time passcodes, password resets, security alerts, and organisation invitations.
- Data category
- Candidate names and email addresses, proctor email addresses, one-time codes
- Region
- Not pinned; global endpoint
OpenRouter
Generates the plain-language session narrative shown to proctors, and classifies domains and tools during policy drafting. Routes to third-party model providers, including a fallback to OpenAI.
- Data category
- Candidate-derived data, including the candidate name, blocked domain names, detected process names and destination addresses
- Region
- United States; onward model provider is not pinned
Exa.ai
Web search, invoked by the model when resolving unfamiliar tools and domains during policy drafting.
- Data category
- Tool and domain names, exam policy descriptions
- Region
- Not pinned
Google Public DNS
Upstream resolver for domains that pass the exam allow-list. Blocked domains are never forwarded.
- Data category
- DNS queries for allow-listed destinations during an exam session
- Region
- Anycast
Google Identity
Single sign-on for the proctor dashboard, when an organisation chooses Google as its identity provider.
- Data category
- Proctor and administrator email address and Google account identifier
- Region
- United States
Google Fonts
Serves typefaces to the proctor dashboard's API reference pages. The marketing site self-hosts its fonts and does not contact Google.
- Data category
- Proctor browser IP address and user agent
- Region
- Global
Airtable
System of record for inbound sales enquiries from the website forms.
- Data category
- Marketing lead data: name, email, company, role, and message content
- Region
- United States
Supabase
Content database for the Aiseptor blog. No exam or account data.
- Data category
- Published article content only
- Region
- Not pinned
Google Workspace
Corporate email and identity for Aiseptor staff.
- Data category
- Employee data. No candidate or exam data.
- Region
- United States
Where we are not finished: AI processing
First, the part that is not AI. Blocking and flagging are deterministic rule evaluation — an allow-list, a denylist and fixed thresholds. No language model decides whether a candidate is flagged. Some product surfaces carry the name “ThreatSense AI”, which is our brand for the network enforcement module rather than a description of a model, and the on-device “LLM scan” detects language models the candidate is running; it does not run one. This is also why enforcement has no false positives: a path is either closed or it is not.
Where a model genuinely is involved: the proctor-facing session narrative and our domain classification are generated by a third-party language model, routed through OpenRouter. Those requests currently include the candidate's name alongside the blocked-domain and process data.
Three things about that are not where we want them. A data processing agreement with OpenRouter is not yet in place. We do not yet pin which onward model provider handles a request, nor set zero-retention routing. And the candidate name is not necessary to produce the narrative, so it should not be in the request at all.
All three are open engineering work, tracked publicly. We would rather you read this here than discover it in a security review. If AI-generated narratives are incompatible with your requirements today, the feature can be disabled for your organisation on request — enforcement does not depend on it.
Software supply chain
Who signs and attests to the agent a candidate installs, and where its runtime components come from.
Certum (Asseco Data Systems)
Certificate authority and timestamping service for the signed Windows agent. Every signature contacts Certum's timestamp server.
- Data category
- No candidate or customer data. Build artifacts only.
- Region
- European Union
Apple
Developer ID signing and notarisation of the macOS agent. The signed binary is submitted to Apple's notary service before release.
- Data category
- No candidate or customer data. Build artifacts only.
- Region
- United States
Package registries
Docker Hub, the npm registry, NodeSource, PyPI and Ubuntu archives supply the runtime components baked into gateway images and service containers.
- Data category
- No candidate or customer data. Build artifacts only.
- Region
- Global
Website only
These run on aiseptor.com and never touch exam sessions or candidate data. All are consent-gated.
Google Analytics 4 and Tag Manager
Aggregate website analytics. Consent-gated; advertising signals are permanently disabled.
- Data category
- Website visitor behaviour
- Region
- Not pinned
Microsoft Clarity
Heatmaps and session replay on aiseptor.com, loaded through the Tag Manager container. Consent-gated.
- Data category
- Website visitor behaviour, including replayed browsing sessions on this site
- Region
- Not pinned
Vercel Speed Insights
Page performance measurement for aiseptor.com.
- Data category
- Web vitals and visitor context
- Region
- Not pinned
Changes to this list
We notify institutional customers before a new subprocessor begins handling their data, giving you the opportunity to object. Contact us to be added to that notification list, or to request a signed DPA.