Qpher

Privacy Policy

Version 1.7.1—Last updated: 2026-10-20
Published

1. Introduction

This Privacy Policy describes how Qpher LLC ("Qpher", "we", "us") collects, uses, stores, and shares personal data when you use the Qpher PQC Security Cloud platform, including the API (api.qpher.ai), Qpher Console (portal.qpher.ai), marketing site (qpher.ai), documentation (docs.qpher.ai), and Qpher Vault: the iOS app available on the Apple App Store and its web client at vault.qpher.ai. We are committed to protecting your privacy and handling your data transparently. This policy applies to all users of the Service, including account holders, administrators, mobile-app subscribers, people who receive a document shared through Qpher Vault, and visitors to our websites. Two-Account Model: Qpher operates two independent product lines with separate billing and separate user databases — (a) SaaS API & Qpher Console (web-based, Stripe billing, intended for developers and enterprises integrating PQC into their own products) and (b) Qpher Vault (an iOS app and a web client at vault.qpher.ai that sign in to the same Qpher Vault account; personal plans are billed through Apple In-App Purchase and organization plans through Qpher Console; for individuals and for the members of an organization's Vault Team). The same email address may be used for both products, but the two accounts remain isolated by design and are governed by the data handling rules described below.

2. Controller and Processor Roles

Qpher acts in two distinct data roles depending on the category of data: Controller: Qpher is the data controller for customer account data (email, name, company), billing and payment data (invoices, payment history, Stripe customer ID), and API usage and audit logs (request counts, error logs, tenant activity). The legal bases are legitimate interest (GDPR Art. 6(1)(f)), contract performance (Art. 6(1)(b)), and legal obligation (Art. 6(1)(c)). Processor: Qpher is a data processor for customer-encrypted data (ciphertext processed via the KEM encrypt API), PQC cryptographic keys (key pairs for our post-quantum algorithms, such as ML-KEM and ML-DSA, managed by our key service), and customer plaintext submitted for encryption (transient, never stored or logged). The legal basis is contract performance (Art. 6(1)(b)). A Data Processing Agreement (DPA) is available at /legal/dpa.

3. Data We Collect

Account Information (SaaS): Email address, full name, company name, and password (stored as bcrypt hash with cost factor >= 12). For Qpher Console sessions we keep a record of each refresh token: a keyed hash of it (never the token itself), the account and organization it belongs to, when it was issued, when it expires and when it was revoked. Changing or resetting your password, or turning two-factor authentication on or off, revokes all of them. Signing out removes the session cookies from your browser. We keep these records, including expired and revoked ones, until your account is deleted. Billing Information (SaaS): Plan selection, billing interval, payment method metadata (card last four digits, expiry). Full payment card details are handled exclusively by Stripe and never reach Qpher servers. Usage Data: API request counts, endpoint usage, response times, error rates, and tenant-level activity logs. Cryptographic Data (as Processor): Ciphertext produced by KEM encryption, digital signatures produced by our post-quantum signature algorithms (ML-DSA and the others we offer), and PQC key pairs (public keys stored in the database; private keys generated by our key service, stored only in encrypted form, and never returned by any API — Sections 6, 6.5 and 7.1 describe how they are encrypted, used and retained). Customer plaintext submitted to the /kem/encrypt endpoint is transient and is never stored, logged, or persisted. Qpher Vault Data: When you use Qpher Vault, in the iOS app or its web client, we additionally collect: - Vault account credentials (email address, display name, password hashed with bcrypt cost factor >= 12) — stored in a database table physically separated from SaaS API user accounts. - Apple StoreKit transaction identifiers (apple_original_transaction_id, transaction_id, and the subscribed product_id) for verifying active Personal or Personal Pro subscription status. - Apple Sign In relay email addresses (in the form *@privaterelay.appleid.com) when the user authenticates via Sign in with Apple. We never attempt to resolve relay addresses to a user's underlying real email. - Encrypted document ciphertext stored on Cloudflare R2 (see Section 6.5 for the encryption design and the operator-trust boundary — Qpher does not read document contents during normal service operation). - Document metadata stored unencrypted in our PostgreSQL database so the application can render your file list: document name (original filename), MIME type, original byte size, file hash, encryption algorithm identifier, key version, and timestamps. Filenames are NOT encrypted for standard Qpher Vault documents in this release — please avoid putting sensitive information directly in filenames if this matters to you. (Platform-wide encrypted filenames are a v2.0 roadmap item.) Legacy Vault documents are the exception: their file names and folder names are encrypted on your device before upload, so Qpher stores only ciphertext for those metadata fields (see the Consumer Health Data Privacy Policy). - Document-relationship records including organization-membership rows (which Vault Team you belong to and your role), document-share records (recipients, permission level, expiration), pending-invitation records, and access audit logs (operations performed on your documents, with timestamps and the actor's user ID). - Multi-Factor Authentication state: an encrypted TOTP shared secret (server-side AES-256-GCM at rest), a count of unused recovery code hashes, and (where applicable) an email OTP delivery audit row. - Sign-in state: we do not store the tokens that keep you signed in to Qpher Vault (access and refresh tokens). They are signed tokens that carry a counter kept on your account. Changing, setting or resetting your password, turning two-factor authentication on or off, deleting your account, or being removed from an organization increases the counter; sessions signed in before can then no longer be renewed and end within 15 minutes. Signing out deletes the tokens from your device or browser. - Apple Push Notification Service (APNs) device tokens, collected from both of our iOS apps and used only to deliver the notifications described here — nothing else. From Qpher Vault (ai.qpher.vault): MFA prompts and shared-document notifications. From Qpher Legacy (ai.qpher.legacy): alerts to the vault owner when a claim is opened on their Legacy Vault, when that claim enters its waiting period, and when documents are released. These Legacy alerts exist so that an owner can exercise their right to stop a claim; we do not send push notifications to heirs or confirmers. A device token is a routing address only — it is not linked to the contents of any document, and it is never shared with anyone but Apple for the purpose of delivering the notification. Tokens rotate when iOS revokes them, are removed when you sign out or turn notifications off, and are deleted with your account when deletion is finalised. If you delete your account, your tokens are retained during the 30-day recovery window rather than removed immediately: an owner whose account is pending deletion is precisely the person who most needs to hear that someone has claimed their vault. We do NOT collect, anywhere in the iOS Vault app: photo library content (we read pixel data into the encryption pipeline but never transmit raw photos), location data (no GPS, no Core Location), contacts, calendar, microphone, advertising identifiers (no IDFA), device identifier-for-vendor (no IDFV), analytics events (no Firebase, Mixpanel, Amplitude, or comparable SDK), crash telemetry beyond what Apple captures via TestFlight, or any third-party tracking data. Website Analytics: Page views, referrer information, and approximate country for the marketing site qpher.ai only (via Plausible Analytics, which is cookie-free and collects no personally identifiable information). The iOS Vault app does NOT use Plausible or any other analytics tool.

3.1. Qpher Legacy Data

If you use Qpher Legacy (our digital legacy vault iOS app) — or if a Qpher Legacy vault owner designates you as an heir or confirmer — we additionally process the following data. Qpher acts as the data controller for these categories. User-designated contacts (heirs and confirmers): the name and email address of each person a vault owner designates, provided to us at the owner's direction. We use this data only to operate the owner's legacy policy: sending the designation notice, claim and status notifications, confirmation requests, and — if the owner's release policy completes — delivering the owner's documents to the designated recipients. When we first contact a designated person, the message identifies who designated them, explains why we hold their name and email, and explains how to object. A designated person may object to our processing of their contact data at any time by emailing privacy@qpher.ai — Qpher itself receives and carries out the objection by suppressing the contact record and notifying the vault owner that their policy needs review. You do not need to ask the owner to remove you. Death certificates: if a claimant does not have a claim code, their claim is routed to a manual review lane and they submit a copy of a death certificate. We use it solely to review that claim in good faith. It is retained as part of the claim record and deleted on the schedule in Section 7.1. Sworn claim attestations: every claim on a Legacy Vault requires the claimant's sworn statement, made under penalty of perjury, that the vault owner has died, together with the claimant's typed legal name and the date. The attestation text, its version, and the acceptance timestamp are retained in the append-only legacy policy ledger as evidence of the basis for the claim. Consumer health data: for Washington and Nevada consumers, our separate Consumer Health Data Privacy Policy at qpher.ai/legal/consumer-health-data also governs any consumer health data we hold.

3.2. Qpher Vault on the Web (vault.qpher.ai)

Qpher Vault also runs in a web browser at vault.qpher.ai. Two kinds of people use it: people who receive a document that a Qpher Vault user shares with their email address ("recipients"), and Qpher Vault account holders who sign in on the web. This section describes what the web client adds to Section 3; the rest of this Policy applies to it. Qpher LLC is the controller of the personal data described in this section. For the encrypted contents of documents, Section 2 applies. If someone shares a document with you - Where your address comes from. The sender gives us your email address when they share. We use it to email you a link, through Twilio SendGrid. If you never open the link, your address stays in the sender's share record, even if the sender revokes the share, until the sender deletes the document or their account, or you ask us to delete it. - What the link shows. Before you verify anything, the link's page shows the sender's name, email address and organization (if any), the document's file name and size, and your email address, to anyone who has the link. Please do not forward it. If the sender added a note, it is in the email in plain text; we do not store it. - The code. To open the document you ask for a 6-digit code, which we email to the shared address. It works once and expires after 10 minutes. We keep only a keyed hash of it, for at most those 10 minutes. - Your recipient profile. When you enter the correct code, we create a recipient profile for that address, or reuse the one you already have. It holds the email address, a display name taken from the part of the address before "@", and a record that the address was verified. It has no password and cannot buy anything. When you first open a document, the profile is also given its own key pairs, so that documents can be encrypted for you and so that you can sign. As with every Qpher Vault account, the private keys are generated and used only inside Qpher's isolated key service (Section 6.5); at rest they are encrypted through Google Cloud KMS, as Section 6 describes. If you later set a password for the address with "Forgot password", or sign in with Apple using the same address, the profile becomes a Qpher Vault account. - What is recorded. Each time you open a shared document, we record it. The sender can see when you first and last opened it, how many times, and that you used a code. If the document belongs to an organization, these events can also appear in that organization's audit log. If you sign a document, your signature and its details (the algorithm, key version, a hash of the signed file and the time) are stored with the sender's document, and the sender can see that you signed. If you reply with a revised file, the reply is stored as an encrypted document in your recipient profile and shared with the sender, with the unencrypted details described in Section 3 (file name, type and size). - Keeping and deleting it. We keep your recipient profile until you ask us to delete it. To ask, email support@qpher.ai or privacy@qpher.ai from the shared address; Section 7.3 applies. Deleting the profile also deletes the shares made to it, your replies, your signatures on the sender's documents, and the records of when you opened them, including in an organization's audit log. The profile's key pairs are not deleted, as Section 7.1 describes. The sender's own documents are not affected. - Why we process it. Before you verify, we rely on our legitimate interest in delivering a document that a Qpher Vault user chose to send you and in protecting the link. After you verify, we process your data to provide what you asked for: opening, signing and replying to the documents shared with you. Logs and abuse counters rely on our legitimate interest in keeping the service secure (Section 4). You may object at any time (Section 8). If you sign in on the web - It is the same Qpher Vault account described in Section 3, whether you sign in with your email and password (and two-factor authentication, if you turned it on) or with Sign in with Apple. Accepting an organization invitation on the web creates that same kind of account. - Category labels. If you give a document a category label (Insurance, Tax, Legal, Medical, Identity or Company), the label is stored unencrypted, like the file name (Section 3). - Tags. If you add tags to documents (labels you name yourself, such as a matter number), each tag name is stored unencrypted, like the file name (Section 3), so Qpher's servers can read it. Please don't put a client's name or other sensitive information in a tag name. Your tags are visible only to your account: a person you share a document with never sees your tags on it, and you never see theirs. We keep a tag until you delete it or your account deletion is finalized. A tag is removed from a document when you remove it, when the document is permanently deleted, or, for a document shared with you, when the sender revokes the share. A share that only expires does not delete your tags on that document; they are hidden until one of those events. Deleted tags remain in our encrypted database backups until those backups expire (Section 7.1). - Cookies. After you sign in, api.vault.qpher.ai sets one cookie, __Host-qv_refresh (HttpOnly, Secure, SameSite=Strict). It is renewed while you use the web client and expires 7 days after it was last renewed, or when you sign out. During Sign in with Apple only, it sets __Host-qv_apple for at most 10 minutes. We use them only to sign you in and keep you signed in, never for analytics, advertising or tracking. The short-lived access token (15 minutes) is kept only in the page's memory. We set no other cookies on the web client, store nothing in your browser's storage, and load no analytics or third-party scripts. Encryption in your browser Documents you open on the web are decrypted in your browser, and documents you send from the web are encrypted in your browser before upload, so their contents reach Qpher's servers only in encrypted form. File names, types, sizes, category labels and tag names are not encrypted (Section 3). To open a document, your browser receives from Qpher's servers, over an encrypted connection, a secret that unlocks that one document's key. This is the operator-trusted model described in Section 6.5, the same as in the iOS app. Network data and logs - vault.qpher.ai's pages are served by Vercel, Inc. (USA), which processes standard request data, such as your IP address and browser type, to deliver them. - The service behind them, api.vault.qpher.ai, runs on Google Cloud. Its request logs record each request's IP address, browser type, the web address requested, the result and the time. These logs, and the service's own logs, which can include your profile's or account's ID, are kept for 30 days. The secret part of a shared link stays in the part of the web address your browser never sends to a server, or travels in request bodies, so it is not in these logs. - To prevent abuse, the recipient and invitation pages count requests per IP address, in a counter that expires one hour after the last request. - Counters that protect a link against guessing (codes sent, failed attempts, locks) are keyed by a hash of the link rather than by your email or IP address, and are deleted automatically at most 400 days after they are created. - Your data is processed in the United States (Section 11).

4. Legal Basis for Processing (GDPR Art. 6)

Contract Performance (Art. 6(1)(b)): Processing account data and cryptographic data is necessary to provide the Service as agreed in the Terms of Service. Legitimate Interest (Art. 6(1)(f)): Processing usage data and audit logs is necessary for platform security, abuse prevention, and service improvement. We have conducted a legitimate interest assessment and determined that these interests do not override data subject rights. Legal Obligation (Art. 6(1)(c)): Retaining billing records and invoices for 7 years is required for tax compliance. Consent: We rely on consent only where required by law (e.g., for optional marketing communications). Consent may be withdrawn at any time.

5. How We Use Your Data

We use your data to: (a) provide and maintain the Service, including account management, authentication, and API access, (b) process billing and payments through Stripe, (c) enforce plan limits and rate limiting, (d) generate audit logs for security and compliance, (e) monitor platform performance and availability, (f) send transactional emails (account verification, password reset, security alerts, billing notifications), (g) improve the Service based on aggregated, anonymized usage patterns, and (h) comply with legal obligations. We do not sell personal information to third parties. We do not use customer cryptographic data (ciphertext, keys) for any purpose other than providing the requested cryptographic operations.

6. Data Sharing and Sub-Processors

Qpher shares data with the following sub-processors: - Stripe, Inc. (USA, EU-US Data Privacy Framework): Payment processing for the SaaS API and Qpher Console. Receives customer name, email, billing address, and tokenized payment card data. - Apple Inc. (USA): App Store Connect billing and StoreKit subscription management for the Qpher Vault iOS application. Receives Apple ID, IAP transaction identifiers, and subscription metadata. Apple's handling of payment data is governed by the Apple Privacy Policy. - Cloudflare, Inc. (USA, Cloudflare Data Processing Addendum): R2 object storage for Qpher Vault documents, in Cloudflare's eastern North America region. Receives the encrypted ciphertext bytes (which Cloudflare cannot read), and a small JSON metadata sidecar per document containing the byte size and PQC algorithm identifier, and — for standard Qpher Vault documents — the original filename in plaintext (these standard-Vault metadata fields are stored unencrypted both on Cloudflare and in our PostgreSQL database — see Section 3 and Section 6.5; for Legacy Vault documents the file name and folder name are encrypted on-device and stored only as ciphertext). Document objects are named by account ID and document ID. Cloudflare does not have access to the document contents themselves. Death certificates submitted for a Qpher Legacy claim that is reviewed manually (Section 3.1) are stored in the same storage unencrypted, named by claim ID. Cloudflare's network also sits in front of our internal administration console (admin.qpher.ai) and carries its traffic, including the account data our staff view there. - Twilio SendGrid (USA): Email delivery in both directions. It sends the emails our services send, such as account verification, password reset, sign-in and two-factor codes, welcome, security, billing, trial and quota notices, organization invitations (including the code for accepting one on the web), the link and one-time code for a person a document is shared with, notifications about organizations, shared documents and Qpher Legacy policies, our replies to emails you send us, and messages sent through the qpher.ai contact form, which go to our team. It also receives email sent to our own addresses (such as support@qpher.ai and privacy@qpher.ai) and passes it to us. Receives the email addresses involved and the content of each email. We have turned off SendGrid's open and click tracking for every email we send through it, so we do not record whether you open our emails or click their links. - Vercel, Inc. (USA): Hosts our websites: qpher.ai, portal.qpher.ai and docs.qpher.ai, our internal administration console at admin.qpher.ai, and, from its launch, the Qpher Vault web client at vault.qpher.ai. For every page it receives standard request data, such as your IP address, browser type and the address requested. Its server functions also handle Qpher Console's sign-in tokens in transit, to set and renew the Console's session cookies; pass our staff's administration-console requests to our API, and the account data those requests return; and send the qpher.ai contact form (name, email address, company and message) to our team through Twilio SendGrid. Vercel does not receive document contents or cryptographic keys. - Google Cloud Platform (Google LLC, USA — us-east1; key backups: us-west1 — Oregon): Compute (Cloud Run), database (Cloud SQL), key management (Cloud KMS), object storage, and in-memory cache / rate limiting (Memorystore Redis). All platform data is encrypted at rest and in transit. - Google LLC (Google Cloud KMS) (USA, us-east1 — South Carolina, Google Cloud Data Processing and Security Terms): Encryption at rest of PQC private keys. Over an encrypted connection, our key service sends each private key to Cloud KMS to be encrypted under a key-encryption key that Qpher controls in Cloud KMS (software protection level, not a hardware security module), stores only the encrypted result, and sends that result back to Cloud KMS to be decrypted when an operation needs the key. Cloud KMS therefore processes unencrypted private keys whenever it encrypts or decrypts one; it never receives document contents or any other customer data. - Anthropic, PBC (USA): Powers the in-product AI support assistant (Claude). Receives the chat messages you send and, for the authenticated Qpher Console chat, your account email, display name, plan, and tenant identifier. Does not receive your documents, plaintext, ciphertext, or cryptographic keys. Per Anthropic's commercial terms, data submitted via the API is not used to train models (see Anthropic's privacy policy). - Plausible Analytics (EU, Germany): Privacy-focused website analytics for the marketing site only (NOT used in the iOS app). Receives page views, referrer, and approximate country. No personally identifiable information or cookies. - BetterStack (EU): Uptime monitoring. Receives API endpoint URLs and response times only. We provide 30 days advance notice via email and a notification in Qpher Console before adding new sub-processors. Enterprise customers with custom DPA terms may object per their contractual agreement.

6.5. Qpher Vault Encryption Design (Operator-Trusted Model)

The Qpher Vault iOS application encrypts your document content on-device before it leaves your phone. The encryption design — described in detail in our Architecture Decision Records ADR-0023 (KEM-DEM scheme), ADR-0031 (hybrid PQC+classical algorithms), and ADR-0010 (private key boundary) — works as follows: 1. On-device encryption: When you upload a document, the Vault app generates a random AES-256-GCM data encryption key (DEK) on your device and encrypts the file locally. The plaintext content never leaves your device. 2. Hybrid post-quantum key wrapping: The DEK is wrapped using X-Wing, a hybrid scheme combining NIST-standardized post-quantum cryptography (ML-KEM-768, formerly Kyber768, FIPS 203) with classical X25519 elliptic-curve key agreement. This dual-layer design provides defense-in-depth against future cryptanalytic advances on either algorithm. Wrapping uses your tenant's public encapsulation key: our key service runs the encapsulation and returns the resulting shared secret to your device, which derives the wrapping key from it and wraps the DEK locally. 3. Storage: The encrypted ciphertext bytes and the wrapped DEK are uploaded to Cloudflare R2. The unwrapped DEK is never persisted server-side. A small JSON metadata sidecar containing the document's byte size and algorithm identifier — and, for standard Qpher Vault documents, the plaintext filename — accompanies the ciphertext on R2 and in our PostgreSQL database (see Section 3). For standard Qpher Vault documents these filename fields are NOT encrypted in this release; for documents selected into a Qpher Legacy Vault, the file names and folder names are encrypted on-device before upload and stored only as ciphertext (see the Consumer Health Data Privacy Policy). 4. Decryption: When you open a document, the Vault app authenticates and sends the document's KEM ciphertext, through our Vault backend, to the Qpher Key Management Service (KMS-Orchestrator). The key service holds the tenant decapsulation private key — encrypted at rest as described in Section 6, and never returned by any API — performs the KEM decapsulation, and returns the resulting shared secret to your device. The app derives the DEK-unwrapping key from that shared secret, unwraps the DEK and decrypts the file locally. Our servers keep the shared secret in memory only while the request is handled; the key service overwrites its working copy as soon as the response is built. This is best-effort: copies made while the response is encoded and relayed are released, not overwritten. Trust model — please read this carefully. Qpher operates this release of the iOS Vault under an operator-trusted model: Qpher's Key Management Service holds the tenant decapsulation private key. This means that, under normal service operation, our automated infrastructure does NOT read the plaintext content of your documents. When you open a document, the decapsulation runs on an authenticated request from your device, and the shared secret is returned to your device. Our servers also decapsulate and use the shared secret themselves when a document is shared with someone outside your own account or organization (including a recipient who opens it on the web), when a share completes after its recipient creates an account, when a .qpher file is exported or imported, and when a Qpher Legacy release is delivered: in those cases our Vault backend unwraps the document's DEK in its memory and re-wraps it for the recipient. It does not decrypt the document, and it does not store the unwrapped DEK. However, a privileged Qpher operator with production KMS access could in principle perform a decapsulation outside the normal request flow. This model is the same one used by, for example, Dropbox, Box, and Apple iCloud's standard data protection — and is materially different from a true zero-knowledge model used by Apple's Advanced Data Protection, Bitwarden, or 1Password (where the encryption keys live only on the user's devices and the service operator cannot decrypt content even if compelled to). What this means for you in practice. - Organizations. Documents encrypted for an organization are protected with a key the organization's members share; who may download a document is governed by Qpher Vault's sharing controls. Holders of the organization's API keys can decrypt organization files they hold until the key is revoked in Qpher Console. - Forgetting your password and resetting it via email does not lose your document access — the encryption keys are managed by Qpher's KMS, not derived from your password. - Qpher is technically capable of complying with a valid legal order (subpoena, search warrant, court order) to decrypt the documents of a specific account. We have not been required to do so to date. We will publish a transparency report if and when we receive such legal demands, including aggregate counts and categories permitted to be disclosed under applicable law. We will notify the affected user unless prohibited by law. - A true zero-knowledge mode is on our product roadmap. Once shipped, that mode will move the decapsulation key to your device and remove Qpher's ability to access content even with operator access. We will publish a separate ADR and updated Privacy Policy section before that capability ships. - App Store Privacy Nutrition Label: per Apple's guidance for apps using end-to-end-style encryption-at-rest where the service operator does not normally access content, we exclude document content from the "User Content" category in the App Store metadata. The metadata sidecar described above (filename, size, algorithm) is collected and disclosed in Section 3.

7. Data Retention

Retention varies by data category and user action. We publish this schedule to satisfy GDPR Article 13(2)(a), UK-GDPR, CCPA, and comparable transparency requirements. See Section 7.1 for the retention schedule by category, Section 7.2 for the criteria used to determine each period, and Section 7.3 for your right to accelerated deletion.

7.1. Retention Schedule by Data Category

Individual account data (Qpher Vault): - While the account is active: retained indefinitely. - After user-initiated deletion: 30-day grace window during which the account is non-functional but recoverable via 'Restore Account'. After grace, account data (email, password hash, MFA secrets, vault document contents, vault metadata) is removed from active systems, except that the internal record the account's encryption keys were generated for, if it had its own, keeps a name that includes the account's email address (see Cryptographic key material below). We delete the account's documents from Cloudflare R2 when its deletion is finalized; our R2 storage keeps no earlier versions. Account data and document metadata remain in our encrypted database backups until those backups expire: we keep 14 daily backups and 7 days of point-in-time recovery logs, and any on-demand backup we take is kept until we delete it. - After administrative removal by an organization administrator: no grace period; the member's organization-level row is removed; the individual's personal vault data (if the user has a personal account outside the organization) is preserved. Organization data: - While active: retained indefinitely. - After owner-initiated deletion: 30-day grace, then removal from active systems in stages (see Section 7.3); copies in our database backups follow the same retention as for individual accounts. Documents in Cloudflare R2 belong to the members who uploaded them and are deleted with each member's account; documents encrypted for an organization can no longer be opened once the organization is deleted (Terms of Service, Sections 7 and 7.2). The Stripe subscription is set to cancel at the end of the current billing period upon grace initiation — see Terms of Service Section 7.3. Cryptographic key material: - PQC private keys are not deleted when an account or organization is deleted: the key pairs generated for it, for every algorithm, stay in our key storage, encrypted at rest as described in Section 6, together with the internal record of the account they were generated for (for a Qpher Vault account, that record's name includes the account's email address). We do not currently destroy the key material of deleted accounts or organizations. - We do not currently delete backup copies of private keys; they have no deletion date. Our key storage is copied daily to a separate disaster-recovery bucket (Google Cloud, us-west1 — Oregon). The copy only adds and updates files, so removing a key from primary storage does not remove its backup copy. The backup also holds older copies from before our key storage moved to Cloud KMS encryption in May 2026; those are encrypted with AES-256-GCM under an older, separate key-encryption key kept in Google Secret Manager, with an encrypted printed copy kept for emergencies. - Archiving a key — available to SaaS customers in Qpher Console only — deletes its private key from primary storage. Our storage keeps the deleted version for about 30 more days, followed by a 7-day soft-delete period, and any backup copies remain. - PQC public keys are kept with their key pairs and are not deleted when the account is. Operational data: - Audit logs (append-only lifecycle events): retained indefinitely. These records are append-only by design — they are the tamper-evident proof that a deletion, restoration, or release actually followed the process we describe, and our deletion automation refuses to act on an account that has no matching audit entry. Each entry holds identifiers and process facts only (which action, when, by which role, against which internal record ID) and never contains your name, email address, document names, or document contents. Data subjects may request a copy of their audit log entries via Section 7.3 while the account exists. - Invoices and billing records: retained 7 years per U.S. IRS 26 CFR §1.6001-1 and applicable EU Member State tax law. - Prometheus operational metrics: 15 days hot storage, 90 days cold storage, then anonymized by removing tenant identifiers. Qpher Legacy data (see Section 3.1): - While a legacy policy is armed, the account is exempt from automatic deletion processes (a "Legacy Hold") — an armed vault is preserved for its designated recipients even if the subscription lapses, until it is claimed, vetoed, or the owner disarms or deletes it. - Legacy Vault documents after a completed release: retained for at least 24 months after release so that recipients can claim and download them, regardless of subscription status. In plain terms, this 24-month clock pauses while any claim is open or while a court-ordered or estate-dispute freeze is in place, and resumes counting when the claim or freeze is resolved — an open dispute never runs the clock out. Before any purge, we notify all known contacts 90, 30, and 7 days in advance. - Death certificates (manual claim-review lane): retained with the claim record for as long as the related claim record is retained, then deleted on the same schedule as the policy's audit records. - Designated-contact records (heir/confirmer name and email): retained while the owner's policy references them; removed when the owner deletes the policy or account (subject to the append-only ledger entries above), or suppressed immediately when the contact objects per Section 3.1. - Legacy policy ledger entries (append-only lifecycle events for designations, claims, confirmations, vetoes, freezes, and releases): retained per the audit-log schedule above.

7.2. Criteria for Determining Retention

The retention periods in Section 7.1 are determined by the following considerations, as required by GDPR Article 13(2)(a) and comparable applicable law: 30-day grace period for account and organization deletion: gives you time to recover from a deletion made by mistake, balanced against the data subject's right to prompt erasure. Legal basis: Article 6(1)(b) (contract performance: the grace period enables the user to restore their ongoing service relationship). Database backups after active-system deletion: we keep 14 daily automated backups of our database and 7 days of point-in-time recovery logs, so that we can recover from an outage or a mistake; any on-demand backup is kept until we delete it. Backup-retained data is inaccessible to Qpher personnel except in bona-fide disaster-recovery scenarios. Legal basis: Article 6(1)(f) (legitimate interest: business continuity; see Section 4 for our legitimate interest assessment). No grace period for administrative removal: a removal by an organization administrator takes effect immediately, which honors the affected user's expectation that a removal is prompt. Legal basis: Article 6(1)(b) contract performance. Indefinite audit log retention: required for forensic review, security incident investigation, dispute evidence (including inheritance disputes under Qpher Legacy, which can arise years after a release), and regulatory compliance. These records are append-only and hold identifiers and process facts only — no names, email addresses, or document contents. Legal basis: Article 6(1)(f) legitimate interest (platform security and evidentiary integrity). 7-year invoice retention: required by U.S. IRS 26 CFR §1.6001-1 and applicable EU Member State tax law. Legal basis: Article 6(1)(c) legal obligation.

7.3. Your Right to Erasure

You may request accelerated deletion (faster than the 30-day grace) at any time under GDPR Article 17, UK-GDPR Article 17, CCPA §1798.105 (for California residents), and comparable applicable law in your jurisdiction. To request accelerated deletion: 1. Email privacy@qpher.ai with your account email and a clear request for accelerated deletion. 2. We verify your request and respond within 1 calendar month of receipt. For complex requests we may extend by up to an additional 2 months, notifying you of the extension and the reason per GDPR Article 12(3). 3. Upon verification, deletion proceeds: active-system removal within 30 calendar days of the verification date; copies in our database backups then expire on the schedule in Section 7.1. 4. We may retain data longer where legal obligations require (e.g., 7-year invoice retention for tax compliance); we identify any such retained data in our response. Automated deletion: the automatic final deletion of an account or organization at the end of its grace window is being enabled in stages. During the grace window, deleted data is not used and can be brought back only by restoring the account. If you need your data removed sooner, or if automatic final deletion does not yet cover your account, use the email path above: it is available today and completes active-system removal within the 30 calendar days stated. You retain all rights under GDPR, UK-GDPR, and CCPA throughout. If you believe your erasure request has not been honored within the stated timeframe, you may lodge a complaint with your local supervisory authority (EEA: your national Data Protection Authority; UK: Information Commissioner's Office; California: Attorney General's Office; other jurisdictions: your applicable authority).

8. Your Rights Under GDPR

If you are located in the European Economic Area (EEA) or the United Kingdom, you have the following rights: - Right to Access (Art. 15): Request a copy of your personal data by emailing privacy@qpher.ai; we respond within 30 days. - Right to Rectification (Art. 16): Update your profile information in Qpher Console settings. - Right to Erasure (Art. 17): Request account deletion; we remove your data from active systems within 30 days (Section 7 explains what we keep, and for how long). - Right to Restrict Processing (Art. 18): Request account suspension (API access disabled, data preserved). - Right to Data Portability (Art. 20): Request a machine-readable copy of your public keys and data by emailing privacy@qpher.ai. - Right to Object (Art. 21): Object to processing based on legitimate interest by contacting privacy@qpher.ai. To exercise these rights, use Qpher Console settings or contact privacy@qpher.ai. We respond to requests within 30 days. You also have the right to lodge a complaint with your local supervisory authority.

9. Your Rights Under CCPA

If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA): - Right to Know (Section 1798.100): Request information about the categories and specific pieces of personal information we collect. Submit your request by emailing privacy@qpher.ai (same mechanism as GDPR Art. 15 above). - Right to Delete (Section 1798.105): Request deletion of your personal information. We process requests within 30 days. See Section 7.3 for the accelerated deletion mechanism, response timeframes, and rollout status. - Right to Opt-Out of Sale (Section 1798.120): Qpher does not sell personal information to third parties. - Right to Non-Discrimination (Section 1798.125): We do not discriminate in pricing or service quality based on the exercise of privacy rights. Categories of personal information collected: identifiers (email, name), commercial information (billing records), and internet activity (API usage logs). To exercise your rights, use Qpher Console settings or contact privacy@qpher.ai.

10. Security Measures

We implement the following security measures to protect your data: (a) all data in transit is encrypted with TLS, and TLS 1.3 is used with clients that support it, (b) all data at rest is encrypted, including PQC private keys encrypted with AES-256-GCM, (c) passwords are hashed with bcrypt (cost factor >= 12), (d) API keys are stored as HMAC-SHA256 hashes, never in plaintext, (e) application-level tenant isolation ensures no cross-tenant data access, (f) a zero trust policy engine evaluates every request to our SaaS API, (g) audit logs track all security-relevant operations and are append-only and retained indefinitely (see Section 7.1), and (h) all changes to security-critical components require peer code review before deployment. Independent third-party penetration testing and SOC 2 Type II certification are planned as part of our enterprise-readiness roadmap and have not yet been performed.

11. International Data Transfers

Qpher is based in the United States. If you are accessing the Service from outside the United States, your data may be transferred to and processed in the United States. Data is stored in the United States on Google Cloud and in Cloudflare's eastern North America region. For transfers from the EEA/UK to the US, we rely on: (a) the EU-US Data Privacy Framework (DPF) where our sub-processors are certified, (b) Standard Contractual Clauses (SCCs) as approved by the European Commission, and (c) supplementary technical measures including encryption in transit and at rest. Enterprise customers may negotiate additional data transfer safeguards in their DPA.

12. Contact Information

For privacy-related inquiries, data subject requests, or complaints: - Privacy Team: privacy@qpher.ai - Security Team: security@qpher.ai - General Inquiries: sales@qpher.ai - Postal Address: Qpher LLC, 8401 Mayland Dr Ste A, Richmond, VA 23294, USA We aim to respond to all privacy inquiries within 30 days. If you are not satisfied with our response, you have the right to lodge a complaint with your local data protection supervisory authority.

13. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, legal requirements, or the Service. Material changes will be communicated via email to the account holder and through a notification in Qpher Console at least 30 days before taking effect. The current version of the Privacy Policy is always available at qpher.ai/legal/privacy. We encourage you to review this policy periodically. Your continued use of the Service after changes take effect constitutes your acceptance of the updated policy.

Ask Qpher AI