Privacy

David Lisitsa operates this website, ailawframework.com, from Australia. Questions about personal information, and requests to see, correct or delete it, go through Enquiries.

When Claude, ChatGPT, Codex or another AI app uses the framework’s MCP server at https://ailawframework.com/mcp, the server receives what the app sends to its tools — typically the task as described, the answers to the framework’s questions and the research findings with their sources. It uses them to apply the framework’s rules and send back a reply.

It keeps nothing about the task. There is no account and no database row for it, and the work record that carries the task from one step to the next travels inside your conversation, signed so it cannot be altered. As for every request to this site, the route, the time, the outcome and how long it took are counted, with no content and no identifier.

What your AI provider does with your conversation is governed by its own terms and privacy policy, not this one. Describe a task without client names where you can; the framework never needs them.

That is the public connector. The signed-in connector for a firm’s own knowledge is described in the next section.

The firm connector at https://ailawframework.com/mcp/firm lets an AI app read your firm’s approved AI policies, its knowledge base and the full precedent library, as you, after you log in here and approve the app. It never returns a knowledge item your firm has marked hidden from agents, or a draft policy you could not read yourself. Like the public connector, it keeps nothing about your task: not the questions your AI asks, not the words it searches for, and not the answers it gets. To make the sign-in work and to let your firm see who read what, it keeps the following, in Sydney:

• The app’s registration: the name the app gives itself, the addresses it may send you back to, when it registered, and a keyed one-way code made from the network address it registered from (never the address). An app that publishes its details at its own web address is kept with that address and re-read every ten minutes while it is used.
• Your connection: your account, your firm, the app, what you allowed (read, or read and save drafts), when you approved it, when it was last used, and when it was disconnected.
• Its keys: a two-minute sign-in code, access keys that last an hour and renewal keys that last 30 days from their last use. Each is stored only as a one-way hash, so a copy of the database cannot be used to read your firm’s knowledge.
• An access log: each time the app reads or saves your firm’s material, your account, your firm, the app’s identifier and name, the tool used, the identifiers of the items returned and the time. Never the question or any text. Your firm’s owners and administrators can read it at Firm › AI agents.
• Drafts: if you allowed it, a draft the app saves is kept as a knowledge item you own, marked as a draft, like knowledge you add yourself.

What the connector returns — your firm’s policy text, knowledge items and precedent texts — goes to the AI app and its provider, and is then governed by that provider’s terms, not this policy. Connect only apps your firm has approved for that material. You can disconnect an app at Firm › AI agents at any time, and your firm’s owners and administrators can switch AI apps off for the whole firm; either ends access at once.

A firm’s owners and admins can download everything the firm keeps here at Firm › Settings: every policy document with each saved version, every knowledge item with its stored files, the agent access log for the last year, and a list of what is inside. The download is recorded in the firm’s access log.

An owner can delete the firm there, after typing its name. Its policies and versions, knowledge items, stored files, invitations, membership, connections to AI apps and access log are deleted at once; stored files that cannot be removed straight away are removed within a day. The people in the firm keep their own accounts and their own records. Copies in the hosting services’ backups expire on those services’ own schedule.

You can read every public page without an account. Two separate counts are kept, and neither uses a cookie.

Vercel Web Analytics counts page views and visitors without cookies, and the site removes query strings before anything is sent. That count is Vercel’s.

This site also keeps its own count, stored in Australia, so the operator can see how the site is used. For each page view it stores the page path with the query string removed and with any shared-link token removed, the name of the site that linked here (not the full address), whether the browser says it is a mobile or a desktop, the country when the host supplies one, and a visitor code. The visitor code is a one-way code made from the network address, the browser, the UTC date and a key that stays on the server. The address itself is not stored. The code kept for one day is a different code the next day, and those stored codes cannot be joined without the address and the browser, which are not kept. The words you type on the search page are counted on their own, not tied to that code. An email address or a long number is not kept. The first tick on a quick checklist is counted as a number. Which box you ticked, and which task you opened, are not stored. To stop a flood of counts, the number of counts from one connection is limited for an hour using a different one-way code. That counter is not the visitor code, it is not stored with a search word, and it is deleted after two days.

Work you do as a guest in My work, and a firm-policy draft you have not saved to an account, stay in that browser’s own storage and are not sent to the server. Choosing a matter on Plan a matter sends the matter type, forum, sensitivity and tool names to the site so the grid can be prepared. That request is not stored. An unsaved plan stays in that browser tab, and a signed-in tab keeps it for that account only.

If you register, the operator of AI Law Framework collects your name, email address, phone number if you give one, firm name and the tools you say you use. You can keep using the site without registering. The details are kept so an account can be created for you and so the toolset you name can be saved. After you sign in you can also save the practice areas and the courts or places you work in. That choice is optional, can be skipped, and is used only to suggest tasks in your workspace. It is not a marketing list. Those details are kept with the work records, software assessments, decision records, firm-policy drafts and knowledge you choose to save. Knowledge you add — the title, the text, the practice area, the forum, the task, the tool, the tags, the source, the review date, whether connected AI agents may read it, an optional link to one of your decision records, and any file you attach — is kept so you can find it while you work. Only the account that saved a note can change or delete it. Other members of the firm the note is saved under can read it, but the app does not show them any decision record linked to it. A decision record can include the task, the tool and an optional matter reference. Do not put a client’s name in those fields. It can also name a supervising practitioner and, if you add it, their email address, so they can be asked to review that record. They can read that record when they sign in with that email. The email, when one is sent, links to this policy. When you are signed in, the hosting, certifications, training position, pricing, capabilities and suggested levels you confirm or edit for a tool are stored on that account, including whether each value came from the published catalogue or from you. A tool name that is not in the catalogue is kept so it can be researched. That queue does not include your email address. A research flag stores the product name, supplier and note you type, against your account, so a tool that is not in the catalogue can be researched. It is not published and it is not used to send you marketing. A decision you share by link can be read by anyone who has that link until sharing is turned off. A work record is saved on the account only after you sign in and save it. A saved firm-policy draft stores the answers you give about the firm (its name, size, practice areas, states, litigation, and choices about tools, uses and client information), the generated wording and any wording you edit, and a short note of tool names, decisions and linked task titles taken from records already stored for that account. The questions ask for the firm’s name and a role for the policy owner. They do not ask for a person’s name or a client’s name. A matter plan stores the matter type, the forum, the tools chosen and the identifiers of decision records opened from that plan. It does not ask for a client’s name. Only that account can read it. A password, when you set one, is stored by the authentication service only as a hash. Work records you save are readable from your account. When you save a work record, the site also stores which published court or regulator instruments and which tool records that record used, so it can tell you later if those records change. That list, and any note you add when you mark a change reviewed, can be read only by your account. Each account’s records can be read only by that account, apart from a link you have turned on or a decision record a named supervisor was asked to review. A registration notice, containing those same details and where on the site you registered, is sent to the operator. The notice and any sign-in email are delivered by Resend, in the United States. Optional updates are a separate, unticked choice and are not required to register. Leaving that box unticked later does not withdraw a yes you already gave. To stop those updates, or to access, correct or delete these details, use Enquiries and name the address. Signing in sets the cookies needed to keep you signed in; there are no advertising or tracking cookies. The information is not sold. The services listed below process it to host the site, store the account and deliver those emails.

From Work records you can ask for an email when a published court or regulator instrument for a saved work record, or a tool record that work record used, is added, updated or withdrawn. The choice starts unticked. The form states what is sent, where it is stored, and that the message goes through Resend, which stores it in the United States, before you tick it. The email uses the address on your account. It names the work record and what changed, and it contains a private link to stop further emails without signing in. It is not a marketing list. The address is stored in Australia. Nothing is sent unless you opt in, and nothing is sent at all until the site’s email sender is switched on. Turn it off from Work records, or use the link in an email you have already received.

If you sign up for court AI rule changes and new tools, your email address and the page you signed up from are kept so that note can be sent about once a month. The address is stored in Australia. If a later send uses a service outside Australia, this policy will name that service before the first send. The form is the consent. To stop it, ask through Enquiries and name the address. To stop abuse, the number of signups from one connection is counted for an hour using a keyed one-way code made from your network address, never the address itself. The address is not shown back to you, and it is not used for anything else.

When you send an enquiry, your name, email address, organisation, topic and message are kept and emailed to the framework’s inbox so that someone can reply. To stop abuse, the number of enquiries from one connection is counted for an hour using a keyed one-way code made from your network address, never the address itself.

• Vercel hosts the site and runs its server code in Sydney, and provides the page analytics.
• Supabase stores accounts, registration profiles, saved records, enquiries, monthly-note addresses and the request counts, the page-view, search and quick-checklist counts, and the firm connector’s app registrations, connections, hashed keys and access log, in Sydney (ap-southeast-2).
• Resend, in the United States, delivers account emails, registration notices and sign-in links, passes enquiries to the inbox, sends a supervisor the link to review a decision record when email is set up, and sends the change digest only after you opt in. That sends the email address, and for an enquiry or a registration notice the message, outside Australia. Resend stores those messages in the United States. The enquiry form, registration form, account signup, password reset and email-link login say so before you submit them. The supervisor field says so before you ask for a review. The change-digest form says so before you tick it. If email is not set up, the review is saved and no message is sent. The monthly-note address is not sent there.
• Nothing is sold, and nothing is shared with anyone else unless the law requires it.

MCP task content is not kept at all, on either connector. For the firm connector, sign-in codes are deleted a day after they expire, keys a day after they expire, disconnected connections after 90 days, app registrations that were never used after 30 days, and access-log entries after one year. When an owner deletes a firm, everything that belongs to the firm is deleted at once, as described above. Request counts and availability checks are kept as operating history. Page views, search words and quick-checklist counts are deleted after 30 days. Accounts, registration profiles and saved records are kept until you delete them or ask for them to be removed. The list of rules and tools a work record used, and the review notes on those changes, are kept with that record. A change-digest address and the record that you consented, or later stopped, are kept until you ask for the account to be closed. Enquiries are kept for as long as needed to deal with them and to keep a record of the correspondence. A monthly-note address is kept until you ask for it to be removed.

You can ask to see, correct or delete the personal information held about you, or ask a question about this policy, through Enquiries. David Lisitsa operates this site from Australia and handles personal information in line with the Australian Privacy Principles. If you are not satisfied with the response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.