What you type is the product's roadmap. Queries are logged, and unanswered ones join the public-facing demand queue that decides what gets built next. Don't type anything you wouldn't want kept.
What we log, exactly. A drill that comes up dry is kept word-for-word — that's the demand queue above. One that grounds writes only call metadata — which domain, which verb, hit or miss, cached or not — never your text, and never the answer served.
Questions ride through a routing model. Question-shaped queries are sent to OpenAI (the small router model named in the header) to pick which records to drill. Answered questions are cached — your wording included — so repeats are instant.
Your email is only taken if you give it (the "notify me" form on a dry hole), and it's used for exactly that: telling you if the thing gets covered. No lists, no marketing.
A "want this?" click on a gap row records exactly that row — the domain plus the gap's own subject line, nothing you typed, no identity. It's the anonymous ask that moves the row up the fill queue.
Operational logs (IP-based rate-limit counters, and access rows at the web-server layer holding your IP plus a truncated copy of the request) exist to keep the service up and free. No accounts, no ads, no third-party analytics or trackers; a little localStorage for your UI preferences.
Reference, not advice. drillable serves recorded, cited reference material — verified where marked. It is not medical, legal, financial, or professional advice; supplements, acupuncture, and insurance-denial records especially are information about what sources say, not recommendations to act on.
As-is. Verification means a record was checked against the named independent source at the time marked — it is not a warranty. Dry holes and corrections are features.
Sources keep their rights. Records cite and point at their sources; quoted facts belong to their owners. If something here oversteps a source's rights, email and it will be fixed.
Be reasonable. Rate limits are enforced; agents are welcome through the MCP endpoint within them. Abuse gets blocked.
Who runs this. drillable is operated by Drillable LLC, an Illinois limited liability company, and these terms are governed by the laws of the State of Illinois.