GrailKey Privacy Policy
Last updated: September 13, 2026
GrailKey (the app also reachable at app.grailkey.com) is an
inventory, grading, and pricing tool for physical collectibles, currently
operated in a closed, single-operator/invite stage. This page describes
what the application actually does with data today. It is written to match
the real, current behavior of the software — not a general template — and
is updated as that behavior changes.
Who operates this app
GrailKey is operated as a single-operator tool: there is no public sign-up,
and accounts are provisioned individually rather than through open
registration.
Information we collect
-
Login credentials. Access is via a passphrase. The
passphrase itself is never stored — only a salted, one-way
scrypt hash of it is kept, and every login attempt is
checked against that hash rather than any stored plaintext value.
-
Optional sign-in via Clerk. In some environments the
app can offer sign-in through Clerk, a third-party identity provider,
as an alternate path to the same account. When used, Clerk issues a
session token that this app verifies server-side; only a single
verified identifier from that token is used, and it is matched against
an explicit mapping to an existing GrailKey account — an unmapped
identity cannot gain access.
-
Photos you capture or upload. Photos of comics or
other collectibles you scan or add are uploaded and stored so they can
be shown back to you in your catalogue.
-
Catalogue and asset data. Item details you enter or
that the app identifies (title, issue, publisher, year, grade,
condition notes) and the pricing/valuation data the app computes for
those items.
-
Listing and marketplace activity. When you choose to
list an item, the item's title, price, and photos are sent to the
relevant marketplace (currently eBay) to create that listing. Actions
you take (list, hold, delist) and their outcomes (listed, sold, ended)
are recorded so the app can show you real historical results.
How your eBay listings work today
Listings are currently published using the operator's own eBay seller
credential, configured on the server — the app does not currently ask you
to connect a personal eBay account, and it does not currently store any
per-user eBay OAuth access tokens or refresh tokens. If GrailKey later adds
a feature where you connect your own eBay account, this policy will be
updated first to describe exactly what is stored and for how long.
Where data is stored
- Your device catalogue view is cached locally in your browser (IndexedDB) for offline access on that device.
- Photos are stored in cloud object storage (Vercel Blob).
- Catalogue, valuation, decision, and listing/outcome records are stored in a hosted Postgres database.
- Some external lookups (for example, pricing and identification data) are cached temporarily in a server-side cache (Upstash Redis) to avoid repeating identical requests. Cached entries expire automatically — cache lifetimes currently in use range from about 24 hours up to 90 days depending on the type of data, after which the cached copy is simply gone and, if needed again, is re-fetched.
Third parties we send data to
Depending on what you do in the app, data may be sent to:
- eBay — to search for comparable listings and, when you list an item, to publish that listing.
- ComicVine — to look up comic identity/metadata.
- PriceCharting — to look up pricing and sales-history data.
- Ximilar — for image-based visual search/verification.
- Anthropic (Claude) — to identify and grade comics from photos, and to power the in-app assistant.
- Clerk — only if you sign in through the optional Clerk path described above.
- Vercel — as our hosting provider, and for cloud storage (Vercel Blob) and caching (Upstash Redis, provisioned through Vercel).
Each of these services receives only the data needed to perform its specific function (for example, an image for identification, or a title/issue for a pricing lookup) and is governed by its own privacy policy.
Retention
Temporary lookup caches expire automatically as described above. Catalogue,
photo, and listing/outcome records are otherwise retained for as long as
your account is active, since the app's core purpose is keeping a durable
history of your items and their outcomes over time. We do not currently
have an automated process that deletes this data on a fixed schedule.
Security
- The site is served over HTTPS.
- Access to your data requires a valid session token; that token is checked, and your ownership of the specific item requested is verified, before any stored photo or record is returned — an unauthenticated or unauthorized request never reaches storage.
- Passphrases are never stored in plain text (see "Login credentials" above).
- Session tokens can be revoked account-wide if a credential is ever compromised.
Your choices
You can ask us about the data associated with your account, or ask us to
correct inaccurate data, by contacting us at the address below.
On deletion: GrailKey does not currently offer an automated,
self-service way to delete all data associated with an account. If you
contact us with a deletion request, we will do what we reasonably can
manually, but we cannot currently guarantee complete or automatic removal
of every stored record. We are disclosing this limitation directly rather
than promising a capability the app does not yet have.
Children's privacy
GrailKey is not directed at, and is not knowingly used by, children under 13.
Changes to this policy
If how the app handles data changes, this page will be updated and the
"Last updated" date above will change accordingly.
Contact
Questions about this policy or your data: privacy@grailkey.com