Waspen is built to keep monitoring local.
Waspen is a desktop monitoring app from AlphaBytez LLC. Its default posture is simple: your Waspers, snapshots, incidents, Eyes captures, AI prompts, and configuration stay on your machine unless you deliberately connect an external service or send information to support.
Short Version
The important bits before the details.
No app telemetry
Waspen does not include analytics, advertising trackers, or background product telemetry in the desktop app.
Local by default
Monitoring configuration, snapshots, screenshots, incidents, local AI prompts, and App Lock data are stored locally unless you choose otherwise.
You control integrations
Data only leaves Waspen when you configure external AI providers, webhooks, Waggles, server connectors, support exports, or store/billing flows.
Information Waspen Stores Locally
Waspen may store the following on your device so the app can monitor systems and show history:
- Wasper, Rule, Job, Eyes, Advisor, AI provider, Waggles, connector, and app preference configuration.
- Snapshots, incident timelines, evidence bundles, screenshots, DOM text, response metadata, logs you choose to monitor, and local summaries.
- Local AI prompts and responses generated through configured local models such as Ollama.
- App Lock settings, passphrase verification data, passkey enrollment state, and related local security preferences.
- License files, entitlement state, or store-related local records needed to unlock features.
This local data is not sent to AlphaBytez by default.
When Data May Leave Your Device
Waspen is designed around user-controlled egress. Data may leave your device only when you choose actions or settings that require it, including:
- External AI providers: prompts, evidence summaries, screenshots, or context may be sent to the endpoint you configure.
- Webhooks and Waggles: alert content, incident metadata, approval details, or workflow output may be sent to destinations you configure.
- Waspen-Server or enterprise connectors: monitored summaries or connector payloads may be sent to a server you configure or that your organization manages.
- Support: information you email or attach, including diagnostics exports, screenshots, logs, or descriptions, is received by AlphaBytez for support handling.
- Store and billing platforms: Apple, Microsoft, payment processors, or commerce systems may process purchase, subscription, receipt, and account information under their own policies.
- Website use: visiting the Waspen website may create ordinary hosting logs, such as IP address, user agent, request path, and timestamp, depending on the hosting provider.
Support and Diagnostics
If you contact support, AlphaBytez uses the information you provide to investigate the issue, respond to you, improve Waspen, and maintain support records. Diagnostics exports, screenshots, and logs can contain sensitive details, so review attachments before sending them.
Please do not send passwords, API keys, license files, private URLs, personal data, or regulated data unless AlphaBytez has explicitly requested it and you understand the risk.
AI and Model Providers
Waspen can use local AI models and user-configured external AI endpoints. Local Ollama-style usage stays on your machine unless your local model server or network setup routes it elsewhere. External AI providers receive whatever prompt, metadata, screenshots, or context you configure Waspen to send. Review the provider's own privacy and data-use terms before enabling external AI.
Data Sharing
AlphaBytez does not sell Waspen user data. AlphaBytez may share information only when needed to provide support, operate the website or store/billing paths, comply with law, protect rights and security, or work with service providers that help operate AlphaBytez systems.
Retention
Local Waspen data remains on your device until you delete it, change retention settings, purge history, uninstall the app, or remove the app data directory. Support emails and support records may be retained for business, security, and troubleshooting purposes unless deletion is requested and AlphaBytez is legally able to delete them.
Your Choices
- Use Waspen without external AI providers or webhooks for the most local-first setup.
- Review and disable integrations before enabling Jobs, Waggles, server connectors, or workflows that send data outward.
- Use backup, diagnostics, purge, retention, and uninstall controls to manage local data.
- Email support to request access, correction, or deletion of support records associated with your email address.
Children's Privacy
Waspen is not directed to children and is intended for adults, IT operators, developers, and organizations monitoring systems they control.
Changes
AlphaBytez may update this policy as Waspen evolves, including for store distribution, licensing, enterprise features, or new integrations. The effective date will be updated when material changes are made.
Contact
Questions about privacy or data handling can be sent to olliec@alphabytez.dev.