“Secure document exchange, built for clinical research — not retrofitted for it.”
By TechData Service Company LLC
Tagline: Secure document exchange, built for clinical research — not retrofitted for it.
30-second version: SecureDepot is TechData Service's secure document exchange for clinical research teams — a dedicated channel for sharing protocols, safety data, and DMC packages with sponsors, CROs, and study teams, without email attachments or generic file-sharing risk. Every upload, download, and account action is authenticated, scoped to the right client/project, and captured in a tamper-evident audit trail architected to 21 CFR Part 11 standards — so you always know exactly who accessed what, and when. Every upload is checked for malware before it is stored. It's fast, modern, and built around how a study team actually works: two-way channels, organized packages, automatic notifications, and file version history, all with the compliance rigor clinical trial data demands.
TechData Service was founded in 2000, and SecureDepot has been part of our work since we built it in 2008. For nearly two decades it has carried sensitive study documents — protocols, safety data, Data Monitoring Committee packages — between our team and the sponsors, CROs, and DMC members we work with every day. SecureDepot has now been rebuilt from the ground up: the same trusted exchange, hardened for the compliance standards clinical research demands today.
SecureDepot isn't a generic file-sharing tool retrofitted for research. Every design decision starts from how a study team actually works:
SecureDepot was rebuilt around six principles that matter most when the documents crossing the wire include clinical trial safety data:
Authentication. Passwords are stored with modern, salted hashing (bcrypt/Argon2id), and passwords carried over from the previous system are upgraded to it automatically at their next sign-in. No administrator can view or change your password: new accounts are activated from an emailed link where you choose your own. Two-factor authentication is required for every TechData staff account, can be required of any individual account, and is open to anyone who wants it — an authenticator app (TOTP, the same standard used by major banking and enterprise apps) or a one-time code by email, whichever fits how someone works. Forgotten your password? Self-service reset by username or email, no help desk ticket required — and the response is identical whether or not the account exists, so the reset form itself can't be used to fish for valid usernames or addresses. An unattended session warns you with a countdown and then signs itself out, and an account that is locked or deactivated is signed out on its very next click, not whenever its session happens to expire.
Authorization. Access isn't a matter of which links happen to be visible — every action is checked against your role and your specific client/project assignment on the server, every time, for every request. A user scoped to one engagement can never reach another's documents, regardless of what they might try to guess or type into a URL — including the one-click links in upload notifications themselves: each one is re-verified against your actual access at the moment you click it, every time, not just trusted because it arrived in your inbox. Isolation between clients/projects is built into how the data is stored and fetched, and it fails closed: if an access check were ever missed, the result would be nothing shown, never another client's documents.
Integrity. Every file is checked for malware with ClamAV before it is stored. An infected file is refused outright rather than quarantined — along with the rest of that upload, so no package ever arrives half-complete — and never becomes available to download; administrators are alerted at once. If the scanner can't give an answer, the upload is refused and can be retried, never quietly accepted unscanned. Every create, update, and deletion of a document, folder, user, or client/project record is captured with the exact before-and-after values — not just "something changed," but precisely what changed, by whom, and when. A deleted document isn't destroyed on the spot: it goes to a Trash an administrator can restore it from, and removing it for good takes their password and a stated reason, both on the record. Nothing disappears with a departing user either: an account that has uploaded anything can't be deleted, only deactivated, so the record of who did what stays whole.
Auditability. That trail isn't just logged — it's tamper-evident. Every audit entry is cryptographically chained to the one before it, so any retroactive edit to history, however it happened, is mathematically detectable. Authorized staff can review, filter, and export the full audit trail themselves — no engineering ticket required to answer "who did what, and when."
Availability. Modern, actively maintained infrastructure — current-generation Linux, MySQL, and a supported application framework — replacing components that had run unchanged, and increasingly fragile, for over a decade.
Confidentiality. Every TechData team member with system access operates under a signed confidentiality agreement, as they always have. Every connection is encrypted in transit with TLS.
SecureDepot is architected to the standards of 21 CFR Part 11 electronic-record requirements — attributable, tamper-evident audit trails and documented, testable access controls — because the documents it carries are used to support real clinical trial oversight.
If you've used the previous SecureDepot, here's what's different day to day:
Everything you relied on is still there: the same two-channel exchange model, the same client/project-scoped access, the same accounts and permissions your team already understands.
Contact your TechData Service representative to learn more about SecureDepot, or to get set up with access for your study team.
TechData Service Company LLC — founded in 2000; SecureDepot in service since 2008.