CACrown ArchivesHistory · sources · collections
Menu
Research dossier · General Reference

PCloud

Internet service

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionMay 12, 2026
Entity authorityQ25484955
Source-derived summary

pCloud is a Swiss-based cloud storage provider founded in 2013. It offers encrypted file storage, lifetime and subscription payment options, and support across multiple operating systems. pCloud operates from two data centers, located in the United States (Texas) and Luxembourg.

History

pCloud was founded in Switzerland by Tunio Zafer and Anton Titov in 2013. While it operates out of Sofia, Bulgaria, the legal entity pCloud AG is based in Baar. By 2019, it had more than 9 million users. In 2025, it counted over 22 million users.

Features

pCloud is compatible with Windows, macOS, Linux (via AppImage), Android, and iOS. A web-based interface and browser extensions are also available.

pCloud uses TLS/SSL encryption for data in transit. Files are protected with server-side 256-bit AES encryption.

Editorial summary

Begin with the source’s own compact description: “PCloud” is internet service. The dossier treats that line as a proposition to test through PCloud, Internet and service, not as a finished interpretation.

Editorial reviewA dependable orientation record for establishing vocabulary, names and a first evidence trail. The current lead gives the account dated anchors—2013, 2019, 2025—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, PCloud, Internet and service is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “internet service” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated May 12, 2026. The linked authority identifier is Q25484955. The first chronological checks are 2013, 2019 and 2025.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “PCloud”, its source revision and the description used here.
  2. Expand the search: follow PCloud primary sources, PCloud archive and PCloud research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “PCloud”?
  2. Which institution is responsible for the underlying evidence?
  3. Which cited source is closest to the event, object or claim?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from PCloud” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.