Privacy
Panoptic Bio, Inc. collects personal information, and this page sets out what we collect, who else sees it, where we keep it, and what you can ask us to do with it. It describes what our systems do today. Where we do not yet do something, we say so instead of promising it.
What this covers
- panoptic.bio, our company website
- trialterminal.bio, the Trial Terminal
- tower.panoptic.bio, the BioTower
- finance.panoptic.bio, the Finance tool
The short version
- On the company website we set no cookies and run no tracking or analytics. Google hosts it and still sees and logs every request.
- Our products have accounts. You sign in with Google, and we never see or store a password.
- No analytics service, ad pixel, tag manager or session recorder runs on any of our sites.
- Our own systems run in the United States, on Google Cloud. A few other companies, listed below, hold copies of specific things.
- We delete nothing on a schedule, and there is no delete button. Email us to have your data removed and one of our developers does it by hand.
The company website
If you only read pages on panoptic.bio, we set no cookies, save nothing in your browser, and load no analytics service, tag manager, advertising pixel, session recorder or error reporter.
Google hosts the site, and Google sees and logs every page request, including your IP address and which browser you used. Nobody at Panoptic has set how long those logs are kept, so they last as long as Google's default keeps them.
Our pages also load their typeface from Google. Your browser asks fonts.googleapis.com for a stylesheet and fonts.gstatic.com for the font file. Both addresses belong to Google, and a request to either one tells Google which browser sent it and from what IP address. The same is true of our product pages.
The contact form
The form asks for your name, your email address, your organisation, what your message is about, and the message itself. It has no other field: no password, no phone number, no payment detail.
What you send goes to a server we run, which turns it into an email to the people here who answer that form. We do not write it to a database, so your message is in that inbox and nowhere else on this site. Two companies handle it on the way and both act for us rather than for themselves: Google Cloud runs the server, and Resend delivers the email. What reaches them is what you typed, together with the address you gave so that we can reply to it.
If a message does not get through, the page you land on says so. We never print a thank you over a message that did not arrive.
Signing in and having an account
Accounts exist only on the products. The company website has no account, no sign up form and no password. You sign in with Google, and the first sign in creates your account. Signing in loads Google's sign in code into the page, and Google's sign in button relies on Google's cookies.
When you sign in, Google tells us four things: your Google account identifier, your email address, whether Google has verified that address, and your display name. Account creation collects nothing else.
Alongside those four things we store a role, an account status, and the timestamps for when we created and changed the record. If we have prepared a payment link for you, we also create a customer record at Stripe and store the identifier Stripe gives us. That happens when we make the link, before any payment. We do not store your postal address, your phone number, your job title or your card number.
While you are signed in:
- We set one cookie, named
panoptic_refresh. It keeps you signed in for up to seven days. Scripts cannot read it, and your browser sends it only to our sign in address, over an encrypted connection. - Your browser's local storage holds your access token, your email address and your display name.
Asking for access
Anyone can ask for access without an account. That form takes your email address, and optionally your company name, which plan interests you, and a message of up to 2,000 characters.
We store what you send. Two people at Panoptic Bio, Inc. also get a copy by email, so that somebody sees it. Resend, an outside email service, carries that email. If Resend is not switched on, no email goes out and your message sits in our database only.
We do not check that the email address belongs to the person who typed it. If someone has put your address on our list without your permission, email us and we will remove it.
What is logged automatically
Every request to our API goes into a log with the IP address it came from, and with your account id if you were signed in. Signing in writes your email address into that log, and so does asking for access, even though you do not have an account. Any request our abuse limits turn away goes into the log too.
Those logs sit in Google Cloud Logging, inside our own Google Cloud account, and we have set no retention period, so they last as long as Google's default keeps them.
IP addresses also feed our rate limits, so one visitor cannot overwhelm the service.
No table in our database has a column for an IP address, a browser, a device or a location. Such details live in our logs and in the rate limit counters.
Paying us
There is no checkout on our sites.
Buying from us happens only after a conversation. A member of our team creates a Stripe checkout page for your account and sends you the link. A subscription covers one named person, so it is tied to your account. You enter your card details on Stripe's own page, and those details never touch any Panoptic system. Stripe's code does not run on our pages.
To create that page, we send Stripe your email address, your display name, and our internal identifier for your account. Stripe then tells us what happened. We store your subscription status, the billing period, invoice amounts, and the complete record of each event exactly as Stripe sends it. Those event records can contain billing details Stripe holds about you, and nothing removes them.
A member of our team sometimes gives an account a paid tier for free. Nobody takes a payment and nothing goes to Stripe, but we keep a record on your account showing which plan you were given and that we granted it rather than charged for it.
People who are not our users
Our products carry public clinical trial records. Some name the investigators running a trial and include their contact details. Where a trial comes from ClinicalTrials.gov, we store the record exactly as that registry publishes it, contact details included. Anyone can read some of it without an account. Feeds from certain other registries strip the investigator contact fields out before we store the record. Academic citations in our model registry carry author names as well.
None of this came to us from the people named in it. It came from public registries and public web pages. If you are named in one and want your details taken out of our copy, email us.
Who else sees your data
- Google. Our websites, our API, our database and our logs all run on Google Cloud. Google's sign in service handles signing in. Google Fonts serves our typeface.
- Stripe. Handles payment, and only for people we have prepared a payment link for.
- Resend. Sends the notification email when someone asks for access, and will carry contact form messages once that form is connected.
- An outside AI provider. Some of the explanatory text in our products is written by an AI model. What we send it is built from disease names, trial statistics and company names. We do not send your name, your email address, your sign in details or anything you type.
- Calendly. Booking a call takes you out through a plain link to Calendly, which we never embed, so your browser sends nothing there until you click through. Once you follow a link like that, you are on someone else's site, where that site's rules apply and ours do not.
No advertising, marketing or analytics service receives anything from any of our sites.
Where your data is kept
Panoptic's own systems run in the United States, on Google Cloud. The database there has no public address, only our own private network can reach it, and Google encrypts it at rest with Google's own keys. If you are outside the United States, we still process your information there.
How long we keep it
We do not delete anything on a schedule, we have not set retention periods, and nothing expires automatically. Records stay until a person removes them.
What you can ask for
Email info@panoptic.bio. You can ask us to:
- tell you what we hold about you,
- send you a copy,
- correct something that is wrong,
- delete your data.
There is no button for any of this. The product has no delete function at all. One of our developers carries out every request by hand, working directly on our database. We can remove an access request from the list straight away.
Some things we cannot fully undo:
- Records that Stripe holds about a payment are Stripe's, and their rules govern them.
- Anything already written into our logs, or into a backup, cannot be picked out one by one.
Changes to this page
If we change what we collect or what we do with it, we will update this page.
Contact
Panoptic Bio, Inc. info@panoptic.bio
San Francisco, CA