How Legalise Handles Your Data and Generated Documents
Legalise is used in a setting where confidentiality is ordinary, not exceptional. Advocates are often working with client facts, drafts, and matter-specific details that cannot be treated casually. That is why the platform's handling of generated documents and account data is a product question, not a decorative trust statement.
Generated Documents and File Saving
Document content is processed to provide the requested service. Saved Desk documents, persisted generated outputs, compiled briefings, reviewer reports, research reports and case-file attachments are stored so you can return to them. Creating a persisted output can store it without a separate Save action. Template filing data that is not saved is not retained as document content, while service metadata is kept for billing, service records and abuse prevention.
Provider retention is a separate question. As the Privacy Policy explains, paid memberships use models under arrangements that do not retain inputs or outputs or use them for training. Providers handling Complimentary requests may retain submitted text under their own terms. Deleting an item from Legalise cannot remove a copy a provider may already hold. Read the current policy before submitting sensitive matter material.
Account, Usage, and Payment Data
Like any functioning platform, Legalise stores the information needed to operate the account and the service. That includes ordinary account details, authentication records, usage information, and payment status records. The important point is not that these categories exist, because they would exist on almost any serious service. The point is that the platform states what is collected and what is not, instead of pretending that no data processing occurs at all.
The live privacy page also makes clear that bank account numbers and card credentials are not stored by the platform as part of its payment records.
Why This Matters in Legal Work
For advocates, the practical question is straightforward. Does the platform treat a generated document like a permanent data-harvesting opportunity, or does it keep the handling tied to the service actually being provided. The way Legalise describes saved files, unsaved generations, and limited metadata is more consistent with the second model.
Read the Live Policy
Because privacy language can change as the service matures, the live Privacy Policy should always be treated as the primary source. This article is meant as a readable explanation of the product logic, not as a substitute for the policy itself.
The most useful next pages from here are the Privacy Policy, the About page, and the sample rental agreement.