Privacy
Local-first, honest about scope.
Where analysis is designed to happen, what optional features change, and what local-first does not promise.
Principle: local-first security analysis
Silent Tears is designed around local-first analysis. The intention is that the analysis of your machine happens on your machine, rather than by shipping your data to a service.
This page describes that design as it is documented. It is a clear, scoped explanation, not legal advice and not a substitute for a formal privacy policy.
AEGIS processing boundary
The documented AEGIS design does not send telemetry to a cloud AI API and does not perform remote reputation lookups. AEGIS reads this machine's telemetry through a gated set of read-only tools.
The optional language model is intended to run locally through Ollama on 127.0.0.1 when it is enabled and configured. It may narrate an already-decided report or select one read-only tool, within documented constraints.
Optional integrations
Some features outside the documented AEGIS workflow are optional and behave differently. When such a feature is enabled and configured, it may transmit information to the relevant external service.
For example, optional notification channels can send information to an external provider when you switch them on. These integrations are separate from AEGIS and are only active if you enable them.
Data on this website
This website is a static-first marketing and documentation site. It includes no analytics, no advertising trackers, no marketing pixels, no forms, and no visitor accounts.
It does not avoid the fact that a hosting platform processes ordinary access logs as part of serving any website. Where deployment defaults affect logging, that limitation should be described accurately rather than denied.
Your control
Local application configuration and optional features determine behaviour. If you do not enable an optional integration, it does not run. Settings that affect monitoring are yours to review and change.
Limits of local-first design
A local-first design does not make an application immune to malware that is already running with your privileges. It also does not guarantee that all data stays local under every optional configuration.
Local-first describes where analysis is designed to happen. It is not a claim of invulnerability or of absolute data containment under all settings.
Contact & data requests
No privacy contact destination has been published yet, so none is shown here. This site does not invent a contact address.
No framework claims