The short version
Scienter is self-hosted. Your data does not leave your machine except when you call a third-party provider, and the list of those calls is enumerable.What is stored, and where
What is deliberately not stored
API keys, in any recoverable form
Hashed, never encrypted. A design that can recover your key is a design that can leak it. There is no recovery path — reissue instead.
MCP tool arguments and responses
The call log hashes arguments and measures responses. It stores neither. You get auditability of what was called without a copy of what was asked.
Third-party data flows
The engine reads public market and chain data. Provider calls are the only egress:The intelligence layer never fetches paid providers on a read path. Benchmarking calls are made by the nightly runner, not by a user request, so a burst of API traffic cannot run up a provider bill through the read surface.
Personal data
Scienter processes wallet addresses and on-chain activity, which are public by construction. It does not require or collect names, emails, or payment details for its core function — there is no account system. Where an operator adds a workspace, member email addresses enter the workspace store. That store is on the operator’s infrastructure, and the operator is the controller for it.Retention
Retention is the operator’s decision, because the operator holds the disk. Nothing here expires state automatically. For a regulated deployment, set a retention policy onstate/ and the workspace store explicitly — the defaults keep everything.
Data subject requests
Since there is no vendor-held data pool, a data subject request lands entirely on the operator. See Compliance for the shape of the responsibility split.Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.