Privacy Policy

Status: DRAFT (Active Development)

Effective Date: August 21, 2026

Last Updated: August 21, 2026

1. Introduction & Overview

Welcome to ibGib. We are committed to transparency, cryptographic self-sovereignty, and user privacy.

This Privacy Policy explains how ibGib (including ibgib.space, ibgib.com, and related open-source applications in this monorepo) collects, uses, stores, and protects your information when you interact with our network, services, and applications.

2. Categories of Information We Collect

A. Identity & Public Directory Data

When you create an account or link authentication methods, the following information is recorded in your identity keystone:

• Chosen Username: A human-readable identifier (e.g. alice).
• Registered Email Address: Provided during account creation or SSO linking to enable account discovery, verification, and recovery.
• Public Keystone DAG Addresses & Challenge Hashes: Cryptographic addresses and mathematical challenge hashes (H = \text{Hash}(S)) that define your identity's evolution timeline.
• Registered Device Delegate Tags: Public labels for devices authorized to sync on your behalf (e.g. pwd-alice-desk-a9a0, passkey-mobile-b4c1).

B. Technical, Connection & Log Data

When accessing our hosted web nodes, standard operational connection data may be logged:

• Internet Protocol (IP) Address and approximate geographic origin.
• HTTP/TLS Request Metadata: Date/time of request, HTTP status code, URL path, and TLS cipher suite.
• User-Agent Strings: Browser type, operating system, and client application version.
• Retention: Operational and access logs are retained for a bounded window (typically 30 to 90 days) strictly for system reliability, rate limiting, intrusion detection, and security forensics, after which they are automatically rotated and deleted.

C. Workspace & Application Data

• User-Created Content: Notes, comments, graph nodes, and files stored within your tenant workspace.
• Storage Status: Workspace data is stored in tenant-isolated domain spaces. Data in transit is encrypted via TLS 1.3. Data at rest on the server is currently stored unencrypted within your isolated space directory (client-side data encryption is planned as a future capability).

3. Public Directory Nature of Identity Keystones

Innovative ZKP DLT vs. Conventional PKI

ibGib is built upon public-key cryptographic principles, but is not conventional Public Key Infrastructure (PKI):

• Instead of relying on asymmetric digital signatures (RSA, ECDSA) and centralized X.509 Certificate Authorities (CAs), ibGib identities utilize a Zero-Knowledge Proof (ZKP) Distributed Ledger Technology (DLT) architecture with symmetric hash-reveal challenge-response pools.
• Public by Design: Identity Keystones function as public directory records. Anyone on the network who knows your username or email address can query the server to retrieve your public keystone.
• Zero Secret Exposure: Public keystones contain only public challenge hashes (H). Revealing a challenge hash gives an observer zero ability to compute your private secret pre-image (S) or act on your behalf.
• Biometric & Password Isolation:
• Passwords, PINs, and passphrase pre-images are processed strictly inside your local browser memory and discarded.
• Hardware biometrics (fingerprints, facial recognition) and security keys operate exclusively within your device's hardware Secure Enclave / TPM via the W3C WebAuthn standard. Raw biometric data is never transmitted over the network or accessible to our servers.

4. How We Use Your Information

We process personal and cryptographic data solely for the following legitimate purposes:

1. Identity Resolution & Discovery: Matching incoming authentication requests and email lookups to the correct tenant domain space.
2. Cryptographic Multi-Device Authorization: Permitting your devices to authorize scoped synchronization claims via local device sync delegates (D_{\text{device}}), while the native ibGib sync engine executes graph synchronization.
3. Account Verification & Sign-In: Sending one-time 6-digit verification codes (OTP) to confirm email ownership and authenticate sign-ins.
4. Security & Abuse Prevention: Enforcing rate limits, detecting brute-force attacks, and preventing server abuse.

We do not use your data for profiling, automated decision-making, or third-party targeted advertising.

5. Third-Party Service Providers

We utilize minimal third-party services essential to core platform functionality:

• Single Sign-On (SSO) Authentication (Optional):
• Google OAuth2: Currently supported for single-tap passwordless account creation and sign-in. When linking Google, we receive verified identity tokens (such as your verified email address and provider user ID) to authenticate your identity. We do not receive or store your Google password.
• Future Providers: We plan to introduce additional OAuth2 providers (such as GitHub and others) in future updates.
• Transactional Email & Hosting Infrastructure:
• Transactional Email: We send emails strictly for transactional account confirmation, sign-in verification codes, and security notices. We never send marketing, newsletter, or promotional spam emails.
• Cloud Server & Storage Nodes: Web nodes, domain space storage, and network routing are hosted on secure cloud infrastructure located in the United States.

6. Immutable Timeline Integrity, Revocations & Data Deletion

Cryptographic Timeline Integrity

ibGib is built on an append-only, directed acyclic graph (DAG) architecture. Similar to version control systems (like Git) and cryptographic ledgers (like Bitcoin), timeline records are mathematically linked using cryptographic hashes to ensure data integrity and tamper-evidence. Just as past blocks in a blockchain cannot be modified without destroying cryptographic integrity, historical keystone frames remain part of the verifiable audit chain.

Revocations & Tombstones

When you modify your identity permissions—such as unlinking a Google SSO provider or revoking a lost device passkey:

• The system publishes a cryptographically signed tombstone evolution frame (n \to n+1).
• This frame officially revokes that authority and unlinks the provider from server-side reverse lookup indices.

Content Takedowns & Full Account Erasure

1. Content & Asset Takedowns: Standalone content nodes and binary file payloads can be unlinked, de-indexed, or removed from server storage upon authorized request or valid legal takedown without compromising structural timeline history.
2. Complete Tenant Erasure: If you request complete account deletion, your entire tenant domain space (including all hosted keystones, delegate frames, and stored data) and reverse email index entries will be permanently purged and removed from server storage.
3. Local Device Data Control: You maintain full control over all data stored locally on your physical devices. You may clear your local cryptographic tokens, delegates, and cached workspace data at any time via the application settings or by clearing your browser's IndexedDB / local storage.

7. Security Architecture & Experimental Protocol Notice

Innovative & Experimental Nature

Identity Keystones, multi-pool challenge-response mechanisms, and decentralized sync delegates represent innovative, experimental cryptographic protocols. While we apply diligent best efforts in cryptanalysis and utilize industry-standard, proven cryptographic primitives (such as SHA-256, SHA-512, AES, and WebAuthn PRF), the composite architecture is actively evolving. Users should evaluate this platform understanding its experimental research nature.

Conventional Security Foundations

All communications, API endpoints, and authentication exchanges between your client devices and our server infrastructure operate strictly over industry-standard TLS 1.3 / HTTPS encryption. Server-side data isolation, atomic file indexing, and timing side-channel protections are implemented following standard enterprise security practices.

8. Your Privacy Rights (Texas TDPSA & US State Privacy Laws)

If you are a resident of Texas (governed by the Texas Data Privacy and Security Act - TDPSA) or other jurisdictions with applicable privacy legislation, you have the following rights regarding your personal data:

• Right to Know / Access: You have the right to confirm whether we process your personal data and to access such data.
• Right to Correct: You have the right to correct inaccuracies in your personal data.
• Right to Delete: You have the right to request deletion of personal data provided by or obtained about you.
• Right to Data Portability: You have the right to obtain a copy of your personal data in a portable and readily usable format.
• Right to Opt-Out of Sale / Targeted Advertising: We do not sell your personal data or process it for targeted advertising, so no opt-out is necessary.
• Right to Non-Discrimination: We will never discriminate against you, deny services, or alter pricing for exercising your privacy rights.

How to Exercise Your Rights

To submit a privacy inquiry, request data export, or request permanent deletion of your tenant domain space, please contact us using the information in Section 9 below. We will verify your identity (using your registered email or cryptographic keystone proof) and respond within the statutory timeframe (typically 45 days).

9. Contact Information & Policy Updates

Contact Us

If you have questions, comments, or requests regarding this Privacy Policy or our data handling practices, please reach out to us:

• Open-Source Packages: Published on npm under the @ibgib scope.
• Email / Privacy Inquiries: ibgib.info@gmail.com

Updates to This Policy

We may update this Privacy Policy from time to time to reflect architectural advancements, legal requirements, or operational changes. When changes are made, the "Last Updated" date at the top of this document will be updated. We encourage you to review this policy periodically.