Contact
Contact, support and product feedback.
For beta access, use Request access so the request is captured with plan interest, profile and consent. Contact stays available for privacy, legal, support, feedback and beta questions.
Last updated: 16 May 2026
No regulated advice channel
Do not send requests for personalized investment advice, execution instructions or portfolio decisions. HornScout can answer product, access, privacy and data-quality questions during beta.
Beta access
Use the Request access form for beta access so we capture the request cleanly and avoid unnecessary personal data.
- Request access form
- Invitation-code questions
- No phone or financial details needed
Beta questions
Ask about product scope, availability, pricing-readiness or how a public page maps to the private workspace.
- Product workflow
- Access status
- Beta expectations
Technical incidents
For login, broken routes or visual bugs, include the URL, browser/device and approximate time.
- Route or screenshot
- Browser/device
- What changed after refresh
Data concerns
If something looks stale, incomplete or wrongly classified, share the ticker, region and page where you saw it.
- Ticker or exchange
- Observed issue
- Why it looks wrong
Privacy and rights
Use the same channel for access, correction, deletion, objection, limitation or portability requests while the formal privacy channel is finalized.
- Identify your account email
- State the right/request
- Do not send sensitive unnecessary data
Legal contact
Until the legal identity and dedicated channels are finalized, mark the subject clearly as legal/privacy so it can be handled separately.
- Subject prefix: Legal or Privacy
- Reason for contact
- Preferred reply email
Beta feedback
Tell us what happened and where.
Precise feedback helps improve the public pages, onboarding, data-quality notices and private research workflow.
Replies may not be immediate during beta.