Personal data or tokens in a URL
Partialmedium severity · reads .ts .tsx .js .jsx .mjs .cjs .pyBeta
URLs end up in server logs, browser history and referrer headers. Marked Partial: confirm the value is real personal data. When Lintsure finds this, it marks it as Partial: it may be fine, depending on context only you can confirm.
What it looks like
A line Lintsure flags in its own test app:
// src/more.ts
fetch(`/api/reset?email=${user.email}`);How to fix it
Send it in the request body or a header instead of the query string.
Through a coding agent, Lintsure suggests the change and waits. Nothing is edited until you approve it.
Controls it relates to
What the framework asks
GDPR Art. 25: Privacy by design and default
Build privacy in from the start, and make the most private setting the default.
Evidence a reviewer may ask for: Design notes showing privacy choices.
GDPR Art. 32: Security of processing
Protect personal data with security that fits the risk: encryption, access control, testing and the ability to recover.
Evidence a reviewer may ask for: Security measures and when they were last tested.
SOC 2 CC6.1: Logical access
Only the right people and systems can reach data. Secrets are protected, passwords are stored safely.
Evidence a reviewer may ask for: Access settings, secret storage and password hashing.
ISO 27001 A.8.11: Data masking
Hide or reduce sensitive data where full values aren't needed, such as in logs.
Evidence a reviewer may ask for: Masking in logs and test data.
Summaries are our own reading of the public texts, not the official wording.
Read more: How to keep personal data out of your logs
Check your code for this
Runs on your machine. Your code is never uploaded.
npx lintsure scanThis rule is in Beta: its mapping to framework controls is waiting for review by a qualified compliance professional. Lintsure is a readiness tool, not an audit or legal advice. A finding, or the lack of one, doesn't make you compliant. Disclaimer