The one part of this
that is not imaginary.

What the forms collect

The reunion form collects the sock's name and how it was found, plus optional tribute reference, discovery date or description, photograph link, and alias. It also asks for confirmation of the report and permission to edit and publish it. Reports go through Web3Forms to the owner's private inbox for review. An approved update may include these details and a photo; submitting a report does not automatically change the public tribute.

The tribute form asks for a sock's name and its story. You can also add when it was last seen, a link to a photograph, an alias to publish alongside the tribute, and a tick in the box requesting an invented obituary. The name, story, and permission to edit and publish are required.

• No email field. The tribute and reunion forms do not ask for your address. If you email the owner separately, your address is included with that message.
• An alias is optional. Leave it blank and the tribute publishes anonymously.
• Anything you type goes to a person. Please keep other people's names, addresses, and private details out of the story.

Delivery runs through Web3Forms, which processes the form fields, delivers them to the owner's private inbox, and performs spam checks. Its current policy describes server logs, including IP addresses and browser details, and retention of submission data for up to three years, unless the plan provides a shorter period or the data is deleted earlier. Its infrastructure and spam-check providers may also process this data, including outside your country.

The owner deletes submissions from the inbox after reviewing them. Approved public content is kept separately in the site's files; raw submissions are not published there. Deleting an inbox message does not automatically delete copies held by Web3Forms or an AI drafting service. You can request deletion using the contact details below.

What becomes public

If a tribute is published, the public version can include the sock's name, the story after editing, the last-seen note, a photograph, and the alias you chose. The memorial edits freely, so the published wording may differ from what you sent.

Published tributes are publicly accessible and may be indexed by search engines. They may later be edited, archived, or removed. Other people can screenshot them, archive them, or quote them. Removing a tribute from this site cannot pull those copies back, so please send only details you are comfortable making public.

Invented obituaries and AI

The form has a box you can tick to request an invented obituary. If you tick it, the owner may use ChatGPT, provided by OpenAI, to draft from the sock's details or photo, then edit the result personally. This is a manual step; the website does not send submissions to ChatGPT automatically. Information used in that chat is processed under OpenAI's privacy policy and the account's data settings. Deleting the submission email does not delete the ChatGPT conversation.

Leave the box unticked and your own words are used, with light editing for length and clarity.

Photographs

Photographs arrive as links, so nothing is uploaded to this site directly. If a tribute is published with a photo, a copy of that image is saved and served from the memorial's own files. The original link is not published.

• Share the single photo, not a whole album or a folder that keeps updating.
• Send only pictures you took or have permission to share.
• Faces, house numbers, and documents in the background are worth checking before you send.

What your browser keeps

Leaving a little love on a tribute saves a mark in your browser's local storage. The heart feature does not send that mark to a server or create a shared count. Other visitors cannot see it.

Clearing your browser's site data removes those marks. If storage is blocked or full, a mark lasts only while the current page remains open; reloading clears it. In private browsing, storage lifetime depends on your browser. The rest of the site keeps working.

The Prevention checklist has no site code that saves or sends its ticks. Your browser may restore them when you return to the page.

Analytics

Every page includes Google Analytics 4 and Ahrefs Web Analytics. Our host also adds Cloudflare Web Analytics to the pages it serves. These scripts are requested when the page opens, without a consent prompt or a site-level opt-out control. Browser settings and blocking tools may prevent them from loading.

Google Analytics 4 measures visits and can use cookies to distinguish browsers and sessions. It processes information such as page URLs, referring sites, device and browser details, and approximate location. Depending on the property's settings, Google's enhanced measurement can also record interactions such as scrolling, outbound clicks, and form starts or submissions. The site's form code sends entered details to Web3Forms, not to an analytics endpoint.

Ahrefs Web Analytics measures aggregate traffic and referring links. Ahrefs describes this service as using no cookies or persistent identifiers.

Cloudflare Web Analytics uses a browser script to measure page views and how quickly pages load. These measurements are sent to Cloudflare. Its Web Analytics documentation describes the service, and its privacy policy explains its data handling.

These services help us understand whether people find the site and how it performs. Google's Analytics opt-out browser add-on applies to Google Analytics; it does not disable Ahrefs or Cloudflare analytics. Google explains its side in how Google uses information from sites that use its services, and Ahrefs explains its own in the Ahrefs privacy policy.

Hosting and fonts

Cloudflare Pages serves this site. Like any web host, Cloudflare processes the requests that deliver each page, including IP addresses, and uses them to keep the site up and to block abuse. Their terms are in the Cloudflare privacy policy.

The two typefaces load from Google Fonts. When your browser requests those files, Google receives your IP address and request information. Google explains its handling of font requests in the Google Fonts FAQ.

Advertising

The site currently has no advertising code, donation widget, or payment form. No advertising provider has been selected.

Removing or changing a tribute

To request a correction or removal of a tribute, photograph, reunion update, or your submission details, email [email protected]. Use a subject such as "Removal request" or "Correction request".

Include the sock's name or a link and explain what you would like changed or deleted. If the tribute has not been published, include roughly when you submitted it. You do not need to submit another tribute to contact the owner.

The owner reviews requests personally and may ask for enough additional detail to identify the record or clarify your connection to it. Please do not send identity documents or other sensitive personal information.

Removing something from this site cannot remove copies held by other people, search engines, or archive services.

Contacting the owner

For questions about this page or a problem with the site, email [email protected].

If you email, your email address, message, and any attachments arrive in the owner's private inbox and are used to handle your request. Contact messages are not published as tributes. Keep your message limited to the details needed to explain the question or problem.

Things this site does not do

• No mailing list. Emailing the owner does not subscribe you to anything.
• Nothing is sold, traded, or handed to a data broker.
• No accounts, no passwords, no logins of any kind.
• No public gesture totals, leaderboards, or visitor profiles.

The memorial is run by one person in the United States as a hobby. You can contact the owner at [email protected].

Changes to this page

When the site adds something that touches your data, such as a new submission service or a donation link, this page changes first and the date at the top moves with it. There is no notification to sign up for, so the date is the thing to check.