US contract and US-hosted data
Salt Technologies, Inc. signs your agreement. Customer documents are stored in Amazon S3 in us-east-1. Our production team is in Pune, India, so work moves overnight across US and India time zones.
Every file is checked by a person with a screen reader (NVDA, JAWS) and validated with PAC. The delivery evidence identifies the reviewed version and review method.
Security & data handling overview (PDF)Meet the founder
Nilesh Gadekar is the founder of DistrictProof. He leads the service’s focus on practical document remediation, human review and clear delivery evidence for district teams.
Why DistrictProof
School teams publish a steady stream of information: board materials, enrollment instructions, menus, forms, and notices. The files need to work for the people who use them. DistrictProof helps districts size that work, set priorities, and record delivery.
A brand of Salt Technologies, Inc.
DistrictProof is a brand of Salt Technologies, Inc., founded by Nilesh B. Gadekar. Delivery is based in Pune, India, serving public school districts in the United States. Project scope, delivery responsibilities, and contracting details are confirmed before work begins.
What guides the work
- Source-first document fixes where practical
- Human review alongside automated checks
- Defined scope and fixed quotes
- Evidence that identifies the version, date, and method
- Practical guidance in plain language
Company facts and questions
For a concise reference, visit company facts. For entity details, procurement documents, or a conversation about your project, contact info@districtproof.io.
Why the district context matters
The people responsible for a district website are often coordinating work across departments. They may manage public notices, board materials, family instructions, and a long archive while depending on different content authors and software vendors. DistrictProof focuses on that operating reality: identify the work, make ownership clear, and keep evidence connected to the files that families receive.
The service model brings together three needs. Docs addresses the existing document work. Web reviews the tasks and templates around that content. Care establishes a routine for what gets published next. A district can use one service or scope them together, without treating every website question as a reason to replace its platform.
How we want buyers to evaluate us
Start with the work, not a slogan. Ask whether the proposal explains the document mix, the source strategy, the human review method, the delivery record, and the publishing handoff. Look for a fixed scope that your team can understand and a revision process that does not leave later changes ambiguous.
We use those same questions to organize the DistrictProof offer. The site explains how the process works, what dated evidence should show, and which details belong in a purchasing review. That gives your team concrete points to discuss before selecting a provider.
A direct relationship with the people responsible
Nilesh B. Gadekar is the founder named for DistrictProof, a brand of Salt Technologies, Inc. Delivery is based in Pune, India, with the service focused on U.S. public K–12 districts and the partners that support them. Contracting details, delivery responsibilities, and project-specific contacts are confirmed before an engagement begins.
Contact info@districtproof.io to discuss a sample, a procurement requirement, or an ongoing publishing need. For a first view of the publicly linked documents on your website, request a free PDF Backlog Report.