Editorial policy · effective 03 Aug 2026
Trust needs visible rules
This policy defines how GenOffice.online separates documented facts from interpretation, handles an exact-match domain responsibly, and updates claims about a fast-moving alpha product.
No product affiliation
GenOffice.online is not owned, operated, endorsed, or reviewed by Genspark, Mainfunc, or the GenOffice maintainers. The domain describes the topic; it does not confer official status.
No hidden commercial influence
The current site has no affiliate links, paid placements, sponsored rankings, lead-generation forms, software mirrors, or checkout. If a commercial relationship is added, it must be disclosed beside the affected content.
Claims stay close to their sources
Version, maturity, platform, capability, architecture, license, and account claims are linked to official product pages, repository files, or release records. Publisher claims are labeled as official rather than presented as independent proof.
Comparison is workload-specific
Products are compared on declared dimensions. No universal winner, synthetic score, or unsupported superlative is used. When hands-on evidence is missing, the site states what a reader should test.
Hands-on status is explicit
The current GenOffice alpha was not installed for this publication. File fidelity, formula behavior, slide rendering, PDF editing, stability, performance, network behavior, privacy, security, and accessibility have not been independently verified here.
AI may assist production, never provenance
Automated tools may assist with research organization, drafting, code, and quality checks. Material factual claims still require a visible source. AI-generated output is not treated as a source and must not invent authorship, experience, or endorsements.
Minimal collection
This static site does not include account creation, comments, payment, uploads, advertising pixels, or an analytics client. The hosting provider may still process ordinary request metadata according to its own infrastructure policy.
Corrections propagate
A material correction should name the stronger source, update the closest claim and every downstream table, FAQ, schema field, and metadata description, and refresh the visible review date when warranted.