ViewGazeViewGaze
Security

Security at ViewGaze

Last updated: July 25, 2026

MRAMS handles scheduling data for Medical Representatives, doctors, clinics, and hospitals, so we treat it carefully. Here's a straightforward look at what we actually do — and don't yet do — to protect it.

Encryption in transit and at rest

All traffic to MRAMS and this website is encrypted over HTTPS. Stored data is encrypted at rest on our infrastructure.

Role-based access control

Medical Representatives, doctors, clinic staff, and union administrators each see only the data and actions relevant to their role — no broader access by default.

Audit logging

Appointment creation, changes, and cancellations are logged so activity can be reviewed and accounted for.

Maintained infrastructure

MRAMS runs on infrastructure we actively monitor and keep patched, with valid, auto-renewing TLS certificates on every domain.

Where we are today

MRAMS is an early-stage (Version 1) product. We do not currently hold formal third-party security certifications such as SOC 2, ISO 27001, or HIPAA — we haven't claimed them anywhere on this site, and we won't until they're genuinely in place. What's described above reflects security practices we've actually built into MRAMS today, not a compliance program. If formal certification becomes a requirement for your organization, talk to us before signing up so we can be upfront about where we stand.

Access and accounts

Every MRAMS account belongs to a specific role — Medical Representative, doctor, clinic staff, union administrator, or super admin — and each role has a defined, limited scope of what it can see and do. Union and hospital administrators control who has access within their own organization.

Data handling

Appointment, doctor, and Medical Representative data entered into MRAMS is used only to operate the product for your organization. See our Privacy Policy for details on what we collect through this website and how it's used.

Reporting a security issue

If you believe you've found a security vulnerability in MRAMS or this website, we want to know about it. Email yashxxbgp@gmail.com with details, and we'll respond as quickly as we can. Please give us a reasonable chance to investigate and address any issue before disclosing it publicly.

Questions

For anything else about how we handle security, email yashxxbgp@gmail.com.