Reference Checker data handling
This notice describes INGOAMPT’s reference-checking component. The hosted checking service is in preparation; the page does not currently accept reference submissions or payments.
When hosted checks are enabled
Submitted references are sent from the website to INGOAMPT’s separate checking server for read-only comparison with a frozen DBLP snapshot. Website sign-in and signed server requests associate checks with your account allowance. The component does not write your references into the DBLP databases.
The usage database stores opaque account identifiers, usage counts, replay-prevention nonces, account links and purchase-entitlement receipts. It does not store the submitted reference text or access tokens. Website jobs retain references and returned evidence in server memory for up to 15 minutes while you retrieve the result. Closing the page does not cancel a running check; restarting the server can make a result unavailable. You can download the returned evidence yourself.
If you select Crossref search, a locally unaccepted reference is sent to Crossref to discover metadata candidates. This option can be left off. Crossref applies its own processing and service terms. External candidates are kept separate from DBLP records and require review.
Using the MCP through ChatGPT, Claude or another host also sends the selected input and tool results through that host. Its account, model and search policies apply separately. WordPress, the identity provider, hosting and payment providers may maintain their own account records and operational logs; this component’s storage description does not claim those services keep no logs.
Do not submit confidential or personal information you are not authorized to share. For a data question or account-data request, use Reference Checker support. Automated account deletion and a verified public ChatGPT release are not offered by this preparation page.
