Editorial Standards
ArrayHash is a WordPress plugin company, not an independent news or magazine publisher. These standards explain how we create and maintain technical articles for ArraySubs today and future ArrayHash products.
- Every current article was written by Emran
- Primary sources and product evidence come first
- AI assists; humans remain accountable
- Company
- ArrayHash
- Current product
- ArraySubs
- Current author
- Emran
- Last reviewed
- July 23, 2026
Editorial and fact-checking policy
Technical accuracy, first-hand product knowledge, and clear source attribution guide every article.
Emran, founder and lead engineer of ArrayHash, wrote and approved every article currently published on this site. ArraySubs is ArrayHash's current product, and future ArrayHash products may also be covered here.
Before publication, the author checks factual and version-sensitive claims against the strongest available evidence. Depending on the subject, that can include official documentation, standards, product code, release notes, configured test environments, or direct product behavior. Sources are linked close to the claims they support whenever practical.
- Distinguish WordPress and WooCommerce core behavior from extensions, payment providers, and ArraySubs behavior.
- State versions, test scope, limitations, and uncertainty when they materially affect a conclusion.
- Do not invent test results, customer outcomes, quotations, credentials, product behavior, or source citations.
- Separate verified facts from recommendations, estimates, and the author's interpretation.
- Prefer primary sources such as official documentation, product code, release notes, standards, and regulator guidance.
- Do not let a commercial preference override factual accuracy or a material limitation.
Product and commercial context
ArrayHash develops and sells WordPress plugins. Articles may discuss ArraySubs, link to product pages, or explain where it fits a workflow. Educational claims, product claims, and commercial calls to action should remain distinguishable so readers can evaluate the evidence and the business relationship.
ArrayHash may invite additional authors in the future. Each invited author will publish under their own name and author profile and will be responsible for the accuracy of their work under these standards.
Reviewer identity rule
ArrayHash does not use generic or fictional team labels for reviewers. An article shows a reviewer only when a real, independent person completed that review. The reviewer must be named and linked to a profile that explains their relevant role and expertise.
If no independent review occurred, the article makes no reviewer claim. When invited authors publish in the future, Emran may be named as reviewer only when he personally performed and accepted responsibility for that review.
Corrections policy
Readers can report a suspected error, and material corrections are verified before publication.
To report an error, email [email protected] or use the contact page. Please include the article URL, the disputed statement, and supporting evidence when available.
- Factual, technical, product, and source-attribution reports are reviewed by the responsible author or engineer.
- A confirmed material error is corrected promptly after verification and recorded in the article's disclosure or update note when the change affects meaning or conclusions.
- Minor spelling, grammar, formatting, or clarity fixes may be made without a correction note when they do not change meaning.
- ArrayHash does not remove fair criticism or change a supported conclusion solely because it is commercially inconvenient.
Content-update policy
Dates have distinct meanings and are changed only when the corresponding editorial work occurs.
- Published identifies the date an article first became public.
- Updated identifies a meaningful revision that includes a factual recheck. It is not changed solely to make an article appear fresh.
- Last verified identifies the factual recheck completed with the latest meaningful update. For current ArrayHash articles, Last verified is kept equal to Updated.
- Visible article metadata shows Written by, Published, Updated, and Last verified. Reviewed by appears only after a genuine independent review by a named person with a linked profile.
- Update reviews may be triggered by WordPress, WooCommerce, ArraySubs, gateway, legal, standards, or source changes; confirmed corrections; new test evidence; or credible reader reports.
- Version-sensitive product claims include relevant version or test scope when that context affects the result.
- Content may be merged, redirected, archived, or removed when it is obsolete, duplicative, unsafe, or no longer supportable; the goal is a useful reader path, not an artificial page count.
Date integrity
A copy edit alone does not justify changing the published date or presenting the article as newly verified. A meaningful update includes a factual recheck, so the Updated and Last verified dates move together after that work is completed.
AI-assistance policy
AI can assist limited parts of the workflow, but it is not an author, reviewer, or source of experience.
Every article currently published on this site was written and approved by Emran. ArrayHash uses AI only as an assistant. Human authorship, judgment, verification, and accountability remain primary throughout the process.
- AI assistance is used during parts of research to organize questions, explore source leads, or identify points that require verification. Claims are checked against the cited or primary sources before publication.
- A small number of article images are generated with AI. A human selects and reviews them, and an AI-generated illustration is not presented as a real interface screenshot or test result.
- In a few articles, AI has assisted with formatting or rephrasing paragraphs after the underlying ideas and facts were written. The final wording is reviewed and approved by the human author.
- AI is not allowed to invent tests, data, quotations, credentials, customer outcomes, product behavior, or citations.
- AI is not credited as an author or reviewer and does not accept responsibility for published content.
Human accountability
The named human author owns the final article. If assisted text or imagery introduces an error, ArrayHash applies the same correction and update standards as it would to any other published error.
Policy review and contact
These standards took effect on July 23, 2026and are reviewed when ArrayHash's authorship, products, research workflow, or use of assistance tools materially changes.
Editorial and correction questions can be sent to [email protected].
Related policies
Each page covers one part of how ArrayHash handles privacy, payments, licenses, refunds, and accessibility.
Privacy Policy
What the ArrayHash website collects, why it is used, cookie consent behavior, and how to exercise privacy rights.
Read policyData Safety
How website data, payment data, and merchant WordPress data are separated.
Read policyRefund Policy
The 30-day ArraySubs Pro refund guarantee and how refund requests are handled.
Read policyQuestion an article or report a correction?
Email ArrayHash with the article URL, the claim, and any supporting evidence. A human will review it.
