GeSIM Journal

Editorial policy.

We write about what we build, what breaks, and what privacy actually looks like from inside the system. Here's how we do it honestly.

Who writes for the GeSIM Journal

Content in the GeSIM Journal is written by the GeSIM team: the people building the product, running the infrastructure, and using GeSIM daily. We do not publish guest posts, sponsored content, or AI-generated articles.

Author bylines reflect the actual person who wrote the piece. "Team GeSIM" indicates a piece was written collaboratively or by a team member who prefers not to be individually named.

What we write about

We publish three types of content:

Product updates. When we ship something meaningful — new features, coverage expansions, pricing changes — we write about it directly. We don't use press releases or marketing language.

Field reports. Honest accounts of using GeSIM in the real world. These include failure cases, friction points, and situations where GeSIM isn't the right tool. We don't publish only success stories.

Technical and privacy context. Explainers on how mobile networks work, why certain privacy properties are hard to achieve, and how the crypto-native approach changes things. These are written to inform, not to sell.

Our standard for factual claims

Claims about competitor products, carrier practices, or the mobile industry are sourced from public documentation, regulatory filings, or direct testing. We cite sources where possible. If a claim is based on our direct experience rather than external documentation, we say so.

Statistics (coverage countries, active users, etc.) are updated as the product grows. If we publish a number, it reflects actual data at time of writing, not projections.

Conflicts of interest

GeSIM is a commercial product. Everything we publish ultimately serves the goal of people understanding and trying GeSIM. We acknowledge this plainly rather than pretending to editorial independence we don't have.

What we commit to: we will not suppress negative field reports, claim capabilities we don't have, or publish comparisons that misrepresent competitors.

Corrections

If we publish something factually incorrect, we correct it and note the correction at the top of the post with the date it was made. We don't silently edit errors away.

If you believe something we've published is incorrect, contact us on Telegram with the specific claim and the correction you believe is accurate. We'll investigate and respond.