Privacy policy

1. Who we are

Clinical Trial Events is run by Revise, LLC (“Revise”, “we”), based in Austin, Texas. Revise decides how the personal data described here is used. How to reach us is in section 13.

2. What we collect

Your account

Your name, email address and password. The password is stored as a one-way hash, never in readable form. If you turn on two-factor authentication, we store its secret and recovery codes encrypted.

Signing in with LinkedIn

If you sign in with LinkedIn, LinkedIn tells us your name, your email address, whether LinkedIn has confirmed that address, and your LinkedIn member ID. We keep the name, the email and the ID. We don’t receive your connections, and we don’t keep your LinkedIn photo or headline.

Your profile, if you fill it in

A handle, job title, organization, short bio, LinkedIn URL, website and photo. All of them are optional.

What you do on the site

Events you mark as going or maybe, and whether you checked in (when, and that it was by location). The sessions you save to your schedule, including any you picked before you had an account. Until you sign in, your browser sends us the event and those sessions’ ids only to show your schedule and the list of picks beside the sign-in form, and the event to choose where you land after you sign in. We don’t save them to an account or link them to you then. After you sign in, the next event page you open sends them to us, and we save them to your account. Reviews and ratings, and whether you posted anonymously. Reports you make about reviews. Thumbs up or down on places near a venue, and places you suggest. Organizer and speaker claims, organizer profile edits, event submissions, and talks or media you add to a speaker profile. Series, speakers, topics, cities, and organizers you follow, and which emails you chose for each. Home airports you save in Settings → Travel, which we use to build your flight links, and the temperature unit you pick there.

Public posts about events, including from people without an account

After an event ends, we collect public LinkedIn posts that mention it. For each post we keep the author’s name, headline and profile link as LinkedIn shows them publicly, the post’s text, date and link, its reaction and comment counts, and copies of up to four photos from it. We never collect profile photos, private posts, messages or connections. We use these posts only to publish event recaps.

Technical data

Your IP address, used to limit how fast requests can be made and to slow down password guessing. While you use the site we keep a session on our servers, which can include your IP address and your browser’s name and version. When you click a link in one of our emails, our email provider records the click.

Visit counts

We use Fathom Analytics to count visits. When a page loads, Fathom receives your IP address and your browser’s user agent, and turns them into a signature that is specific to this site and changes every day, so a visit can’t be linked to you or followed from one day to the next. We see only totals: pages viewed, the sites that sent visitors, browser, device type and country, and how often things happen, such as clicks through to an event’s website, hotel or sponsor, adding an event to a calendar, sharing a page, opening slides, searches that find nothing, following a page, sign-ups and event submissions. We also count clicks on flight search links, by destination airport only, never the airport you’d fly from. These counts never include your name, your email or what you searched for. Fathom sets no cookies.

Nothing on the site takes payment, so we never collect payment details.

3. What other people can see

• Reviews show your name, unless you post anonymously. An anonymous rating still counts toward the event’s average.
• Attendee lists show your name, job title and organization, whether you’re going or maybe, and whether you checked in. Never your email. You can leave one event’s list, or hide yourself from every list in Settings.
• What you follow is private. A page shows how many people follow it, never who.
• Your home airports are private. Only you see them, on your own flight links and in Settings.
• Your profile page is visible only if you make it public. It’s off until you turn it on.
• Organizer and speaker pages show what the organization or speaker publishes, not who manages them.
• Event recaps show public LinkedIn posts about an event: the author’s name and headline, the post’s text and photos, and a link to the original post. A recap’s summary never names or quotes anyone except the event’s listed speakers.

4. How we use it

To run your account and sign you in; to show the reviews, lists and profiles you choose to share; to review listings, claims and reports; to send the emails in section 6; to keep the site secure and stop abuse; and to meet legal obligations.

Where the law asks for a legal basis, ours are: providing the service you asked for (your account and what you post), our legitimate interest in running a safe and accurate directory (moderation, rate limits, security), our legitimate interest in recapping the public conversation about professional events (event recaps, section 2), and your consent where we ask for it (your location, below).

5. Your location when you check in

Check-in asks your browser for your location. The reading is sent to our server once, compared with the venue’s position (you need to be within about a kilometer), and then discarded. We never store, log or share it, and we don’t track where you go. We keep only the fact that you checked in, and when. Your browser asks your permission first, and check-in is optional.

6. Emails

We send the emails your account needs: confirming your email address and resetting your password. If you represent an organization, we also email you about its claims, profile edits and event submissions. If you join an event’s chat, we email you a daily summary of its new messages, only on days with new ones, until you turn it off in the chat or with the link in the email. If someone mentions you in an event or meetup chat and you haven’t read it about five minutes later, we email you the message, at most once every 15 minutes for each chat, until you turn mention emails off in the chat or with the link in the email. If you’re in a meetup, we email you when its time or place changes, or when it’s cancelled or taken down. If you follow a series, speaker, topic, city, or organizer, we email you when something you asked to hear about happens: a new edition or its dates, its agenda, a ticket price that goes up in a week, a speaker you follow being booked or posting slides or a recording, or a new event on a topic, in a city, or from an organizer. In Settings → Following you choose which of these each follow sends, and whether they come as they happen (at most one email a day), as a weekly roundup, or not at all. With the weekly roundup, a reminder that a ticket price is about to go up still comes on its own day. Every one has a link to unfollow. We don’t send marketing email. If we add a newsletter, it will be opt-in, and every issue will have an unsubscribe link.

7. Who we share it with

We don’t sell or rent personal data, and we don’t share it with advertisers. A few service providers process it for us, under contract:

• Laravel Cloud hosts the site, its database, and its sessions. It runs the site behind Cloudflare, which protects it from attacks and sets one cookie to tell people from bots (see our cookie policy).
• Cloudflare R2 stores photos, logos and uploaded files.
• Bento, our email provider, delivers the emails in section 6. It adds a tracking code to the links in them, so it records when you click one.
• Fathom Analytics counts visits, as described in section 2. It gives us totals only and sets no cookies.
• Laravel Nightwatch monitors the site for errors and slow pages. It receives the addresses of the pages you request and of the page you came from; your browser’s name, version, and language; the error and log messages those pages produce; and, if you’re signed in, your account number. We remove email addresses, passwords, and access codes before it receives anything, and it never gets your name, your IP address, or your location.
• LinkedIn, only if you choose to sign in with it. What happens on LinkedIn is covered by LinkedIn’s own privacy policy.
• OpenAI, our AI provider, processes signed-in visitors’ search queries and public listing text, including the text of shared slide decks, so search can match by meaning. It receives only that text, never your name, email or account.
• Apify runs the searches that find public LinkedIn posts about an event. It receives only the search terms, such as the event’s name.
• Anthropic or OpenAI, whose AI assistants our team uses to sort collected posts by topic and to draft recap summaries. A person on our team reviews every recap before it’s published. They receive the public posts, never your account details.

Our servers also ask Geoapify and Google about venues and the places near them. Those requests carry venue names and locations, not your personal data. Map links open Google Maps in your browser, where Google’s privacy policy applies. Flight links open Google Flights the same way: clicking one sends Google the airports and dates in the link. A link with no home airport carries no origin, and Google may use your location on its side.

We may disclose information when the law requires it, to protect someone’s safety, or as part of a sale or merger of Revise, in which case this policy keeps applying to it.

8. How long we keep it

We keep your account data while you have an account. When you delete it, we delete your profile, RSVPs, check-ins, follows, reviews, place reactions, and your organizer and speaker claims. We delete your home airports too. A few records stay without your name because other people rely on them: places you suggested, organizer edits you submitted, and reports about reviews, which keep a copy of the reported review for our moderation records. A speaker profile linked to your account stays on the site, unlinked. Deleting your account also erases the text of your event chat messages and cancels the meetups you host.

An event’s chat closes a week after the event ends. 90 days later we delete it, with its meetups and any reports about its messages and meetups.

Posts collected for a recap stay with the recap. If a post stops being public on LinkedIn, its photos come off our site. If you ask us to remove your post, we hide it at once and delete your name, the text, the link and the photos within 14 days; the post still counts toward the recap’s totals, without your name. If you ask us by email, we keep that email address for 90 days after we decide, then delete it.

Sessions end after 2 hours without activity. Backups and server logs are kept for a limited time, then deleted.

9. Your choices and rights

In Settings you can change your details, choose or turn off follow emails, hide yourself from attendee lists, keep your profile private, disconnect LinkedIn and delete your account, and you can post any review anonymously. Depending on where you live, you may also have the right to a copy of your data, to correct or delete it, to object to or limit how we use it, and to complain to your data protection authority. To use any of these rights, contact us (section 13). We answer within 30 days.

Is one of your posts in a recap? Use “Request removal” under the post or photo, or the form at clinicaltrialevents.com/posts/removal. You don’t need an account, and we won’t collect that post again.

10. Security

Passwords are hashed, two-factor authentication is available, the site is served over HTTPS, and only the people who run the site can reach personal data. No system is perfectly secure. If we learn of a breach that affects you, we’ll tell you as the law requires.

11. Children

The site is for professionals and isn’t meant for anyone under 16. We don’t knowingly collect data from children.

12. Where your data is stored

Revise is based in the United States, and the site and its data are hosted in the United States. Where a provider processes data in another country, we rely on appropriate safeguards where the law requires them.

13. Changes and contact

We’ll update this policy when what we do changes. The date at the top shows the last change. If a change is significant, we’ll email account holders before it takes effect and say so on the site.

Questions or requests, including the rights in section 9? Email privacy@revisetrials.com, or write to us at: