Privacy Policy
Last updated: 20 November 2026. This policy explains the current operation of LUCIDWIRE, published by Ajaj Ansari as an individual. Contact: the protected contact form on this website.
You can read public pages without creating an account. Reader accounts, comments and online purchases are not offered. Newsletter registration is disabled; the site does not display a signup form and rejects signup requests without saving an email address.
The application has no separate audience-analytics or advertising-tracking integration. Netlify hosts the website, and Turso provides its database. Hosting and other providers may process technical request information to deliver and secure their services. Private site backups use Google Drive, and contact-form messages are delivered to the owner through Gmail. Each provider has its own privacy policy.
Authorized newsroom accounts store an email address, role and password hash. Admin login uses an essential session cookie that lasts up to eight hours and can end earlier on logout or a password change. The application also stores editorial content, uploaded media, action logs and security rate-limit records. The private privacy-request register records the requester email, category, received date, a minimal summary, identity-check status, review flags, suggested replies and action history. It does not connect to the mailbox, send replies or automatically delete personal data. The owner manually records requests received by email.
There is currently no automatic age-based deletion schedule for request records, audit records, job logs or private backups. We do not promise immediate removal from every backup or provider system. Published editorial content and requests to correct or remove information need individual review.
Privacy inquiries, corrections, deletion requests and general grievances can be sent through the contact form by choosing the Privacy / Grievance topic. Include the relevant page link and a short description. Do not send passwords, OTPs, payment details or identity documents. The owner reviews each request manually, checks identity and authority where relevant, and considers security, editorial, legal and backup restrictions before deciding what action is possible. A request does not automatically erase data. Legal notices, disputed identity, children’s information, sensitive information and third-party disputes require extra review. Nothing in this policy limits rights available under applicable law.
Policy changes will be reflected on this page with an updated date. Service-provider processing is also subject to their own policies: Netlify, Turso and Google. The current notice describes our practices; it is not a certification of legal compliance.
