What happens to a question you type
The home page and unsigned Send flow use the browser's sessionStorage for a one-time, 15-minute text handoff so your draft can reach the workspace after Google sign-in without being placed in the URL. The workspace reads and immediately removes that handoff. An unsigned draft is not sent to Legal Orchestration or saved to Memory. After sign-in, the question is sent for retrieval and a model-generated answer. Provider requests use storage disabled, but the external provider may retain separate abuse-monitoring records under its own terms.
If a question includes attachments, its text, mode and selected files travel together in running browser memory only. This attachment handoff is not written to session storage and expires after 15 minutes if it is not consumed. No filenames, file contents or preview URLs are added to the page URL.
Each signed-in message you submit and each completed assistant response is encrypted and saved to your account history until you delete that chat. The legal-answer service also keeps bounded encrypted replay content for no more than 24 hours so retries are idempotent. Signing in does not attach a previously submitted anonymous chat. Saved responses are historical context only; every new legal answer still requires fresh retrieval and source checks.
Files, photos and camera access
The chat's plus button opens file and photo pickers. Selected files stay in running browser memory. Supported raster images get local thumbnails; other files show only their name and size. The interface does not read document text, upload files, analyze their contents or establish authenticity. Use sample files without personal details. The current preview allows up to 5 files per message, each 20 MB or smaller; these are local interface limits, not a production upload policy.
Choosing Take a photo requests camera access through your browser. It requests video only, without microphone access. The camera stops after capture, on closing the camera dialog, when the page is hidden, or when the control is unmounted. A captured photo is reviewed locally before you add it. No image is sent to a server by these controls.
Removing an attachment releases this interface's reference to it. New conversation clears the current transcript and attachments. Refreshing, closing the page, or leaving the conversation loses its attachments; leaving the home composer for a tool also clears its selected files. Local image preview URLs are revoked when their previews are removed. These actions do not delete the original file or promise to erase browser, operating-system, camera-app or device records.
What is kept as an interface preference
If you change the interface language, the browser stores only en, si, or ta under law-for-all:language in local storage so that choice can be restored on a later visit. This preference record does not contain your question, legal content, name, document, or case details. If local storage is unavailable or invalid, the interface falls back to English.
What is stored and what is not
- Signed-in legal-answer replay content may remain encrypted for up to 24 hours independently of the longer Memory chat history.
- Signed-in chat titles, user messages, and completed assistant responses are encrypted in the Memory service until you delete that chat.
- Deleting a chat removes its active Memory records; this public test does not promise deletion from backups or an external provider's systems.
- No product analytics integration in this repository records conversation content or usage events.
- No document or evidence upload service receives, stores, scans, or shares files.
Document Camera, ProofPack, forms, feedback, and law-status screens remain interface demonstrations. Their controls do not establish that information has been submitted, stored, verified, reviewed, or sent to an institution.
Hosting and sign-in are separate boundaries
The hosting provider, browser, network, email delivery provider, Google sign-in when enabled, and external model provider may process technical information such as connection data, cookies, security events, or operational logs under their own notices and settings. Application credentials stay in HttpOnly cookies rather than browser-readable storage.
What must be decided before production
A production privacy policy still needs approved rules for backups and account-wide deletion, data location, service providers, evidence handling, analytics, children and vulnerable users, incident response, and user requests. The current signed-in history rule applies only to this bounded public test and must not be treated as a general production retention policy.
No privacy or data-deletion contact is published here because the responsible contact and request process have not been finalized. This page will need revision before any real legal-data processing is launched.
Independence and legal limits
Law For All is an independent public test. It is not a Sri Lankan Government website, court, Police service, public authority, Legal Aid service, or law firm. It retrieves source material for each answer but does not claim independent human verification, an official determination, or a confidential lawyer-client service.
