Editorial Policy
OpenToolsKit is open source, so public content should be clear, accurate, and easy to verify against the implementation and source repository.
Tool descriptions
Tool pages should describe what the tool is for, expected inputs, expected outputs, and practical limitations. We avoid implying that a browser tool can guarantee perfect results for every file.
Privacy claims
Privacy copy must reflect the actual implementation. When processing is local where applicable, pages should say that clearly without overstating behavior for every possible third-party link or browser feature.
Source and attribution
OpenToolsKit preserves AGPL source availability and attribution for PDFCraft-derived work through visible repository and NOTICE links.
Monetization boundaries
Advertising and partner surfaces, when enabled, must be labeled and kept separate from core tool actions. They should not be presented as editorial recommendations.
Corrections
Users can report outdated copy, broken links, mistranslations, or tool behavior mismatches through support email or GitHub Issues.
Request a correction
Use the contact page or the public issue tracker to report inaccurate content, stale metadata, or broken internal links.