Website privacy notice

Data the website handles

Inquiry data

The inquiry form asks for a name, email address, focus area, and a message. Company or team name is optional. The site also uses a hidden spam-prevention field.

When the form uses the website inquiry endpoint, the submitted fields are stored in Google Cloud Firestore with the submission time, source, IP address, browser user-agent, and referring page if those request details are available. If an email-draft option is configured, it may be used instead of the endpoint or as a fallback after an endpoint error. In that case, the inquiry fields are also placed in the visitor’s email application. Depending on why an endpoint attempt failed, the endpoint may already have received the submitted data before the email draft opens.

Usage and event data

Website analytics is disabled by default. The site does not create an analytics session identifier or send usage events unless the operator explicitly enables analytics after approving the applicable legal basis, visitor controls, notice, and retention process.

If enabled, event records can include the event and label, page pathname (without its query string or page fragment), a randomly generated session identifier, limited event metadata, submission time, IP address, browser user-agent, and referrer. The session identifier is stored in browser session storage for the current browsing session. If Firebase Analytics is also configured, the site may send page and event information to Google Analytics. That service may use cookies or similar device identifiers under Google’s own terms and privacy documentation.

Why the data is used

• To receive, assess, respond to, and follow up on inquiries.
• To route operational notifications so an inquiry is not missed.
• To filter automated or abusive submissions.
• When analytics has been lawfully enabled, to understand site use, diagnose failures, and improve content and conversion paths.
• To protect the site and keep records needed for service security and operational accountability.

Storage and service providers

Inquiry records, and site-event records if analytics is enabled, are stored in Google Cloud Firestore. The website runs on Firebase services. Depending on the operator’s configuration, inquiry notifications may also be sent through an SMTP email provider and/or a Discord webhook. Those notifications can contain the submitted inquiry and related request metadata. Google Analytics may receive usage data only when analytics is explicitly enabled and its configuration is present.

These providers process data to supply hosting, storage, notification, and analytics functions. Their infrastructure may process data in countries other than the visitor’s own. The current site code does not provide an advertising-data sale or data-broker integration.

Retention

The current implementation does not enforce an automatic deletion period for inquiry or site-event records. Records may remain until they are manually deleted. No fixed retention promise is made here until the operator has adopted and implemented a verified retention schedule.

Choices and requests

Depending on the law that applies to a visitor, they may be able to request access, correction, deletion, restriction, or a copy of personal data, or object to certain uses. These rights and any exceptions depend on the applicable law; this notice does not claim a jurisdiction that has not been verified.

The currently published contact route is the inquiry form. When it is available, use it and state “privacy request” at the start of the message, along with enough information to locate the relevant record. Do not include sensitive information that is not needed for the request.

Security and updates

The site uses HTTPS and managed cloud services, but no internet or storage system can be guaranteed completely secure. This notice may change when the site’s data flows, service providers, controller details, or approved policies change. The review date above will be updated when material revisions are published.