How JRS handles your information
JRS is a documentation-governance standard, and it holds itself to the same discipline it asks of a record: collect only what is needed, say plainly why, and keep it defensible. This page explains what we collect, how it is stored, the choices you make when you give it, and how to see or delete it.
1. Who we are
JRS (the Justification Review Standard) is operated by Phillip Wikes. For any question about this policy or your information, contact info@jrsstandard.com. This is the single point of contact for access, correction, and deletion requests.
2. What we collect, and why
We collect information only where you actively provide it or where it is needed to run the site. We do not buy personal information, and we do not build advertising profiles. The specific things we collect:
| Training enrollment | If you enroll in JRS training and certification, we store your name, organization, title, and email, together with the consent choices you make on the form. Purpose: to deliver the training, issue a certificate, and, only where you consent, to contact you. |
| Review-study submissions | If you take part in a JRS review or detection study, we store your reviewer code and your reads (determinations and notes) on the records. Reviewer codes are pseudonymous identifiers, not your name. Purpose: to compute study reliability and accuracy. |
| Form submissions | Observation, pilot, and contact forms store the text you enter and the choices you select. Purpose: to respond to you and to record the observation you submitted. |
| Guide downloads | When an Investigator Guide is downloaded through a tracked link, we record which edition was downloaded and a short channel tag identifying where the link was shared (for example, the site or a newsletter). It is a count only, not linked to your identity. |
| Analytics | We use Google Analytics 4 to understand aggregate site usage (pages viewed, general location, device type). This uses cookies and is not used to identify you personally. |
On some pages, free-text fields pass a sensitive-identifier screen in your browser before they are sent, which prompts you to redact personal identifiers such as email addresses, phone numbers or record numbers that do not need to leave your organisation. It does not run on every field. It matches four patterns, it is a prompt rather than a filter, and if you choose to continue your text is sent as written. Treat it as a reminder, not a safeguard, and redact before you paste.
3. The consent choices you make
Where we collect your name, organization, and email, we ask for consent explicitly rather than assuming it. There are two separate consent decisions, and they are deliberately kept apart, because being contactable and being publicly named are not the same thing and should not be priced as one.
The first decision, made with one tick box when you register. The box names the registration terms and links to them, and the panel it opens sets out all three parts in full before you tick it. They travel together because they describe a single relationship: we hold your details, we may write to you, and that record follows the project if it changes hands.
- 1Contact. We may contact you about JRS.
- 2Storage. We may store your details securely for that purpose.
- 3Transfer with the asset. Your record may transfer to a successor organization if the JRS assets are sold or transferred.
Ticking that box does not publish your name. Nothing about you appears on any public page as a result of it.
The second decision, made separately and only if you want to. Appearing on the public International Registry of Supporters is offered on its own, after you already have whatever you came for: the guide is downloaded, the training is open, the diagnostic is running, the endorsement is recorded. It is one click, it is never a condition of any of those things, and if you never click it your name stays private. Where it applies, only your name and organization are published. Your email address is never published.
Both are genuine choices, and declining either costs you nothing you have already been given. The Justification Review Standard itself, the published research, and the site remain free to read and use without registering at all. If you have already made either choice and change your mind, write to us and we will undo it.
You can withdraw your consent at any time by emailing info@jrsstandard.com. On withdrawal we remove you from the public Registry, stop contacting you, and delete or anonymize your record on request. Withdrawing does not affect anything already done while consent was in place.
4. How your information is stored and kept private
Personal information is held in a hosted database with access controls designed so that it stays private by construction, not by promise:
- ·Personal records (enrollment details, review submissions, form text) are written and read only by our server-side functions. The public website cannot read them.
- ·Row-level security is enabled on these tables with no public read access. A request from the public site for this data returns nothing.
- ·Public dashboards show only aggregate counts. Names, titles, emails, and individual answers never appear in any public page or export.
- ·The connection to the site is encrypted in transit.
5. When we share information
We do not sell your personal information, and we do not share it for advertising. We share it only in these limited situations:
- ·Service providers that run the site on our behalf. Every one of them is named below, with what it receives.
- ·A successor organization in the event of a sale or transfer of the JRS assets, for the records of people who registered and ticked the consent box described in section 3. Records held for people who never registered, and records of anyone who has since withdrawn, are not transferred.
- ·Where the law requires it, such as a valid legal request.
The service providers we use
These are the external services that process data for JRS. They are grouped by what they actually receive, because the name of a service and the data it gets are different questions.
Services that can receive data from your visit
- ·Vercel hosts this site and runs its functions, so it processes every request, including your IP address and the pages you open.
- ·Supabase is our database. It holds what you submit, such as enrollment details, study submissions, downloads and the consent choices described in section 3. It also holds things you do not type: which pages and links you open, the country your request came from, and a shortened version of your browser user-agent string.
- ·Anthropic provides the model behind the record review tools. Text you paste into a review tool is sent there to be assessed. The text itself is not stored in our database. On the versioned engine route, some of what the model writes back about your record is kept as programme telemetry, including a short per-condition note and a suggested rewritten version of the passage. That is model output about your record rather than your record. It is kept for 90 days and then removed. What stays is the evaluation record: the date, the five condition statuses, the routing outcome, the run count, the consistency figure and the engine version. The text you paste is never stored at all.
- ·Google Analytics 4 receives your IP address, your browser user-agent and the pages you open, on the pages that carry the analytics tag. This is the service described in section 8.
- ·Google Fonts delivers the typefaces this site uses. Your browser fetches those files from Google when a page loads, and that request discloses your IP address to Google. It happens on nearly every page here, including pages that carry no analytics tag, and it happens whatever choice you make about analytics cookies. Blocking Google Analytics does not stop it.
- ·Formspree relays the form on the pilot page. Whatever you type into that form passes through Formspree.
- ·api.jrsstandard.com is an address on our own domain that three pages try to send to: an observation note on the home page, a selection on the pilot page, and the survey answers in the training. That address is not currently reachable, so those attempts fail and nothing arrives. When one fails, the page hands your answers back to you as a file download instead, and they stay on your computer. We name it because the attempt is real even though the delivery is not.
Services that are not running
These are named because the code that would call them is still in the repository, and because two of them did receive data in the past. Naming a service we have stopped using is more useful to you than quietly dropping it from the list.
- ·OpenAI and Google (Generative Language, the Gemini models) were used in a nightly study comparing how different models read the same material. That study closed on 21 August 2026 and the nightly run has been switched off since then, so neither service currently receives anything. While it ran, the material sent to them was constructed for the study. Based on our review of the code that sent it, it contained no personal data. That is a finding from reading the source rather than a verification of the traffic as it went out, and it is stated that way on purpose.
- ·Resend and SendGrid: email-sending code exists, but the function stops before it reads any credential, so no message is sent and neither service has an account with us in use. They are named here so that nobody finding the code later mistakes it for an active service.
Naming these services tells you where data goes. It is not a statement about the terms we have with any of them, and it is not a statement that any particular legal or regulatory requirement has been met.
Registry members are listed by name and organization, which is what joining the Registry means and what the separate optional button says. Study reviewers are treated separately and more strictly: where a reviewer's name is shown publicly, for example on a named study panel or in a publication, it is shown only with that reviewer's specific approval of the exact wording, and any reviewer may withdraw before publication. Being named reflects participation only and is not an endorsement.
6. How long we keep it
We keep personal information only as long as it is needed for the purpose it was collected: enrollment and certification records for as long as the certification is meaningful or until you ask us to delete them; study submissions for the life of the research record they belong to; and form submissions until the matter they concern is resolved. Aggregate counts and de-identified data may be kept indefinitely because they do not identify you.
7. Your rights
You can ask us to do any of the following with the personal information we hold about you:
- ·Access: get a copy of what we hold.
- ·Correct: fix anything that is wrong.
- ·Delete: have it removed, subject to any record we are legally required to keep.
- ·Withdraw consent: turn off contact or transfer consent at any time.
Email that address and we will action your request. Depending on where you live, you may also have rights under laws such as the GDPR or state privacy laws; this policy is written to respect those rights, and the same contact address serves them.
8. Analytics and cookies
We use Google Analytics 4, which sets cookies to measure aggregate usage. You can block cookies in your browser or use a browser extension to opt out of Google Analytics, and the site will still work. We do not use cookies to identify you personally or to serve advertising.
One thing that opting out does not cover. This site loads its typefaces from Google Fonts, and your browser requests those files from Google on nearly every page here. That request carries your IP address. It is separate from analytics, it is not a cookie, and blocking Google Analytics does not prevent it. It is listed among the service providers in section 5.
9. Children
JRS is a professional tool for organizations and is not directed to children. We do not knowingly collect information from anyone under 16.
10. Changes to this policy
If we change how we handle information, we will update this page and change the date at the top. Material changes to how we use personal information will be reflected here before they take effect.