Privacy Notice
Version: 1.0. Effective date: October 14, 2026. Operator and privacy contact: DNL, sec@mindsle.com. The initial release is intended for adults in the United States.
Information and purposes
| Information | Processing and purpose |
|---|---|
| Account and sign-in | We store your verified email, account identifier and, for Google sign-in, the name and Google identifier returned by Google. Email sign-in, when enabled, sends the recipient address and one-time-code message through Resend. Verification challenges are hashed, time-limited and single-use. Codes are not stored as plaintext account passwords |
| Public filings and reports | SEC filings are fetched and parsed by the service. Parsed public source data and general reports generated from it may be cached across users. Private uploaded material and account identity are not placed in that shared source cache |
| Uploaded PDFs and private reports | Uploaded files, private reports and the questions stored with them are held on FilingMaster's service to fulfill your requests. An unmatched PDF is treated as an unverified private source, not as an authenticated official filing |
| Questions and answers | Desktop conversation history is stored locally. Questions, necessary filing excerpts and limited context are sent to the service and, for AI processing, through OpenRouter to the selected model provider. A mobile follow-up stores its question, task state and answer on the Relay so your explicitly selected desktop and phone can exchange them |
| Devices and pairing | We store persistent device identifiers, device names, online state, hashed capability credentials, pairing records and remote-task records. Short-lived QR codes identify a specific desktop; the phone asks you to confirm it. These records enforce authorization and prevent tasks moving to another computer without your choice |
| Usage and records | Analysis and question counts, followed companies, quota reset periods, estimated model costs, consent versions/hashes/times and feedback tickets support requested features, quotas and problem investigation. In-app tickets are not currently forwarded to a support team |
| Local credentials and preferences | User sign-in and device capability credentials use the product's OS-protected storage, including Keychain where supported. Appearance, language and local history are stored on your device. AI provider keys stay on the service and are not sent to clients |
| Connection and update metadata | SEC receives source-request network metadata and a product contact User-Agent. Cloudflare handles HTTPS traffic and the independent download source and can process IP addresses and request metadata. Desktop updates download an application package, not your financial reports |
This release does not collect payment-card information, enable advertising or sell account information or private report content. The optional diagnostics control does not currently enable a content-telemetry service. Operating systems and third-party services may process their own diagnostic or account information under their policies.
Recipients and location
We use Google for Google sign-in, Resend for enabled email-code delivery, OpenRouter and the selected model provider for AI requests, Cloudflare for network/download services, and the separately managed FilingMaster server for application data. Ordinary account, report and usage features use the API; only desktop Harness requests use the separate Relay. A selected computer and its owner can see the tasks sent to that computer.
Data is not guaranteed to be processed or stored only in the United States. Cloudflare operates a distributed network, and model processing depends on the provider selected for a request. Do not assume every provider offers zero retention or excludes training. Review the applicable OpenRouter privacy information and the selected provider's policy before sending confidential material. Google and Resend also process the information needed for their sign-in/delivery services under their own policies. Contact sec@mindsle.com for questions about this processing.
Access is limited to operating and securing the service, delivering your requests, addressing reported issues and complying with applicable legal obligations. Accepting the Terms is not permission for undisclosed marketing or unrelated content use. Do not upload sensitive personal or confidential business information without authority to transfer it to these services.
Retention and deletion
Account details, usage, follows, consent records, private reports and tickets remain associated with your account while it exists; individual reports can be deleted earlier. Pending verification challenges expire and cannot be used again. Public source data may remain cached independently of an account because it does not identify that account. Local history remains on a device until it is removed from that device.
Settings lets you delete individual reports or your account. Account deletion removes the associated account records, private reports, uploads, follows, usage, consents, feedback and Relay connections/tasks on the service and clears local history and sign-in credentials on the device performing deletion. A failed physical file deletion is registered for retry; the application reports pending cleanup rather than claiming the file is gone. An interrupted local deletion resumes at the next application start.
Deleting an account revokes access but does not remotely erase every offline computer, exported copy or user-created backup. Remove such copies from devices you control. The service cannot promise immediate deletion from independently operated providers' records. Any provider retention or legally required retention is subject to that provider's actual terms and applicable law, not a universal zero-retention guarantee.
Choices and requests
You can change local preferences, revoke a paired device, sign out, export consent records, delete reports or delete your account. Signing out does not delete service data. Revoking one desktop prevents new authorized work on that desktop and does not silently select another computer.
For access, correction, deletion, other applicable privacy rights, or a security concern, email sec@mindsle.com. We may ask for proportionate information to verify control of the affected account; do not send a sign-in code or identity document unless a justified secure process has been explained. Applicable statutory rights and complaint channels remain available. No specific response-time guarantee is made by this notice.
Security, children and changes
Controls include HTTPS, account authorization, isolated product data, protected device credentials, bounded uploads, redacted application logs and private-context separation. No system guarantees absolute security. This release is not intended for children or persons under 18. Report an underage account or security issue to sec@mindsle.com.
Material changes are versioned and presented in the application. Your consent record identifies the text and version you reviewed. A change does not authorize an undisclosed new use of your private content.