Security and data handling
Know where each kind of input goes.
Website requests, browser processing, local packages, assistant providers and institutional engagements have different data routes. Choose the approved route before supplying a source.
Processing routes.
| Route | What happens | What remains your choice or must be agreed |
|---|---|---|
| Website visit | The host serves static pages and files. Hosting and network providers may keep ordinary request logs. | Do not put confidential source text in page addresses or ordinary inquiry email. |
| Browser method | Explicit inputs are processed in browser memory. The method does not submit those records or fetch supplied source references. | Save before closing. Downloads can contain complete inputs. Use approved storage and sharing. |
| Local command package | The command processes explicitly selected local inputs and writes explicitly selected outputs. | Check the package instructions, local permissions and files you select. A local method does not activate an assistant. |
| Assistant client or provider | If you supply a file or record to an assistant, the chosen host and model provider may process it under their account terms. | Approve that account and route before sharing. Local helper execution does not make the surrounding conversation local. |
| Institution engagement | Sources, access, storage, providers, correction handling and deliverables depend on the agreed engagement. | Confirm the specific route, confidentiality, recipients, retention, destruction and exit terms in writing before transfer. |
Keep restricted inputs out of public methods.
Do not supply credentials, account numbers, Social Security numbers, card information or customer and member nonpublic personal information. Use fictional, public or properly redacted records that your institution permits.
The methods do not automatically redact sources or independently verify your source permission. Review a complete export before forwarding it.
Saving and retention.
Tool entries remain in memory until you leave or reload. The optional scope notes can be saved on this device by explicit choice; delete them using the notes control. Saved files remain where you put them and may contain all supplied text. The public methods do not create an account, application database or cloud history.
Standard hosting and email-provider processing remains separate. No universal log-retention or confidential-engagement destruction period is promised here; ask for the actual provider and written handling terms relevant to the proposed work.
Website and inquiry choices.
This site contains no advertising trackers, marketing pixels, session replay or third-party analytics. First-party aggregate counts contain event names and fixed page paths, separate from short-lived abuse fingerprints. Private notes remain local unless you explicitly attach and send them. The separate short inquiry form sends the fields you confirm; an email-draft action remains your separate choice.
Use a general description for the first inquiry. A reply or ordinary email does not by itself create a confidential source-transfer route.
Read the current privacy policy Read review responsibilities
Evidence fingerprints have a limited purpose.
Fingerprints compare supplied records. They do not verify source origin, a reviewer's identity, effective authority or approval.
These methods do not connect to a core, execute institution code, take financial action or certify compliance. There is no production remote MCP endpoint, and Grok web or remote connectors are unavailable here.
Ask for the route before sending the source.
Bring the decision, deadline and accountable owner in general business terms. We agree the workflow, permitted sources, review responsibilities and exclusions before work begins.
Scope and fee are fixed in writing after one working session.
Prepare a scope request or email info@llmsquared.com. Do not attach confidential sources to an ordinary inquiry.
How the inquiry reaches us.
The server accepts a short general business inquiry with explicit consent, then sends the team message and an acknowledgment. A reference identifies the request. Acceptance by the mail transport is separate from inbox arrival and meeting confirmation.
Private inquiry retry records are stored outside the public site. After 90 days they are eligible for deletion at the next cleanup-triggering request. Email and provider backups have separate retention. Read the exact handling and deletion choices.