Privacy / Public website

Minimal collection. Clear purpose.

This notice explains the information handled when you use the Stone Signal Labs public website or submit a briefing request. It was last updated August 17, 2026.

Public-site boundary

Only send what is needed to start the conversation.

Browsing public pages does not require an account. A briefing request is optional and should contain only professional contact information and a high-level description of the decision or authorized work you want to discuss.

Stone Signal Labs does not sell public-site inquiry information or use it for cross-site advertising.

01

Information you submit

The briefing form accepts your name, organization, business email, area of interest, and the context you choose to provide. Please do not submit passwords, credentials, client data, exploit material, or other secrets.

02

Why it is used

Submitted information is used only to evaluate and respond to the requested briefing, product discussion, authorized assessment inquiry, or security report.

03

Delivery and abuse protection

Cloudflare Turnstile processes a challenge token and limited request metadata for abuse prevention. Resend delivers the request to the designated Stone Signal Labs mailbox. Those providers process data under their own service terms.

04

Storage and logging

The website does not maintain a briefing-request database and routine application logs exclude form contents. The delivered message remains subject to mailbox retention, access control, legal obligations, and documented deletion procedures.

05

Portal separation

The authenticated RookHaven Portal is a separate product service with its own customer agreement, access controls, audit requirements, and operational data-handling terms. This notice covers only the public Stone Signal Labs website.

06

Your choices

You may request access, correction, or deletion of public-site inquiry information by using the briefing form. Identity and applicable legal or security-retention requirements may need to be verified before a request is completed.

Questions and requests

Use the protected briefing channel.

Select the privacy or security-report topic and avoid including sensitive technical evidence until a protected follow-up channel has been established.

Prepare a request