Data Policy

Who operates LIW

Labor Intelligence Works LLC operates Labor Intelligence Works (LIW).

Contact support@laborintelligenceworks.com for support and billing, or privacy@laborintelligenceworks.com for privacy and data requests. These addresses forward to the operator’s designated inbox. Do not include passwords, provider keys or unnecessary case contents in a request.

The case record

A case record can include original uploads, parsed emails and attachments, extracted text, classifications, timelines, analyst annotations, reference documents and generated work product. Original material and derived content are distinct. The existence of an uploaded original does not establish that every page, attachment or embedded object was extracted or analyzed.

Email and attachments

Email processing separates message text, correspondence metadata and retained attachments. A sent timestamp describes the message, not necessarily the events recounted within it. Unsupported, unreadable or omitted material can limit the usable record. Analysts should review the listed messages and attachments and resolve material omissions before treating a review as complete. Re-uploading a file is not permission to overwrite unrelated evidence or silently merge different records.

Record versions and coverage

Analysis is based on the record available to its workflow. Adding, replacing or correcting evidence can make an estimate or earlier output stale. Coverage indicators distinguish processed information from unavailable, failed, skipped or unsupported inputs. A targeted answer uses retrieved passages and must not be interpreted as an exhaustive review of every record. Preserve the original and relevant source locations when correcting extraction or interpretation errors.

Processing stages and approval

Upload and extraction, cost estimation, AI analysis, analyst review and export are separate operations. An estimate is not approval to spend. Approvals must identify the applicable operation and maximum cost. Waiting for analyst approval or additional spending authorization is different from being queued for a worker. A retry must not be assumed free unless the interface explicitly says it only reloads status or performs a nonbillable operation.

AI providers and confidentiality

AI-assisted workflows can send selected text and metadata to the configured external providers described in the Privacy Policy. Masking reduces some identifiers without guaranteeing anonymity. Do not upload information whose confidentiality, privilege, residency or contractual restrictions prohibit that processing. Use any separately agreed restrictions for your organization; ordinary subscription access does not itself establish a special provider retention agreement.

Findings and supporting evidence

Analysts must distinguish allegations, recorded facts, inferences, authority and conclusions. Review material quotations and source locations, conflicting evidence and information gaps. A technically valid citation can still fail to support an assertion. Generated grievance responses, case decisions and recommendations remain drafts until the appropriate analyst has reviewed them; the software does not replace the responsible decision-maker.

Permissions and reference libraries

Case permissions and work-product visibility apply independently of paid-plan eligibility. Reference-library access does not authorize disclosure of another customer’s records. Reusing a document across cases does not automatically share the cases themselves. Library documents and case associations have separate lifecycles; deleting a case should not be treated as deleting every reusable reference document.

Exports

Supported exports reflect the selected record and output version and may include sensitive information. Review the export’s contents, source locators, omitted-material notices and review status before external use. Keep original records and any organizationally required copies. Files downloaded, emailed or stored outside LIW are subject to the recipient’s controls. A generated or completed status does not by itself establish that an output is factually correct.

Archiving, deletion and backups

Archiving, subscription cancellation and permanent deletion are different. Archiving can preserve read access while preventing changes; it does not by itself establish a substantive case closure date. Deletion can involve multiple storage and database steps and must not be assumed complete after a partial failure. Previously downloaded copies, legal holds, audit records and provider backups can remain subject to separate handling. A restore can reintroduce records and requires reconciliation with recorded deletion instructions.

Usage and large records

Processing, storage and access are subject to the limits disclosed for your plan and operation. Large or complex records may require additional time, an approved cost budget or a supported alternative workflow. Missing or unpriced operations should be refused rather than silently treated as free. Record size is not permission to suppress material contradictory evidence or claim complete coverage after undisclosed truncation.

Requests and operational issues

For a missing attachment, stalled job, disputed citation, export problem or data request, begin with the case or job reference and the issue through the published contact method. Do not send passwords or provider keys. Where feasible, retain the relevant original and identify the affected output version. Customer-specific retention, residency, legal-hold or incident obligations require an applicable agreement and verified implementation.

What case deletion retains

The current case-deletion workflow attempts to remove this case’s stored files and database records, checks that the case row is gone, and performs a final sweep for files written during deletion. It can refuse deletion while an email upload holds a live processing lease and can report partial failure that needs a retry. Billing and AI-usage records remain; shared reference-library documents remain while this case’s links are removed; personal workspace notes remain with their author. A successful active-case deletion is not a promise of immediate deletion from backups, provider systems or previously downloaded copies.