Privacy Policy
Evidence files are read in your browser and their extracted text is sent to the configured AI model to produce the requested one-time result. Files are not uploaded as stored objects.
Retention and training
Free explanations save a random result ID, journey ID, result status, the missing dependency, explanation, cited source excerpts, next question, conclusion boundaries, conditional next steps, open questions, hypotheses, ranked evidence items and their information-gain calculations, private reopen path, and creation/update timestamps. A SHA-256 hash of the trimmed input and ranking version are stored to reuse the same saved explanation for repeated submissions. The full input and original files are not stored by this endpoint; generated explanations and cited excerpts can still contain information from your input. Anyone with the private link can view the saved result.
Denial packets are different: we store the submitted denial text, classification, disposition or analysis, generated packet content, result and journey IDs, planned send date, status and creation/update/delivery timestamps. Placeholder-only templates store their generated draft, mode, IDs and timestamps, not a submitted denial. Existing free saved links and downloads do not require email or payment.
Separate packet purchase
Where the separate packet unlock is enabled, its source wording and validated preparation packet are retained before checkout. We store a hash of a private recovery code, the test/live environment, Stripe session/payment references, payment and fulfillment status, and refund observations. Stripe processes checkout; this app does not store card numbers. The private purchase uses a secure HTTP-only cookie; a fresh browser requires the recovery code entered in a form, never a URL. A result ID or a success-page visit alone does not grant access. The purchase flow does not send a packet email. Purchase support stores its protected result reference and the submitted technical message. The operator queue is protected separately; saving a ticket is not proof that an operator has seen it.
Optional packet email
Only if you explicitly consent, we store your email address, consent timestamp and scope, source (wdis-result), and traffic label, and send the generated packet text with TXT and PDF attachments once after generation and saving. We also store recipient address, provider message ID, send status/time and any delivery/failure or receipt status. Provider acceptance is not proof of inbox arrival. This permission is not marketing consent. Without consent no email is sent; your saved link and downloads still work. This app does not use your input as training data.
Support and operational records
The support form stores a ticket ID, your technical-issue message, optional result ID, real/synthetic traffic label and timestamp. It attempts to email the configured support operator with your message and saved result link. Protected purchases require a private recovery credential; that credential is never included in support email. Notification failures are shown to you. Provider acceptance is not proof of inbox arrival. Do not include personal or health information in a support message.
Operational events store random event/result/journey IDs, event names, product/page, timestamps, verdict and evidence hashes, fixed rationales, engine/build version when available, processing duration, evaluation state and usefulness feedback. General page events can also store referral/attribution information. Events are intended to exclude raw evidence and filenames. Server access logs include request IDs, methods, URL paths (including result IDs), response status and timing; application logs can include error diagnostics and delivery-provider details. Query strings and request bodies are not included by the access logger.
Input text is processed by the configured AI provider. If configured, the shadow Acclaimly evaluation hook also receives denial text and packet propositions; it does not block packet delivery. External providers have their own retention policies.
There is currently no automatic expiry or scheduled deletion of saved results, packets, support requests or event records. These remain stored until manually deleted. Server-log and external-provider retention are not controlled by an app deletion schedule, and no fixed retention period is promised. Legacy records may also contain checkout/payment references, refund or retry details and earlier email records. The separate purchase remains closed unless its release controls are explicitly enabled; a test-mode offer is not a live purchase.
Minimize sensitive data
Avoid names, account credentials, health details, or other sensitive personal information. Experimental tool; results are AI-generated drafts. Check them before use.