Cookies, Access and Accessibility Policy
GSQA-WEB-001
Language preference storage
The site defaults to English and may use network-edge country information to suggest a local language in that language, switching only after confirmation. Manual choice takes priority. The gsqa_locale cookie stores the preference for 180 days, not award markets, and cannot change product scope. Use the header to change language or this page to clear that preference.
What clearing a preference does
The language-clear control deletes only gsqa_locale. It does not clear all cookies, close an account, erase applications or feedback, or withdraw report-publication permission. Logout handles the login session; browser settings can manage other browser storage. These actions have different effects.
Accessibility assistance
The site supports use through clear labels, keyboard access, visible focus, text status and suitable contrast. Report images, scans and third-party originals may require additional reading assistance. Report the address, device, action and assistance needed. Accessibility explanations do not replace reports or constitute an unassessed claim of full conformity.
Login sessions
The gsqa_session cookie identifies a login session and relevant account permissions. Its configured duration is seven days and attributes including HttpOnly restrict script access. Logout terminates the current session. Cookie expiry is distinct from removal of account data, case records or expired server rows. Public rules and award searches require no applicant session.
Form session storage
Public forms and the workspace use sessionStorage for request identifiers supporting retries, duplicate prevention and receipt access. This is not an advertising cookie. Retention depends on browser session and restoration behaviour. Clearing it may affect retries or the original receipt access method but does not erase material already received by the server.
Optional technologies and separate choices
Advertising, analytics and other non-service purposes cannot be classified as necessary merely for convenience. Before enabling an additional technology requiring a choice, identify its actual provider, purpose, storage or access, duration and controls and implement the required choice and withdrawal. Clearing language preferences is not an all-site accept-all or reject-all consent manager.
Report previews and external content
Award records use authorised actual files; private reports require account permission. Same-origin previews differ from visiting an external source, which sends a request to another site under its rules. Third-party embeds requiring choice must satisfy the corresponding notice and controls before loading. Embedding an entire external site is not the default report display.
Storage issues and privacy requests
Report unexpected language persistence, logout problems or unusual requests with the page, time and action. Do not provide passwords, session cookies or complete access credentials. Personal-data access, correction or deletion uses the privacy route. Browser storage settings do not establish that all server-side personal data has been handled.
Finding rules and services
Navigation, headings and text links lead to evaluation criteria, award records, document requirements and feedback channels. Reading public rules and searching records do not require a particular app, a telephone call or the purchase of assistance.
Reports and images
Award records are searched by brand, model or award number. There is no product showcase directory, recommendation ranking or default list of winners. Complete verification reports are handled through access-controlled applicant accounts. Award records referring to authorised public material must identify its source, version and publication scope. Requests for text-reading assistance or reports of access problems may be submitted through the contact channels. Assistance text does not replace the original report.
Keyboard and assistive-technology use
Main navigation, forms and report viewers must support keyboard operation and provide clear focus, field labels and error messages. Status must also be described in text. Form errors must identify the specific item while preserving information already entered.
Reporting an access barrier
Where a page, file or action impedes use, describe the problem and assistance needed so that it can be examined and addressed. Accessibility statements reflect actual checks. The website does not claim full conformity with a standard without a complete assessment.
Request accessibility assistance
Identify the page, file or action causing difficulty and the specific barrier. A reply channel may be provided for follow-up. Only information necessary to understand the problem is needed; medical history and award applications are not required.
Changes to storage purposes
Material changes to names, purposes, providers, periods or related requests require updated information and any necessary choice. A preference must not be shown as saved without a functioning control. Refusing unrelated purposes must not block public rules or record searches. Differences between actual settings and this inventory require examination and correction.
Assistance requests and outcomes
Accessibility assistance needs information sufficient to understand the barrier, not medical history or an award application. A reply channel assists investigation and communication, with feasible measures and limits explained for the issue. Supporting text aids understanding but does not rewrite reports or decisions. Source errors follow correction or technical procedures.
Server security identifiers and cookies
The server may generate hashed bucket identifiers from network requests, operations and time windows for abuse prevention, with window-based expiry and cleanup. These are server identifiers, not browser cookies. Not storing full IP addresses for project language preferences does not mean infrastructure processes no network information. The privacy policy covers relevant personal-data issues.
Browser controls and case records
Browser blocking or clearing may affect login, language and retries. Accounts and cases continue according to records actually received and retained; closing a browser is not application withdrawal. Withdrawal, account closure and personal rights use their corresponding routes, with the formal receipt retained.