Security
Advisory work depends on discretion. This page summarizes how we think about protecting Evolve My Business AI customer data—without overstating certifications we have not completed.
Encryption and transport security
Web traffic to Evolve My Business AI uses HTTPS (TLS) so data is encrypted in transit between your browser and our services. Backend integrations and cloud APIs also rely on TLS for typical request paths. Encryption at rest is provided by our cloud infrastructure as part of standard object and database storage practices; exact mechanisms can vary by component and region, and we can answer diligence questions on a case-by-case basis.
Access control and authentication
Access to projects should be deliberate. The product is designed so work happens in scoped workspaces with explicit membership—rather than broadly shared drives with unclear permissions. Strong passwords, careful handling of session links, and prompt removal of users when engagements end remain customer responsibilities we reinforce in documentation and support conversations.
No control eliminates risk entirely. Phishing, credential reuse, and device compromise remain common failure modes across SaaS. We monitor and improve our application security posture over time; customers should pair platform controls with firm-level policies (MFA where available, MDM on consultant devices, clean separation of personal and client accounts).
AI processing and subprocessors
Features that summarize or draft from uploaded content may rely on model providers operating under contractual terms intended to restrict use of customer content for training public models. Configuration details can evolve; for regulated engagements, review the current privacy policy, data processing terms, and your own client obligations before uploading highly sensitive material.
Typical infrastructure categories that may process or store customer data include: cloud hosting and databases, object storage for uploads, identity and authentication services, payment processing, transactional email, and AI inference providers. Exact vendors and regions depend on your deployment; diligence questionnaires should be completed with the specific stack your organization uses—not assumptions from this general page.
Logging, availability, and incident reporting
Like any cloud SaaS product, Evolve My Business AI relies on service providers for uptime and operational monitoring. We do not guarantee uninterrupted availability; we work to detect failures and restore service proportionate to severity. If you believe you have discovered a security vulnerability, contact us through the support channel on our contact page with enough detail to reproduce the issue—please avoid publicly posting sensitive exploit material.
Compliance programs (honest status)
Formal attestations such as SOC 2 Type II require sustained controls, evidence collection, and independent audit. We do not claim SOC 2 completion on this marketing page unless and until we publish an attestation report for a specific scope and period. If a compliance roadmap item is in progress, we will describe it as roadmap work—not as finished certification.
If your procurement team needs a questionnaire answered or a review call, contact us via the channels on our contact page. We will distinguish what is implemented today from what is planned, so you can make an informed vendor decision.
