Privacy policy.
This policy explains browsing data, published records, administrative accounts and email contact. We respect the privacy of readers, victims and their families and describe actual practices without making absolute security promises.
At a glance
- Read and search without an account or name.
- No public contact forms on the website.
- General contact takes place through external email.
- No advertising, external analytics or embedded social widgets.
- Statistics describe recorded content, not readers’ identities.
Responsibility and scope
This policy covers browsing the Houthi Crimes Archive, using search and source links, and operating editorial and administrator accounts. Muhammad Abdulqaher Sinan runs the archive. General contact is by email, not through a website form.
Website operational data, published record content and correspondence through an external email service are distinct. Displaying an email address does not embed Yahoo services in archive pages.
Data minimisation
You can read and search without an account or providing a name or email address. The public interface has no visitor-information submission form and does not create interest profiles. Archive pages contain no advertising, marketing trackers or external analytics libraries.
Operational data is used to deliver pages, protect administrative accounts and investigate errors or abuse. Published incident information serves a documentation purpose, not unrestricted reuse of victims’ personal details.
Browsing and server data
Opening a page creates a network request through the hosting infrastructure. Server logs may contain a network address, request time, page path, browser details and response status. Their scope and retention depend on actual hosting settings; this policy does not claim an unimplemented retention period.
The application does not attach a reader’s name to an incident record or display their identity to editors. Having no built-in analytics does not eliminate technical logs maintained by hosting providers, networks or browsers.
Search and filters
Search terms and filters are processed against the archive database, not sent to an external search engine to generate results. Terms and selected filters appear in page URLs and may therefore remain in browser history or server request logs.
Avoid entering private personal information in search. Clearing the input does not automatically delete a stored URL from browser history or hosting logs. Browser-history controls are managed in your browser settings.
Content statistics
Statistics describe recorded crimes, recorded victims, governorates, categories and source organisations in the database, not visitor behaviour. They do not list who read an incident or how often an individual visited.
Recorded-crime totals are not an exhaustive count of all crimes, and translations are not extra incidents. Victim totals aggregate available fields and may include the same person across different events. Missing values do not mean zero victims.
Email contact
The contact address is [email protected]. Its link opens your chosen email application or service; the website does not send a message on your behalf or save its draft or contents in the archive database. Sending email happens outside the website at your choice.
A general enquiry sent by email provides the mailbox with your sender address, subject, contents and any attachments you choose to add. Mail services may process delivery-related technical data. Include only information appropriate to your enquiry.
External email services
The mailbox is hosted by Yahoo, and you may use a different provider to send email. Those services process messages under their own policies, terms and account settings. Website code does not control their storage locations or retained copies.
Copying the address does not send a message. Opening a mail application or sending email may initiate external connections under your settings. We do not promise end-to-end encryption, absolute confidentiality or an immediate response; contact details are not an emergency service.
Information in published records
Records may include victims’ names, ages, incident dates and places, and published information about injury, death or detention. Entries link to published sources and use information to describe and document the event.
Information should be necessary and proportionate to that purpose. Names, figures and attribution are reviewed when new published evidence emerges. A name’s appearance in an earlier source does not justify unrestricted publication of other details about that person or their family.
Children and family members
Information about children requires particular care. Documenting an incident does not justify unnecessary disclosure of their daily routines, schools or contact details. Published age or family relationship information may be included when relevant to understanding the event.
Children’s images or stories should not be used for degrading or gratuitously shocking presentation. Mentioning one family member does not imply that other relatives were involved or that their private information should be published.
Images and files
Linking a source does not automatically load its photographs. Any future published image requires review of its relationship to the event, usage rights and visible personal information. The archive’s logo is not an incident photograph.
Only authorised accounts can upload images, and accepted uploads are re-encoded. This does not replace editorial review or automatically conceal readable information or faces within an image. Unnecessary personal details should be reduced before publication.
Editorial and administrator accounts
Administration accounts are for editorial and operational staff, not public readers. The application stores usernames, roles and password hashes rather than plaintext passwords. Publishing, deletion and configuration permissions depend on roles.
Administrative and editorial actions are recorded in an audit log. Operators should protect credentials, change initial passwords and avoid shared accounts. A strong password alone does not secure a compromised device or hosting environment.
Technical safeguards and limits
The application uses input validation, prepared database queries, role and session controls, protection for administrative requests and login rate limits. Upload and import controls help reduce malicious-input risks.
These safeguards are not an absolute guarantee or certification from a comprehensive penetration test. Operation requires updated PHP and server software, protected backups, appropriate monitoring and HTTPS. Storage folders, databases and environment files must not be exposed over the web.
Access permissions
Visitors can read published records; administrative information and internal revisions are not part of the public interface. Server operators or hosting providers may have technical access under their management and support arrangements.
Incoming email is managed through the mail-provider account, not a public website form or submission inbox. Sending an enquiry does not authorise publication of the sender’s address or message in an incident record. Operational access should be limited to authorised people.
Retention and backups
Published records are retained in keeping with the archive’s purpose, while revisions and backups may preserve earlier versions. Removing information from a current page does not automatically remove all backup copies or copies previously obtained by others. Backups should remain non-public.
Server-log retention depends on hosting settings; email retention depends on provider practices and mailbox management. This policy does not claim automatic deletion that has not been implemented. Operators should periodically review and remove unneeded operational data and correspondence as appropriate.
Privacy enquiries
For an enquiry about published personal information concerning you, email the page URL and a brief explanation of your request. Usually identifying the relevant information is preferable to sending unnecessary documents or extra personal details. Requests are considered in light of the data, publication purpose and potential harm.
Proportionate verification may be needed. We cannot promise an identical outcome in every case or deletion of third-party copies. Reducing or restricting information may be more appropriate than removing an entire event, subject to applicable legal obligations.
External links and search engines
Source links lead to independently operated sites with their own privacy practices, cookies or subscriptions. The archive does not control their content or availability. Linking to a source does not send it administrator login credentials.
Search engines may index public pages or retain cached versions, and updates may take time to appear. The site has no embedded social tracking widgets. A future external social link would not by itself embed that platform’s content in the page.
Hosting and processing location
The locations of archive files, backups and server logs depend on the provider hosting the deployed site. Arabic content or a domain name does not imply processing within a particular country. Email services may process messages separately from the archive’s host.
The operator is responsible for choosing hosting, configuring permissions and reviewing services. This policy does not assert universal legal compliance or describe processing agreements that have not been established.
Your choices
You can read without contacting the archive, copy the email address without opening an email program, and choose not to open external sources. Browser history, cookies and application permissions can be managed on your device.
Not contacting us does not restrict access to published records. If you send email, review recipients, attachments and your provider’s policy first. Closing the archive page does not cancel a message already sent through an external mail application.
Policy updates and contact
This policy is reviewed when functionality or operating arrangements change, and its displayed date is updated. Changes do not constitute unrestricted retroactive permission to reuse data collected for another purpose. Appropriate notices or consent should be considered when required.
The Arabic and English versions describe the same practices. General and privacy enquiries can be sent to [email protected], also displayed on the Contact page. There is no website submission form.