Company maintains a risk-based security program designed to protect the confidentiality, integrity, and availability of the Services. The program is intended to evolve as the platform, customers, threats, and regulatory expectations change.
Security controls may vary by environment, feature, provider, customer contract, and implementation stage.
The platform is designed to minimize unnecessary collection of sensitive information. Customers should configure forms and workflows to collect only the information needed for lawful operational purposes.
Unless a signed agreement authorizes regulated data processing, the platform should not be used as a repository for HIPAA-regulated protected health information, legal medical records, or designated record sets.
The platform supports role-based and permission-based access. Customer administrators are responsible for assigning appropriate access levels, reviewing users, removing inactive users, and limiting access to personnel with a business need.
Company administrative access to production systems is limited based on job function and business need. Credentials should be unique, protected, and not shared.
The Services may use passwords, PIN flows, session controls, token-based authentication, and other measures designed to protect account access. Company may add or modify authentication requirements to address evolving risk.
Customers are responsible for training users to protect credentials, avoid credential reuse, secure devices, and report suspicious access.
Company uses encryption in transit where supported and relies on infrastructure providers for encryption at rest where supported by the hosting and storage stack.
Customer remains responsible for protecting data after export, download, email transmission, print, screenshot, or entry into third-party systems.
Company may maintain operational, security, error, authentication, and administrative logs to support troubleshooting, security monitoring, abuse detection, compliance, and platform reliability.
The availability and retention of audit logs may vary by feature, customer tier, infrastructure provider, and contract.
The Services may use cloud hosting, databases, object storage, email, analytics, monitoring, mapping, and other third-party providers. Company selects providers based on operational, security, reliability, and business needs.
Provider availability, security commitments, certifications, and subprocessors may change over time. Company will use commercially reasonable efforts to manage provider risk.
Company may use version control, code review, testing, build processes, deployment workflows, and production monitoring to reduce the risk of defects and regressions.
Emergency changes may be made where necessary to address security, availability, data integrity, legal, or operational risk.
Company may use dependency review, patching, code review, monitoring, testing, and external reports to identify and remediate vulnerabilities based on severity and exploitability.
Security researchers must avoid accessing data that is not their own, disrupting services, degrading availability, or publicly disclosing vulnerabilities before Company has had a reasonable opportunity to investigate and remediate.
Company uses backup and recovery practices intended to support continuity and restoration. Recovery objectives may vary by system component, customer tier, provider capability, and incident type.
Company does not guarantee that every deletion, edit, or customer configuration change can be reversed. Customers should maintain independent records where required.
Company maintains processes to receive, investigate, contain, remediate, and document suspected security incidents. If Company determines that notice is required by law or contract, Company will provide notice in accordance with applicable requirements.
Customers must promptly notify Company of suspected credential compromise, unauthorized access, misuse, data exposure, or security incidents involving the Services.
Customer is responsible for user access, administrative settings, agency policies, endpoint security, network security, local storage, downloads, printed reports, exported files, user training, and compliance obligations that apply to Customer operations.
Customer is responsible for deciding what data may be entered and for configuring forms, modules, retention, and permissions consistent with Customer legal and operational requirements.
Company may provide security questionnaires, summaries, exhibits, or additional evidence under appropriate confidentiality terms. Security documentation may be updated as controls and providers evolve.
No security program can prevent every vulnerability, outage, attack, misconfiguration, credential compromise, or unauthorized event. This Security Overview does not create a warranty unless expressly stated in a signed agreement.
Security inquiries, responsible disclosures, and urgent security concerns should be sent to support@cordialsystemlogistics.com with 'Security' in the subject line, or submitted through the security or support contact channels designated by Cordial Systems, LLC.