Skip to content

Say where AI reads what people enter, and never to enter personal information - #90

Merged
NDL3wis merged 1 commit into
mainfrom
feat/no-personal-info-notes
Nov 5, 2026
Merged

NDL3wis merged 1 commit into
mainfrom
feat/no-personal-info-notes

Conversation

@NDL3wis

@NDL3wis NDL3wis commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Why

Some of what people type or upload in JDWriter goes to the AI as is. Structured HRTMS exports are parsed in code first, so only their job content is sent. But free text is sent whole: a description pasted or uploaded into Classify, the role description on the home page, build-page edits and notes, the vacancy form's magic-wand notes, and documents an admin imports. Anything personal in those reaches the AI provider. Users should be told plainly, and Classify in particular should say that it uses AI.

What changed

  • New shared NoPersonalInfo note. It says what the AI reads there, then: "Never enter personal information: names, employee IDs, position numbers, or anything else that identifies a person."
  • Placed on:
    • Classify, above the paste box: "Classify uses AI: everything you paste or upload here is sent to the AI…". The page header now says "AI reads it and matches it to a job class".
    • the home page's "Describe the role" box;
    • the build page, under the intro;
    • the vacancy form, above the narrative questions that have the magic wand;
    • Back end, above the document import.
  • Settings: the two headings in "Who can use JDWriter" are now h2 rather than h3. An automated accessibility scan flagged the page jumping from h1 straight to h3. It looks the same.

Validation

  • Client npm test -- --run: 218 passed. New tests cover the Classify and home-page notes.
  • tsc -b and npm run lint are clean.
  • Lighthouse accessibility (axe) scans, run locally on this branch against the dev server: Home, Classify, Settings, Back end and Descriptions each scored 100. Settings scored 98 before the heading fix.
  • Checked the Classify note visually in a screenshot.
  • Server tests not run, since there are no server changes.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7d4e05ef-7230-4376-b79e-66d5f9d3fef9
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

…er personal information

Classify now says plainly that it uses AI. Every box whose words reach the AI
(Classify, the role description, the build page, the vacancy form's magic wand,
and the admin document import) carries one shared note: never enter names,
employee IDs, position numbers or anything else that identifies a person.

Also fixes a heading-order issue on Settings (h1 straight to h3) found by an
automated accessibility scan.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@NDL3wis
NDL3wis force-pushed the feat/no-personal-info-notes branch from 95c5811 to e431048 Compare November 5, 2026 18:31
@NDL3wis
NDL3wis merged commit c91dfa5 into main Nov 5, 2026
4 checks passed
@NDL3wis
NDL3wis deleted the feat/no-personal-info-notes branch November 5, 2026 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant