Trust & security
What we do today, stated plainly — including what is not yet in place.
Account security
- Passwords are hashed with PBKDF2-SHA256 (600,000 iterations); sign-in is rate-limited with progressive lockout.
- Two-step verification (authenticator app) with single-use recovery codes. It is optional; accounts that turn it on confirm it again for sensitive actions.
- Server-side sessions you can review and sign out remotely; alerts for sign-ins from new devices.
Patient information
- Marketplace content — listings, proposals, profiles, reviews, and ordinary chat — must not contain patient information. It is automatically screened, and suspected content is held for review. Automated screening is an extra safeguard, not a guarantee.
- By default, coding happens in your own EHR or VDI environment; ClinicalCoders never collects EHR passwords.
- A restricted clinical workspace for identifiable data is disabled. It can only be enabled after the required agreements, security review, and data-residency approvals are recorded.
Accountability
- Sensitive actions are recorded in a tamper-evident, hash-chained audit trail.
- Staff access is role-limited; high-risk actions require a second approver.
What we do not claim
ClinicalCoders does not claim HIPAA, GDPR, PIPEDA, PHIPA, or other certifications or compliance. Legal documents on this site are drafts pending qualified legal review. Operating countries are limited to those explicitly enabled.
Your data
- Download a copy of your data and send access, correction, or deletion requests from Privacy and your data. We answer within 30 days.
- You can close your account when nothing is outstanding and reopen it within 30 days; after that your personal details are removed and a deletion certificate is emailed to you. Records we must keep (contracts, payments, audit) are kept for their retention periods without your name.
Service providers
Providers that process data for ClinicalCoders when enabled in production:
- Square — card payments and seller payouts (card details go directly to Square, never to our servers).
- Email delivery — not configured (development uses a local mail pickup folder) (emails contain no patient information or message content).
- Hosting — not configured (development runs locally).
The inventory with data categories and regions is maintained in the operator's privacy register and published before launch.
Contacts
Privacy questions: info@clinicalcoders.net
Report a security concern: info@clinicalcoders.net