Pusat Ketelusan

Lima perkara yang anda boleh sahkan dalam 60 saat

• Sifar data pada pelayan saya. Habis cerita. (Lihat "Subprosesor" — hanya Apple menyentuh teks tersulit, dan hanya kerana anda memilih penyegerakan iCloud.)
• Sifar analitik, sifar SDK pengiklanan, sifar perkhidmatan laporan ralat. (Lihat senarai Subprosesor lengkap di bawah.)
• Log insiden keselamatan awam. Kini kosong. (Lihat "Insiden" di bawah.)
• Roadmap dengan tarikh. Teras kripto sumber terbuka + audit bebas dikomitkan untuk 2026. (Lihat "Roadmap" di bawah.)
• Laluan pengesahan bebas. White paper + GitHub + e-mel juruaudit — sahkan setiap tuntutan terhadap sumbernya. (Lihat "Sahkan" di bawah.)

Data processors (full list)

Below is the complete list of every entity that processes your data on my behalf. This list is intentionally short.

• Apple Inc.: Cupertino, California, USA. Role: data processor for iCloud Keychain sync, CloudKit Private Database sync, StoreKit subscription handling. Data handled: AES-256-GCM ciphertext only (Apple cannot decrypt). Privacy contact: [email protected] / apple.com/privacy. Legal mechanism for EU/UK transfers: EU-US DPF + SCCs Module 2.
• Have I Been Pwned (haveibeenpwned.com): Operated by Troy Hunt. Role: optional breach detection (only if user enables). Data sent: first 5 characters of a SHA-1 hash of a password (k-anonymity). The actual password never leaves the device. No personal identifier is sent.
• (That's it.): There is no analytics provider, no advertising network, no error reporting service, no marketing automation, no email service, no chat widget, no third-party SDK. If a new subprocessor is ever added, this page will be updated and material changes will trigger an in-app notice.

Security incident log

By architecture, I have no plaintext access to your vault data — which materially limits the scope of any plausible breach to my own infrastructure (e.g., a marketing database compromise). If a personal data breach occurs, I commit to: (1) notify the relevant supervisory authority within 72 hours of becoming aware (GDPR Art. 33 / PIPL Art. 57); (2) notify affected users without undue delay (GDPR Art. 34 / CCPA § 1798.82); (3) post a public notice here.

Current status: 0 incidents: No security incidents to report at this time. This page is updated whenever the status changes; previous incidents (if any) remain visible for transparency.

Public roadmap

Trust requires concrete dates, not vague promises. Below is what I have committed to deliver.

• Open-source the crypto core (Q3 2026): The Argon2id key derivation, HKDF key hierarchy, and AES-256-GCM field encryption code will be published to GitHub under MIT license. The non-crypto UI / business logic remains closed source for now. Follow @ByteGuardApp on GitHub to be notified.
• Independent third-party security audit (Q4 2026): Targeting one of: Trail of Bits, Cure53, or Doyensec. Scope: crypto core + Keychain integration + iCloud sync + AutoFill extension. Final report will be published in full at /security/audit-2026.
• Bug Bounty program (after audit): Once the audit is complete, a bug bounty program will be launched on HackerOne or Intigriti. Initial scope: encryption / authentication flows. Minimum reward: $100 USD.
• SOC 2 Type II self-attestation page: While I do not have a formal SOC 2 audit (small-scale processor), I will publish a SOC 2-aligned self-attestation page mapping the five trust principles (Security, Availability, Processing Integrity, Confidentiality, Privacy) to the actual implementation.

How to verify any claim independently

Trust me less, verify more. Every architectural claim on this site can be cross-checked against:

• The Security Whitepaper at /whitepaper — every cryptographic decision documented in formal spec form, with parameters, threat model, and references.
• The GitHub repo (after Q3 2026) — read the Argon2id parameters, the AES-256-GCM IV handling, the BIP39 entropy source. Verify the spec matches the source.
• The /security key derivation diagram — actual flow inside the app, not a marketing diagram. Compare it with the white paper.
• Email me a specific question with the line of source you can't make sense of: [email protected]. I respond within 7 days. (If I don't, that itself is a signal.)
• After Q4 2026: read the third-party audit report at /security/audit-2026.

Contact channels

Different concerns reach me through different addresses. I aim to respond within stated SLAs.

• General privacy / data subject requests: [email protected] · 30 days SLA (GDPR Art. 12(3)) · 15 working days (PIPL Art. 50) · 45 days (CCPA / CPRA, extendable).
• Security vulnerability reports: [email protected] (subject: [SECURITY]) · acknowledged within 48 hours · responsible disclosure preferred. After Q4 2026 a HackerOne / Intigriti channel will replace this.
• B2B / DPA requests (Data Processing Agreement): [email protected] (subject: [DPA REQUEST]) · I do not have a pre-signed DPA template (small-scale, no enterprise customers yet); for now, the GDPR Art. 28(3) requirements are met via the published Privacy Policy + this Transparency page. Custom DPA negotiation possible for committed enterprise pilots.
• Press / media inquiries: [email protected] (subject: [PRESS]) · public information only — no comment on individual users or accounts under any circumstances.
• Legal supervisory authority complaints: EU/UK: your national DPA (ICO, CNIL, BfDI, IDPC, etc.). Mainland China: Cyberspace Administration of China (CAC) or local cyberspace authority. California: California Attorney General. I will cooperate with any lawful inquiry.