Home / Trust pack for law and title offices
Trust pack for law and title offices
What this page is. The terms and facts a law or title office usually asks for before it puts client files near new software: who owns the data, where it lives, who can see it, how it is protected, and what happens when you leave. It is written by LLPRO LLC, the company that makes and runs LLPRO Business (called Edge360 until 20 Nov 2026), in plain words. It is not legal advice and it does not tell a lawyer how to meet a professional duty. A licensed attorney has not read it yet. To receive it as a signed agreement, write to support@llpro.ai.
Quick view: 1 Data processing agreement · 2 Security summary · 3 Confidentiality of client files · 4 Lawyers' duties when using AI · 5 What we have not done
1. Data processing agreement
Parties and roles. The customer is the office that installs or uses LLPRO Business. LLPRO LLC, a Wyoming limited liability company (30 North Gould Street, Suite N, Sheridan, WY 82801), is the processor: it handles customer data only for the customer, only to provide the service the customer asked for.
The customer owns the data. Every record, document, finding and decision in the customer's LLPRO Business, and every file the customer gives LLPRO LLC for a service, belongs to the customer. LLPRO LLC gets no rights in it beyond what is needed to provide the service. We do not sell it, we do not use it for advertising, and we do not use it to train any AI model.
What LLPRO LLC does and does not receive. LLPRO Business is installed on a computer or server the customer controls. LLPRO LLC does not receive the customer's database and receives no usage data from it. LLPRO LLC handles customer data only when the customer hands it over: for example files given to us during setup or an operating service, or an attachment sent to support. That is the data this agreement covers.
- Instructions. We use customer data only as the customer tells us, in writing (an email is enough), and only to provide the service.
- Who sees it. Only the people and software agents working on that customer's service, and only while the work needs it. Each is bound by section 3.
- Other companies. We hand customer files to no other company, except one the customer chooses. The companies we use for other things see no client files: Cloudflare (website traffic), Stripe (card payments), Resend (licence emails). If the customer turns on Claude, the text of each request goes to Anthropic under the customer's own terms with Anthropic; that is the customer's choice, it is off until switched on, and it is explained in the LLPRO Business privacy policy, sections 3 and 5.
- Security. The measures in section 2.
- If something goes wrong. If customer data we hold is acquired by someone who should not have it, we tell the customer promptly, without unreasonable delay, so the customer can meet its own duties; Louisiana residents are notified as La. R.S. 51:3074 requires. If we find a defect that has exposed, or is likely to expose, data on the customer's own install, we tell the customer too.
- Help with requests. If someone asks the customer for access to or deletion of their information, we help find what we hold, within 30 days of the customer asking.
- Deletion on exit. When the service ends, or when the customer asks in writing at any time, we return what we hold (a readable copy, delivered the way the customer chooses), then delete our copies, including copies in our backups, within 30 days, and confirm in writing. The software on the customer's own machine is the customer's to keep or remove: Export makes a full readable copy at any time; Remove takes the software off and keeps the data; deleting for good is the customer's own command. We keep only what the law requires, which is billing records for seven years, and a short log that we handled files (dates, what kind, who authorised it) with no file contents.
- Proof. On request we show the customer what data of theirs we hold and where.
2. Security summary
Where the data lives
- On the customer's own machine. Either the office's own Windows computer (the recommended install) or a cloud server the customer opens in its own cloud account. LLPRO LLC has no account inside the install and no login to the customer's server.
- Nothing is sent to LLPRO LLC. No copy of the database and no usage data. A licence check reads a file on the machine and makes no network call.
- What leaves the machine, only if the customer turns it on: Claude through the customer's own Anthropic key or app; a mail, bank or accounting connection; a cloud server the customer chose. Each is off until switched on and can be switched off again.
- Files we are handed (section 1) are kept on servers LLPRO LLC controls in the United States.
Encryption
- On the Windows install the records are encrypted on disk. The build checks this and fails if it is not true.
- Sign-in secrets for connections (for example a mailbox app password) are encrypted before they are written, and are not kept in a settings file.
- On a cloud server install the software does not encrypt the records by itself, so we ask the customer to turn on the cloud provider's disk encryption.
- Website traffic is encrypted in transit (HTTPS).
Access
- On the Windows install the program listens only on that computer (127.0.0.1). Nothing else on the office network can reach it. On a cloud server it listens only on the server and is reached through an SSH tunnel.
- Sign-in is a long access token, never put in the web address or a cookie; a wrong one is refused. The program does not run as an administrator account.
- LLPRO Business proposes and the owner decides: every kind of action starts switched off, money, contracts and hiring always go to the owner, one switch stops everything, and every request through the Claude connection is logged.
Keys: LLPRO LLC does not hold them
- The encryption key and the access token live on the customer's own drive or server. LLPRO LLC never holds a customer's passwords, access token or encryption keys.
- By default the key sits in a separate file in the LLPRO Business folder, readable only by its owner account, so copies of that folder need to be kept as safe as the machine itself.
Backups, updates, problems
- Backups run every hour on the machine (168 kept) and the risk scan every 6 hours; the health page turns "degraded" if either stops.
- Packages are signed and published with a checksum. Every reported or self-found flaw is kept in a register that ships with each package.
- To report a security problem write to support@llpro.ai with the subject "Security report"; see the security page.
3. Confidentiality of client files
This section applies to every file, document and record that belongs to the customer or the customer's clients and that LLPRO LLC, its software agents or its operator can see while providing a service. It is an agreement to keep them confidential.
- Use. Client files are used only to do the work the customer asked for. Not for any other customer, not for product development, not for training any AI model, not for marketing.
- Access. Limited to the people and software agents doing that work, for as long as the work needs. Files stay inside the service: we do not forward, post or paste them into outside tools, except one the customer chose (section 1).
- Examples. When we need to show something, we use made-up documents. Real files are never shown to another customer.
- Legal process. If someone demands customer data from us, we tell the customer first when the law allows, give only what the law requires, and leave it to the customer to raise any privilege.
- Privilege. LLPRO LLC reads client files only as far as the requested service needs. It does not decide what is privileged and does not waive anything.
- Duration. This continues after the service ends, for as long as we hold any such file; our copies are deleted as in section 1.
- People and agents. Everyone and every software agent given access is bound by these terms. LLPRO LLC answers to the customer for how they behave.
4. Lawyers' duties when using AI: a plain note
This is a summary of public sources so a lawyer can see the questions to ask. It is not legal advice, and LLPRO LLC does not tell any lawyer what the rules require. Each lawyer decides for themselves and checks the current rule text.
- Competence (Rule 1.1). ABA Formal Opinion 512 says a lawyer needs a reasonable understanding of what a generative AI tool can and cannot do, and should not rely on its output without an appropriate degree of independent verification or review. In LLPRO Business: every finding shows the sentence or record it came from, so it can be checked, and Louisiana procedure dates are shown as conservative bounds, never as deadlines.
- Confidentiality (Rule 1.6). The opinion says a lawyer should think about where client information goes when it is put into a tool, and that informed client consent may be needed before putting it into a tool that shares it outside the firm; general boilerplate in an engagement letter is not enough. In LLPRO Business: the records stay on the office's machine; only the optional connections in section 2 send anything out, and each is off until the owner turns it on.
- Supervision (Rules 5.1 and 5.3). The opinion treats generative AI like other assistance: lawyers with managerial or supervisory authority should set policies and train and supervise people who use it. In LLPRO Business: it proposes and a person approves; nothing acts alone.
- Client communication (Rule 1.4). The opinion says a lawyer may need to tell clients when generative AI is used in their matter, and to explain it. In LLPRO Business: a journal records what was read and proposed, and this page lists where data goes.
- Fees (Rule 1.5). The opinion says fees must stay reasonable: a lawyer does not bill hours the tool saved as if the work were done by hand, and general overhead is not charged as a separate expense. LLPRO Business is a flat monthly fee.
Louisiana. Louisiana lawyers are bound by the Louisiana Rules of Professional Conduct, which have rules numbered 1.1, 1.4, 1.5, 1.6, 5.1 and 5.3. On 20 Nov 2026 we found no formal ethics opinion from the Louisiana State Bar Association on generative AI. Summaries we read say its Ethics Advisory Service gives non-binding informal guidance, and one 2026 course listing mentions Louisiana Supreme Court direction and Act 250, which we could not confirm. A lawyer who needs a Louisiana answer should ask the LSBA Ethics Advisory Service and read the current rules and any standing orders of the court where they appear.
Sources (read 20 Nov 2026): American Bar Association, Formal Opinion 512, "Generative Artificial Intelligence Tools", 29 July 2024 (copy of the opinion); ABA Business Law Today summary; Louisiana Rules of Professional Conduct, as published by the Louisiana Supreme Court; LLPRO Business privacy policy.
5. What we have not done
- An outside security audit, or a SOC 2 or ISO 27001 report. We do not have them.
- A licensed attorney has not reviewed this page or the Louisiana rules inside LLPRO Business.
- A paid bug bounty. We do not run one.
Questions, a signed copy, or a deletion request: support@llpro.ai. LLPRO LLC.
Page dated 2026-11-20.