Eyes On Your AI Privacy Notice
Previously presented as AgentLedger. Storm And Me LLC remains the operator.
Updated: November 3, 2026. Operator: Storm And Me LLC. Contact: hello@stormandmeofficial.com.
Information we process
We process account and workspace information, salted password-verification data, session records, agent configuration, policy scopes, API-key hashes, authorization decisions, alerts, and audit-event data submitted by customers or their integrations. Audit-event details may contain personal or sensitive information if customers choose to send it.
Connected telemetry
Connected sources can submit supported operational metadata such as source identifiers, trace and span identifiers, timestamps, service and resource attributes, execution status, and source-reported inventory. This describes activity reported by connected sources, not device-wide discovery of every AI tool.
Supported telemetry ingestion filters prompt and response content rather than intentionally retaining those payloads. Other customer-supplied metadata may still contain personal information. Separate audit-event fields may contain details customers choose to submit. Do not send credentials, unnecessary personal information, or regulated data.
Early-access requests
We collect the name, email address, optional team or company, and use-case category supplied in access requests to review and respond to those requests, not to create subscriptions or charges. Unselected requests are removed from the active queue after 90 days. Copies may remain in encrypted recovery backups as described below. Contact us to request removal from the active queue sooner.
Billing
Stripe processes subscription billing. We store identifiers and subscription status needed to determine access. Card details are entered into Stripe-hosted Checkout rather than intentionally stored by Eyes On Your AI.
How we use information
We use information to operate accounts, evaluate configured policies, maintain audit and telemetry records, provide exports and reports, support subscriptions, prevent abuse, diagnose failures, recover data, and respond to support requests.
Service providers
Current providers include Railway for application hosting, Amazon Web Services S3 for recovery backups, Stripe for payments, and Resend for configured transactional email. Google sign-in, when enabled, also involves Google. Provider access is restricted to authorized operators. Contact us for current hosting-region information and contractual data-processing requirements before sending sensitive or regulated data.
Security and backups
We use authenticated access, salted password hashes, hashed API keys, Stripe webhook signature checks, audit-chain integrity checks, and encrypted backup workflows. No online service can guarantee absolute security. Historical records that cannot be cryptographically verified must not be represented as verified evidence.
Retention and deletion
Plan-specific capacity limits do not establish a fixed deletion schedule or promise unlimited retention. Contact us for account-data review, export, or deletion. Some records may need to be retained for security, billing, contractual, or legal reasons.
Recovery backups are separate from active records and may contain older account and audit data. The historical recovery archive currently has no automatic expiration schedule; we do not promise a fixed backup-deletion deadline. Removing active records does not immediately remove every historical backup version. Contact us about archive handling and applicable deletion obligations; restored records remain subject to those obligations.
Customer-controlled data
Customers must have authority to transmit information and configure integrations appropriately. Contact us about data-processing agreements or special retention requirements before relying on the service for those needs.
Changes
Material changes to this notice will be reflected by an updated date.