Data storage by country—or a strict EU zone.

A country placement constrains durable primary and replica objects to that country. zone:EU constrains them to the European Union; it does not let the caller choose an EU country.

Choose the boundary that fits your files.

Callers select a placement, never a storage vendor. This public comparison focuses on the geographic boundary and the evidence a receipt provides; vendor selection remains Privatefile's operational responsibility.

Check GET https://api.privatefile.sh/v1/availability for current write availability by placement.

country:IS

Iceland

Storage boundary: primary and replica durable objects remain in Iceland.

Geographic target
Iceland
Storage company
Incorporated in Iceland. Its ultimate parent is not confirmed from a primary source; receipts mark it unverified.
Data-protection frame
EEA; GDPR applies through the EEA framework and Icelandic Act No. 90/2018.
Intelligence shorthand
Iceland is absent from the cited Five, Nine, and Fourteen Eyes lists. That does not prove an absence of intelligence cooperation or lawful access.

country:CH

Switzerland

Storage boundary: primary and replica durable objects remain in Switzerland.

Current geographic target
Geneva, Switzerland
Storage company
Incorporated in Switzerland. Its ultimate parent is a Mexican group, disclosed by name in every receipt.
Data-protection frame
Swiss Federal Act on Data Protection; the EU recognizes Switzerland as adequate for EU personal-data transfers.
Intelligence shorthand
Switzerland is absent from the cited Five, Nine, and Fourteen Eyes lists. Absence is not immunity from Swiss process or international cooperation.

zone:EU

Strict EU zone

Storage boundary: primary and replica durable objects remain in the European Union. The current geographic target is Paris, France.

Current geographic target
Paris, France
Storage company
A company incorporated in France, an EU member state, confirmed from Privatefile's own account contract. Its ultimate parent is not confirmed from a primary source; receipts mark it unverified.
What the caller chooses
The EU boundary, not France and not a movable list of preferred countries.
Intelligence shorthand
A 2014 European Parliament resolution listed France in Nine/Fourteen Eyes and Germany in Fourteen Eyes. The EU itself is not a single “Eyes” member; national-security responsibility remains with Member States.

country:US

United States

Storage boundary: primary and replica durable objects remain in the United States.

Geographic target
United States
Storage company
Incorporated in the United States. A controlling holder is not confirmed; receipts mark the parent unverified.
Data-protection frame
US federal and state law; EU transfers need a valid Chapter V basis. The EU–US Data Privacy Framework covers participating certified organizations, not the United States in the abstract.
Intelligence shorthand
The United States is a Five Eyes member. That label alone does not establish whether a particular file can or will be accessed.

The placement covers durable objects—not every operation.

Location boundary for every production placement.
LayerLocationWhat it means
Primary and qualified replica objectsSelected placementThe country or EU-zone promise recorded in the receipt.
Public ingress and authorizationNuremberg, GermanyRequests enter the shared Privatefile control plane.
Metadata and receiptsNuremberg, GermanyOperational records are processed outside some durable placements.
Encrypted transient spoolNuremberg, GermanyTemporary, non-durable processing before provider storage.

No exclusive-processing claim: a country placement is not a statement that all metadata, network transit, provider administration, support, or legal process occurs only in that country.

Storage company jurisdiction: Privatefile only routes copies to a provider company incorporated in the selected country, or in an EU member state for the EU zone. Each receipt names that company and its ultimate parent, marked verified or unverified. A foreign parent is disclosed, not excluded.

Start with the requirement, not the ranking.

  1. Write down whether the requirement names an exact country, the EU or EEA, an approved provider, or simply a transfer mechanism.
  2. Map the controller, processors, provider legal entity, subprocessors, support access, replicas, and Privatefile's Germany control plane.
  3. Check whether the applicable rule accepts the resulting path. “EU,” “EEA,” “Europe,” and “adequate country” are not interchangeable.
  4. Confirm live placement availability before the write. Do not infer it from this catalog, a price, a configured adapter, or a previous receipt.
  5. Retain the signed residency receipt as operational evidence, alongside the contract and legal analysis it supports.