How SableApps tools are built and checked
This page records what the tools do, where input is processed, what our automated checks cover and which decisions remain with the user. Updated 21 October 2026.
Our scope
SableApps builds focused browser tools for documents, developer data and local cricket operations. A tool must complete a defined task before it is listed publicly. We do not publish inactive tool cards, scraped results, framed third-party applications or pages whose only purpose is attracting search traffic.
The interactive tool is the main content. Guides support the task by explaining preparation, verification, limitations and unusual cases. They do not replace a working feature. Each guide is reviewed against the current interface and links back to the exact tool it describes.
Processing and storage model
JPG to PDF and PDF to JPG read selected files through browser APIs and perform conversion in the page. Age, epoch, JWT and Base64 utilities process entered values in page memory. These inputs are not submitted to a SableApps application server. Ordinary website requests still reach Cloudflare and can contain standard connection data such as IP address, URL, browser information and request time.
Auction-Book and Scorebook need persistence during an event, so they save the active record in the browser's IndexedDB. The data is tied to that browser profile and does not become a cloud account. Each product supports a downloadable JSON backup, and each can export a CSV result. Clearing site storage removes the active browser record.
Current automated validation
| Area | Checks | Current coverage |
|---|---|---|
| Daily utilities | Calendar intervals, invalid dates, epoch units, standard and URL-safe Base64, invalid Base64, HS256 creation, verification and JWT decoding | 5 focused automated cases |
| Auction-Book | Purse reservation, bid increments, squad limits, replay, unsold return, CSV parsing, backup validation and safe export | 5 workflow tests |
| Scorebook | Extras, legal balls, zones, wickets, free hits, strike, overs, chase results, penalties, undo, backup replay and retired batters | 11 scoring tests |
| Published site | Unique metadata, canonical URLs, rendered headings, internal links, substantial guides, sitemap, robots, ads.txt, security headers and true 404 response | Every public route |
| Production | HTTP status, canonical host, rendered content, metadata, sitemap, robots, ads.txt, headers and permanent routes | Checked after deployment |
Passing these checks reduces known regressions; it does not prove that every browser, file or local tournament rule will work. We keep explicit limits on each tool page and ask users to test with non-sensitive sample data before an important workflow.
How guide content is prepared
Guides begin with the decisions a user must make before pressing a button. Document guides explain source quality and output checks. Developer guides distinguish representation from security and link concepts to the relevant standards. Cricket guides separate software state from decisions made by the umpire, scorer or tournament committee.
We use examples written for SableApps and avoid copying competitor instructions. Publishing a large number of near-identical articles would make the site less useful, so one maintained guide covers each tool. Review dates change when the content or related workflow is actually reviewed.
Primary technical references
- RFC 4648 defines Base64 and URL-safe Base64 alphabets.
- RFC 7519 defines JSON Web Tokens and registered claims.
- MDN Web Crypto API documents the browser cryptography interface used for HS256 signing.
- PDF.js is the browser PDF renderer used to create page images.
- MDN IndexedDB documents the local browser database used by the cricket tools.
Known boundaries
The document tools do not provide optical character recognition, PDF signature verification or guaranteed recovery from a damaged source file. JWT decoding alone does not establish trust; the optional verifier covers HS256 only, and production systems must still validate claims and authorization on the server. Base64 is not encryption. The date tools do not interpret legal eligibility rules. Auction-Book and Scorebook do not provide accounts, cloud sync or simultaneous operation across unrelated devices.
These boundaries are intentional and visible so users can choose another product when the task requires cloud collaboration, regulated records, legal interpretation or specialist document recovery.
Corrections and product feedback
SableApps is owned by Ms. Manali Sable and developed and maintained by Mr. Amit Sable. Report an incorrect result, unclear limitation, broken route or accessibility problem through the contact page. Include the tool, browser, input shape and expected result using non-sensitive sample data.