Jev log personal data review

Review a log statement for personal data

Show the logged fields and how the logger or redactor handles them. Check whether personal values reach the output or whether the implementation needs closer review.

log personal data reviewLive API
Try an example

A personal contact field reaches output directly.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Review the log call using supplied field and serializer facts.

Decision rules and labels
ExposedRedacted or nonpersonalReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

The log format alone does not reveal every value it will contain. A nested object or serializer can carry personal fields into output even when the visible message is generic.

Redacted or nonpersonal needs positive implementation evidence. A function name such as safeLog is not enough, and an unknown identifier should remain unknown rather than being declared safe or personal by spelling.

The source semcheck rule asks whether selected log calls write personal data. This original example adds explicit uncertainty handling and uses synthetic fields only; it does not audit a repository or certify a logging system.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for personal data in logs.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Show the logged fields and how the logger or redactor handles them.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Exposed, Redacted or nonpersonal, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Email written directlyExposed97.0%
Verified redactionRedacted or nonpersonal98.0%
Service event onlyRedacted or nonpersonal99.0%
Nested personal addressExposed99.0%
Unknown helperReview94.0%
Ambiguous identifierReview100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Personal data in logs: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing a small log call with known argument types.
  • Testing a documented redactor's output contract.
  • Identifying implementation facts needed before approving a log statement.

Outside this demonstration

  • Treating one clean sample as a system-wide privacy or compliance audit.
  • Pasting real personal records when synthetic data can test the rule.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Is every ID personal data?

No. Its meaning and context matter. This example asks for the supplied field definition instead of inferring it from the name id.

Does the tool run my serializer?

No. It reads the behavior you provide. A real review should verify that description against the actual implementation and tests.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.