Legal & trust
Trust & Security
Updated September 10, 2026
How we separate public inquiries from care information and establish responsibilities with partners.
On this page
Clear responsibilities around care
MySeema provides care navigation, coordination, and care-management support. We help organize appointments, communications, records, and follow-through. Our navigation service does not diagnose conditions, prescribe medicines, or decide or change medical treatment. Those decisions belong to your treating physicians and other appropriately licensed treating clinicians.
Provider-sponsored programs use agreed access, documentation, and review or escalation arrangements with the healthcare organization. Applicable business associate agreements govern how protected health information is handled for the partner. A signed agreement and website statement do not replace the technical and operational work required to protect information.
Public website and initial contact
The website uses HTTPS and Amazon Web Services hosting and content delivery. Organizational inquiries use Google reCAPTCHA and Zapier to route general business details to the team by email. The family path opens the visitor’s email application or telephone and does not submit family medical details through that form.
These channels are for initial contact, not medical records or emergencies. Ask for the appropriate care-information channel before sending detailed health information. Ordinary email is not an authenticated patient portal. Website hosting and inquiry tools should not be assumed to have the same role or controls as a partner’s clinical systems.
Working with a healthcare organization
Our default partner model uses access supplied by the organization to its existing EMR. We agree how work is documented and how concerns reach the appropriate care team. Relevant service and business associate agreements control the work. This does not mean that all supporting information exists only in that EMR.
Before a partnership begins, diligence should address access permissions, authorized users, systems receiving information, vendor responsibilities, record retention, incident reporting, and any cross-border access relevant to that program. Contact us to discuss the documentation and agreement applicable to your proposed service.
Security information for diligence teams
Ask about the safeguards and supporting evidence relevant to your scope, including access controls, encryption, workforce practices, subcontractors, continuity arrangements, and incident response. Documentation may require confidentiality arrangements and must match the systems and services under review.
This page does not claim SOC 2 certification, HITRUST certification, government certification, or a universal security configuration across all services. Confirm a specific requirement with MySeema during diligence rather than relying on a marketing statement.
Report a security concern
Email support@myseema.com and identify the message as a security concern. Provide a general description and a way to contact you; do not send patient records, passwords, or payment details. We can arrange the appropriate exchange of sensitive evidence. Security testing must be authorized in advance.
We review reported concerns and provide or coordinate legally required incident notifications and notices required by the applicable partner agreement. Notice timing depends on the incident, information, jurisdiction, and agreement. Public website terms do not extend a shorter contractual or legal deadline. See our Privacy Policy and Health Information Privacy notice.
Contact and assistance
MySeema
support@myseema.com
(415) 727-3362
2250 Morgan Pkwy, STE 100
Farmers Branch, TX 75234
For privacy, accessibility, security, or membership requests, tell us the type of request so it can be routed to the responsible team. Please keep the first message general. Do not send passwords, payment-card details, or medical records through a marketing inquiry.
About our program references
Our program pages link to CMS sources and identify the rate year, setting and assumptions used in examples. National payment benchmarks are distinct from a practice’s actual collections and costs. Illustrative workflows and calculations are labeled; partner testimony and published research are attributed separately.
These references support a conversation with your clinical and billing teams. They do not establish eligibility or approve a claim. A source-check date does not represent a clinical review of an individual patient. Send corrections or questions to support@myseema.com, without patient information.