Privacy policy

Who operates the site

Evicenter is published by Advection LLC.

Questions about this policy, and requests to delete an account, can be sent to justin.yu@advection-solutions.com.

Reading the site

Reading the site requires no account. Its pages are static files hosted on GitHub Pages, which receives the network address and browser details sent with every request to the site.

Links to cited documents open other websites, such as PubMed, journal publishers, and regulatory agencies, whose own privacy policies apply.

Analytics

The site uses Google Analytics to measure visits and the pages read. The Google Analytics tag loads only on pages served from www.evicenter.com, and does not load in a browser controlled by automation software.

Google Analytics sets cookies in the browser and sends Google information about each visit, such as the pages viewed, the referring page, the approximate location derived from the network address, and the browser and device type.

Google provides a browser add-on that stops Google Analytics from collecting data (opens in a new tab).

The site administrator can view aggregate Google Analytics, Google Search Console, and uploaded AI visibility reports in a private dashboard. The imported reports are stored in Supabase and are not available to other readers. They contain aggregate measurements, not individual visitor records.

Information stored in your browser

The site keeps the following in the browser's local storage:

• Display settings: the appearance, the reading text size and width, and where the PDF viewer opens.
• The five reports opened most recently, which the drug library lists.
• For each quote you flag, the label you chose, so that the flag is shown on a later visit.
• A random identifier created in the browser the first time you flag a quote, which is sent with each flag so that flags from one browser can be grouped.
• While you are signed in, the sign-in session, kept by Supabase Auth.

Display settings, recent reports, and flag labels stay in the browser. Clearing the site's data in the browser removes everything in this list.

Accounts

Readers need an account to ask questions about a report. The site administrator also uses an account to access private site statistics. Accounts are managed by Supabase Auth and can be created with Google sign-in or with an email address and a password.

With an email address and a password, Supabase Auth stores the address and a hashed form of the password, and sends a confirmation email whose link must be opened before the account can be used. A password reset email is sent only when one is requested.

With Google sign-in, Google shares the email address and basic profile information (name and profile picture) of the Google account with Supabase Auth, which stores them with the account. The site uses the email address to identify the account and shows it in the account menu. The site requests no other Google account data. Evicenter does not sell Google user data, share it with third parties for their own use, or use it for advertising.

Google and email sign-in with the same verified address open the same account.

Before an account is created, the site records a salted hash of the network address that Supabase Auth reports for the request, the sign-in method, the domain of the email address (the part after the @), and the time. These records are kept to detect and limit the creation of many accounts from one network.

Questions asked about a report

A signed-in reader can ask a question of up to 500 characters about a report. The question is sent to a Supabase Edge Function, which sends it to Anthropic's API together with the report's list of headings and the excerpts of the report that match the question. Anthropic's Claude models choose the relevant headings and write the answer from those excerpts. The request to Anthropic contains the question and the report text, and no email address or account identifier.

The question, the answer, the report it concerns, the time, the number of tokens processed, and the cost of the request are stored with the account in the site's Supabase database. They are used to return the answer, to apply the daily limit on questions, and to keep the cost of answering within a daily limit.

An answer can be shown again to another reader who asks the same question about the same version of the report. That reader receives the answer alone, with no information about who first asked the question.

Email notifications

The form at the foot of each page signs an email address up to be notified when a drug page is added. Signing up stores the address, the page the form was sent from, the time, and a salted hash of the network address. Each sign-up request is also recorded with a salted hash of the network address and the time, to limit the number of sign-ups from one network.

Notification emails are sent through Resend. Each one carries an unsubscribe link, and a mail program that offers its own unsubscribe control can use that control instead.

Unsubscribing marks the address as unsubscribed and records the time. The address stays on the list with that status and receives no further notification emails.

Quote flags

Each quote and table can be flagged as inaccurate, unsupported, incomplete, outdated, or not relevant, with an optional note of up to 1,000 characters. A flag records the label, the note, the quoted text and its place in the report, the address of the cited source, the version of the site, the time, the random browser identifier described above, and a salted hash of the network address. A flag carries no account or email address.

The hash is used to limit the number of flags sent from one network in an hour. Notes are read by a person and used to correct the reports, so a note should contain no personal information.

Service providers

The following companies process information on behalf of the site:

• GitHub hosts the site's pages and files on GitHub Pages.
• Supabase hosts the database, the accounts, and the server functions, and stores the account, question, sign-up, subscriber, and flag records described above.
• Anthropic receives each question with the report excerpts it concerns, and returns the answer.
• Google provides Google sign-in, for readers who choose it, and Google Analytics.
• Resend delivers the account confirmation and password reset emails and the notification emails.

How long information is kept

• Questions and answers: 90 days from when the question is asked. Deletion runs each time any reader asks a question, so a record can remain past 90 days while no questions are asked. Questions and answers are also deleted when their account is deleted.
• Records of account creation and of notification sign-up requests: two days. Older records are deleted the next time an account is created or an address is signed up, respectively.
• Accounts: until the account is deleted.
• Notification subscriber records, including unsubscribed addresses: until they are deleted. No automatic deletion period applies.
• Quote flags: until they are deleted. No automatic deletion period applies.
• Google Analytics data: for the retention period set in the site's Google Analytics property.
• Imported aggregate statistics and AI visibility exports: until replaced or deleted by the administrator. No automatic deletion period applies.
• Browser storage: until it is cleared in the browser. Signing out removes the sign-in session.

Deleting your information

• To stop notification emails, open the unsubscribe link in any notification email.
• An account, together with the questions and answers stored with it, can be deleted on request by writing to justin.yu@advection-solutions.com.
• Signing out removes the sign-in session from the browser. Clearing the site's data in the browser removes the other stored items.

Changes to this policy

When this policy changes, the new version is published on this page with a new effective date.