EAINE website and selected-review privacy notice.

Selected-review applications are currently paused. The public site does not accept new review-application information while privacy, retention, abuse-prevention, deletion, and operational-response controls are being completed.

Website hosting and essential operational telemetry

The hosting and content-delivery service processes ordinary request metadata, such as IP address, browser or user-agent information, requested path, and security signals, to deliver and protect this site. Cloudflare may set the essential __cf_bm cookie for bot management. Cloudflare states that it expires after 30 minutes of continuous inactivity and is generated independently for each protected site. EAINE also uses identifier-free request IDs, aggregate response timing, and sanitised server-error events to operate and secure the site. Server-error events record only the request method, a broad route class, status, and a random request ID—not the URL, IP address, user agent, form content, identity, error message, or stack.

Optional Google Analytics on public pages

If a production Google Analytics 4 Measurement ID is configured, EAINE asks before loading the Google tag. Declining leaves the tag unloaded. Allowing analytics permits public-page views, three coarse journey-completion events, and sampled rounded performance timing. Advertising storage, advertising user data, personalisation, Google signals, and automatic page-view collection are disabled in the site configuration.

EAINE does not send protected reviewer routes, account identity, form content, assessment answers, maturity scores, scope labels, free-form text, URL query strings, error messages, or stack traces to Google Analytics. The site sends only the public origin and path for a page view. Protected routes have a stricter content-security policy that does not allow the Google tag or Analytics collection endpoints.

You can decline when first asked or change your decision at any time through Analytics settings in the footer. Turning analytics off updates consent, removes EAINE's first-party _ga cookies where present, and reloads the page so the optional tag is no longer active. The choice itself is stored only in the browser's local storage. Google describes its Analytics privacy controls and IP-address handling in its privacy safeguards documentation.

Interactive demonstration and self-assessment

The interactive EAINE demonstration and maturity self-assessment run locally in the browser. EAINE does not submit, persist, or receive the choices, scope label, scores, evidence-reference checkboxes, or generated action brief. A downloaded brief is created on the user's device. Do not enter confidential, regulated, client, credential, or unnecessary personal information into the optional scope label.

Public requests

The Start with EAINE form collects a request category, name, email, optional organisation, optional short note, the consent statement and version, routing destination, status, source, and timestamps. EAINE uses this information only to route, review, and respond to the request. It does not subscribe the person to marketing or grant membership, approval, or protected access.

Public requests are restricted to authorised operators and are automatically eligible for deletion after 180 days. A person can request earlier access, correction, or deletion through the confidential contact route. Do not submit confidential, regulated, credential, identity-document, or client information in the short note.

Public release and community update registration

The public updates form collects an email address, the selected update categories, the consent statement and version, the registration source, and registration/update times. It does not ask for a name, employer, role, phone number, profile, assessment result, or free-form message. Registration remains disabled in production until the launch owner explicitly activates the approved runtime control.

EAINE uses this information only to administer the requested release, article, and community updates. EAINE does not sell the address, use it for advertising, or treat registration as endorsement of the framework. Access is limited to the authorised operator responsible for public communications. Update emails must include an unsubscribe method before delivery is activated.

EAINE sends a transactional verification email through Azure Communication Services after a valid submission. The single-use link expires after 30 minutes; only a hash of the token, its delivery-operation reference, expiry, and use time are retained. Verifying this email activates only the selected updates and does not verify a customer or grant protected access.

A registration remains active until it is unsubscribed, deleted on request, or removed because the update service ends. The owner must review active records at least annually and delete records no longer needed for the selected purpose. Until a verified self-service unsubscribe link is delivered in each email, a person can request access, correction, or deletion through the confidential route described under Your choices.

Historical review package and protected assets

The frozen EAINE Founding Review Edition v0.9 is a historical reviewer package, not the active First Edition manuscript. It is not published as an anonymous public file on this site. Controlled delivery may require verified reviewer identity, an expiring grant, and an accountable download record as described in the reviewer access flow.

Customer-only publications, private previews, reviewer packages, or licensed assets may use trusted sign-in, a separately verified relationship, private storage, and accountable delivery. Those capabilities remain fail closed until their production controls are activated. Signing in or registering for updates does not create eligibility or communication permission.

Framework participation requests

A signed-in person can separately ask to be contacted about framework participation. EAINE records the exact purpose and consent statement independently from newsletter choices. A request records interest only; it is not membership, endorsement, certification, reviewer approval, or access to protected material.

See the Cloudflare cookie documentation for the provider's current technical description.

Information previously submitted

Earlier application versions requested a name, work email, role, industry, and proposed contribution. These records, if any, must remain restricted to review administration and must not be publicly displayed, sold, or used for advertising.

Limited reviewer programme

The prepared public flow collects a name, email, optional organisation, optional role and professional-profile URL, review focus, proposed contribution, and acceptance of the private-copy conditions. A short-lived email link verifies control of the address before EAINE manually reviews the request. Verification is not approval, endorsement, membership, or proof of professional standing. The new flow does not request a mobile number, WhatsApp permission, work-email proof, social sign-in, or identity document. Public intake remains disabled until its operational and privacy controls are explicitly activated.

If approved, EAINE records the decision, reviewer number, access deadline, and a purpose-bound digest of the personal delivery token. The raw token is sent by email and permits one personalized PDF download. EAINE records the delivery time and unique watermark identifier so misuse can be investigated. It does not use an IP address or browser fingerprint as the reviewer identity. A direct administrator invitation uses the same delivery records.

Use and sharing

Azure Communication Services is selected, but not yet activated, for production request-verification and reviewer-delivery email. Email engagement tracking is disabled for these transactional messages. Before public intake, this notice must record the final Microsoft/Azure role, every purpose, processing location or transfer basis, and applicable retention terms.

Do not send confidential, regulated, client, credential, source-code, or unnecessary personal information through public repository issues or discussions.

Retention

Existing application records must be reviewed and deleted or irreversibly anonymized no later than 180 days after collection, unless a participant relationship requires a documented longer period. The accountable owner must review retained records at least monthly while the intake remains paused.

The local implementation includes request-driven cleanup and a scheduled retention-sweep hook for inactive requests after 180 days, and removes expired verification and delivery grants with their application. A production schedule, monitoring alert, and deletion test must be configured before activation. An applicant can also permanently request deletion through the confidential contact route. Deletion immediately ends reviewer access, subject to any documented legal or security retention requirement.

Your choices

Participation is voluntary. While the monitored privacy mailbox is not yet verified, submit a confidential privacy, access, correction, or deletion request through the EAINE contact directory. Do not use a public repository issue for personal or sensitive information.

Security and legal contact

Use the same private reporting route for security concerns. The planned `security@eaine.org`, `privacy@eaine.org`, and `legal@eaine.org` aliases are not published as operational channels until monitoring, access, retention, and response tests are complete.

Updated 3 August 2026 · Public-update registration and optional analytics remain runtime-disabled until their approved production controls are activated · Public review intake paused by Phase 0 control.