Your data doesn't need another place to live.

Our technical partner is ISO 27001 certified. The certification applies to our technical partner and the scope of its certified information-security management system. Kepler26 does not represent the Mody & Associates or Kepler26 legal entity as independently ISO 27001 certified.

Kepler26 leads the engagement and assembles the technical team required for the solution. Depending on the project, that can include software and AI engineers, solution architects, cloud specialists, cybersecurity specialists, DevSecOps engineers, and identity and access-management experts from our technical delivery organization.

No. Kepler26 works from workflow diagnosis and solution architecture through software development, integration, secure deployment, adoption, and ongoing optimization. The work can start small without ending at a recommendation or prototype.

Yes. The delivery model can scale from a focused workflow automation to a larger custom system or enterprise integration. Scope, architecture, staffing, and delivery stages are defined around the implementation rather than forcing every project into the same team structure.

Kepler26 remains the primary engagement relationship and coordinates the technical resources required for delivery. Specialists from our technical partner can participate directly in architecture, security, and implementation discussions when useful while Kepler26 retains solution ownership and client leadership.

Data location is determined by the approved architecture for the engagement. Where practical, information remains in client-controlled systems, regions, providers, and access boundaries. Team location and data-processing architecture are separate considerations and should not be treated as the same decision.

Not necessarily, and often no. Where practical, Kepler26 designs workflows around systems the organization already controls, such as Microsoft 365, SharePoint, approved AI platforms, cloud environments, and internal knowledge repositories.

Not always. One of our first questions is how much can be accomplished using technology the organization already owns and has approved.

When the intended workflow, available capabilities, client approval, and appropriate access support it, workflows can be designed around Microsoft 365, SharePoint, OneDrive, Teams, Copilot, Azure, and related systems. Feasibility is confirmed for each implementation.

Where the organization's plan, permissions, available integrations, and governance policies support the intended workflow, Kepler26 can design around approved enterprise AI environments.

No. We generally prefer the opposite approach: determine the minimum information required for the workflow and limit access accordingly.

AI can accelerate quality checks, evidence review, consistency checks, annotation, claims analysis, and preparation for review. Final approval decisions should remain with appropriately authorized human reviewers.

If a workflow doesn't require restricted personal information, it should not receive it. Workflows involving PHI, PII, or other restricted information require additional architecture and governance review.

Kepler26 does not design client engagements around pooling confidential client information into a shared training dataset. Data handling requirements, model-provider terms, retention, and permitted uses should be explicitly defined for each implementation.

Absolutely. Kepler26 expects security, privacy, IT, legal, or procurement stakeholders to be involved when the workflow warrants it. We can document proposed data flows, providers, permissions, integrations, and human-control points for review before production deployment.

Access should be reviewed and removed when it is no longer required. Project-specific retention or deletion requirements should be agreed as part of the implementation rather than assumed.