CONTACT REQUESTS
Pilot application privacy
This page describes supplier and buyer pilot contact requests, together with supplier-workspace sign-in. Source-data processing requires a separate scope and agreement.
What the contact form collects
Loomwell stores your email, supplier or buyer role, request identifier, contact consent and submission time. Optional information includes your name, company, website, job title, workflow interests, product or logging stack, data-location categories, session or trace volume range, retained feedback or outcome categories, intended use and business summary.
Why we collect it
We use this information to assess a possible pilot and contact you about your request. Submitting authorizes this contact-request processing; it does not authorize source access, model training, data licensing or a paid agreement.
Who can access it
Loomwell operators review requests through the private operator service. Service providers supporting hosting and storage process request information to operate the service. Contact requests are not published or included in dataset or environment releases.
If operator signup alerts are enabled, the email provider processes an alert containing the request role and an application reference and review link. The automated alert omits your submitted contact details and business summary.
Keep source material out
The contact form is for business summaries and provides no finance source-upload channel. Do not include client names, deal documents, other people’s personal information, credentials, confidential records or material nonpublic information. Any source-informed work needs a separately agreed scope, permissions, privacy review, retention plan and transfer channel. Synthetic reconstruction does not automatically remove sensitive information or establish permission.
Supplier sign-in
If you use GitHub sign-in, we store your GitHub user ID and username and any supplier account you explicitly link with an approved access key. We do not request repository access or retain GitHub access tokens. Browser sessions use an HTTP-only cookie; the server stores a hash and expiry rather than your session token or raw supplier key. Sessions expire after seven days by default. Sign out on shared devices and ask your Loomwell contact to remove a sign-in identity or supplier link.
Retention and your choices
Contact requests are retained for assessment and follow-up without automatic expiry. Deletion is operator-assisted. You may withdraw contact consent or request access, correction or deletion; ask us to confirm the scope and timing, including any backup or required record retention.
For an access, correction, or deletion request, reply to the Loomwell representative who contacts you. You can also submit a contact request noting the privacy request in the business-context field.