Trust & security
The controls we use, the checks we ran, and the limits of this review.
Contact supportRelease verification · 5 October 2026
Evidence, not a promise.
All 245 checks in this release snapshot passed. They cover security controls, functionality, accessibility structure, SEO and interface regressions—not 245 security tests.
- Total checks
- 245231 test cases + 14 assertions
- Accounts
- 30test cases
- AI application
- 201test cases
- WordPress bridge
- 14assertion checks
This is a dated, revision-bound automated test record, not an independent penetration test, security certification, full WCAG assessment or guarantee of safety. Isolated fixtures and mocked services are used where appropriate. New releases and connected systems need their own review.
1. Technical controls and boundaries
1.1 Server-side secrets
AI, search and OCR provider credentials are read from server environment variables and are not rendered into public HTML or browser JavaScript.
1.2 Internal workspaces
Internal workspace routes are disabled by default and require explicit server configuration to enable. Administrative APIs require authenticated server-side authorization.
1.3 Public abuse controls
Public Nova endpoints use request-size limits and rate limiting. Security headers restrict framing, browser permissions and unexpected cross-origin behavior.
1.4 Source boundaries
Controlled Nova knowledge, live web results, uploaded PDFs and image interpretation are labelled separately so provenance is not silently blended.
1.5 Account boundary
WordPress/WooCommerce remains the master identity source. Passwords stay with WordPress; the Accounts service and Alle's ClinXAi exchange only short-lived one-time authorization codes, a minimum internal user identifier and opaque session references with expiry. Sessions use secure, HttpOnly, SameSite cookies, have a one-hour maximum and require a valid parent Accounts session. Durable revocation rejects reused or revoked access; failed session checks deny access rather than silently accepting it.
2. Scope, identity and sessions
2.1 What this summary does and does not establish
This page describes controls in the current AI application and the intended boundary between public tools, accounts and internal workspaces. It is not an independent penetration-test report, an ISO or SOC certification, or a guarantee that the wider WordPress, payment, hosting and provider systems have identical controls. Security depends on the connected systems as well as this application.
2.2 Shared identity, separate permissions
Accounts uses the main WordPress identity to support sign-in to the AI site. A successful login authenticates an identity; it does not by itself grant administrator access, purchasing authority or access to another customer’s records. WooCommerce and WordPress enforce their own role and order permissions. The public Nova catalog connection retrieves products and document links and does not expose private checkout or customer data.
2.3 Session handling and shared devices
Application sessions use secure, HttpOnly, SameSite cookies on the HTTPS deployment. Accounts and AI sessions have a one-hour maximum; the parent Accounts session expires after 30 minutes of inactivity. AI sessions cannot outlive that parent and are validated server-to-server. Signing out of AI or Accounts revokes the corresponding shared Accounts session and its AI access. It does not sign out WordPress, the customer shopping account or Google. Browser-saved conversations and drafts are separate from authentication and can remain after sign-out; clear them before handing a shared device to another person.
3. Inputs and source handling
3.1 Input controls and external processing
Public requests are subject to size limits and rate limiting. Uploaded data is processed for the requested AI, extraction or image feature and may be sent to configured providers. File validation and limits do not turn a public chat into an approved repository for confidential or sensitive records. Redact unnecessary information and verify your organisation’s requirements before selecting a file.
3.2 Sources and untrusted material
Public pages, search results and uploaded files are evidence to review rather than authority to perform actions. Nova responses can include inaccurate interpretations or text from an untrusted source. Do not follow a source’s request to disclose credentials, pay an invoice, grant account access or execute instructions without independent verification. A legitimate-looking product link should still be checked for the expected host and document identity.
4. Reporting and user checks
4.1 How to report a vulnerability
Send care@allesclinx.com a concise description, the affected page or endpoint, the approximate time and steps that reproduce the issue using your own account and data. Redact passwords, tokens, personal records and provider secrets. Do not retrieve another user’s information, disrupt service, evade limits or publish exploit details before the issue can be investigated. This contact route does not authorise unrestricted testing or promise a bug-bounty payment.
4.2 Incident and account concerns
For an unexpected login, suspicious redirect or exposed information, stop the affected activity and contact support. Change compromised credentials through the main site’s account or recovery process and review the Google account if social sign-in is involved. We investigate relevant reports and address notifications where applicable law requires them. The timing and scope of a response depend on the incident; this page does not make an unverified 24-hour response or complete-prevention guarantee.
4.3 Checks users should make
Use the expected allesclinx.com, auth.allesclinx.com and ai.allesclinx.com addresses, keep browsers updated and avoid sharing access links. Check product and safety decisions against current published documents. Keep independent copies of approved operational records: a saved browser draft or AI reply is not a controlled compliance record or backup. Report a mismatch between this summary and observed behaviour so it can be reviewed.
5. Verification record
5.1 Release evidence
Automated results verified on 5 October 2026. Descriptions below correspond one-to-one with checks in the pinned releases; some names are simplified for readability. The 14 bridge checks are individual PHP assertions, not 14 separate application test cases. Page changes after this snapshot are checked separately and do not silently increase this total.
Accounts
30 passed test cases
Revision 92a5a2c69163c0bee1492f8ec91d68b68a48ea7b
AI application
201 passed test cases
Revision d89b18ce26851c3853225ac2b28b860f899eb36e
WordPress bridge
14 passed assertion checks
Revision 4ab3bc267336a4dc6a694e9422aa4e3718c0a99c
Repository evidence links may require permission to access our private GitHub repositories. This public record contains every check’s description, source location and pinned revision. Download the complete public record with source files, check numbers and release revisions.
5.2 Live checks
These manual production observations on 5 October 2026 are separate from the 245 automated checks. They used the normal account flow, not a load test or attack against production.
- HTTPS login and AI responses were checked for content-security, transport, framing and content-type protection headers.
- A fresh WordPress → Accounts → AI sign-in completed after the bridge update.
- Signing out of Accounts made the related AI session unusable, including when its browser cookie remained.
- Signing out of AI ended its parent Accounts session; the next sign-in required authentication again.
The automated bridge race check uses interleaved fake requests. It does not establish performance or behaviour under every production database, hosting topology or traffic level.
5.3 Review limits
- No independent penetration test, ISO/SOC certification or full manual WCAG conformance assessment is claimed.
- WordPress password-reset revocation hooks, MFA and password policies, unrelated plugins, payment systems, backups and recovery drills were not comprehensively reviewed.
- Host WAF rules, distributed rate limiting and multi-host session storage were not verified. Current application limits are per process.
- The AI site retains inline-script compatibility in its content-security policy. Header checks do not prove that every possible cross-site scripting issue is prevented.
- Provider retention, model training practices and third-party security are governed separately. Do not submit confidential records, credentials or unnecessary personal information.
- Publishing remains disabled until an owner-approved publisher identity and required production settings are configured. Passing its isolated tests does not mean publishing is enabled.
Report concerns to care@allesclinx.com. Send a redacted description and affected page; never send passwords, login codes or session tokens.
5.4 All 245 checks
Open a category to read each check. “Passed” means the named automated condition passed in the release snapshot—not that the feature is independently certified, enabled in production or proven on every device. The list works without JavaScript.
Accounts application30 passed
- 001Health responses use coded application identifiersPassed
- 002Public account routes existPassed
- 003Login state is signed and expiresPassed
- 004Sessions are signed and expirePassed
- 005Accounts session cookies are parsed correctlyPassed
- 006Return targets are limited to configured originsPassed
- 007Bridge remains off until every protected setting existsPassed
- 008Authorization code exchange sends credentials only server-sidePassed
- 009Public origin is normalized and callback URL is exactPassed
- 010Login starts with a browser-bound secure state cookiePassed
- 011A valid signed state from another browser cannot establish a sessionPassed
- 012Matching browser state exchanges the code and clears the temporary cookiePassed
- 013A GET logout cannot mutate the sessionPassed
- 014State matching fails closed and return URLs cannot contain credentialsPassed
- 015Revocation persists through restart, idle and absolute expiry fail closedPassed
- 016Durable handoff codes are one-time, client-bound and revoked with their parentPassed
- 017Storage corruption cannot fall back to memory or erase revocationsPassed
- 018Overlapping app workers cannot overwrite revocations or reuse a codePassed
- 019Rate limits are bounded, expire and reject a saturated key mapPassed
- 020Hosting header repair preserves routing, is idempotent and validates its pathPassed
- 021Logout is CSRF-protected and a copied cookie is rejected immediately after sign-outPassed
- 022Introspection and revocation require the confidential application clientPassed
- 023Legacy tokens cannot establish access and login endpoints return 429 without flooding a hostPassed
- 024HTTPS auth responses enforce CSP, HSTS and no-storePassed
- 025A private logout-only proof revokes the original session when a browser omits its cookiePassed
- 026The AI sign-in client requires an exact protected configurationPassed
- 027Downstream authorization codes are random, short-lived and one-timePassed
- 028Service client secrets use constant-time comparisonPassed
- 029Account pages do not expose a staging label or runtime environmentPassed
- 030Removing the environment label preserves the login return destinationPassed
AI sign-in & sessions13 passed
- 031Account configuration requires every protected valuePassed
- 032Login state and application sessions are signed and expirePassed
- 033Return paths stay on the AI applicationPassed
- 034Authorize and callback URLs use exact first-party originsPassed
- 035State must match the HttpOnly browser cookiePassed
- 036Authorization code exchange keeps the client secret server-sidePassed
- 037Main pages show account entry while the Nova chat document stays unchangedPassed
- 224AI validates its parent session server-to-server and rejects revoked, mismatched and legacy sessionsPassed
- 225AI logout requires a successful central revocation rather than merely clearing cookiesPassed
- 226AI sessions have a one-hour maximum and cannot outlive the parentPassed
- 227A legacy token exchange without revocable parent identity fails closedPassed
- 228Every HTML response gets an early CSP fallback without changing plain responsesPassed
- 229Logout-only proofs cannot become sessions, be tampered with, or survive their short lifetimePassed
Publishing & content controls8 passed
- 043HTML sanitizer preserves editorial content but strips active content and DOM clobberingPassed
- 044Content validation bounds HTML and rejects unsafe image URLs and path-like slugsPassed
- 045Drafts survive restart; publishing, staged edits and unpublishing preserve contentPassed
- 046Optimistic revisions prevent concurrent edits and duplicate slugsPassed
- 047Storage is never memory-only and a corrupt file is not overwrittenPassed
- 048Public article has one H1, canonical SEO, author/date schema and no admin dataPassed
- 049Admin page and every API require explicit access; writes require session-bound CSRF and exact originPassed
- 050Production admin remains closed without configuration and published pages enter discovery indexesPassed
AI sources, files & answer controls15 passed
- 178Nova knowledge store retrieves only approved sources and examplesPassed
- 179Nova crawler stays inside its allowlist and extracts same-origin pagesPassed
- 180Nova crawler rejects hosts outside the configured allowlistPassed
- 181Nova removes unsupported SDS section pointers without a controlled sourcePassed
- 182Nova preserves document pointers when a controlled source is connectedPassed
- 183Nova strips bare numbered sections from an ungrounded SDS tablePassed
- 184Nova web search uses Groq browser search when Groq is availablePassed
- 185Nova web search can fall back to Brave structured resultsPassed
- 186Nova PDF scanner extracts embedded text without an OCR providerPassed
- 187Nova PDF scanner falls back to OCR for image-only PDFsPassed
- 188Nova image analysis sends supported data URLs to Groq visionPassed
- 189Nova capability adapters reject unsupported or unavailable inputPassed
- 190Answer controls copy complete text and persist mutually exclusive feedbackPassed
- 191Read aloud has pause and stop controls and stops another answerPassed
- 192Unsupported speech disables read aloud while preserving copy and feedbackPassed
Product & document retrieval4 passed
- 163Library parses product documents and resources, rejecting external linksPassed
- 164Matching uses live product descriptions and SDS aliases without unrelated cardsPassed
- 165Refresh is coalesced and expired content is never presented as live after failurePassed
- 166Resource query returns the matching checklist rather than a product PDFPassed
Page semantics, SEO & crawling26 passed
- 038Search indexes canonical public pages without private workspacesPassed
- 061About is visible in company navigation and public SEO indexesPassed
- 062Updates and Blog are visible in public navigation and SEO indexesPassed
- 097SEO sitemap registry includes every live tool canonicalPassed
- 098All live tools expose a complete indexable SEO contractPassed
- 099Google Search Console verification file is served from the site rootPassed
- 100Public pages advertise LLM-readable indexesPassed
- 101LLM index is generated from public SEO routes and excludes private workspacesPassed
- 102Public pages render canonical SEO metadata and structured dataPassed
- 106Guide and trust page families use stable SEO slugsPassed
- 153Not-found page is a real noindex HTML surfacePassed
- 193Route inventory renders every declared public pagePassed
- 194Every public page has one meaningful H1 and one main landmarkPassed
- 195SEO-bearing routes have complete canonical, robots, social and structured metadataPassed
- 196Indexable pages have unique SEO titles and descriptionsPassed
- 197Core SEO inventory stays synchronized with public core routesPassed
- 198Public HTML has unique IDs and valid aria-labelledby targetsPassed
- 199All rendered images carry alt text and lazy/eager intentPassed
- 200Links on public pages resolve to declared routes or valid page anchorsPassed
- 201Form controls on public pages expose an accessible namePassed
- 202Public pages keep baseline document semanticsPassed
- 206Production sitemap and public pages are crawlable despite the private /site prefixPassed
- 207Non-production remains fully blockedPassed
- 208Public sitemap alias returns the same XML without a redirect or private URLsPassed
- 230Every public HTML page has a parseable linked schema graphPassed
- 231Tool and article entities link back to their canonical pagePassed
Runtime & access boundaries17 passed
- 114Integration status never renders provider secretPassed
- 115Dynamic runtime labels are escapedPassed
- 209Health responses use coded runtime identifiersPassed
- 210Core workspace routes are definedPassed
- 211Groq environment config stays server-sidePassed
- 212Legacy public routes redirect to canonical SEO slugsPassed
- 213Robots and sitemap endpoints expose canonical public structurePassed
- 214Constant-time secret comparison rejects mismatchesPassed
- 215Nova chat endpoint reports unavailable provider safelyPassed
- 216Administrative AI endpoints remain closed without required access controlsPassed
- 217Nova crawler config defaults to Alle's ClinX hostsPassed
- 218Nova capability configuration remains server-sidePassed
- 219Nova relay status exposes search, PDF and image capability flagsPassed
- 220Internal workspaces are opt-in in every environmentPassed
- 221Internal workspace HTTP routes stay private unless explicitly enabledPassed
- 222Unknown browser routes return a branded HTML 404Passed
- 223Server applies production security headers to responsesPassed
Navigation & header29 passed
- 041Frame locks parent-brand placement and trigger-anchored menusPassed
- 052Launch truth contract keeps public products and navigation synchronizedPassed
- 076Shared footer uses the oversized pale Alle's ClinX watermark treatmentPassed
- 077Public footer never exposes runtime environment labelsPassed
- 078Shared footer omits the company legal-name suffixPassed
- 079Global menu hides the normal shared header while openPassed
- 080Global menu is full-screen and opens top-downPassed
- 081Global menu is available across public, product, and workspace pagesPassed
- 082Site pages use one global menu while working tools intentionally remove global chromePassed
- 083Shared navigation keeps the existing chrome and exposes four dropdown groupsPassed
- 084Squeezed header capsule is fixed to the viewport centerPassed
- 085Shared header keeps the brand mathematically centered at every breakpointPassed
- 086Shared header keeps its size while scroll direction controls visibilityPassed
- 087Header dropdowns stay centered beneath the shared headerPassed
- 088Global header uses the refined floating menu and structured dropdown panelsPassed
- 090Discovery pages keep deliberate endings and parent-brand footerPassed
- 095Public links stay arrow-free and first content breathes below the headerPassed
- 116Production footer omits preview languagePassed
- 118Global header gutters use a soft backdrop blur while header content stays crispPassed
- 119Header pixel system keeps exact desktop geometryPassed
- 126Sector navigation uses real tool paths, without tool hash linksPassed
- 129Guide and support articles provide overview and in-page navigationPassed
- 141Nova conversational shell keeps provider state, clear action and app navigationPassed
- 144Focused tool headers keep a small internal top and side gutterPassed
- 157Header actions are icon-only with accessible names and unchanged destinationsPassed
- 158Signed-in account icon preserves account and sign-out destinationsPassed
- 159Compact controls preserve touch size and grey eight-pixel menu cornersPassed
- 175Scroll header hides down, reveals up and preserves keyboard access without resizingPassed
- 177Neutral surface and fixed header respect access preferencesPassed
Calculators & tool pages28 passed
- 105Nova, Metricon and CheckMate expose one shared decision-trail languagePassed
- 107CheckMate landing has search and category browsing for live verification toolsPassed
- 108CheckMate tools have stable live comparison routesPassed
- 109Metricon landing exposes only launch-ready calculatorsPassed
- 110Metricon finder uses clear labels, icons, quick searches, and user-facing categoriesPassed
- 111Metricon landing presents calculators as problems to solvePassed
- 112Metricon catalog exposes all registered calculators as launch-ready toolsPassed
- 113Metricon calculation engine preserves archived calculator formulasPassed
- 121Healthcare tool route exposes a working CareClean PlannerPassed
- 122Education tool route exposes a working CampusClean PlannerPassed
- 123Hospitality tool route exposes a working RoomFlowPassed
- 124Industrial tool route exposes a working ShiftHousePassed
- 125Sector secondary tools have dedicated working routesPassed
- 136Nova chat page is a live working surfacePassed
- 137Nova chat supports editable B2B briefs and structured answersPassed
- 138Nova answers render structured tables and follow browser scrollingPassed
- 139Nova chat uses a focused ChatGPT-style no-image workspacePassed
- 140Nova chat renders as a standalone working toolPassed
- 142Nova working surface exposes responsive sidebar controlsPassed
- 143Nova conversations use the browser scrollbar instead of a nested thread scrollbarPassed
- 146Metricon and CheckMate tools use the minimal back-context-work-boundary shellPassed
- 148Configured internal knowledge tools expose crawl, training and retrieval controlsPassed
- 149Nova chat exposes web, multi-file, voice and image controlsPassed
- 150Nova capability upgrade wires multi-file requests, regenerate, voice and grouped sourcesPassed
- 152CheckMate public tools expose working local comparison surfacesPassed
- 155Editorial design is applied across main pages and excluded from Nova chatPassed
- 169Sector task links resolve to tool pages while local sections remain visiblePassed
- 204Calculator method labels fit small native pickers without changing mode keysPassed
Landing pages & guides37 passed
- 039Search remains available on discovery pages and focused workspacesPassed
- 042Sector pages have no empty headingsPassed
- 057Product landing pages lead with problems and link to permanent working pagesPassed
- 058Page taxonomy separates core, landing, tool and information pagesPassed
- 059About Alle's ClinXAi explains the product, system and boundaries without invented proofPassed
- 060Updates and Blog use distinct publication patternsPassed
- 063Discovery and information page families use deliberate hero foundationsPassed
- 064Public home leads with task-first choicesPassed
- 065Home omits the removed facility proof stripPassed
- 066Shared public heroes use the same inset cinematic systemPassed
- 067Homepage hero is a task-first cinematic routerPassed
- 068Homepage hero keeps copy concise and task actions visiblePassed
- 069Homepage copy wraps naturally and keeps decorative arrows out of contentPassed
- 070Homepage avoids repeated scroll stories and problem slidersPassed
- 071Home presents three tools as one accessible sliderPassed
- 072Home craftsmanship keeps a task-to-problem narrativePassed
- 073Homepage layout preserves the intended hero, card and gutter geometryPassed
- 074Public and product landing pages use the curated operational stock libraryPassed
- 089Sector pages move through context, action, accountability and verificationPassed
- 091Public home keeps shared chrome without legacy home overlaysPassed
- 103Guides masthead makes search immediate while preserving the editorial publication flowPassed
- 104Guide library and guide articles keep text intact across layoutsPassed
- 120Sector pages preserve distinct responsibilities and execution signals inside the new flowPassed
- 127Support and sector guide articles render as real article pagesPassed
- 128Guides and help expose deeper knowledge architecturePassed
- 130Guides and Help expose searchable discovery surfacesPassed
- 132Guide and support articles include contextual media inside the reading flowPassed
- 133Image-led discovery heroes keep shared media while Guides stays text-firstPassed
- 154Discovery and information families keep distinct hero compositionsPassed
- 156Homepage prioritizes direct task links over scroll-story dialogsPassed
- 160Homepage bento tiles have real gaps instead of shared divider edgesPassed
- 161About and Journal inherit the same frame and accessible compact actionsPassed
- 167All major landings share the parent frame, public search and one H1Passed
- 170Article and working-tool pages are not assigned the landing framePassed
- 172Minimal home hero keeps task routing below concise glass actionsPassed
- 173Guide search stays outside the minimal masthead without losing semanticsPassed
- 174Minimal hero styles scope glass to public hero actions and provide accessible fallbacksPassed
Layout & presentation24 passed
- 040Working tools progressively disclose trust context without dropping review statesPassed
- 051Configured workspace routes render their intended pagesPassed
- 053All legal and trust pages use the shared readable document templatePassed
- 054Legal accordion styling follows the supplied compact grey templatePassed
- 055Public trust pages state the current data flow without internal control namesPassed
- 056Healthcare sector exposes authoritative reference frameworkPassed
- 075Curated stock library keeps source pages alongside image idsPassed
- 092Working tools and support hubs render complete purposeful surfacesPassed
- 093Visible micro-labels use natural sentence casePassed
- 094Public site locks the Alle's ClinXAi whitespace and Inter signaturePassed
- 096Shared document loads Inter and keeps lighter global chromePassed
- 117Closing grey confidence cards fit their text with balanced side paddingPassed
- 131Finder bars share keyboard search affordancesPassed
- 134Unrelated top-level page families have distinct structural identitiesPassed
- 135Children under the same parent share their page-family grammarPassed
- 145Focused working tools keep restrained top and side guttersPassed
- 147Public page families declare deliberate psychological flowsPassed
- 151Public launch routes avoid skeleton language and broken internal linksPassed
- 162Publication empty states and topic grids retain neutral surfaces at mobile widthsPassed
- 168Product finders and actions precede optional explanationsPassed
- 171Product finders count visible results and recover from an empty searchPassed
- 176Compact labels preserve source and safety contentPassed
- 203Shared geometry layer follows legacy styles on every public templatePassed
- 205Polish preserves native select semantics and accessibility fallbacksPassed
WordPress sign-in bridge14 passed
- 232A valid one-time code returns only the minimum account identifierPassed
- 233Identity responses carry a no-store cache policyPassed
- 234Sequential replay cannot read the account identity againPassed
- 235Only the successful code-consumption request returns identity when requests interleavePassed
- 236A failed code deletion cannot issue an account identityPassed
- 237A code at the 90-second expiry boundary is rejectedPassed
- 238A code older than the 90-second lifetime is rejectedPassed
- 239A future-issued code is rejectedPassed
- 240A malformed issue timestamp is rejectedPassed
- 241A code bound to another application client is rejectedPassed
- 242The callback destination must match the code’s bound destinationPassed
- 243A missing account is rejected and its code remains consumedPassed
- 244Invalid application credentials are rejected before code storage is readPassed
- 245Malformed codes are rejected before code storage is readPassed
