Who we are

The PDFalot Editorial Team

Every guide, tutorial and article on PDFalot is written and reviewed by the small team that builds the product itself. We publish under a shared byline — "PDFalot Editorial Team" — because most articles pass through more than one of the people below before they go live.

Who contributes

Product & AI Engineering

Document AI, model selection, accuracy testing

Builds and maintains the AI features — summarisation, chat, translation, smart split and the analyst. Runs the accuracy checks behind every AI claim we publish, and writes the articles that explain how the models actually behave on real documents rather than on demos.

  • AI
  • Product
  • Guides

Document Engineering

PDF internals, conversion fidelity, OCR

Owns the non-AI toolchain: merge, split, compress, convert, OCR, forms, redaction and signing. Tests every tool against awkward real-world files — scanned invoices, multi-column reports, forms with broken field maps — and documents what works and what to watch for.

  • Tools
  • Conversion
  • OCR

Legal & Compliance Review

POPIA, GDPR, data residency, retention

Reviews anything we publish that touches privacy, retention, contracts or compliance before it goes live. Also maintains our Terms, Privacy Notice and Refund Policy for PDFALOT Proprietary Limited, a company registered in South Africa.

  • Legal
  • Privacy
  • Security

Customer Support & Research

Real user workflows, feedback, case studies

Answers support mail and turns recurring questions into documentation. Most of our workflow articles — the accountant reconciling a 400-page invoice dump, the student studying on a commute — start as a support conversation.

  • Workflows
  • Students
  • Finance

How we work

  • We test before we write. Any claim about a tool's output — table fidelity, OCR accuracy, split boundaries — comes from running the tool on real files, not from a spec sheet.
  • We name the limits. If a feature struggles with a file type, the article says so. Guides that only describe the happy path are not useful.
  • Legal and privacy copy gets a second reader. Nothing about retention, residency or compliance is published on one person's say-so.
  • We correct in public. Substantive corrections are noted on the article rather than quietly edited away.
Read our editorial standards →

Recent articles

Spotted something wrong?

Corrections, disagreements and better examples are all welcome. We read every message.

Contact the editorial team →
Try AI Now