Privacy Policy

Effective date: November 8, 2026

Publication scope

This policy concerns the independent Java Tooling Notebook website at dirty-joe.com and messages sent to its editor. The operator does not run the former DirtyJOE application, collect its telemetry or hold its developer’s user records.

The publication provides no code-upload analysis service or developer account system. Readers need not submit a program, repository credential or application dataset to consult the guides.

Technical access information

Serving a page may involve records of the resource requested, request time, internet address, browser details and response outcome. Hosting and security providers can use these details to maintain delivery, investigate faults and respond to abusive traffic.

Necessary operational handling is based on legitimate interests in a functioning and secure publication. Those purposes should not be extended to collecting private source code or profiling the projects a reader works on.

Editorial correspondence

An email contains the sender’s address and information they choose to supply. The operator uses it to understand a reported technical error, assess supporting documentation and reply where appropriate, in pursuit of legitimate interests in editorial accuracy.

Contributors should remove credentials, private datasets and confidential code before sending a message. Material that raises special privacy or confidentiality requirements needs separate assessment rather than routine inclusion in an editorial record.

Cookies and choices

No optional analytics, advertising, affiliate tracking or newsletter registration is enabled on Java Tooling Notebook. Essential storage may support administrative sessions or protective infrastructure within the needs of those functions.

Browser controls allow cookies to be viewed, deleted or restricted, with possible effects on a function relying on necessary storage. A future optional service must explain its purpose and provide applicable consent choices before processing starts.

When consent is the processing basis, a reader may withdraw it at any time through the available controls or by emailing [email protected]. Withdrawal does not alter the lawfulness of processing already completed on that basis.

Providers and references

Hosting, email and security suppliers may process information to perform their services, with access limited to the relevant purpose. Applicable safeguards must be considered if information is handled across jurisdictions.

Documentation sites and software projects linked from a guide are separately operated and have their own privacy policies. External media embeds are not intentionally activated by this publication.

Retention and protection

Technical logs should remain identifiable only while needed for supported operational, security or legal purposes. Correspondence may be retained during investigation of a correction and for a justified record of its resolution.

Records should be deleted or anonymised when those purposes end, unless retention is required by applicable obligations. Reasonable access restrictions and technical precautions help protect information without guaranteeing complete security of an internet service.

Rights and complaints

Applicable law may provide rights of access, correction, erasure, portability, restriction and objection. Send requests to [email protected] with enough context to identify the interaction; proportionate identity verification may be needed before records are disclosed or changed.

Readers can also complain to the relevant privacy regulator or data protection authority independently of contacting the operator. The website is not directed at children under thirteen and does not knowingly seek their personal information; guardians may report a child’s message for appropriate action.

Changes to this notice

New features or changed information practices require review of this policy and its effective date. The Cookie Policy explains storage controls relevant to the publication.