Your Privacy, Protected.

Your message goes straight from this page to the clinic’s intake endpoint. There are no portals to sign up for, no accounts to create, and no detours through third-party marketing tools. You type, we securely relay, the clinic receives. That’s it. This direct path helps clinics respond faster and keeps your information with the people who can help you, not in a general database. It’s simple, predictable, and designed for medical follow-through.

We don’t store the content of your message after transmission. Medixlinx operates as a pass-through relay, not a warehouse. We keep only a small delivery record—like a timestamp, success flag, and a technical hash for audit—not your words, symptoms, attachments, or contact details. No message bodies are indexed for search, mined for advertising, or exported to data brokers. If a clinic asks, we confirm delivery status without exposing what you said.

Your connection is protected with modern TLS encryption from your browser to the clinic’s endpoint. That means the message text you type is scrambled in transit, so only the intended recipient can read it. We enforce secure transport settings, discourage weak ciphers, and apply HSTS on our domains to help browsers default to encrypted requests. These safeguards work quietly in the background while you focus on describing your need clearly and quickly.

We maintain an envelope-only routing log that records metadata needed for reliability, not message content. Think of it like a postal receipt: a unique message ID, when it was sent, where it was delivered, whether it succeeded, how long it took, and an irreversible checksum that proves consistency without revealing details. This audit trail helps clinics verify handoffs and helps us improve uptime—while keeping your actual words out of logs, analytics, and dashboards.

We keep PHI pages free of advertising pixels, retargeting tags, and cross-site trackers. Nothing you type here is used to build marketing lists or behavioral profiles. We don’t fingerprint devices, sell data, or share message content with analytics providers. Public marketing pages may use simple, aggregate analytics, but the intake flow stays clean and private. That boundary ensures your medical request isn’t repurposed for ads and that staff see only what they need.

If the clinic is closed or temporarily offline, we may place your message in a short-lived, encrypted queue and deliver it automatically at the next opening. Queued messages have strict time limits and are destroyed after delivery or expiry. This lets you reach out when it’s convenient without worrying your request will get lost overnight. We’ll also show a clear after-hours notice so you know when to expect a response.

Medixlinx is built to support HIPAA obligations under Business Associate Agreements. Our role is limited: transmit the message to the provider’s designated endpoint and keep a minimal delivery record. We provide security controls—transport encryption, access discipline, rate limits, and logging that excludes content—to align with least-data principles. If your organization requires BAAs, we’ll sign them and flow those obligations to any essential subprocessors, keeping responsibilities clear and your data footprint small.

Your rights under privacy and health laws are exercised through your provider, who controls the patient record. Because we don’t retain message content, we can’t edit, export, or delete what we don’t store. If you need a copy of your message or want to correct information, contact the clinic directly. We’ll support them in fulfilling requests covered by our agreement and confirm delivery details when necessary—without exposing the content of your communication.