Privacy Policy
Privacy Policy v1.1 — Last updated: April 10, 2026
1. Data Handled by SummerEyes
Submitted Data
SummerEyes functions as a formal reasoning engine that processes Claims, Evidence, and Actors you submit for mathematically grounded analysis. The SummerEyes MCP and API are designed to process this data ephemerally and do not hold submitted data after processing is complete. We do not store the data you submit for long-term retention.
Authentication Data
All authentication data, including user identity and JSON Web Tokens (JWTs), is held and managed by a third-party authentication provider, such as Clerk.
Investigation Sessions
When you create an investigation session, SummerEyes stores the investigation data you provide — including claims, evidence, actors, and analysis results — in our database so you can return to it, refine it, and re-analyze over time. Session data is associated with your account and retained until you delete it or until the session expires after 365 days of inactivity. You can delete any session at any time through the API or MCP tools.
Saved Investigations and API Keys
If you save an investigation draft or create an API key, this data is stored on our servers and associated with your account. Saved drafts contain only the investigation input you composed — not analysis results. You can delete saved investigations and revoke API keys at any time from the dashboard.
Operational Data
We collect and retain limited operational data, such as access logs, which are necessary for diagnosis, performance monitoring, and service stability.
2. Data Deletion and Backups
Deletion
When you delete an investigation session, saved investigation, or API key, the data is removed from our production database immediately.
Database Backups
Our database is backed up daily for disaster recovery purposes. Deleted data may persist in backup snapshots for up to 30 days after deletion. Backups are stored in access-controlled cloud storage and are used solely for service restoration in the event of a system failure. Backup data is not accessed for any other purpose and is automatically purged as backup snapshots expire.
3. Data Visibility and Diagnostics
Data Access
The SummerEyes team does not access the content of customer data submitted for analysis during normal operation.
Diagnostic and Debugging Access
Data submitted for analysis will only be visible to the SummerEyes team if a customer explicitly grants permission for diagnostic and debugging purposes related to a specific support request or service issue. In such cases, access is granted temporarily to resolve the issue.
Questions about this Privacy Policy? Contact us at paul@upside-down-research.com.