Privacy

Previous bookmarks

Individual-work bookmarks have been retired. Previous bookmarks remain private and tied to your account. We store the work reference and when you saved it. They are not public favorites or ownership claims. You can view or remove them in Previous bookmarks. If a work is withdrawn from public view, its details no longer appear there.

Previous bookmarks do not subscribe you to emails, publish a selection, or grant permission to use photographs. Account deletion and other information-removal requests are handled through the contact process below.

Makers you follow

Following is private. We store the maker reference, when you followed, and a count and revision used to keep your view up to date. We also store when For you last loaded successfully, to mark newly documented work on your next visit across devices. This is not a record of which individual pieces you viewed. For you brings together currently public work from makers you follow, including older work. Unfollow at any time in For you or on the maker’s page. Following sends no emails or notifications and does not create a public profile or follower count.

Unfollowing removes that connection. Account-level bookkeeping remains until an account-removal request is processed through the contact process below.

Who runs the site

Death Before Melt is operated by Two Pizzas LLC. For privacy questions or requests, email andrey@twopizzas.dev.

Browsing and signing in

You do not need an account to browse the public archive. Accounts and submissions are for people aged 13 or older, subject to the eligibility conditions in our terms. We do not ask for a date of birth or collect identity documents to verify age.

We use Clerk to manage sign-in. If you choose Google, Google shares basic identity information—your account identifier, email, name and profile image—with Clerk for authentication. Our application uses the authenticated account identifier and session token to keep drafts, follows and previous bookmarks private and check access. We do not request access to Gmail messages, Drive files, contacts or your photo library through Google sign-in.

Clerk uses session-related cookies and storage. Our hosting and infrastructure providers may process technical information such as IP addresses, browser information and request/security logs to operate and protect the service. We use Vercel Web Analytics on public pages to understand visits and clicks that open pieces, makers or collections, or start a contribution or maker verification. Click events use fixed categories, not form contents or account identifiers. We strip URL queries and fragments, exclude account and editing pages, and honor Do Not Track and Global Privacy Control. We do not use advertising trackers.

What you contribute

A contribution can include photographs, piece details, the stamps you can see on the piece, maker information and a note to the editor, which can include links. For photographs, we record your declaration that you took them or have permission to share them for DBM’s public archive once accepted. We record submission and review dates, consent, revisions and review outcomes. If we accept your contributions automatically, we record that, the editor’s private reason, and when it started or ended.

Continuing past the Photos step stores your draft privately and uploads its photographs; the notice beside the button says that continuing confirms you took them or have authority to share them for DBM’s public archive. After that the draft saves as you work. Uploaded photographs stay with your draft and are not published unless you send it and it is accepted, by an editor or automatically for contributors we trust. Choosing a file alone does not upload it. We save the links you include for review without fetching or copying anything from them.

Uploads are processed into full-resolution archival copies with embedded metadata, such as camera details and GPS location, removed. We remove the temporary input after processing and keep smaller copies for display. A HEIC photo is converted to a JPEG on your device before it uploads, which removes that metadata first. Metadata removal cannot remove information visible in a photograph, so leave receipts, addresses and other people’s personal details out of the image.

A photograph attached to a source, such as a certificate, uses the same upload and declaration. It stays private with the source unless an editor records permission to display it. Redact names, messages and other personal information visible in it before uploading.

What becomes public

An editor reviews contributions before publication, unless we accept them automatically from a contributor we trust. Accepted piece details, and the sources they cite with their links and quoted words, may appear in the archive. Your name, contact email, account identity, drafts, messages to editors and original upload files are not part of the public record, and contributions are not credited to you by name.

Photographs shared under the public-archive notice may be published after you send them and they are accepted, credited as a community contribution, on the site and in DBM’s own social media posts, newsletters and ads; public copies are resized and stripped of embedded metadata. The stamps you record, with how they read and the part of a photograph that shows them, may appear with the piece. Photographs attached to sources stay private unless an editor records permission to display them. Not being named cannot remove identifying content visible inside a photograph or material you supply, so review it carefully. A verified maker account publishes details and photographs of its own pieces directly.

Who helps operate it

Clerk provides authentication, Convex stores application records and photographs, and Vercel hosts the website. Cloudflare stores and delivers cached copies of public photographs and maker stickers. Photoroom removes backgrounds from new photo uploads using a metadata-free copy. We retain a private archival copy before background removal. Authorized editors can access contributions, their photographs and sources for review. Service providers process information as needed to deliver their services, including on infrastructure outside your country.

When enabled, Resend delivers operational email alerts to the archive operator. These contain event summaries and links to private review screens, without account identities, private notes, verification codes or photographs. They do not subscribe you to emails.

We use account and contribution information to operate the archive, review submissions, contact you about them, respond to requests and prevent misuse. We do not sell personal information or use Google sign-in data for advertising. We may disclose information when legally required or when necessary to address fraud, security or rights concerns.

We use accepted photographs and piece details to help identify pieces, including with identification tools we build. When you add a photo, we may send it to an AI service to suggest its details; the service processes it for us and doesn’t train its own models on it. We’ll name that service here when we use one. To keep your photographs out of our identification tools, email andrey@twopizzas.dev.

Provider information: Clerk, Convex, Vercel, Cloudflare, Photoroom, Google, and Resend.

Keeping and removing information

Drafts, declined proposals, archival photo copies and review history are kept privately unless removal is requested and processed. You can delete a photograph from a draft before you send it. There is no automatic draft expiry or account-wide self-service deletion. Public removal does not, by itself, delete private archival copies, review history or backups.

To request access, correction, deletion, a change of credit or removal of a photograph, email andrey@twopizzas.dev. Include the relevant page or submission and enough information to locate your account. We may need to verify your connection to it. We handle requests manually and will explain any information we must retain for legal, security or rights-related reasons. Backup copies may remain until the relevant backups are replaced or expire; we do not promise immediate erasure from every backup.

Deleting a Clerk account or revoking Google access does not automatically delete contributions already held in the archive. Contact us to request those separately. You can also revoke Google access in your Google Account connections.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete or receive your personal information, object to or restrict certain processing, withdraw consent, or contact your local data-protection authority. Contact us to exercise a right or ask how it applies to your information. Withdrawing permission does not undo processing that already took place.

We do not offer accounts for children under 13. If you believe a child under 13 has created an account or sent us personal information, contact us so we can address further collection and removal. Previously recorded contribution permissions and agreements remain part of our private consent history. If our practices change, we will update this page and its date; material changes affecting your choices will be brought to your attention where appropriate.