1. Information we receive
- Submission content: pasted or locally extracted legal text, citations, quotations, research questions, selected jurisdiction, opaque document identifiers, file types and sizes, page or location ranges, and any facts or names contained in the text.
- Generated research data: extracted citations, source matches, candidate cases, snippets, source excerpts, rankings, audit labels, scores, and packet selections held in your browser during the page session.
- Technical and usage data: IP address, request time, route, browser and device information, response status, security signals, and service diagnostics that hosting or network providers ordinarily process.
This beta has no user accounts, payment flow, advertising tracker, or application document database. The site does not intentionally log request bodies. A process-local abuse limit temporarily holds a truncated hash derived from an IP address and a request count for approximately ten minutes; individual server instances may end sooner.
2. How a research run is processed
Document intake. When you select a supported file, locally served code reads it in your browser and extracts text before submission. For a PDF page with a missing or suspicious text layer, the browser may render that page into temporary memory and run a locally served Tesseract.js OCR engine and English language model. The original binary, rendered page image, and filename are not intentionally uploaded or sent to an OCR provider. The application sends the extracted or OCR-recovered text, an opaque document identifier, file type and size, and available page or character ranges to our Vercel-hosted function. Your browser uses the opaque identifier to display the filename locally with returned findings. Removing a file before starting a run excludes it from that submission.
Citation audit. Our Vercel-hosted function receives the extracted or pasted submission and detects citations across it. Depending on the available retrieval path, CourtListener may receive bounded text containing citations or individual citation searches; historical citation details may be sent to the Caselaw Access Project; and the official Florida Courts opinion archive may receive a bounded Florida case-name or docket search. TypeSafe receives isolated propositions and context, case metadata, and retrieved opinion evidence needed for Jev to classify support and attribution. The workflow attempts eligible claim-bearing citations within operational limits; missing sources, interrupted work, and provider limits can prevent a completed model audit. Each result identifies its status.
Authority research. CourtListener receives up to the first 2,000 characters of the research query plus the selected court filter. TypeSafe receives the research query and candidate metadata/snippets for ranking. For the strongest candidates selected for automatic source audit, TypeSafe also receives retrieved opinion evidence and related metadata.
Broader-web citation checks. For unresolved or conflicting case identities, TinyFish Search may receive the extracted case name and reporter citation. This path does not send the uploaded file, its filename, the full submission, or the claim being evaluated. Case names can still identify people or organizations mentioned in a submission. Search queries and unverified result links may be displayed with the audit; these results do not by themselves verify a case or establish fabrication. Repeated references to the same case share a search result within a run.
Results return to your browser over HTTPS. The “Copy packet as Markdown” control writes only the authorities you select to your device clipboard when you click it. Packet selections are not intentionally stored by the application after the page session.
3. Why we process information
We process information to provide requested research, retrieve sources, rank and audit candidates, show progress and counts, prevent abuse, secure and troubleshoot the Service, comply with law, and enforce the Terms. We do not sell submission content or use it for advertising. LegalJev does not keep a training dataset or train or fine-tune models with your submissions. Processing by our AI and search providers is governed by their policies and our applicable agreements; this is not a guarantee about every provider’s independent practices.
4. Service providers and legal-data sources
- Vercel hosts the site and functions and processes network, request, security, and operational information.
- TypeSafe AI provides Jev model processing. TypeSafe’s own policy and our applicable agreement govern its processing and retention; review those policies before submitting information.
- CourtListener / Free Law Project provides case search, metadata, citation resolution, and opinion passages.
- Caselaw Access Project may provide bounded historical case and opinion evidence.
- Florida Courts may receive a bounded case-name or docket query and provide an official Florida DCA opinion PDF when the general providers do not supply one.
- TinyFish provides broader-web discovery for public case-name/citation queries when case identities cannot be resolved or conflict. Search leads are not automatically accepted as opinion evidence.
Linked courts, government sites, and other sources have their own practices. Providers may keep technical logs or input under their policies, contracts, security needs, and legal obligations. Do not treat this Notice as a promise that third parties retain no data.
5. Retention
LegalJev does not keep saved copies of your documents, pasted text, research questions, audit results, or generated packets. There is no application content database or saved account history, and the app does not intentionally log submitted text. We cannot restore previous work from a saved history. Copies you make, such as clipboard exports, remain under your control.
This no-saved-content design does not eliminate temporary processing or technical records. Original selected-file data and extracted text may exist in your browser memory during the page session; submitted text and metadata exist in server and provider memory while a request runs and are returned to your browser. Hosting and provider logs, backups, security records, and legally required records may remain under each provider’s retention practices. We keep any operational information we control only as long as reasonably needed for the purposes above, legal compliance, disputes, and security.
6. Cookies, analytics, and browser signals
This beta does not set application cookies and does not load an advertising or audience analytics script. Because no sale or cross-context behavioral advertising occurs, there is no sale/share opt-out flow. Browsers do not provide a uniform “Do Not Track” standard; this site does not change behavior in response to DNT. If our practices materially change, this Notice and the interface will be updated before the new collection begins where required.
7. Security and confidentiality limits
We use HTTPS and scoped server-side credentials, keep provider API keys out of browser code, and parse supported files locally before sending extracted text. Browser-local OCR can still produce materially incorrect text, including incorrect names, quotations, reporter citations, and pinpoint pages. Local extraction does not make the submitted text confidential. No parser, transmission, storage, provider, or security measure is perfect. We cannot guarantee complete extraction, confidentiality, security, deletion, privilege, or that unauthorized access will never occur. The safest control is not to select or submit sensitive material to this public beta.
8. Your choices and requests
You choose whether and what to submit. You can omit names and identifying facts, ask the browser to stop a running request, close the page, or avoid the Service. Cancellation cannot recall content already sent to a provider, and in-flight provider work may finish. Because the beta has no accounts or application content store, we generally cannot retrieve a past submission for you. For access, correction, deletion, or privacy questions about operational information we control, contact the service administrator through the channel by which you received access. We may need to verify your request and may retain information where law permits or requires. You may also contact a listed provider about data it controls.
9. Children and international use
The Service is not directed to children and is limited by the Terms to users 18 or older. Do not submit information about a child. The Service and providers may process information in the United States and other locations where they operate; those laws may differ from the laws where you live.
10. Legal disclosures and changes
We may preserve or disclose information when reasonably necessary to comply with law, legal process, or valid government requests; protect rights, safety, and service integrity; investigate abuse; or support a merger, financing, reorganization, or service transfer subject to applicable safeguards. We will post revisions here with a new effective date. Material changes affecting a research run will be paired with updated notice or renewed acknowledgment where appropriate.