Privacy & information handling
A deliberate boundary around your information.
This notice describes the public emiger website and its optional inquiry and educational briefing features. Last updated September 17, 2026.
01Privacy & information handling / 01
01The inquiry form requests contact and organization details, an audience selection, and an optional description of what you would like to discuss.
These details are used to understand and respond to your inquiry. When delivery is enabled, the form sends the inquiry through the configured email delivery provider, Resend. Provider acceptance confirms the submission was accepted for sending; it does not confirm arrival in an inbox or that someone has read it.
02Keep inquiries high level.
Do not include credentials, personal records, classified or controlled information, confidential documents, or detailed incident evidence. The public form is not a secure incident-reporting channel. Appropriate arrangements should be established before sensitive information is exchanged.
02Privacy & information handling / 02
How the educational AI briefing works.
01The interactive briefing uses selections from predefined options.
It does not ask you to upload documents or describe your private systems. When the live feature is configured and available, selected options and reviewed public-source material are sent to OpenAI to generate an educational response.
02The briefing cannot inspect your organization, access private accounts, or take actions on your behalf.
It is not a security assessment. Its source links come from a reviewed catalog. An unavailable live service is identified as unavailable; an illustrative scenario is not presented as a live result.
03OpenAI processes requests under the terms and data-handling arrangements applicable to emiger's configured API account.
This notice does not promise a particular model-provider retention period or zero retention.
03Privacy & information handling / 03
Operating the site responsibly.
01Hosting, delivery, and security services may process technical request information needed to operate the website and limit abuse.
Application code is designed not to log inquiry text, personal contact details, model inputs, or secrets. This does not mean that hosting and service providers process no technical metadata.
02When abuse protection is enabled, the application uses a keyed, daily-changing representation of a trusted network address for rate limits.
It does not save the raw address in that counter. Rate-limit records expire after two hours, and shared usage-budget records expire after 48 hours. These are technical controls, not storage of inquiry content.
03Optional website analytics use Vercel Analytics when enabled by the site operator.
Page URLs have their query strings removed before being sent through the site's analytics integration. The site does not intentionally include inquiry text, personal contact details, or generated briefing text in analytics events.
04Access to submitted inquiries should be limited to the people and service providers who need it to respond and operate the service.
This public site does not publish a fixed retention period for correspondence. Ask about the handling requirements relevant to your inquiry before sharing sensitive information.
04Privacy & information handling / 04
Questions about your information.
01Use the contact page to raise a privacy question or request concerning information you previously submitted.
Provide enough context to locate the inquiry without sending additional sensitive material. Availability of the contact service is shown on that page.
02External research links take you to third-party websites governed by their own practices.
This notice may be updated as the site and its services evolve; the date above identifies this version.