Privacy notice

This notice describes the data JQJ currently uses.

Accounts and content

Registration uses a username, display name and password. Passwords and recovery keys are stored as one-way hashes; a newly generated key is temporarily held in your server-side session until you confirm saving it. Profiles, submissions, bookmarks and reports are stored in the site database. This release does not collect email addresses or send email. If you sign in with a social account, you leave this site to authorize there. JQJ stores only the account id and nickname that come back, so it can link the account and sign you in again. Access tokens are not stored. The first time this creates an account, it has no password and you receive a recovery key.

Letters to the Junction

The Junction letter box stores the name, category, message and follow-ups you choose to provide, plus the time sent. If signed in, the letter is linked to your account. Letters and replies are visible to the sender and site administrators. They are not public and no email is sent automatically. Anonymous visitors use a receipt ID and access key; only the access-key hash is stored. Anyone holding the complete receipt can read that letter, so keep it private. Do not include passwords, recovery keys or other secrets.

Workshop projects and local drafts

Tool settings are saved in this browser; clearing site data removes local drafts. Projects you explicitly save while signed in store their name and settings in our database. They are accessible only through your account and can be deleted. Icons, share cards and typography files are exported in your browser; local files are not uploaded.

What is public

A Junction submission copies the settings of any project you attach when you submit it. Only the approved copy becomes public; later changes to your private project do not change that published copy. Approved entries, display names and publication times are public, and may appear in RSS readers and search engines. Drafts, recovery keys, account settings and bookmark lists are private. Do not include confidential information in submissions.

Cookies and operational records

Cookies support sign-in sessions, CSRF protection and language preferences. There are no advertising trackers. Request IP addresses are used for rate limiting; rate-limit identifiers are hashed with a site secret and periodically cleared. Server access logs support troubleshooting and security.

Your choices

You can update your profile, remove bookmarks, unpublish entries or deactivate your account. Deactivation hides public entries and clears bookmarks. Administrators can handle further deletion requests through site administration; backup copies age out with the backup retention cycle. Copies already fetched by RSS readers or search engines may remain after an entry is unpublished.