Last updated: November 12, 2026
Privacy Policy
How CreditKit processes developer workspace data, end-user wallet tokens, and privacy-preserving /24 IP subnet hashes without third-party tracking cookies.
1. Privacy-Preserving Anonymous Wallet Resolution
To allow software creators to offer instant free starter trials without forcing a registration wall—while preventing incognito tab abuse—CreditKit computes a one-way cryptographic device hash (anon_device_hash):
- IP Subnet Truncation (
/24IPv4 //48IPv6): CreditKit truncates the last octet of IPv4 addresses (e.g.,203.0.113.0/24) before hashing so full raw IP addresses are never persisted in wallet rows. - One-Way SHA-256 Hashing: The truncated subnet is combined with your
projectIdand non-invasive browser display parameters (screen resolution, timezone, hardware concurrency) via irreversibleSHA-256. - Signed First-Party Token (
ck_vt_...): CreditKit stores an HMAC-signed token inlocalStorageon the host application domain for0msbalance recognition. No third-party cross-site advertising cookies are used.
2. Developer-Provided Auth & Cross-Device Wallet Sync
CreditKit piggybacks directly off the host application's own authentication system. When a signed-in user is bound via data-user-id, CreditKit.identify({ userId, email }), or your backend CreditKitClient, their external user ID or email is linked to their project-scoped wallet_id so balances and subscriptions sync across devices.
Cross-device wallet binding is authorized via your server secret key (sk_live_...) or an HMAC-SHA256 X-CreditKit-Identity-Signature, preventing unauthorized wallet enumeration.
3. Payment Card Data (PCI-DSS Compliance)
CreditKit never collects, touches, or stores raw credit card numbers, CVVs, or Apple Pay tokens. All payment credentials are handled directly by Stripe (checkout.stripe.com), a PCI-DSS Level 1 certified processor.
4. Infrastructure Subprocessors
| Subprocessor | Role | Data Scope |
|---|---|---|
| Cloud Hosting & Managed US PostgreSQL | Application runtime, FIFO lots, holds & audit trail | wallet_id, user_id, email, /24 hash |
| Stripe Inc. | Checkout & Connect payouts | Payment method, billing email |
| Resend Inc. | 6-digit OTP & password reset emails | Email, 6-digit OTP |
| Google LLC / GitHub Inc. (Optional) | Developer Console OAuth sign-in | Developer name, email (when used) |
5. Data Retention, Export & GDPR / CCPA Deletion
Developers can view, export (CSV), deduct, or revoke any end-user wallet from the User Wallets & CRM tab of the CreditKit Console, or delete an entire project (which cascades deletion across all associated wallets, credit lots, holds, and telemetry events) from the SDK, API Keys & Webhooks tab. For privacy inquiries or GDPR / CCPA data requests, email support@creditkit.dev.