About ColumnaLATAM

Every congress, conference, course, workshop or webinar listed here comes from a real, public source — a society's official page, a hospital or university's continuing medical education calendar, an event organizer's own site, or an open public RSS feed/API. We never invent events, dates, organizers or URLs.

Every event page lists its data source(s) and a “last verified” date. When a source only publishes a month/year, or states an event is annual with dates not yet announced, we say so explicitly (via a date note) instead of inventing a specific day.

The event submission process is deliberately simple and auditable: administrators add and periodically re-verify events through the admin panel, and every event links to at least one source you can check yourself. We don't scrape sites that prohibit it, bypass access controls, or generate abusive request volumes against any source.

Surgeons create their own account and submit their profile. A profile is never publicly visible until an administrator reviews and approves it — draft or submitted profiles are only visible to their owner and to administrators.

We never invent surgeon identities, titles, license numbers, contact details, or photos. Any sample profile used to illustrate the directory before real submissions are onboarded is clearly labeled “Sample profile” everywhere it appears, including on its own page.

A “verified” badge means the profile passed our review process for completeness and internal consistency — it does not replace independently confirming a surgeon's license and credentials with their local medical board or institution before making any care decision.

Authentication, password storage, and session handling are delegated entirely to Supabase Auth — we never see or store plaintext passwords. Every table is protected by Row Level Security, so regardless of application bugs, the database itself enforces who can read or write each row.

Sensitive administrative actions (approving, rejecting, suspending or deleting a profile; creating or editing events) are logged to a write-only audit trail that no role — not even administrators — can edit or delete from the application.