Skip to content
KeysetDB

Privacy Policy.

This policy explains how KeysetDB handles information when you browse the archive or contribute a keyset, release, or correction.

Last updated:

Browsing the archive

You can browse KeysetDB without creating an account. Requests to the site and its image hosts include technical information such as your IP address, requested URL, browser information, and request time. Hosting providers may process that information to deliver content, maintain operational logs, and protect the service.

KeysetDB uses Vercel Web Analytics to measure page views and aggregate traffic information, including referring sites, approximate location, and browser and device information, without third-party cookies. See the Vercel Web Analytics privacy documentation for details.

The application does not add advertising trackers or session replay, and does not use application cookies or browser storage to build a visitor profile. Search and filter choices appear in page URLs, which may also appear in browser history and hosting logs. The application does not change its behavior in response to a Do Not Track browser signal.

Information you submit

When you contribute, we receive the catalog details, source links, images, credits, contributor name, and any maintainer comment you provide. We use them to review, verify, and maintain the archive. Please avoid including sensitive personal information or information about other people that is unnecessary for the record.

Submissions create a branch, commit, and pull request in the GitHub dataset repository for maintainer review. Your contributor name and maintainer comment are included in that review workflow; a maintainer comment is not part of the public catalog record.

Public contribution credit

Public contribution credit is optional. If you enable it and your contribution is accepted, your display name, public summary, optional profile link, contribution date, and change type may appear in the keyset’s public contribution history.

Accepted catalog information, source and image credits, and images may be displayed publicly regardless of whether you choose contributor credit. Review those fields before submitting.

Service providers & external links

KeysetDB uses Vercel for hosting and web analytics, GitHub for catalog storage and contribution review, and Cloudflare R2 for uploaded images. These providers process information needed to operate those services under their own terms and privacy policies. Processing may take place outside your country.

Uploaded images are processed into web display versions with embedded metadata stripped during server processing. Display versions intended for the archive may be accessible through public image URLs, so do not upload private images.

Read the Vercel, GitHub, and Cloudflare privacy policies. Vendor, source, and profile links take you to independent sites with their own privacy practices.

Retention & your choices

Catalog records and contribution history are maintained as an ongoing archive. Submission details can remain in GitHub commits and pull requests, including after review is complete. Hosting logs and backups are retained according to the providers’ configurations and policies. Removing information from the current page does not automatically erase repository history, backups, or copies made by others.

You can leave public contribution credit off, omit the optional profile link, and avoid including personal information in catalog fields. To propose a correction to information in a catalog record, find the keyset in the archive and use its correction form. The form edits catalog details; it does not directly edit contribution history or delete past submissions. Applicable privacy rights depend on your location.

Policy updates

We will update this page when these practices change and revise the date above. Review this policy before making a new submission.