1. Who operates this service
Law For All is operated by ZTEX 0 (PVT) LTD, at 86/8, Parakrama RD, Galudupita, Ragama. For privacy questions or requests, email contact@ztex0.com.
This policy describes the connected public test and its current limitations. Broader production arrangements for backups, account-wide erasure, residency, and new processing features remain subject to approval before those features launch.
2. Information we use and why
- Account information: the identity and email information needed to verify sign-in, protect access, and associate saved chats with the correct account. Ordinary legal questions do not require a separate name, NIC number, or phone number.
- Submitted questions and answers: the text needed to retrieve sources, prepare guidance, and save your signed-in conversation so you can reopen it.
- Technical information: connection, authentication, security, and operational information needed to run the service, prevent abuse, and diagnose failures. Legal content is kept out of routine audit and event records.
- Preferences: your interface language and a content-free last-activity timestamp used to coordinate automatic sign-out across browser tabs.
Signed-in chats are not used for cross-chat profiling, reuse across accounts, or training. Public marketing analytics and advertising tracking are not enabled. Hosting and security logs may still contain connection information separately from chat content.
3. Drafts, questions, and AI processing
You can browse and draft without an account. Sending a question in the current web test requires sign-in. The browser uses a one-time text handoff in session storage for up to 15 minutes to carry a draft to the workspace or through sign-in. The workspace removes it after reading it; the question is not placed in the URL.
Once submitted, the question and bounded recent context are sent to the legal-answer service for source retrieval and AI generation. OpenAI is used for the current public-test model processing. Non-English or transliterated input may also pass through the separate translation service, which receives only the text or grounded answer blocks needed for that operation.
Model requests use storage disabled (store=false). This does not promise deletion from the provider's separate abuse-monitoring systems. Provider processing follows the provider's own terms and may retain information longer than the local copies described below.
Signing in does not attach an earlier anonymous conversation. A draft with attachments is handed off in running browser memory only, expires after 15 minutes if unused, and is not carried through sign-in as uploaded or saved files.
4. Saved chats, retention, and deletion
- Submitted signed-in messages, chat titles, and completed assistant responses are encrypted and saved to your account history until you delete that chat.
- Legal-answer replay content is encrypted locally for no more than 24 hours, independently of your saved chat history, so retries do not repeat the same work.
- Translation request and response content uses a shorter configured lifetime of 15 minutes. Expiry workers and a scheduled purge remove expired local sensitive content.
- Deleting a chat removes its active saved-chat records. It does not promise deletion from backups, separate replay records before their expiry, or an external provider's systems.
Use the per-chat delete control in the chat-history drawer. Starting a new conversation or refreshing a page does not delete earlier saved chats. Saved answers remain historical context; each new legal answer still needs fresh source checks.
For other access, correction, deletion, or privacy enquiries, contact contact@ztex0.com. Account-wide erasure and backup-deletion guarantees have not yet launched; we do not describe an email request as proof that those actions are complete.
5. Files, photos, and camera access
Selected files and captured photos stay in running browser memory as local previews. These controls do not upload files, read document text, analyze content, establish authenticity, or provide an evidence vault. The current interface allows up to 5 files per message, each 20 MB or smaller; these are local preview limits.
Camera capture requests video permission only, without microphone access. Capture stops after a photo is taken, when the dialog closes, when the page is hidden, or when the camera control unmounts. You review a photo locally before adding it.
Removing an attachment releases the interface's reference and revokes its local preview URL. Refreshing or leaving loses local attachments. These actions do not delete the original file or erase operating-system, browser, camera-app, or device records.
6. Cookies and browser storage
Account credentials are held in HttpOnly cookies rather than browser-readable storage. A content-free activity timestamp helps keep same-origin tabs in sync; the web test signs out after ten continuous inactive minutes and clears that timestamp on sign-out.
If you change the interface language, the browser stores only en, si, or ta under law-for-all:language in local storage. This preference does not contain your question, legal content, name, document, or case details. If the preference is invalid or unavailable, the interface falls back to English.
You can manage cookies and local storage through your browser. Blocking or clearing them can affect sign-in, draft handoff, and language preferences. It does not remove server-side saved chats.
7. Service providers, sharing, and security
Hosting and network providers process connection information. Google processes sign-in when used; an email-delivery provider may process account messages when that access method is enabled. Model and translation providers process the bounded text necessary to answer a submitted question. These are separate processing boundaries, governed by their applicable notices and configurations.
We minimize personal information, encrypt sensitive stored content, restrict saved chats and billing records to their authenticated owner, and keep provider credentials on the server. No method of transmission or storage can guarantee absolute security. Do not treat this service as a confidential lawyer-client channel.
Any disclosure required by applicable law or a valid legal process must be handled within that obligation. We do not authorize unnecessary sharing of your legal situation.
8. Payment and billing information
Paid checkout is not currently available. When introduced, PayHere checkout requires billing contact information such as your name, email, phone number, and billing address. These checkout details are separate from the minimal information needed to ask a legal question.
Card credentials are entered in the payment-provider flow. Law For All's billing records use payment references, amount, currency, and status; full card numbers and security codes do not belong in those records or support messages. Final payment-data retention and live processing arrangements must be approved before checkout opens.
9. Changes and contact
We publish changes here with a revised date. New upload, analytics, payment, or other sensitive-data processing requires an updated notice and the applicable approvals before activation.
Contact contact@ztex0.com about this policy. Include only what is needed to describe the request; do not email passwords, full payment credentials, or sensitive case documents. See support information and our Terms & Conditions for related service limits.
