Privacy notice

1. What is recorded when you visit

When a page is opened, the server writes the time, the requested address, your IP address and your browser type to its system log. It is used only for security and troubleshooting and is deleted automatically after 30 days.

2. Cookies and browser storage

The site sets no advertising cookies, and sets sign-in cookies only when you sign in. Only the following is stored in your browser.

• gsj_lang cookie — remembers your chosen language for one year (a functional cookie).
• gsj_theme — light/dark display setting (browser storage).
• gsj_user cookie — a signed value that keeps you signed in for 30 days; deleted when you sign out, and set only if you sign in (a functional cookie).
• gsj_oauth cookie — a temporary value that prevents forgery during sign-in; it disappears after 10 minutes (a functional cookie).
• gsj_cmv cookie — remembers the numbers of the community posts you viewed recently (up to 40) so a page refresh alone does not raise the view count (a functional cookie).
• gsj_chat_v1 — your chatbot conversation. Stored only in your browser for 7 days and never sent to the server for storage. You can delete it any time with the trash button in the chat window.
• Whether the chat window is open — gone when you close the tab.

3. AI chatbot

When you ask the chatbot a question, the question and a few earlier messages pass through this site's server to Anthropic's Claude API (United States) to produce the answer. This site's server does not store the questions or answers.

To prevent abuse, a hash of your IP address is used only to count questions in server memory; it disappears when the service restarts.

How Anthropic processes and retains what it receives is governed by Anthropic's own policies. Please do not type personal information such as names, contact details or account details. Answers can be wrong, so check numbers on the source pages shown.

4. Measurement submissions

The “Submit your measurement” form collects the following. It does not collect contact details such as email.

• Device name and type, chip, memory, operating system, engine and version, model, quantization, context length, measured speed and token count (optional: power, memory use, the command you ran).
• An evidence image (screenshot of the measurement). Please hide names, accounts or addresses before uploading; images showing them may be rejected.
• A hash of your IP address — used only to prevent abuse such as repeated submissions. Your original IP address is not stored with the submission.

5. How submitted information is used

Evidence images are kept in a non-public area of the server and opened only by the reviewing administrator. Only measurements that pass review (device, model and the numbers) are published, graded as “user-submitted (evidence checked)”; the image and the IP hash are never published. Rejected submissions are not published.

6. Members (sign-in)

Writing posts or comments, recommending and reporting in the community require a social sign-in. Reading needs no sign-in. There is no sign-up with an email and password.

• Google sign-in — you are sent to Google's sign-in page only to prove who you are. This site receives and stores only the account's unique number from Google; it does not request or store your email, name or profile photo. How Google handles sign-in information follows Google's own policies.
• Nickname — you choose it yourself after the first sign-in. It is 2 to 12 characters, cannot match another member's, and when you change it the new nickname also shows on your earlier posts. Nicknames are public, so do not use your real name or contact details.
• What is stored — the sign-in provider, the account's unique number, nickname, time of joining, time of last sign-in, time of the last nickname change, and block status (reason and period). Tokens, authorization codes and secrets from the sign-in process are not stored and not written to logs.
• Signing out and leaving — both are done on the account page. When you leave, the account number and nickname are replaced with meaningless values so you can no longer be identified, and signing in again with the same account creates a new member. Your posts and comments stay under the name “withdrawn member”; if you choose “also delete my posts and comments” when leaving, they are deleted too.
• Blocking — a member who breaks the rules may be blocked. A blocked member can still sign in but cannot write, recommend or report. The reason and period are seen only by the operator.

7. Community (boards)

When you write a post or comment in the community, the following is received and stored. Contact details such as email or phone number are not collected.

• Nickname, title, body and time of writing — posts and comments are public to every visitor. The author is tied to your member account, so when you change your nickname the new one also shows on earlier posts. Do not put personal information such as your name, contact details or address in the text.
• A hash of your IP address — used only to prevent flooding and spam, to stop repeat recommendations and reports, and to block abusive access. The original IP address is not stored with posts or comments and is not published. The member number is recorded for the same purposes.
• Reports — when you report something, the target, the reason, the reporter's member number and IP hash are stored to stop duplicate reports from the same person and for the operator to review. The outcome is not notified individually.
• Deletion — you can delete your own posts and comments while signed in. A deleted post has its body emptied and is shown only as “deleted”. The IP hash and report records needed to prevent abuse may remain after deletion.
• Anonymous posts written before sign-in existed — edited or deleted with the post password set at the time. That password is stored only as a hash, so the operator cannot see it and cannot tell you if you forget it. New posts and comments have no post password.
• If you forgot the password, or want a post containing your personal information removed, tell us with the post's address through a post or video comment on the YouTube channel “GitSeonjeap” (@GitSeonjeap) or the contact method in the channel's About section. We will hide or remove it as soon as it is confirmed.

8. Outside services

The site uses these outside services.

• Anthropic — generating chatbot answers (see “AI chatbot”).
• Google — community sign-in (you go to Google's sign-in page only when you choose to sign in with Google; see “Members (sign-in)”).
• YouTube (Google) — videos load from youtube-nocookie.com only after you press play. Nothing is requested from YouTube before that.
• Cloudflare — handles only the domain name (DNS); site traffic does not pass through it.
• Contabo — server hosting (data center in Japan).

9. Your requests

To view or delete a submitted measurement or image, or to ask about any other information this site holds, contact us through a post or video comment on the YouTube channel “GitSeonjeap” (@GitSeonjeap) or the contact method in the channel's About section. We will handle it as soon as it is confirmed.

10. Children

This site is not aimed at children and does not knowingly collect their information.

11. Changes

If this notice changes, it is posted on this page and the effective date is updated.