SEC filingsOct 12, 2026 to Oct 19, 2026: insiders reported 840 purchases and sales across 212 companies.840 insider purchases and sales in 7 daysSee the filings →
HornScout

Privacy

Privacy baseline for the controlled beta.

This page explains, in practical terms, the personal data HornScout may process while operating the beta. It is a provisional baseline pending legal review before broader launch.

Last updated: 5 October 2026

Provisional privacy notice

The legal bases, provider list, transfer safeguards and cookie policy must be reviewed by legal counsel before broader availability.

Data controller

The controller of your personal data in HornScout is HornScout, S.L., the company that operates the service: Tax ID (NIF) B88930938, registered office at Alameda Mazarredo 25 - 1, 48009 Bilbao (Bizkaia), Spain, registered with the Commercial Registry of Bizkaia, sheet BI-88431. Contact: the privacy channel listed above.

Data we may process

Depending on your interaction with HornScout, we may process account email, invitation/access status, authentication/session data, language and preferences, product usage, technical logs, support communications and beta feedback.

  • Account and invitation data
  • Product preferences and workflow state
  • Technical logs for security and stability
  • Communications and feedback
  • Cookies or session storage needed for login and language
  • Product usage records — which product pages you visit (home and symbol views) and your last activity time, linked to your account; used to operate and improve the beta, stored in our own database and never shared with third parties. Kept at most for the duration of the beta; afterwards they are anonymously aggregated or deleted

Purposes

Data is used to provide and secure the service, manage controlled access, support users, improve product quality, investigate incidents, comply with legal obligations and communicate beta or account information.

Legal bases to be confirmed

The expected legal bases may include performance of a contract or pre-contractual relationship, legitimate interest in operating and securing the beta, consent where required and compliance with legal obligations. This framing is pending legal review.

Third-party data from public registers

Besides your own data, HornScout publishes information from official registers that names people: the officers, directors and major shareholders of the listed companies you can browse here. It comes from the filings those people are required by law to submit to the U.S. Securities and Exchange Commission, and we show it as the register records it, with a link to the original document.

We do not obtain it from the person concerned but from the public register, which is why we set it out here. It always concerns how someone acted in a professional role at a listed company, never their private life. We do not build profiles of these individuals and we take no automated decisions about them: the product's analysis is about the company, not about whoever signed the filing.

The purpose is to report facts that the law requires to be disclosed. The expected legal basis is our legitimate interest in informing readers from a register that is public by legal mandate, weighed against the rights of the person named. That assessment, like the rest of this notice, is pending legal review.

Anyone named can object to the processing on grounds relating to their particular situation, or ask for access, rectification or erasure, by writing to the privacy channel. No HornScout account is needed — identifying the filing or the company is enough. One limit we would rather state than leave you to discover: we are not the source. The original filing remains public at the SEC, and that part is outside our hands.

  • Forms 3, 4 and 5 — insider transactions and holdings
  • Form 144 — announced intent to sell
  • Schedules 13D and 13G — declared major stakes

Recipients and processors

Data may be handled by technical service providers that support hosting, authentication, email, logs, analytics or security. For page-view analytics we use Cloudflare Web Analytics — a service that sets no cookies and does not track individual users across sites, and that records only aggregate page views and page-load timings (no advertising profiles). It is not loaded on pages whose address carries an access code or token. The final provider list and data-processing terms must be confirmed before launch.

Error monitoring is provided by a third-party service (Sentry, EU region) to detect and fix faults you may encounter. Error reports are scrubbed of credentials, tokens and personal data before they are sent, identify users only by a pseudonymous account key, and never include session recordings. The processing basis is our legitimate interest in operating and securing the beta.

Rights

Where applicable, users may request access, rectification, erasure, objection, restriction and portability. During beta, send requests to the privacy contact channel with the account email needed to identify the request. People named in public filings do not need an account: their route is described under third-party data above.

Cookies, sessions and international transfers

HornScout may use cookies or similar storage for authentication, language and security. Our page-view analytics (Cloudflare Web Analytics) is cookieless and sets no analytics or advertising cookies. A specific cookie policy and international transfer assessment will be prepared if the final provider stack requires it.

The home page also counts, per day, which steps of the demo and which company previews are used. These are plain daily totals: no cookies, no record per visit, and no data about who visits (not their address, browser or account).

Security and retention

HornScout applies reasonable technical and organizational measures for a pre-launch product. Data is kept only as long as needed for the beta, support, security, legal obligations or legitimate product operation, subject to final policy review.

Privacy contact

Ask about beta data or exercise a privacy right.

Use a clear subject and include the account email connected to the request so we can identify it safely.

Do not include unnecessary sensitive information in the request.