Privacy & Telemetry Policy
CLIMoney is engineered to run securely in the background. We log compiler wait metrics and process latency to verify attention yields—without ever scanning your code.
Zero Code Scanning
We do not index, view, parse, or transmit code files, repository trees, git logs, or environment parameters.
Metadata-Based Telemetry
Only compiler wait-times, Reasoning latency metrics, window focuses, and keystroke frequencies are checked.
Razorpay & Supabase Guard
MFA-backed authentication, strict RLS isolation rules, and Razorpay payouts process all account data securely.
Telemetry & Active Waiting Metrics
CLIMoney is designed to run in background telemetry mode. To calculate your developer yield fairly, our local background daemons and editor extensions track specific execution signatures.
- Process execution state checks (detecting compile cycles and wait intervals).
- Window focus state logs (Proof-of-Attention to ensure active presence).
- Keystroke rate telemetry evaluated client-side to filter bot/loop activity.
- Reasoning model latency tracking (timing duration parameters in seconds).
The Zero-Access Pledge (Code Privacy)
We enforce a strict code-level privacy sandbox. Because CLIMoney is built for developers, we treat your codebase as entirely confidential.
- We NEVER scan, compile, parse, index, or upload your proprietary source files.
- We NEVER access, read, or store environment variables or local credentials.
- We NEVER view local database schemas, local ports, or git history records.
- All terminal commands are proxied locally, maintaining full workspace integrity.
Authentication & Supabase Security
Your account credentials, sync logs, and accumulated balance details are kept isolated using Supabase database policies.
- All database records are guarded by strict Supabase Row Level Security (RLS) layers.
- Authentication is delegated entirely to Supabase Auth protocols with secure MFA signatures.
- Your unique VS Code / IDE sync tokens are cryptographic keys that you can cycle instantly.
- We log editor session connections with machine IDs, showing them on your Hub console.
Razorpay & Financial Integrity
Financial transactions, payout requests, and ad campaign bookings are securely processed via Razorpay's financial infrastructure.
- Developer payouts are processed via Razorpay directly to your linked bank account.
- Advertiser campaign budgets are handled using Razorpay payment pipelines.
- No credit card or banking routing details are processed or stored on our servers.
- Ledger audit trails are logged transparently and mapped to your Supabase UUID.
Advertiser Disclosures & CPM Verification
Sponsors are whitelisted to guarantee developers only view high-value software tools and cloud infrastructure assets.
- Sponsors receive aggregate statistics (e.g. view counts, click counts, avg. reasoning wait).
- Individual developer details, code signatures, or email identities are NEVER shared.
- Proof-of-Attention logs are verified through our platform before advertiser budgets debited.
- Ad creative placements can be toggled to video, banner, or typing challenge modes.
Developer Data Control & Deletion
We put developers in absolute control of their local editor sessions and account details. You are never locked in.
- Review and disconnect active IDE editor links instantly on your dashboard page.
- Export your full ledger transaction audit trails in standard formats.
- Request complete account deletion, removing Supabase profiles and ledger records.
- The CLI wrapper is open-source, allowing you to review our telemetry implementation.
Developer Trust Console
CLIMoney believes trust is built on visibility. If you have questions about reasoning latency telemetry, Razorpay setups, or want to audit the client-side wrappers, drop our team a message.