JRS public website · Data and consent boundaries
Website privacy notice
Public review resources and self-paced training may be read without registration or submission of personal information. This notice covers the site's public contact form, optional named training registration, and consent references on retained research and contributor pages. It does not authorize submission or automated processing of organizational decision records.
General professional contact
The public Contact form requests a visitor's name and reply email, with optional organization, inquiry category and a general non-sensitive message. It sends the inquiry to the existing third-party Formspree service, whose account inbox receives the submission and may forward an email notification to the JRS mailbox. The information is used for responding to that inquiry, not as authorization for marketing, research enrollment or transfer. General contact inquiries are not entered into the JRS research participant ledger; they remain separate from consented study records.
Provider acceptance confirms the form service received a submission; it is not evidence that an email notification reached the intended mailbox. Formspree retention and deletion settings have not been independently verified.
Optional reviewer training registration
The training modules are open without registration. A visitor choosing optional named enrollment supplies a name and email address, and may provide an organization, professional title and an answer to an optional software-related question. The server also records a limited source tag, country code derived from the request, consent values and a timestamp.
The website sends these fields to an existing access-controlled operational contact datastore through the site's server-side registration endpoint, where training registration is distinguished from research enrollment. This uses the site's server-side enrollment endpoint, not the Formspree contact form. The endpoint does not return the registration details publicly. The privacy and access design depends on actual deployed credentials, database permissions and administrator controls; independent production assurance of these controls and the provider's retention/deletion configuration has not been completed.
Enrollment is voluntary. The required contact checkbox covers storage and communication reasonably necessary for the requested named completion record. It does not authorize unrelated marketing or project updates; those would require separate consent. A separate, optional checkbox concerns whether the enrollment record could be transferred with the JRS project to a future successor. That checkbox is not an authorization for commercial sale, public disclosure or release of protected records. No name is published through enrollment. A training completion record is not a professional certification or accreditation.
Training progress and completion. The six module-completion flags and selected training preferences are saved in this browser when local storage is available. They do not synchronize automatically across devices and may disappear when browser data is cleared. All six modules and the locally generated PNG completion record can be used without registration or an email address. Only visitors who have successfully chosen optional named enrollment in this browser are eligible for a separate server-side completion event. The website does not prompt unregistered readers for an email upon finishing the modules. A server-side completion event is marked as sent only after the endpoint confirms acceptance.
Consent references on retained research and contributor pages
Some retained research and contributor pages link to this section as their privacy reference. Their on-screen consent text describes the particular contact, storage and optional attribution choices being requested. A link to this notice does not itself record consent or establish that a submission was accepted. Providing contact details does not by itself authorize public naming, quotations or unrelated marketing. Do not submit case records or personal information about third parties through those forms.
Those historical interfaces may refer to transfer of their records with the JRS project. Their actual data handling, storage permissions, transfer arrangements, retention and deletion settings have not been independently verified for a current production release. Refer to the specific consent choices shown on the page, and use the access, correction or deletion contact below for a question about submitted personal information.
Resource access and site measurement
Public guide and PDF downloads may be counted through the site's existing interaction-event system, including document identifiers and limited technical metadata such as country and user agent. Training also records selected module interactions and optional survey responses through interaction-event requests, even when named enrollment is not used. Some public pages use Google Analytics and page-access or link telemetry. On the public homepage, Resources, Training, campaign initiative pages, publication-edition comparison and organizational-information pages, limited aggregate events may indicate tool or guide navigation, training entry, a first module opening during a page view, campaign entry, navigation to an illustrative example or DRR explanation, and navigation to edition or organizational information. The custom event fields are fixed resource identifiers and public page categories. They contain no names, email addresses, search terms, case details, complete URLs or custom visitor identifiers. Analytics blockers can prevent recording. A click does not prove a completed review, downloaded PDF, unique practitioner or returning user. Do not enter identifying case facts or confidential information in training fields. Download and interaction counts are activity indicators, not proof of actual professional adoption or record review. Research datasets, reviewer records and owner-private dashboards are governed separately.
The public interaction counters may also record a click on a named PDF, movement from either initiative page to an existing free resource, or use of the check's Copy Summary or Print controls. These Google Analytics events use fixed action and resource categories only. They do not include the content of the copied summary, any checkboxes or responses, any file or case text, or a visitor's identity. An event indicates an attempted action, not completion of a review or proof that a resource was used professionally. Where links arrive with ordinary campaign tags, Google Analytics may attribute the visit to a stated outreach channel. JRS does not add recipient identifiers to those links.
Voluntary one-click initiative support
The Right to Know Why and Decisions You Can Defend pages provide optional buttons for expressing support for their stated principles. Clicking does not authenticate a person's role, verify organizational authorization or establish institutional adoption. The browser submits a first-party request to the existing /api/support endpoint. If the request is accepted, the existing interaction ledger records the initiative code, a fixed source label, a two-letter country code where available, a limited user-agent value and the time of the request. No name, email or organization is requested by the button.
The service uses a first-party HttpOnly cookie with a one-character counted marker to limit repeat recording from the same browser and initiative for up to one year. The marker is not a person identifier; activity across different devices or browsers cannot be reliably deduplicated. Historical counts before 13 August 2026 include raw clicks rather than the later browser-based deduplication. The confirmation page states whether the server accepted a new event, recognized a prior browser marker, or could not confirm recording. Aggregate endorsement totals must not be described as unique people, verified organizational supporters, JRS adoption or evidence of improved record quality. Campaign page views are separate from endorsements and may be recorded through the existing Google Analytics configuration, subject to its limitations.
Access, correction and deletion requests
For a question about your own submitted information, or to request access, correction or deletion, contact info@jrsstandard.com. Requests require appropriate verification and review. No universal retention period or guaranteed immediate deletion is asserted while provider settings and governing obligations remain under review.
Limitations and future changes
This notice describes observed website source behavior and current public uses, not an independent privacy audit, formal certification, processor agreement or legal compliance determination. Future controlled evaluations involving decision records require a separately authorized data-flow, retention, deletion and legal review before any such processing begins.