Privacy Policy

Home, the company directory, and policy pages are public. Guests can view calendar events within the next 30 days (including today, based on U.S. Eastern Time). Company details require sign-in. During the free beta, Google sign-in through Supabase unlocks all company research, calendar events, and comparison tools without payment.

When a user chooses Google sign-in, Google can supply Supabase with a Google account identifier, email address, display name, and profile image when supplied. For the application's access decision, Biocatalystwatch checks only the verified subject identifier (sub) in Supabase claims.

Biocatalystwatch uses Google sign-in data to complete authentication, maintain the signed-in session, and control read-only access to company workspaces, calendar events, and comparison tools. Weekly-email consent is a separate, optional choice described below.

Google sign-in data is not used for advertising, payments, personalized profiles, or AI model training.

When configured, Kakao, Facebook and X sign-in pass the provider account identifier and available profile details to Supabase; email may be absent depending on the provider and permissions granted. We do not post to your social accounts or access your messages. Passwordless email sign-in uses the address you enter to deliver a sign-in link. These methods grant the same free-beta read access as Google sign-in, not administration rights.

Email authentication requires a configured delivery service. Resend is the selected SMTP provider; when enabled in Supabase, it processes the recipient address and authentication message for delivery. Enabling email sign-in does not subscribe you to a newsletter.

You may separately opt in to future weekly clinical and FDA updates in Email preferences. The checkbox is unchecked by default, consent is not required to use the service, and you can withdraw it on the same page.

We store your choice, its update time and notice version, and the associated verified account email in your Supabase account. Consent for an old address does not automatically apply to a changed email address. The current feature records preferences only: no newsletter, mailing schedule, or contact transfer to Resend is enabled. Newsletter delivery will be announced separately when ready.

Supabase SSR authentication uses browser cookies to read, refresh, and maintain the login session. Those cookies may contain authentication session data, including access and refresh tokens. Depending on the authentication response and configuration, the cookie payload may contain other account or token values as well.

Relevant cookies are sent with application requests and are processed during server-side session validation. Signing out asks Supabase to end the application session and update the related session data.

Company access requires a verified login session. Legacy bcw_company_previews cookies are no longer read or used to grant access.

The browser's local storage may retain opened tabs, the last workspace location, comparison selections, and update timestamps so the interface can reopen in a familiar state. This interface state is separate from authentication cookies and can be cleared with browser storage controls.

Google processes the OAuth sign-in, Supabase processes authentication, session, and access-control data, and Vercel may process request and technical delivery data while hosting and serving the application. Authenticated requests reaching the Vercel-hosted application can include the session cookies described above.

Google sign-in data is handled through the Google-to-Supabase-to-Vercel application flow for sign-in, session maintenance, access control, application delivery, and optional email preferences. Biocatalystwatch does not sell that data or disclose it outside this service flow for advertising, payments, personalized profiles, or AI model training. Additional configured sign-in providers and authentication email delivery are described above.

Questions about this notice or the application's data handling can be sent to the email below.

We use Vercel Web Analytics to measure aggregate visits and page views, including page paths, referring sites, country, browser, and device type. Web Analytics does not use tracking cookies. Our page-view integration removes URL query parameters and fragments before sending the page URL and does not attach account names or email addresses to analytics events.

This policy may be revised when the service or its data handling changes. The current revision date is shown on this page.