Digital delivery
Delivery may include a hosted environment, software package, repository access, documentation, training materials and deployment support. The exact list is set in the project agreement.
Timing
Prototype, test version and production milestones follow the schedule agreed by both parties. If an external hosting, network or service incident affects delivery, we communicate the impact and a revised date as soon as reasonably possible.
Delivery records
We provide release notes, access instructions and operational documentation at the agreed handover points. Clients are responsible for maintaining access to accounts and infrastructure that they own.
Communication and updates
Project communications are normally handled by the named business contacts and the support email. We keep decisions, approvals and changes in a written record so both parties can understand what was agreed. If a policy or project condition changes, we explain the effect on information handling, delivery timing or support responsibilities and identify the date the change takes effect. Written communication helps each party coordinate staff, preserve an accurate project history and resolve questions without relying on memory.
Questions and requests
Requests about privacy, delivery, a service scope, an account or a policy can be sent to support@keshersoftwarellc.com. Please include enough context for us to identify the relevant business relationship without sending unnecessary sensitive information. We may ask for reasonable verification before changing account information or disclosing project records. We aim to acknowledge a clear request within three business days and will provide a practical response or explain what additional information is needed.
Business continuity
We plan work around documented access, backups, release notes and clear ownership. External services, hosting providers and network conditions can affect availability, so project agreements identify the responsibilities that remain with each party. When an incident affects a committed milestone, we communicate the known impact, the next action and an updated expectation. Continuity planning may include alternate communication channels, staged releases, recovery copies and a temporary change freeze while the cause is investigated.
Definitions and scope
In these policies, “Kesher,” “we” and “us” mean Kesher Software LLC. “Client,” “you” and “your” mean the business or individual authorized to discuss a project with us. “Services” include software discovery, design, development, integration, deployment, maintenance, support and related professional work described in a proposal or contract. “Deliverables” include agreed source code, configurations, documentation, reports, training materials and deployed software. These pages describe our general operating rules; a signed contract, statement of work or data processing arrangement controls whenever it contains a more specific requirement.
Records and access
We maintain business records needed to respond to enquiries, administer accounts, deliver contracted work, document approvals and support an audit trail. Access is limited to personnel and service providers who need the information for an assigned responsibility, and access may be removed when that responsibility ends. Client contacts should tell us promptly when an employee changes role or no longer needs access. We may retain invoices, approvals, technical decisions and support history for the period required by contract, accounting practice or applicable law. When retention is no longer required, records are deleted, anonymized or securely disposed of according to the nature of the material.
Operational responsibilities
Each party is responsible for the information, permissions and decisions it controls. Clients should provide accurate business requirements, nominate an authorized approver, protect their credentials and review proposed releases within the agreed review window. Kesher is responsible for performing the contracted work with reasonable care, documenting material assumptions, reporting known risks and preserving the agreed acceptance evidence. A delay caused by missing access, late feedback, unavailable third-party systems or a change in direction may require a revised schedule. We will describe the dependency and proposed adjustment so the parties can make an informed decision.
Security and confidentiality
We use practical safeguards suited to the size and sensitivity of a project, including role-based access, password protection, encrypted transport where supported, controlled repositories and careful handling of production credentials. Confidential business information is used only for the relationship in which it was provided, unless the client authorizes another use or disclosure is required by law. Staff and approved vendors are expected to follow confidentiality obligations. Clients should avoid sending full payment card numbers, authentication secrets or unrelated personal information through a general contact form. If a security concern is reported, we record it, assess the affected systems and communicate appropriate containment and follow-up steps.
Changes and effective dates
We may revise a policy when our services, technology, legal obligations or operating practices change. The current version is published on this website with an effective date or a clear indication of the latest update. Changes normally apply prospectively and do not reduce a party’s rights under a signed agreement unless the parties expressly agree to amend that agreement. For an active project, we will use the agreed communication channel to highlight a material change that could affect delivery, data handling, support or fees. If you have a question about which version applies, contact us before relying on a provision.