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
The live privacy page explains the core distinction clearly. Document content is processed so the draft can be generated. If the user chooses to save that draft, it remains available in the account's case files. If the draft is not saved, it is not kept as a standing document record in the same way. What remains for service and billing purposes is limited operational metadata rather than a stored archive of every unsaved working draft.
That distinction matters in practice. A lawyer may want the convenience of saving a working document inside the platform for continued use in the matter, but may not want unsaved generation sessions hanging around as separate retained drafts.
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.
[EDITORIAL NOTE: Verify all claims in this post against the current Terms of Use and Privacy Policy at legalise.pk/terms and legalise.pk/privacy before publishing.]