Where we operate
The question is where your data lives, not where our desks are
We are a distributed company without public offices, and we would rather say so than list addresses that route nowhere. What procurement actually needs from this page is residency, coverage and a real contact route.
- Structure
- Distributed
- Residency
- Selectable
- EU option
- Available
Definition
Where does CirculeID store customer data?
In the region selected for each tenant. EU-resident deployments keep passport records, supply chain events and credentials within the EU. Residency is a configuration decision made per customer, rather than a consequence of where the company or its people happen to be located.
This matters more for passport data than for most SaaS. A market surveillance authority may need to reach a record for the service life of the product, which can be considerably longer than the life of a hosting arrangement.
Residency
What is held where
| Data | Held in | Notes |
|---|---|---|
| Passport records | The tenant’s selected region | Includes every restricted tier and its access policy |
| Supply chain events | The tenant’s selected region | The append-only EPCIS history |
| Verifiable credentials | The tenant’s selected region | Signing keys held in an HSM, or by you |
| Public tier responses | Cached at the edge | Only data already published to anyone who scans |
| Anchoring digests | A public ledger | A hash only — never record content |
| Operational logs | The tenant’s selected region | Includes our own access, for audit |
Coverage
How a distributed company reaches you
Regional residency
Selected per tenant at provisioning, and stated in the agreement rather than on a marketing page.
European business hours
Standard support coverage, extended by agreement where you operate across other regions.
Incident response
Passport resolution is public infrastructure, so an outage is not a business-hours matter.
On site when it helps
Implementation workshops and architecture reviews happen wherever is useful to you.
Contracting entity
Named in the agreement, along with the jurisdiction it is established in.
One route in
Everything reaches the same place, and it reaches people who work on the product.
Answers
Frequently asked questions
Where is our passport data physically held?
In the region you select for your tenant. EU-resident deployments keep passport records, supply chain events and credentials within the EU. This is the part of the question that matters legally, and it is answered by configuration rather than by where any of our people happen to sit.
Does CirculeID have physical offices?
We are a distributed company and do not maintain public offices. We would rather say that plainly than list addresses that route nowhere. Meetings happen wherever is useful to you, including on site, and every contractual address is stated in the agreement itself.
Which timezones does support cover?
European business hours as standard, with coverage extended by agreement for customers operating across other regions. Because passport resolution is public infrastructure, incident response is not limited to business hours — the distinction is between a question and an outage.
Can data be compelled by a foreign authority?
That depends on residency and on the legal entity holding the contract, and it is a fair question to put to any vendor. We will answer it specifically for your jurisdiction during procurement rather than generically here, because a generic answer to that question is not worth anything.
Next step
Ask the residency question specifically
Tell us your jurisdiction and the product groups involved, and we will answer it for your case rather than in general. Or write to ceo@fistasolutions.com.