Privacy Policy
Last updated: July 20, 2026 · Data controller: BELANCHUK PAVEL ALEKSANDROVICH PE (sole proprietor), Republic of Armenia, RA, Yerevan, Movses Khorenatsi str., bld. 26a, 201 o, 0010 · Data contact: privacy@kontinuum.cloud
This document is published in English, Russian, and Spanish. In case of discrepancies, the English version prevails.
1. Our approach: “private, not anonymous”
kontinuum is designed so that the content of your data stays confidential — it is protected by end-to-end encryption, and we are technically unable to access it. At the same time, we honestly do not promise anonymity: certain metadata and identifiers (your identity identifier and, under certain settings, network addresses) are required for the P2P network to operate. We draw this line explicitly.
2. Who we are
The data controller is Pavel Belanchuk PE, Armenia. Contact for data matters and data-subject requests: privacy@kontinuum.cloud.
3. What data is processed
- On your device (stored locally): identity (display name), devices, spaces, files and their metadata, contacts, settings. Secrets and keys are encrypted at rest (recovery phrase → Argon2id → ChaCha20-Poly1305; Stronghold vault). Other local metadata (file/space names, contacts) is stored unencrypted in the device’s local databases — it is protected by access to the device itself; to protect against loss or theft of the device we recommend enabling disk encryption.
- Transmitted over the network (P2P / relay nodes): file and collection contents and names are transmitted only in encrypted form (see §5) — nodes see ciphertext. Visible for routing purposes: pseudonymous identifiers (spaces, devices), peer information; under certain settings — network addresses (see §6).
- Payment data: processed by Paddle (Merchant of Record); we do not store payment details.
- Waitlist email (pre-launch): if you left your email in the waitlist form — only with your explicit consent and solely to notify you of the launch; deleted after the launch notification is sent, and no later than 6 months after collection. Never added to other marketing lists.
4. What we do NOT collect
- App telemetry and analytics — NONE (as of this date). The app does not collect telemetry, analytics, or crash reports, and uses no third-party trackers (Sentry, Google Analytics, etc.). We have an analytics component (kontinuum Pulse), but in the current version it is inactive and no app data flows into it. Any future activation of analytics/Pulse will happen only with your explicit opt-in consent and after this Policy has been updated in advance to describe exactly what is collected — never retroactively.
- Our website uses only self-hosted, cookieless analytics on our own infrastructure (aggregate visit counters; no cookies, no IP-address storage, no third-party trackers).
- Email is not required and not collected when creating an identity.
- Photos/avatars are not uploaded (they are generated from initials).
- Update checks (functional): depend on how you installed the app. In versions from Google Play / App Store, updates are performed by the store (and the network request carrying your IP address goes to the store, not to us). In the version installed directly from our website, the app periodically contacts our update server (
updates.kontinuum.cloud), revealing the request IP address to it. No profiling takes place in either case.
5. Encryption
- End-to-end (E2E): the contents of your spaces and files — including file and collection names — are encrypted on your device (per-object AES-256-GCM) before being sent. Relay nodes and cloud storage see only ciphertext; keys remain only on your devices. The same applies to cloud backup — it is encrypted client-side before upload (object names are obfuscated).
- At rest on the device: secrets and the recovery phrase are encrypted (Argon2id → ChaCha20-Poly1305); keys live in a protected keystore (Stronghold) and are non-extractable.
6. Metadata and network addresses (“not anonymous”)
- Identifiers: the network operates on pseudonymous identity/device/space identifiers.
- IP address: the “identity identifier ↔ IP” mapping is published to the distributed table only with your consent and only if you do not use your own relay node; if you run your own relay, the relay’s address is published instead of your personal one.
- Metadata at relays: relay nodes routing operations see routing and membership metadata — the fact of space membership, pseudonymous identifiers, device certificates, timestamps, operation types. They do NOT see contents or names (those are encrypted, see §5), but this metadata is not E2E by design.
- Your own relay node (metadata minimization): if you use your own relay node, routing and membership metadata stays on your infrastructure rather than on our or third-party nodes.
- First contact: when a contact is first established, your display name may be transmitted unencrypted (technically — before key exchange). This is part of the “not anonymous” boundary.
7. Data recipients (sub-processors)
| Recipient | Purpose | What it sees |
|---|---|---|
| Cloud object-storage provider (USA; Standard Contractual Clauses) | cloud backup | only encrypted content (E2E); has no access to plaintext |
| Paddle (Merchant of Record) | payment processing, invoicing, taxes | payment data (we do not store it) |
| Our update server (updates.kontinuum.cloud) | version checks (direct installs only) | request IP address |
We disclose recipients by category; the name of the specific storage provider is available on request at privacy@kontinuum.cloud. There are no third-party analytics.
8. Legal bases (GDPR)
- Performance of a contract — providing the core functionality of the Service.
- Legitimate interest — security, operation and routing of the P2P network, update checks.
- Consent — publication of your network address (§6), the waitlist email (§3), and other optional features.
9. International data transfers
Encrypted backups are stored with a cloud object-storage provider in the USA on the basis of Standard Contractual Clauses (SCC). Since only E2E-encrypted content reaches the cloud, the provider has no access to the contents. Payment data is processed by Paddle under its own privacy policy.
10. Retention and deletion
- Local data stays on your device until you delete it.
- Account deletion (§12) erases all local data.
- Cloud backups (encrypted) are kept until you delete them or delete your account.
- Payment records are retained by Paddle for the periods required by applicable law (tax/accounting).
- Waitlist emails — until the launch notification is sent, and no longer than 6 months.
11. Your rights
Under the GDPR (and similar laws) you have the rights of access, rectification, erasure, restriction, portability, and objection. Send requests to privacy@kontinuum.cloud. We are technically unable to retrieve or hand over end-to-end-encrypted content — but we will help with the data we do hold (account metadata).
12. Account deletion
You can completely delete your account and all local data from within the app: Settings → Delete account (PIN-protected). Deletion irreversibly wipes all local stores (including physical overwrite, not just logical deletion). If you no longer have access to the app, write to privacy@kontinuum.cloud and we will help with the data we hold.
13. Children
The Service is not intended for children under 16; we do not knowingly collect their data.
14. Changes
We will announce changes to this Policy in the app and on this page, updating the date above. Material changes will be announced in advance.
15. Contact
privacy@kontinuum.cloud · Pavel Belanchuk PE, RA, Yerevan, Movses Khorenatsi str., bld. 26a, 201 o, 0010.