Canonical: https://ai.allesclinx.com/trust-security
Description: Review the trust and security principles for Alle's ClinXAi, including server-side secrets, source visibility and accountable decisions.

# Trust & security

The controls we use, the checks we ran, and the limits of this review.

[Contact support](<https://ai.allesclinx.com/contact>)

Security summary · Reviewed 6 October 2026

**Alle’s ClinX · Champaran Innovatives Private Limited**

This document explains trust & security for the AI tools and connected accounts. Product purchases remain governed by the main website’s commercial policies.

Release 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

[View checks](<https://ai.allesclinx.com/trust-security#verification-checklist>)[Download record](<https://ai.allesclinx.com/assets/verification-checks-2026-10-05.json>)

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`

[CI evidence](<https://github.com/alles-clinx/Keystone/actions/runs/37346454369>)

#### AI application

201 passed test cases

Revision `d89b18ce26851c3853225ac2b28b860f899eb36e`

[CI evidence](<https://github.com/alles-clinx/meridian/actions/runs/37346465474>)

#### WordPress bridge

14 passed assertion checks

Revision `4ab3bc267336a4dc6a694e9422aa4e3718c0a99c`

[CI evidence](<https://github.com/alles-clinx/passage/actions/runs/37349430754>)

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](<https://ai.allesclinx.com/assets/verification-checks-2026-10-05.json>) 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](<mailto: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 application 30 passed

1. 001 Health responses use coded application identifiers Passed
2. 002 Public account routes exist Passed
3. 003 Login state is signed and expires Passed
4. 004 Sessions are signed and expire Passed
5. 005 Accounts session cookies are parsed correctly Passed
6. 006 Return targets are limited to configured origins Passed
7. 007 Bridge remains off until every protected setting exists Passed
8. 008 Authorization code exchange sends credentials only server-side Passed
9. 009 Public origin is normalized and callback URL is exact Passed
10. 010 Login starts with a browser-bound secure state cookie Passed
11. 011 A valid signed state from another browser cannot establish a session Passed
12. 012 Matching browser state exchanges the code and clears the temporary cookie Passed
13. 013 A GET logout cannot mutate the session Passed
14. 014 State matching fails closed and return URLs cannot contain credentials Passed
15. 015 Revocation persists through restart, idle and absolute expiry fail closed Passed
16. 016 Durable handoff codes are one-time, client-bound and revoked with their parent Passed
17. 017 Storage corruption cannot fall back to memory or erase revocations Passed
18. 018 Overlapping app workers cannot overwrite revocations or reuse a code Passed
19. 019 Rate limits are bounded, expire and reject a saturated key map Passed
20. 020 Hosting header repair preserves routing, is idempotent and validates its path Passed
21. 021 Logout is CSRF-protected and a copied cookie is rejected immediately after sign-out Passed
22. 022 Introspection and revocation require the confidential application client Passed
23. 023 Legacy tokens cannot establish access and login endpoints return 429 without flooding a host Passed
24. 024 HTTPS auth responses enforce CSP, HSTS and no-store Passed
25. 025 A private logout-only proof revokes the original session when a browser omits its cookie Passed
26. 026 The AI sign-in client requires an exact protected configuration Passed
27. 027 Downstream authorization codes are random, short-lived and one-time Passed
28. 028 Service client secrets use constant-time comparison Passed
29. 029 Account pages do not expose a staging label or runtime environment Passed
30. 030 Removing the environment label preserves the login return destination Passed

AI sign-in & sessions 13 passed

1. 031 Account configuration requires every protected value Passed
2. 032 Login state and application sessions are signed and expire Passed
3. 033 Return paths stay on the AI application Passed
4. 034 Authorize and callback URLs use exact first-party origins Passed
5. 035 State must match the HttpOnly browser cookie Passed
6. 036 Authorization code exchange keeps the client secret server-side Passed
7. 037 Main pages show account entry while the Nova chat document stays unchanged Passed
8. 224 AI validates its parent session server-to-server and rejects revoked, mismatched and legacy sessions Passed
9. 225 AI logout requires a successful central revocation rather than merely clearing cookies Passed
10. 226 AI sessions have a one-hour maximum and cannot outlive the parent Passed
11. 227 A legacy token exchange without revocable parent identity fails closed Passed
12. 228 Every HTML response gets an early CSP fallback without changing plain responses Passed
13. 229 Logout-only proofs cannot become sessions, be tampered with, or survive their short lifetime Passed

Publishing & content controls 8 passed

1. 043 HTML sanitizer preserves editorial content but strips active content and DOM clobbering Passed
2. 044 Content validation bounds HTML and rejects unsafe image URLs and path-like slugs Passed
3. 045 Drafts survive restart; publishing, staged edits and unpublishing preserve content Passed
4. 046 Optimistic revisions prevent concurrent edits and duplicate slugs Passed
5. 047 Storage is never memory-only and a corrupt file is not overwritten Passed
6. 048 Public article has one H1, canonical SEO, author/date schema and no admin data Passed
7. 049 Admin page and every API require explicit access; writes require session-bound CSRF and exact origin Passed
8. 050 Production admin remains closed without configuration and published pages enter discovery indexes Passed

AI sources, files & answer controls 15 passed

1. 178 Nova knowledge store retrieves only approved sources and examples Passed
2. 179 Nova crawler stays inside its allowlist and extracts same-origin pages Passed
3. 180 Nova crawler rejects hosts outside the configured allowlist Passed
4. 181 Nova removes unsupported SDS section pointers without a controlled source Passed
5. 182 Nova preserves document pointers when a controlled source is connected Passed
6. 183 Nova strips bare numbered sections from an ungrounded SDS table Passed
7. 184 Nova web search uses Groq browser search when Groq is available Passed
8. 185 Nova web search can fall back to Brave structured results Passed
9. 186 Nova PDF scanner extracts embedded text without an OCR provider Passed
10. 187 Nova PDF scanner falls back to OCR for image-only PDFs Passed
11. 188 Nova image analysis sends supported data URLs to Groq vision Passed
12. 189 Nova capability adapters reject unsupported or unavailable input Passed
13. 190 Answer controls copy complete text and persist mutually exclusive feedback Passed
14. 191 Read aloud has pause and stop controls and stops another answer Passed
15. 192 Unsupported speech disables read aloud while preserving copy and feedback Passed

Product & document retrieval 4 passed

1. 163 Library parses product documents and resources, rejecting external links Passed
2. 164 Matching uses live product descriptions and SDS aliases without unrelated cards Passed
3. 165 Refresh is coalesced and expired content is never presented as live after failure Passed
4. 166 Resource query returns the matching checklist rather than a product PDF Passed

Page semantics, SEO & crawling 26 passed

1. 038 Search indexes canonical public pages without private workspaces Passed
2. 061 About is visible in company navigation and public SEO indexes Passed
3. 062 Updates and Blog are visible in public navigation and SEO indexes Passed
4. 097 SEO sitemap registry includes every live tool canonical Passed
5. 098 All live tools expose a complete indexable SEO contract Passed
6. 099 Google Search Console verification file is served from the site root Passed
7. 100 Public pages advertise LLM-readable indexes Passed
8. 101 LLM index is generated from public SEO routes and excludes private workspaces Passed
9. 102 Public pages render canonical SEO metadata and structured data Passed
10. 106 Guide and trust page families use stable SEO slugs Passed
11. 153 Not-found page is a real noindex HTML surface Passed
12. 193 Route inventory renders every declared public page Passed
13. 194 Every public page has one meaningful H1 and one main landmark Passed
14. 195 SEO-bearing routes have complete canonical, robots, social and structured metadata Passed
15. 196 Indexable pages have unique SEO titles and descriptions Passed
16. 197 Core SEO inventory stays synchronized with public core routes Passed
17. 198 Public HTML has unique IDs and valid aria-labelledby targets Passed
18. 199 All rendered images carry alt text and lazy/eager intent Passed
19. 200 Links on public pages resolve to declared routes or valid page anchors Passed
20. 201 Form controls on public pages expose an accessible name Passed
21. 202 Public pages keep baseline document semantics Passed
22. 206 Production sitemap and public pages are crawlable despite the private /site prefix Passed
23. 207 Non-production remains fully blocked Passed
24. 208 Public sitemap alias returns the same XML without a redirect or private URLs Passed
25. 230 Every public HTML page has a parseable linked schema graph Passed
26. 231 Tool and article entities link back to their canonical page Passed

Runtime & access boundaries 17 passed

1. 114 Integration status never renders provider secret Passed
2. 115 Dynamic runtime labels are escaped Passed
3. 209 Health responses use coded runtime identifiers Passed
4. 210 Core workspace routes are defined Passed
5. 211 Groq environment config stays server-side Passed
6. 212 Legacy public routes redirect to canonical SEO slugs Passed
7. 213 Robots and sitemap endpoints expose canonical public structure Passed
8. 214 Constant-time secret comparison rejects mismatches Passed
9. 215 Nova chat endpoint reports unavailable provider safely Passed
10. 216 Administrative AI endpoints remain closed without required access controls Passed
11. 217 Nova crawler config defaults to Alle's ClinX hosts Passed
12. 218 Nova capability configuration remains server-side Passed
13. 219 Nova relay status exposes search, PDF and image capability flags Passed
14. 220 Internal workspaces are opt-in in every environment Passed
15. 221 Internal workspace HTTP routes stay private unless explicitly enabled Passed
16. 222 Unknown browser routes return a branded HTML 404 Passed
17. 223 Server applies production security headers to responses Passed

Navigation & header 29 passed

1. 041 Frame locks parent-brand placement and trigger-anchored menus Passed
2. 052 Launch truth contract keeps public products and navigation synchronized Passed
3. 076 Shared footer uses the oversized pale Alle's ClinX watermark treatment Passed
4. 077 Public footer never exposes runtime environment labels Passed
5. 078 Shared footer omits the company legal-name suffix Passed
6. 079 Global menu hides the normal shared header while open Passed
7. 080 Global menu is full-screen and opens top-down Passed
8. 081 Global menu is available across public, product, and workspace pages Passed
9. 082 Site pages use one global menu while working tools intentionally remove global chrome Passed
10. 083 Shared navigation keeps the existing chrome and exposes four dropdown groups Passed
11. 084 Squeezed header capsule is fixed to the viewport center Passed
12. 085 Shared header keeps the brand mathematically centered at every breakpoint Passed
13. 086 Shared header keeps its size while scroll direction controls visibility Passed
14. 087 Header dropdowns stay centered beneath the shared header Passed
15. 088 Global header uses the refined floating menu and structured dropdown panels Passed
16. 090 Discovery pages keep deliberate endings and parent-brand footer Passed
17. 095 Public links stay arrow-free and first content breathes below the header Passed
18. 116 Production footer omits preview language Passed
19. 118 Global header gutters use a soft backdrop blur while header content stays crisp Passed
20. 119 Header pixel system keeps exact desktop geometry Passed
21. 126 Sector navigation uses real tool paths, without tool hash links Passed
22. 129 Guide and support articles provide overview and in-page navigation Passed
23. 141 Nova conversational shell keeps provider state, clear action and app navigation Passed
24. 144 Focused tool headers keep a small internal top and side gutter Passed
25. 157 Header actions are icon-only with accessible names and unchanged destinations Passed
26. 158 Signed-in account icon preserves account and sign-out destinations Passed
27. 159 Compact controls preserve touch size and grey eight-pixel menu corners Passed
28. 175 Scroll header hides down, reveals up and preserves keyboard access without resizing Passed
29. 177 Neutral surface and fixed header respect access preferences Passed

Calculators & tool pages 28 passed

1. 105 Nova, Metricon and CheckMate expose one shared decision-trail language Passed
2. 107 CheckMate landing has search and category browsing for live verification tools Passed
3. 108 CheckMate tools have stable live comparison routes Passed
4. 109 Metricon landing exposes only launch-ready calculators Passed
5. 110 Metricon finder uses clear labels, icons, quick searches, and user-facing categories Passed
6. 111 Metricon landing presents calculators as problems to solve Passed
7. 112 Metricon catalog exposes all registered calculators as launch-ready tools Passed
8. 113 Metricon calculation engine preserves archived calculator formulas Passed
9. 121 Healthcare tool route exposes a working CareClean Planner Passed
10. 122 Education tool route exposes a working CampusClean Planner Passed
11. 123 Hospitality tool route exposes a working RoomFlow Passed
12. 124 Industrial tool route exposes a working ShiftHouse Passed
13. 125 Sector secondary tools have dedicated working routes Passed
14. 136 Nova chat page is a live working surface Passed
15. 137 Nova chat supports editable B2B briefs and structured answers Passed
16. 138 Nova answers render structured tables and follow browser scrolling Passed
17. 139 Nova chat uses a focused ChatGPT-style no-image workspace Passed
18. 140 Nova chat renders as a standalone working tool Passed
19. 142 Nova working surface exposes responsive sidebar controls Passed
20. 143 Nova conversations use the browser scrollbar instead of a nested thread scrollbar Passed
21. 146 Metricon and CheckMate tools use the minimal back-context-work-boundary shell Passed
22. 148 Configured internal knowledge tools expose crawl, training and retrieval controls Passed
23. 149 Nova chat exposes web, multi-file, voice and image controls Passed
24. 150 Nova capability upgrade wires multi-file requests, regenerate, voice and grouped sources Passed
25. 152 CheckMate public tools expose working local comparison surfaces Passed
26. 155 Editorial design is applied across main pages and excluded from Nova chat Passed
27. 169 Sector task links resolve to tool pages while local sections remain visible Passed
28. 204 Calculator method labels fit small native pickers without changing mode keys Passed

Landing pages & guides 37 passed

1. 039 Search remains available on discovery pages and focused workspaces Passed
2. 042 Sector pages have no empty headings Passed
3. 057 Product landing pages lead with problems and link to permanent working pages Passed
4. 058 Page taxonomy separates core, landing, tool and information pages Passed
5. 059 About Alle's ClinXAi explains the product, system and boundaries without invented proof Passed
6. 060 Updates and Blog use distinct publication patterns Passed
7. 063 Discovery and information page families use deliberate hero foundations Passed
8. 064 Public home leads with task-first choices Passed
9. 065 Home omits the removed facility proof strip Passed
10. 066 Shared public heroes use the same inset cinematic system Passed
11. 067 Homepage hero is a task-first cinematic router Passed
12. 068 Homepage hero keeps copy concise and task actions visible Passed
13. 069 Homepage copy wraps naturally and keeps decorative arrows out of content Passed
14. 070 Homepage avoids repeated scroll stories and problem sliders Passed
15. 071 Home presents three tools as one accessible slider Passed
16. 072 Home craftsmanship keeps a task-to-problem narrative Passed
17. 073 Homepage layout preserves the intended hero, card and gutter geometry Passed
18. 074 Public and product landing pages use the curated operational stock library Passed
19. 089 Sector pages move through context, action, accountability and verification Passed
20. 091 Public home keeps shared chrome without legacy home overlays Passed
21. 103 Guides masthead makes search immediate while preserving the editorial publication flow Passed
22. 104 Guide library and guide articles keep text intact across layouts Passed
23. 120 Sector pages preserve distinct responsibilities and execution signals inside the new flow Passed
24. 127 Support and sector guide articles render as real article pages Passed
25. 128 Guides and help expose deeper knowledge architecture Passed
26. 130 Guides and Help expose searchable discovery surfaces Passed
27. 132 Guide and support articles include contextual media inside the reading flow Passed
28. 133 Image-led discovery heroes keep shared media while Guides stays text-first Passed
29. 154 Discovery and information families keep distinct hero compositions Passed
30. 156 Homepage prioritizes direct task links over scroll-story dialogs Passed
31. 160 Homepage bento tiles have real gaps instead of shared divider edges Passed
32. 161 About and Journal inherit the same frame and accessible compact actions Passed
33. 167 All major landings share the parent frame, public search and one H1 Passed
34. 170 Article and working-tool pages are not assigned the landing frame Passed
35. 172 Minimal home hero keeps task routing below concise glass actions Passed
36. 173 Guide search stays outside the minimal masthead without losing semantics Passed
37. 174 Minimal hero styles scope glass to public hero actions and provide accessible fallbacks Passed

Layout & presentation 24 passed

1. 040 Working tools progressively disclose trust context without dropping review states Passed
2. 051 Configured workspace routes render their intended pages Passed
3. 053 All legal and trust pages use the shared readable document template Passed
4. 054 Legal accordion styling follows the supplied compact grey template Passed
5. 055 Public trust pages state the current data flow without internal control names Passed
6. 056 Healthcare sector exposes authoritative reference framework Passed
7. 075 Curated stock library keeps source pages alongside image ids Passed
8. 092 Working tools and support hubs render complete purposeful surfaces Passed
9. 093 Visible micro-labels use natural sentence case Passed
10. 094 Public site locks the Alle's ClinXAi whitespace and Inter signature Passed
11. 096 Shared document loads Inter and keeps lighter global chrome Passed
12. 117 Closing grey confidence cards fit their text with balanced side padding Passed
13. 131 Finder bars share keyboard search affordances Passed
14. 134 Unrelated top-level page families have distinct structural identities Passed
15. 135 Children under the same parent share their page-family grammar Passed
16. 145 Focused working tools keep restrained top and side gutters Passed
17. 147 Public page families declare deliberate psychological flows Passed
18. 151 Public launch routes avoid skeleton language and broken internal links Passed
19. 162 Publication empty states and topic grids retain neutral surfaces at mobile widths Passed
20. 168 Product finders and actions precede optional explanations Passed
21. 171 Product finders count visible results and recover from an empty search Passed
22. 176 Compact labels preserve source and safety content Passed
23. 203 Shared geometry layer follows legacy styles on every public template Passed
24. 205 Polish preserves native select semantics and accessibility fallbacks Passed

WordPress sign-in bridge 14 passed

1. 232 A valid one-time code returns only the minimum account identifier Passed
2. 233 Identity responses carry a no-store cache policy Passed
3. 234 Sequential replay cannot read the account identity again Passed
4. 235 Only the successful code-consumption request returns identity when requests interleave Passed
5. 236 A failed code deletion cannot issue an account identity Passed
6. 237 A code at the 90-second expiry boundary is rejected Passed
7. 238 A code older than the 90-second lifetime is rejected Passed
8. 239 A future-issued code is rejected Passed
9. 240 A malformed issue timestamp is rejected Passed
10. 241 A code bound to another application client is rejected Passed
11. 242 The callback destination must match the code’s bound destination Passed
12. 243 A missing account is rejected and its code remains consumed Passed
13. 244 Invalid application credentials are rejected before code storage is read Passed
14. 245 Malformed codes are rejected before code storage is read Passed

**Contact**

Email: [care@allesclinx.com](<mailto:care@allesclinx.com>)

**Related policies**

Last updated: 6 October 2026 · Questions or grievances: care@allesclinx.com
