Privacy Policy
Lane Global Holdings LLC, d/b/a Lane Compliance Systems (“LCS”, “we”, “us”) builds configurable document pre-review software for regulated organizations. This policy explains what we do and do not collect, and how we protect it. The defining fact: the documents you review are processed entirely in your browser and are never transmitted to or stored on our servers.
| Data | Leaves your device? | Linked to identity? | Purpose | Retention |
|---|---|---|---|---|
| Documents you review | No — processed in your browser | — | First-line review, on your device | Not received or retained by us |
| Access key | Yes, at sign-in | To your organization | Authenticate; route to your workspace and role | Until your owner deletes it |
| Organization configuration (owner-set) | Yes | To your organization | Operate the service | Until deleted |
| AI authoring guide text (optional) | Yes, to your chosen AI provider | To your organization | Draft advisory style rules | Per your provider’s terms |
| AI judgment-pass / suggested-edit document text (optional) | Yes — to your AI provider (your organization's shared key, or each reviewer's own browser key) or an endpoint you control | Controlled by you | Optional advisory semantic pass or suggested wording edits | Per your provider/endpoint |
| System-of-record review metadata (optional) | Yes — metadata only, never document text | To your organization | Examiner-ready coverage trail | Until your owner deletes it |
| Operational metadata (IP, timestamp) | Yes, via our host | Not used to profile you | Deliver and secure the service; rate-limit | Minutes (counters expire) |
| Local device storage (session, settings, decisions) | No — stays on your device | On your device | Run the application | Until you clear it |
This label summarizes the detail below. Where a feature is marked optional, it is off by default and only transmits data once your organization turns it on. See our AI Disclosure for exactly how the optional AI features handle data.
1. Documents you review never reach our servers
The review engine runs client-side in your browser. Files you upload and text you paste are parsed, checked, annotated, and scored locally. They are not sent to LCS, are not stored by LCS, and do not pass through our functions. Exported audit records are generated on your device. Because of this design, with respect to the case content you review, your organization is the data controller and LCS is not a processor of that content.
2. What we do process
a. Access-key validation
When a user signs in, the access key they enter is sent to our sign-in function and checked against the owner-managed key store to return the organization, workspace, and role associated with that key. We do not receive a name, email, or password for end users.
b. Organization configuration (owner-set)
An organization's owner may store, through the owner console, the company name, workspace/vertical, an optional internal contact, notes, and a writing-guide. This configuration is stored to operate the service.
c. Optional AI-assisted authoring
If an organization enables the optional “Draft with AI” feature, the writing-guide / SOP text the admin typed (a configuration artifact — not case documents) is sent to the configured AI provider to propose advisory style rules. The provider API key is stored encrypted at rest. For drafting it is used server-side only and is never returned to any browser; it is delivered to a signed-in reviewer's browser only if the organization enables the optional shared-key judgment pass. Organizations that do not enable this feature transmit nothing to any AI provider; an equivalent on-device derivation is available with zero network egress. See our AI Disclosure for a full description of where AI is and is not used.
d. Operational metadata
Our hosting provider processes standard request metadata (such as IP address and timestamp) to deliver and secure the service, including coarse rate-limiting counters that expire automatically. We do not build advertising or behavioral profiles.
e. Optional system of record (review metadata)
An organization's owner may enable a system of record. When enabled, the outcome of a review — findings, the rules and authorities they cite, the reviewer's decisions, deadline statuses, the file's name and a one-way hash, scores, and timestamps — is stored in that organization's tenant-scoped, tamper-evident trail so it can produce an examiner-ready coverage report. The member document itself is never sent or stored: document text, evidence excerpts, and the calendar dates extracted from the file are excluded before anything leaves the device, and the server additionally drops any such fields it receives. This feature is off by default.
3. Information stored on your device
The application stores certain data in your browser's local storage on your device — for example your session, interface settings, and your reviewer decision/activity log. This local-storage data never leaves your device unless you explicitly export it (the optional AI features and system of record in section 2 transmit only the specific data described there, and only when enabled), and you can erase it at any time using Settings → Clear local data in the app or by clearing your browser storage.
4. Cookies and tracking
We do not use advertising cookies, third-party analytics, or cross-site trackers. The application relies on local storage (described above) to function, not on tracking cookies.
5. Service providers (subprocessors)
- Netlify — hosting, content delivery, serverless functions, and encrypted key/configuration storage.
- Anthropic — only if an organization enables AI-assisted authoring, and only for the writing-guide text described in section 2(c).
- Voyage AI — embeddings provider. Used (a) server-side to index your organization’s own policy text (a configuration artifact, never case documents) into a searchable library, and (b) only if your organization enables the optional semantic grounding of the judgment pass, to embed a de-identified query sent directly from the reviewer’s browser — never through LCS — so the most relevant passages of your own policies can be surfaced. Case documents are never sent to Voyage.
These providers process data in the United States. Where required, appropriate transfer mechanisms apply.
6. Retention
Organization configuration and access-key records are retained until the owner deletes them or closes the account. Encrypted AI provider keys are retained until removed by the organization. Rate-limiting counters expire within minutes. Because case documents are never received by us, we have nothing to retain about them.
7. Security
We protect data in transit with TLS and enforce HTTP Strict Transport Security, a strict Content-Security-Policy, and related hardening headers. Stored provider keys are encrypted with AES-256-GCM. Administrative interfaces are credential-gated and rate-limited. See our Security page and security.txt. If we become aware of a security incident affecting data we hold about your organization, we will notify the affected organization without undue delay and consistent with applicable law.
8. Your rights
Depending on your location, you may have rights to access, correct, delete, port, or restrict the processing of personal data, and to object to certain processing. Residents of the EU/EEA and UK (GDPR) and of California (CCPA/CPRA) have these and related rights, including the right not to receive discriminatory treatment for exercising them. We do not sell or “share” personal information. Because end-user case content is processed only on your device, requests about that content should be directed to the organization that operates the workspace. To exercise rights regarding data we hold, contact us using the details below; we will verify your request and respond within the timeframe required by applicable law (generally within 30–45 days). We will not deny, charge differently for, or degrade the service because you exercised a privacy right.
9. Children
The service is intended for use by organizations and their staff and is not directed to children under 16.
10. Changes
We may update this policy; we will revise the effective date above and, for material changes, provide a prominent notice in the application.
11. Contact
Privacy questions: support@lcs-global.com.
This document is provided for transparency and does not itself constitute legal advice.