Mask names
Keep structure visible while hiding business identifiers.
privacy
Code privacy must be designed before launch, not patched later.
The formatter is designed with a clear separation between internal training examples and visitor input. Any public launch should make the processing path visible and predictable for the user.
privacy direction
User input stays separate from training examples.Local mode should work without sending code away.Future server mode should explain what is processed.Sensitive identifiers can be masked before processing.
Current local behavior
In this local build, the pages are static files and the formatter runs inside the project environment. The training examples are internal material used to improve visual tracing behavior.
- Visitor input should not be mixed with the internal example list.
- Public deployment should clearly state whether processing is local or server-side.
- Any future account, analytics, or storage feature should be explicit.
Future privacy idea
A privacy-focused screen can mask identifiers before server-side processing. For example, table names, column names, and literal values can be replaced with neutral placeholders while preserving structure.
Preserve shape
Keep joins, clauses, blocks, and nesting useful for tracing.
Explain mode
Tell the visitor exactly which mode is active before formatting.