WikiFix Privacy Policy

No account needed. We keep your documents temporarily to run the check and let you review the report, then delete them. Your text is sent to OpenAI for analysis. We never sell your data or use your documents for advertising.

What you upload

When you run a contradiction check, you submit two documents as pasted text, text-based PDFs, Word .docx files, or a mix of formats. We validate readability and size before payment. For prepaid checks, text is sent to OpenAI only after payment confirmation. We extract the text and discard original uploaded files after extraction finishes, whether it succeeds or fails.

Only upload material you have the right to share. Do not submit anything you cannot authorize for cloud processing.

Where your text goes

Your text is processed by our AI analysis provider, OpenAI, to produce the report. This means:

OpenAI processes the text we send for your check. By default, OpenAI does not use API data to train its models unless the account explicitly opts into sharing.
OpenAI may retain abuse-monitoring logs, typically for up to 30 days, with exceptions such as legal requirements.
We request non-stored responses. This is not the same as zero data retention: OpenAI's own retention rules, including applicable prompt-cache retention, still apply. See OpenAI's data usage controls.

Your document text is never sent to analytics tools, ad networks, or session-replay services.

How long we keep things

Reports: expire 30 minutes after your check completes, or 45 minutes after you submit, whichever comes first. Expired reports are inaccessible immediately. Automatic cleanup runs every 60 seconds and retries failed removals. Closing your browser tab does not delete them sooner.

Normalized document text and report bodies are held in temporary application storage until deletion or expiry. Restarting the service makes temporary reports unavailable. This content is not backed up; temporary storage does not guarantee absolute physical erasure.

What we store in our database: limited service metadata, including random session identifiers, hashed session tokens and IP-based rate-limit subjects, check status, consent records, usage and budget records, discrete feedback, and fixed event counts. First-party events include source categories, bounded error codes and pseudonymous deduplication keys. We never store your document text or full report bodies in our database.

Job and event metadata are kept for 30 days, then removed by scheduled cleanup. Budget aggregates may be kept longer to monitor operating costs.

Deleting your data

Every report from a submitted check has a delete option. Use it to remove a check before automatic expiry. The check becomes inaccessible immediately; temporary-file cleanup is retried if it fails.

Deleting a check does not recall text already sent to OpenAI or remove logs retained under its rules. Limited service metadata follows the retention policy above.

Human audits

Human audits are not currently available. Before offering a $49 human audit, we will publish who can access your documents and when audit working files are deleted, before accepting documents or payment for that service.

Payments

Paid reports and checkout are not currently available. We plan to use Stripe for payments and will publish the applicable payment privacy information and record-retention rules before accepting payment.

What we never do

No customer accounts, customer passwords, or permanent document archive.
We never sell your data or use your documents for advertising.
We do not send document text to analytics or use session-replay services.

Cookies

One anonymous session cookie remembers your session for 24 hours. It supports check access and rate limits. The same session also deduplicates first-party home and sample-view counts. We do not use advertising or third-party tracking cookies.

Contact

This is a local development preview. Operator identity, controlled production domain and support contact must be configured and reviewed before public release.

Changes to this policy

If this policy changes in a material way, we will update the date on this page and note the change on the site.

Last updated: October 5, 2026.