Effective July 27, 2026

Privacy notice.

This notice explains how the independently operated FDADeviceCheck service processes lookup inputs, technical analytics and information submitted through its request form.

Responsible operator

Amaury Covo, operator of FDADeviceCheck.

FDADeviceCheck is an independent Covo Capital project. It is not affiliated with FDA. Privacy and correction requests can be initiated through the site's contact route; include “privacy request” and do not submit patient information, passwords or other sensitive secrets.

Information processed by the service

Lookup inputs

The manufacturer name, FEI or registration number you enter, plus optional country and establishment-role filters, are sent to the FDADeviceCheck API and used to query openFDA.

Technical and analytics data

Hosting providers may process standard request data. Google Analytics is optional and is not requested unless you allow it; after consent, it may process device, browser, page, timestamp and interaction events.

Request-form data

The form requires an email and may include name, company, use case, page URL and the lookup context associated with the request.

Do not submit sensitive data: FDADeviceCheck does not need patient records, health information, government IDs, payment-card data, passwords or confidential technical files to run a public-data lookup.

How the information is used

  1. Run and display the public-data lookup requested by the user.
  2. Measure reliability, errors, result outcomes and conversion activity so the service can be maintained.
  3. Route a submitted request for manual follow-up, a dated record, pilot information or bulk-service discussion.
  4. Protect the service, investigate abuse and retain operational delivery receipts when needed.

No automatic activation: submitting the request form does not itself start a payment, monitoring schedule or subscription.

Service providers and external sources

openFDA

The search criteria needed for the lookup are transmitted to the public FDA API. openFDA applies its own government-system and API terms.

Hosting and optional analytics

The site uses Vercel infrastructure. Google Analytics loads only after opt-in, with advertising signals disabled and IP anonymization requested; each provider applies its own policies.

Request delivery

Submitted requests may be routed through configured email, webhook or internal-notification providers so they can be received and reviewed.

Retention and user choices

Lookup requests may appear in infrastructure logs subject to provider retention settings. Request-form submissions and delivery receipts may be retained for operational follow-up and recordkeeping. To request access, correction or deletion of information associated with your email, use the contact route and provide enough information to verify and locate the request.

Analytics choice: the browser stores only your “granted” or “denied” preference under fdc_analytics_consent. Without a saved choice, the site also respects an enabled Global Privacy Control signal by keeping analytics off. Use “Privacy choices” in the footer at any time to withdraw or change the preference.

Third-party links and changes

Official FDA links and other external sites operate under their own privacy notices. This notice may be updated as the lookup, providers or request flows change. The effective date at the top identifies the current published version.