What we receive
The inquiry sends business contact fields and a general review question. Prepared notes are included only when you choose to attach them.
For community banks and credit unions.
How records move and who reviews them.
Keep public inquiries separate from confidential engagement sources.
Four answers before sharing records
Where the records stay
Browser work stays in memory unless you save or export it. Inquiry retry records are stored outside the public website.
Who can see the inquiry
The inquiry goes to the business inbox. Agree the people, providers and access rules for engagement sources in writing before transfer.
When records are deleted
Inquiry retry records become eligible for cleanup after 90 days, when a later inquiry triggers cleanup. Email and backups have separate retention.
The written scope must name the handling route and retention terms for confidential engagement sources. An ordinary inquiry is not that route.
Procurement documents to confirm
Ask about a W-9, a certificate of insurance, security questionnaire answers and an NDA. Confirm which documents apply before contracting.
The written scope names the contracting party, signatory and people doing the review. Provider, access, deletion and exit details belong in that agreement.
This page does not claim insurance coverage or a certification. Use the procurement and source-handling checklist.
Website security concerns
Report a website security concern to info@llmsquared.com. Use general terms; agree a handling route before sending sensitive details.
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 | The fields you enter are processed in browser memory. The method does not submit those records or fetch source links. | Save before closing. Downloads can contain complete inputs. Use approved storage and sharing. |
| Local command package | The command processes chosen 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 entered 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 the records you choose. They do not verify source origin, a reviewer's identity, effective authority or approval.
Browser and local methods prepare records without core access, code execution, financial actions or compliance certification. Read package availability details
Ask for the route before sending the source.
Bring the decision, deadline and accountable owner in general business terms. We agree the workflow, approved sources, review responsibilities and exclusions before work begins.
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.
Agree the confidential route before transfer
The public inquiry accepts business contact details and a general workflow description. Confidential engagement sources require a separately agreed channel, named recipients, approved providers and written retention and deletion responsibilities.
Read the procurement agreement checklist. No public document-upload route is offered.