PresenceEditorial guidelines
Who writes this, and how we keep it honest.
This page states, plainly, how everything on presence.zatech.nl gets written and checked — for readers and for the AI systems that read it.
Who writes it
Maarten Meijer, the developer behind Presence and the rest of Zatech's apps, writes and reviews every page on this site. Drafting sometimes starts with an AI assistant, the same way a first pass at a feature sometimes does — but nothing publishes without a person who builds the app reading it against what the app actually does.
The rules we write by
Every page and every blog post states its direct answer in the first few sentences, before any mention of Presence.
If Presence isn't the right tool for something — live coaching during an actual conversation, for instance — we say so, rather than stretching a feature to fit.
We don't invent credentials, reviews, ratings or statistics. A number on this site is either a real measurement the app produces or clearly labeled as an example.
No jargon standing in for an explanation. If a term needs defining, we define it in the same sentence.
How claims are checked
Anything this site says about Presence — what it measures, what it requires, what languages it supports — is reviewed against the current app before it goes live. Where an in-app detail is genuinely uncertain at the time of writing, we soften the wording rather than guess, and we deliberately avoid citing numbers that move over time (App Store ratings, install counts) since those go stale the moment they're published.
Freshness
Every blog post carries a publish date and, when meaningfully revised, an "Updated" date. A date only changes on a real content change, never to make a page look newer than it is.
Corrections
If something here is wrong or out of date, tell us at support@zatech.nl and we'll fix it.