TrialCurrent is a business-to-business platform operated by TrialCurrent LLC, a Wyoming limited liability company, and used by employees of clinical research organizations. It is not a consumer service, and it is not used by clinical trial participants. This policy explains what we collect, why, and who we share it with.
1. Who this covers
Three groups:
- Website visitors — anyone reading trialcurrent.com.
- Account holders — people whose organization has given them a TrialCurrent login.
- Business contacts recorded in the platform — sponsor contacts, investigators, and site staff whose professional details a customer enters as part of normal use.
2. The website
This marketing website is a set of static pages. It runs no analytics or advertising scripts, sets no cookies, and has no forms that submit to us. Two things leave the page:
- Requesting a demonstration opens Calendly, a third-party scheduling service. Anything you enter there is handled under Calendly's own privacy policy, not this one.
- Emailing us at info@trialcurrent.com reaches a mailbox hosted by Google Workspace.
Web fonts are loaded from Google Fonts, which means your browser makes a request to Google's servers when a page loads.
3. The application
Account information
When your organization creates your account we store your name, email address, assigned role, and a hashed password. Passwords are hashed with Argon2id and are never stored in a readable form.
Business data your organization enters
Records your team creates in the course of using the platform: accounts, contacts, opportunities, studies, sites, investigators, notes, and uploaded documents such as protocols. This belongs to your organization — see the Terms of Service.
Survey responses
When a site is invited to complete a feasibility questionnaire, the person responding provides their name, email, and answers. This is collected through a unique, non-guessable link tied to that specific outreach; no account is required.
Logs
The application records authentication events — whether a sign-in succeeded or was rejected — without recording passwords or credentials. Our hosting provider also keeps standard request logs.
4. How we use it
- To operate and maintain the platform for your organization
- To authenticate users and enforce role-based access
- To send the optional daily portfolio digest, if your organization enables it
- To send feasibility outreach on your organization's behalf and receive responses
- To provide support and maintain security
We do not sell personal information, and we do not use customer data to train AI models.
5. Service providers
We share data only with the providers needed to run the platform, and only what each one needs:
| Provider | Purpose | What it receives |
|---|---|---|
| Vercel | Application and website hosting | Application traffic |
| Supabase | Database hosting | Customer records stored in the platform |
| Anthropic | AI features — protocol extraction, digest narrative | The specific document text or portfolio figures for that feature |
| Resend | Sending the morning digest and outreach email | Recipient address and message content |
| Calendly | Demonstration scheduling from this website | Whatever you enter when booking |
| Google Workspace | Our email | Messages you send us |
This list is maintained as the platform changes. We may also disclose information where required by law.
6. AI features
TrialCurrent uses Anthropic's Claude models for three things: extracting structure from an uploaded protocol, capturing contacts and tasks from written notes, and drafting the narrative in the morning digest. Because protocols are sponsor-confidential, it is worth being precise about what that involves.
- Only what that feature needs is sent. A protocol document, a single note, or the day's portfolio figures — not your database, and not other customers' records.
- It is not used to train models. Under Anthropic's commercial terms, inputs and outputs from the API are not used for model training by default. See Anthropic's published position.
- It is not retained indefinitely. Anthropic's commercial data retention policy deletes API inputs and outputs from its systems within 30 days.
- A person still decides. Extraction results are presented for review rather than applied silently, and values that conflict with something already entered are surfaced rather than overwritten.
- Stricter arrangements exist. If your sponsor agreements require it, Anthropic offers zero-data-retention terms for eligible customers. Raise it with us and we will work through what your agreements need.
AI is used where the system reads. It is not used where the system decides — Control Tower signals, feasibility verdicts, win probability, and deal economics are rule-based and show their arithmetic.
7. Security
See the Security page for a fuller description. In summary: passwords are hashed with Argon2id, sessions are signed and can be revoked, access is role-based, each customer organization's records are scoped to that organization on every read and write, and data in transit is encrypted with TLS.
8. Retention
We keep customer data for as long as an organization maintains an active account. Deactivating a user preserves their historical records so that audit history stays intact rather than deleting them. If you need data exported or deleted, contact us and we will work through it with you.
9. Your rights
Depending on where you are, you may have rights to access, correct, or delete personal information we hold about you. Contact info@trialcurrent.com. If you are a business contact recorded by one of our customers rather than an account holder, your request may need to go to that organization, since they control the record.
10. Children
TrialCurrent is a business tool. It is not directed at children and we do not knowingly collect information from them.
11. Changes
We may update this policy. The date at the top of this page reflects the most recent revision.
12. Contact
TrialCurrent LLC, a Wyoming limited liability company.
Privacy questions: info@trialcurrent.com