Security is engineered into every layer.
The GMA MyCompass System uses a defense-in-depth architecture spanning identity, applications, managed devices, sensitive information, cloud infrastructure, approved integrations, secure engineering, AI processing, and operational response. Access remains permission-based, every environment remains governed, and oversight continues throughout authorized use.
Purpose-built for high-responsibility support environments where privacy, continuity, and controlled access are not optional.
Purpose-Built · Permission-Based · Continuously Governed
Nothing receives implicit trust.
No person, device, application, integration, environment, automated process, or AI capability receives unrestricted authority simply because it is known to GMA or already operates within MyCompass. Identity, authorization, context, integrity, sensitivity, and responsibility remain subject to verification and control.
Every request must earn access. Every permission must have a purpose. Every meaningful action must remain accountable.
Identity, role, context, device posture, application integrity, and operational need remain subject to validation.
Permissions are restricted according to responsibility, consent, purpose, and least-necessary access.
Previously approved identities, devices, sessions, integrations, and workflows are not treated as permanently trustworthy.
Automation can support verification, prioritization, restriction, and response, while material authority remains governed by authorized people.
A coordinated security stack across every boundary.
MyCompass layers identity, device, application, information, cloud, integration, monitoring, and response controls so that no single safeguard carries the entire burden. Each layer reinforces the others within one governed security environment.
Protection is layered. Trust remains limited. Oversight continues across the entire system.
Access must be explicitly earned.
Identity, authorization, role, responsibility, and operational need are evaluated before access is permitted and throughout authorized use.
Multifactor Authentication · Role-Based Access · Controlled Administration
Protection continues at the point of use.
Managed-device controls, application-integrity verification, secure configuration, and mobile threat defenses help protect the environments through which people access MyCompass.
Managed Devices · Application Integrity · Mobile Threat Defense
Protection begins the moment information enters the environment.
Information is protected during transmission, encrypted upon entry into the GMA-controlled environment, and governed throughout authorized storage, processing, and use.
Encryption in Transit · Encryption Upon Entry · Sensitive-Data Monitoring
Multiple controls protect the digital environment.
Cloud infrastructure, applications, APIs, network activity, and public-facing services remain protected through coordinated application, traffic, access, and threat-defense controls. Built on AWS cloud infrastructure.
Cloud Security · Application & API Defense · Web & Network Controls
Vendor approval does not create unrestricted trust.
Approved integrations remain permissioned, contractually governed where appropriate, logged, monitored, and subject to GMA’s own security and privacy controls.
Integration Review · Limited Access · Appropriate BAAs
Security awareness continues after deployment.
Security events, application activity, sensitive-data findings, device status, availability, and operational concerns are evaluated to support risk prioritization, investigation, authorized response, and continued improvement.
Continuous Monitoring · Risk Orchestration · Incident Response
Secure engineering and healthcare governance support the entire stack.
Structured Code Review · Environment Separation · Authorized Penetration Testing
Controlled Change Management · Healthcare Privacy Governance · Continuity & Incident Readiness
Secure development, controlled releases, authorized adversarial testing, contractual safeguards, documented policies, and continued improvement reinforce every layer of the operating stack.
Multiple protection layers. No single control carries the burden.
Zero-trust principles and continuous governance extend across the entire stack.
Security signals become governed action.
The MyCompass security environment brings together signals from identity, applications, managed devices, sensitive information, cloud infrastructure, network activity, approved integrations, system availability, and engineering workflows. Governed orchestration helps enrich findings, establish context, prioritize meaningful concerns, and support timely investigation and authorized response.
Signals are correlated. Risk is contextualized. Response remains governed.
Continuous Awareness
Governed Orchestration
Authorized Response
Every environment remains governed.
Security controls extend across the complete MyCompass software lifecycle. Development, testing, staging, and production remain separated and governed through controlled access, protected configuration, traceable change, structured testing, monitoring, and authorized promotion.
No environment is treated as an acceptable weak point.
The path to production is protected with the same seriousness as production itself.
The system is tested against more than expected behavior.
MyCompass combines structured engineering review, systems-assurance testing, authorized adversarial validation, and documented remediation to identify weaknesses, unexpected behavior, and operational risk before they become accepted conditions. Findings are prioritized, corrected, and tested again as appropriate.
Approval is not the end of assurance.
Controls are challenged. Findings are addressed. Improvements continue.
A finding is not considered resolved merely because a change was made. Remediation is validated according to its risk, scope, and operational impact.
Security assurance does not end when a change is approved.
Controls are challenged, findings are addressed, and improvements continue.
The objective is not to claim that weaknesses can never exist. It is to identify, understand, remediate, and learn from them before they become accepted risk.
Information enters MyCompass through a governed security boundary.
Information received from approved devices, applications, and third-party integrations is protected during transmission and encrypted upon entry into the GMA-controlled environment. From that point forward, it remains subject to GMA’s access, logging, monitoring, privacy, retention, and authorized-use requirements.
Vendor approval does not replace GMA security.
An approved source does not receive unrestricted trust, and incoming information does not bypass GMA’s own security and privacy controls.
Additional Privacy Controls Before AI Processing
When information is authorized for AI-assisted support, identity is minimized, context is limited, access remains permission-based, and human authority remains central.
Only the context appropriate to the authorized purpose proceeds into the governed AI workflow.
Nora is governed before, during, and after model processing.
Nora Caregiver Intelligence uses enterprise foundation models through Amazon Bedrock within a controlled GMA security and privacy workflow. Information is limited according to the authorized purpose, direct identifiers are removed or replaced where appropriate before model processing, access remains permission-based, outputs remain governed, and meaningful concerns may be routed to authorized caregivers while human authority remains in control.
Protecting the person’s information is part of Nora’s architecture. It is not a secondary consideration.
Your Information Is Treated as a Responsibility.
Nora is designed to use only the context needed for the authorized task, within defined privacy, access, safety, and human-oversight boundaries.
Nora’s safeguards remain subject to testing and refinement.
Security concerns, engineering changes, identified risks, operational findings, and authorized assurance activities inform continued review and strengthening of Nora’s protections.
Test · Review · Refine · Strengthen
Approval to operate does not end assurance.
Additional technical information may be made available through approved security reviews, procurement processes, or controlled discussions.
Your information is not exposed to an unrestricted AI workflow.
Nora uses authorized, purpose-limited, identity-minimized context within a governed workflow. Access remains restricted, outputs remain permission-based, and the person’s privacy, consent, and support needs remain central.
Nora’s intelligence is designed to support the person, not expose them.
Privacy obligations are translated into operating controls.
GMA reinforces technical safeguards through documented privacy practices, appropriate contractual protections, controlled access, accountable information handling, incident readiness, continuity planning, and evidence that supports oversight.
Compliance is not treated as a document stored on a shelf.
It is reflected in how access, information, vendors, incidents, responsibilities, and operational decisions are governed.
Security carries a human consequence.
We protect the system because people rely on it.
MyCompass supports people whose privacy, safety, independence, and continuity of support can be affected by the integrity of the systems surrounding them. That responsibility is why GMA treats security as an operating obligation — not a feature added later or a minimum requirement checked once.
Every layer of protection, every controlled permission, every engineering review, every monitored event, and every safeguard around Nora exists for the same reason: people, families, caregivers, and organizations place real trust in the system.
The device operates inside a managed security boundary.
MyCompass extends protection to the endpoint people use every day. Device configuration, applications, access, mobile threats, connectivity, content safeguards, and ongoing oversight remain part of one coordinated security environment configured around the person.
A device does not receive unrestricted trust merely because it belongs to the MyCompass environment.
Its configuration, applications, connectivity, security posture, and permitted use remain governed according to the authorized purpose, the person’s preferences and consent, and the responsibilities of approved supporters.
Resilience is designed into how MyCompass responds to disruption.
MyCompass combines continuous awareness, fail-safe operating principles, approved fallback pathways, controlled rollback, regional recovery readiness, protected backups, documented response procedures, and recovery validation to help preserve responsible operation through incidents, outages, unstable changes, and changing conditions.
Continuity is not one backup. It is a coordinated operating discipline.
The objective is to recognize disruption, limit impact, preserve the safest available operation, recover deliberately, and verify that restoration is working as intended.
Recovery decisions are made with the people relying on MyCompass in mind.
Availability, connectivity, system behavior, information protection, and caregiver communication can all affect continuity of support. GMA’s resilience practices are designed to help reduce disruption, preserve responsible operation, and support informed human response when conditions become difficult.
The goal is not to pretend disruption cannot happen. The goal is to be prepared when it does.
Documented responsibilities and continuity practices help guide investigation, containment, communication, restoration, and improvement during security events and operational disruption.
Detailed assurance. Shared responsibly.
The public Security page explains GMA’s operating principles without exposing the implementation blueprint. Organizations evaluating MyCompass may request access to selected security, governance, procurement, and assurance materials according to their role and legitimate review needs.
Transparency does not require unrestricted disclosure.
GMA provides meaningful evidence while protecting client security, confidential controls, proprietary architecture, and information that could increase operational risk if published openly.
Access is matched to purpose, role, and sensitivity.
Materials may be provided through gated access, qualified professional review, or a controlled confidentiality process according to the nature of the request and the sensitivity of the information.
Evidence for the right people. Protection for everyone relying on the system.
We build security with the standard we would expect for someone we love.
Every person using MyCompass is someone’s parent, child, sibling, family member, friend, or person entrusted to care. Their privacy, dignity, independence, and safety are not abstract technical requirements.
That is why GMA has worked deliberately to build security and privacy into every layer we control. That includes engineering, access, information handling, managed devices, and operational resilience, as well as Nora’s governed AI workflow and authorized human response.
We do not believe minimum safeguards are enough when real people place their trust in the system.
We continually ask a simple question: would we accept this level of care and protection for someone in our own family?
Every person deserves safeguards built with that same seriousness.
Let’s understand the person, the environment, and what must remain protected.
Every setting carries different responsibilities. GMA begins by understanding the individual, the environment, and the privacy, access, and continuity requirements that should shape the solution.
No predetermined package. No generic security profile. We begin by listening.
