Privacy boundary
What WaitEarn is designed to collect
If WaitEarn cannot explain a data field publicly in one sentence, it should not collect it.
WaitEarn version check, concept preview
waitearn --version
waitearn/0.1.0 · concept preview
Every collected field is explainable in one sentence.
What we send
| Field | Proposed purpose |
|---|---|
| Event ID | Prevent duplicate counting. |
| User/account ID | Attribute settings and any future payout eligibility. |
| CLI version | Debug compatibility. |
| Shell family | Support installation issues. |
| OS family | Support compatibility. |
| Command category | Describe broad inventory without raw command content. |
| Duration bucket | Evaluate wait length without precise timing. |
| Visibility time | Evaluate whether a card was visible; re-checked server-side. |
| Campaign ID | Attribute proposed sponsor delivery. |
| Click event | Prepare aggregate interaction reporting. |
| Fraud signals | Prevent fake impression farming. |
Proposed event fields and their purpose.
- Field
- Event ID
- Proposed purpose
- Prevent duplicate counting.
- Field
- User/account ID
- Proposed purpose
- Attribute settings and any future payout eligibility.
- Field
- CLI version
- Proposed purpose
- Debug compatibility.
- Field
- Shell family
- Proposed purpose
- Support installation issues.
- Field
- OS family
- Proposed purpose
- Support compatibility.
- Field
- Command category
- Proposed purpose
- Describe broad inventory without raw command content.
- Field
- Duration bucket
- Proposed purpose
- Evaluate wait length without precise timing.
- Field
- Visibility time
- Proposed purpose
- Evaluate whether a card was visible; re-checked server-side.
- Field
- Campaign ID
- Proposed purpose
- Attribute proposed sponsor delivery.
- Field
- Click event
- Proposed purpose
- Prepare aggregate interaction reporting.
- Field
- Fraud signals
- Proposed purpose
- Prevent fake impression farming.
What we never send
Local only
None of these items are ever sent. They stay on your machine, full stop.
- Source code and source files
- Raw command text
- Shell history
- Terminal output
- Prompts and AI-agent messages
- Secrets, environment variables, credentials, and tokens
- Project paths and repository names
- Git remotes
Planned checks before an impression can qualify
- The command passes the configured minimum wait threshold.
- The sponsor card meets the configured visible-time threshold.
- The event comes from an interactive user session rather than obvious automation.
- The event does not show impossible volume or other abuse signals.
- The campaign is active and eligible for the relevant cohort.
Final thresholds are not public commitments. Qualification remains backend-authoritative.
Live platform transparency
Metrics will populate after launch from the backend that processes events. Sponsors see campaign-level aggregates, never individual developer activity.
- Qualified impressions
- Pending
- Visibility rate
- Pending
- Active campaigns
- Pending
- Day-7 retention
- Pending
- Reconciliation
- Pending
- Developer accounts
- Pending
Local controls in the current CLI
- waitearn pause
- pauses sponsor cards for the next invocation.
- waitearn resume
- resumes cards after a pause.
- waitearn off
- disables WaitEarn locally.
- waitearn exclude <path>
- excludes a path from card display.
- Any key
- dismisses a displayed sponsor card.
Your data rights are part of the design
- Access
- You will be able to see what is associated with your account.
- Export
- You will be able to take your data with you in a portable form.
- Delete
- You will be able to request erasure of your account and the data tied to it.
Comfortable with the boundary?
Join the waitlist to hear when WaitEarn has a reviewed next step to share.
Join the waitlist