Subprocessors & AI Providers

1. OpenAI — active AI document processor

Provider and technology: an OpenAI AI service in a separately isolated shared server worker, authenticated through a server-managed authorization. Purpose: multi-document extraction-assisted review, limited public-resource research, issue identification, complete case-report generation, appeal drafting and creation of the paid ZIP package from which the free preview is derived. Data: uploaded document text or page images, safely extracted archive contents, user description, category and a constrained server-generated instruction. Location: processing may occur in the United States and other locations permitted by OpenAI’s terms.

Configuration: credentials remain only in the shared worker; DenialFight does not intentionally opt in to training or feedback sharing; each review uses ephemeral AI execution and read-only sandbox settings. Public web searches are instructed to exclude user identifiers and sensitive claim details. Actual provider data use depends on the authorized account’s plan and Data Controls. OpenAI may retain safety or abuse-monitoring data under its applicable policy unless an approved zero-data-retention arrangement applies.

2. Google Gemini — planned/conditional AI processor

Provider and technology: Google paid Gemini API or an enterprise Google Cloud/Vertex AI configuration. Purpose if activated: fallback availability, document understanding or quality comparison. Data may include the same document content and instructions sent to the primary AI processor. DenialFight will not use unpaid Gemini API, unpaid AI Studio or a consumer Gemini account for uploaded claim documents because their data-use terms differ.

Status: not active in the current review path. Before activation, DenialFight will validate the paid or enterprise account, contractual data controls, retention, security and lawful transfer basis and update this page if the material processing changes.

3. Google Analytics and Google Tag Manager — active analytics providers

Purpose: optional audience, acquisition, engagement and conversion-funnel measurement, plus consent-state signaling through Google Consent Mode v2. Data may include page URL and title, referrer, campaign parameters, broad device and location information, Google Analytics client/session identifiers and low-cardinality funnel attributes. Completed live purchases are sent server-side with the same consented client identifier so payment-provider redirects do not erase the original acquisition source.

DenialFight does not send uploaded document contents, filenames, claim narratives, contact details or full IP addresses as Google Analytics event parameters. Analytics storage requires an affirmative choice; advertising storage, ad-user-data and ad-personalization signals remain denied. Google Tag Manager is used only to deploy and govern the Google Analytics tag.

3. Other artificial-intelligence providers

DenialFight may add a functionally similar provider—for example Anthropic, Microsoft Azure-hosted AI, Amazon Bedrock or another enterprise document/AI service—only after reviewing its business terms, no-training controls, security, retention and transfer mechanisms. If such a provider will receive identifiable review content, this page and the upload disclosure will identify it before or at the time required by law. DenialFight does not grant permission for a processor to use user documents for its own advertising.

4. Hosting and infrastructure — active

Server, container, networking, TLS, storage, monitoring and backup providers process uploaded files, extracted text, generated answers, IP addresses and operational logs as needed to host and secure the Service. Review data is segregated from application releases and scheduled for active-server deletion within 10 days. Infrastructure providers may maintain limited system or security records under contract.

5. PayPal — active-capable payment processor

Purpose: PayPal wallet checkout, Advanced Credit and Debit Card Payments, payment authorization and capture, receipts, refunds, disputes, fraud prevention and 3-D Secure authentication when required. Data when checkout is started: cardholder name, card number, expiration date and security code entered directly into PayPal-hosted Card Fields, plus order identifiers, review-specific opaque identifiers, IP/device signals and transaction metadata. DenialFight does not receive or store full card numbers or security codes, and uploaded denial documents and generated package contents are not sent to PayPal. PayPal is a payment processor and does not become DenialFight’s merchant of record. Activation depends on PayPal account eligibility, production credentials and webhook configuration.

6. Paddle — payment processor and intended merchant of record

Purpose: hosted checkout, tax calculation, order administration, payment status, receipts, refunds, chargeback administration and fraud prevention. Data when checkout is started: name, email, billing details, order identifiers, review-specific opaque identifiers, IP/device signals and payment information supplied directly to Paddle. Uploaded denial documents and generated package contents are not sent to Paddle. DenialFight receives transaction metadata rather than full payment-card numbers. Status: Paddle Sandbox integration is prepared for development verification and transfers no real funds. Live checkout remains disabled until Paddle completes account approval and production credentials are installed. Live package access will require a Paddle transaction linked to review-specific custom data and a signature-verified completed-transaction webhook.

7. Lemon Squeezy — backup payment processor and merchant of record

Purpose and data categories are substantially the same as for Paddle when Lemon Squeezy is selected: hosted checkout, tax calculation, orders, receipts, refunds and fraud prevention using contact and billing details, opaque review identifiers, provider device signals and payment information supplied directly to Lemon Squeezy. Uploaded denial documents and generated package contents are not sent to Lemon Squeezy. Lemon Squeezy receives checkout data only if it is selected as the active provider and the user starts checkout. Package access requires a review-linked, signature-verified paid-order webhook.

8. Support, email and professional providers

Email, support, legal, accounting, security and incident-response providers may process contact details, correspondence or a limited record needed for the assigned task. Do not email a claim document unless support expressly provides a suitable secure method. Professional advisers are bound by contractual, ethical or legal duties as applicable.

9. Government and user-directed recipients

A court, regulator, law-enforcement agency or other recipient may receive information when disclosure is legally required, necessary to protect rights or safety, or directed by you. These recipients are not ordinary subprocessors and may have independent legal authority. DenialFight does not send an appeal to an insurer through the current review flow.

10. International processing

The Service is directed only to the United States, but providers may operate globally and a U.S. user may submit a European-company denial. Where the GDPR, UK GDPR or Swiss law applies, DenialFight uses an available lawful transfer mechanism such as adequacy, Standard Contractual Clauses, the UK Addendum or another valid safeguard. Foreign-law content in a review does not change the Service’s U.S. market positioning.

11. Provider changes and objection

Providers can change for availability, security, performance or product development. Material new use of identifiable document content will be disclosed through this page, the Privacy Policy and, where required, a new consent prompt. If you do not accept a listed processor, do not upload a document. You may request deletion of an existing DenialFight review, subject to lawful exceptions and processor capabilities.

12. Questions

Questions about a provider, processing location, contract category or retention control may be sent to privacy@denialfight.com. Security questions may be sent to security@denialfight.com. Last updated August 10, 2026.