Legal & trust
Security
Local research. Protected credentials. Explicit approval before external changes.
Last updated 3 November 2026
The local boundary
The desktop UI, CLI and local MCP interface share the local service. Research is stored in SQLite on your computer; that database is not itself end-to-end encrypted. Protect your account, disk and backups. The development HTTP adapter listens on loopback and checks the host, origin and client header before accepting API requests. Do not expose it on a public interface.
Credentials and store access
App Store Connect key material is managed in the desktop main process using Electron safeStorage and a separate protected credential file. The research database contains connection metadata, not the private key. Saving credentials is unavailable through the ordinary browser preview and agent research tools. Operating-system protection must be available; keep your device secure and use least-privilege store keys.
Plans and integrations
Listing plans show changes for review. Creating or exporting a plan does not mean it has been published to a store. Grant agents only the access they need. Never place keys in keywords, prompts, URLs, screenshots or support reports. Revocation and account controls at Apple remain important even after disconnecting locally.
Hosted features and assurance
The configured R2 bucket is private; D1 and R2 use EU jurisdiction. Cloud customer sync, cloud credential custody, hosted AI, Paywalls event intake and continuous background-helper operation remain unfinished. We do not claim independent security certification, a completed penetration test or verified end-to-end sync encryption for this build.
Responsible disclosure
Email support@sansavision.com with “Sansora security report” in the subject. Describe the affected version, reproducible steps and likely impact, using a disposable workspace where possible. Do not include live keys, access other people’s data or degrade the service. Coordinate further testing with us. This is a disclosure channel, not a promise of a bounty. Our security.txt publishes the contact.