Privacy

Thingfile is software you run on your own infrastructure. This page covers the thingfile.app website and the project itself. Last updated: 2026-11-11.

Who we are

Thingfile is built and published by Spergs, LLC, a Florida limited liability company. We publish the software. We do not run a hosted Thingfile service, and we have no access to any catalog built with it.

The software (self-hosted)

Thingfile runs on your server. The items you catalog, the photos and attachments you upload, the accounts you create: all of it lives in your PostgreSQL database and your object store or disk. None of it reaches us, because there is nowhere for it to reach: the software has no telemetry, no phone-home, and no account with us.

If you run an instance for other people, you are the data controller for whatever it holds, and the obligations that come with that are yours rather than ours.

One thing to know before you enable image scanning

Thingfile's scan feature finds the separate objects in a photo and then asks a language model to name and categorise them, and to read any printed details off the item or its box. It sends a scaled-down copy of the whole photo along with the cropped regions. That call goes to Anthropic's Claude, from your server, using your credentials, so those images leave your infrastructure and are processed by a third party under whatever terms you have with them.

It is opt-in by construction: scanning only happens when someone actively uses it, ordinary uploaded photos are never sent anywhere, and an instance configured without those credentials falls back to local detection with generic labels. If you are running Thingfile for other people, this is the part worth telling them about.

Prices, deals and phone alerts

The pricing side talks to two outside services, and only when you use it. Saved searches go to eBay's Browse API, from your server with your eBay developer keys: eBay sees the search words and filters, never your catalog. Listings that come back are kept no longer than eBay's licence allows. The sold prices you record are yours and stay on your server.

Deal and bid alerts reach your phone through Expo's push service and Google's Firebase. A push carries the listing's title, its price and score, and the search's name. Nothing about your account or your items goes with it. A phone that never turns notifications on is never registered.

Connected apps and AI assistants

A key you make under Connected apps lets that software read your catalog, or add to it if you chose that. Where the data goes next is up to the software you gave it to. The MCP server runs on your own machine and never changes your items; but an AI assistant using it will pass what it reads to whoever runs that assistant's model, under your terms with them.

This website (thingfile.app)

A static site. No analytics, no tracking cookies, no advertising, and no third-party requests at all. It is HTML, CSS and two images, every one served from this domain. Standard server access logs are kept for operating the site and are not used to build a profile of you.

External links (the notdsk credit in the footer, for one) go to sites with their own policies.

Changes

If this policy changes we will update the date above, and anything material will be called out on this page rather than summarised as "we updated our privacy policy".

Questions

Spergs, LLC
privacy@spergs.com