Privacy Policy

• Account information: your name, your email address, and how you sign in (Google, Microsoft, Apple, or an email address and password). When you sign in with Google, Microsoft or Apple, that provider tells us your email address, your name and an identifier for your account; we never see your password there. If you use Apple's "Hide My Email", we receive a private relay address; you can ask us to link it to your lab.
• Access information: your role, the labs you belong to, your default and active lab, your approval status, and who approved you and when.
• Lab data: inventory (antibodies, vendors, catalog and lot numbers, clones, fluorophores, storage locations and box positions, concentrations, amounts, low-stock thresholds and titers), reservations, panels and panel runs, titration records, instrument QC files and events, validation evidence, and the audit trail of who did what and when.
• Files you attach: titration figures (PDF, PNG, JPEG or TIFF), instrument QC files and validation evidence, stored for your lab.
• Contact form: your name, work email, organization, team type, what you need help with, and your message. It is emailed to us.
• TiterPubs submissions: the dataset files you upload and, if you give them, your name and email address (when you are signed in, your account's name and email). The files are stored in Metrdy's Google Drive, in a folder labelled with the date and your email address if you gave one, and we are notified by email.
• Payment: the Subscribe button opens Stripe's own checkout page. Stripe processes the payment and shows us your email address, the name on the payment and what you bought; we never see your card number. Stripe's privacy policy applies to that page. We match a payment to your Metrdy account by email address.

The Metrdy mobile app is a bench-side tool for your lab's inventory, reservations, panels, panel runs and titrations. Besides the information above, it handles:

• Label photos (Scan & add inventory, Find a vial by photo): when you photograph a vial label, packing slip, receipt or invoice, the app reads its text on the phone (with Google's on-device ML Kit; the photo is not sent to Google) and sends the photo and that text to the Metrdy backend over HTTPS. The backend sends the photo to Anthropic's Claude vision model to read catalog numbers, lot numbers and other fields, and you review the result before anything is saved. Metrdy does not keep these photos: they are read and discarded. Anthropic processes them under its commercial terms.
• Titration figures: a photo or file you attach to a titration record is uploaded and kept with that record, so the people in your lab can open it later. Before it is stored, our server removes location data and other photo metadata (EXIF, such as the GPS position and camera details). If you are offline, the app keeps the figure on the phone until it can upload it.
• Data kept on the phone: so the app works on a slow or absent network, it keeps an encrypted copy of your last-loaded inventory, panels, reservations, panel runs and lab selection in the platform's secure storage (Keychain on iOS, EncryptedSharedPreferences on Android). The copy stays on the phone, and signing out or deleting the app removes it. Changes you make offline are kept the same way until they can be sent.
• Generated documents: when you open a panel run's protocol, the app builds the PDF on your phone. It is not uploaded; Share or Print hands the file to your phone's share or print system.
• Crash reports: when the app crashes or hits an error, it sends a report to Sentry: the error, the app version, the device type and operating system, and the app actions just before it. We do not attach your email address or other personal details.
• Device and diagnostic information: the app version, platform (iOS or Android), and request identifiers, used to operate, debug and secure the app.

• Camera — to photograph a vial label, packing slip or invoice, a vial you want to find, or a titration figure. Used only when you tap a camera action.
• Photo Library — to pick an existing photo or PDF instead. Metrdy reads only the file you choose.
• Network — to sign in, sync your lab's data, send changes and upload the photos and files you choose.

The app does not access your contacts, calendar, microphone, location, health data, motion data, or advertising identifier.

The website shows the same lab data as the app, and adds panel planning, titration and instrument QC tools, user approvals, and the public tools (TiterFinder, TiterPubs, TiterGuide). Besides the information above, it handles:

• Add Inventory photos and files: images or PDFs you upload to read inventory fields are sent to Anthropic's Claude vision model, the same way as the app's label photos, and are not kept by Metrdy.
• Protocol download history: when you download a protocol PDF from the panel planner, the website records the panel name, the panel as it was, the time and your user id, so you can open that PDF again later.
• Usage and diagnostic information: basic information used to keep the website running, find faults and improve it, and, only with your consent, Google Analytics (next section).

Google Analytics. The website uses Google Analytics 4 to see which pages are used and how people find them, and it runs only if you accept it in the cookie banner. Until you do, its script is not loaded at all, so Google receives nothing from it. Google Analytics never runs on TiterPubs (metrdy.com/titerpubs and every page under it), even after you accept, or on the sign-in link pages under metrdy.com/auth, whose addresses carry one-time sign-in codes. When it runs, Google receives the address and title of the pages you view, the page that sent you, your browser, device type and screen size, and an approximate location worked out from your IP address; Google Analytics 4 does not log or store IP addresses. We do not send it your lab data, your name or your email address. Google keeps this data for the period set in Metrdy's Google Analytics account, at most 14 months.

Changing your answer. “Cookie settings” at the bottom of every page withdraws your answer: Google Analytics stops, its cookies are removed, and the banner asks again. Clearing this site's data in your browser does the same.

What the website keeps in your browser. Only Google Analytics needs your consent. Everything else is needed for the site to work or to remember a setting you chose, is read only by Metrdy's own pages, and is never used to track you.

• sb-…-auth-token Cookie

  Your sign-in session, set by Supabase Auth when you sign in, so you stay signed in from page to page. A long session may be split into several cookies with the same name and a number on the end, and a short-lived companion cookie is used while a sign-in, or a link we email you, completes.

  How long: Until you sign out, or the session expires.

• metrdy_recovery Cookie

  Set only when you open a password-reset link: it lets you choose a new password without being emailed a second code.

  How long: 15 minutes, or until you change your password.

• metrdy_cookie_consent Browser storage (localStorage)

  Your answer to the cookie banner: accepted or declined.

  How long: Until you change it with “Cookie settings” or clear this site’s data.

• metrdy_antibody_dataset_v3 Browser storage (localStorage)

  A copy of the public antibody database that TiterFinder, the vendor comparison and the OMIP order sheet read, so those pages open quickly. It holds no personal data.

  How long: 24 hours, then it is fetched again.

• metrdy_titerfinder_sort Browser storage (localStorage)

  How you last sorted the TiterFinder table.

  How long: Until you go back to the default sort or clear this site’s data.

• _ga and _ga_L8JXCD4Q0K Cookie · only with your consent

  Google Analytics’ cookies, which tell your visits apart from other visitors’. Set only after you accept analytics.

  How long: Up to 2 years (Google’s default), or until you withdraw consent, which removes them.

Videos. The videos on the home page load from YouTube (youtube-nocookie.com) only when you press play; until then nothing is requested from YouTube. Once you play one, Google's privacy policy applies to it.

Metrdy uses information to:

• Sign you in, and check that you are approved for a lab or organization.
• Show the inventory, reservations, panels, titrations and QC data of the lab you have selected.
• Record inventory transactions (use, edit, reserve, cancel a reservation, new stock, bulk use, run or reserve a panel) and update amounts.
• Read inventory fields from photos and files you choose to upload, so you need not retype them.
• Keep titration figures and files with the records you attach them to.
• Keep an append-only audit trail for accountability and traceability.
• Generate protocol PDFs for panels and panel runs.
• Send the emails you or your lab expect: expiring vials, low stock, run reminders and released reservations, and the messages that sign-in needs.
• Answer contact-form messages and TiterPubs submissions, and match a payment to your account.
• Understand how the website is used (Google Analytics, only with your consent) and fix crashes in the app.
• Keep the service secure and stop spam and abuse.

Sign-in is handled by Supabase Auth. On the website you sign in with Google, Microsoft, or an email address and password. In the mobile app you sign in with Google, Apple (on Apple devices), or an email address and password.

If you use an email address and password, Supabase stores the password only in hashed form; Metrdy never sees it. Supabase emails you to confirm your address, to reset a forgotten password, and with a one-time code when you change your password on the website. If you turn on two-factor sign-in, Supabase stores the key your authenticator app uses.

Being able to sign in does not by itself give access to lab data: a lab manager or a Metrdy administrator must approve you for a lab. New sign-ups are checked automatically for signs of automated (bot) accounts and reported to Metrdy staff by email for review.

Metrdy uses these companies to run the app and website. Each receives only what it needs for the job described. Metrdy's database and servers are in the United States.

• Supabase — the database (lab data, audit trail, protocol download history), sign-in (Supabase Auth), and storage for the files you attach.
• Render — hosts the Metrdy website and backend servers.
• Cloudflare — sits in front of metrdy.com for its domain names, content delivery and protection from attacks, so it handles your IP address and the requests your browser makes.
• Google — Google sign-in (website and app); Google Analytics (website, only with your consent, never on TiterPubs); Google Drive (files contributed to TiterPubs).
• Microsoft — "Sign in with Microsoft" on the website.
• Apple — "Sign in with Apple" in the app.
• Resend — sends Metrdy's emails: contact-form messages and TiterPubs submission notices to us, and lab notifications to you.
• Anthropic — its Claude vision model reads the label photos, packing slips and invoices you choose to scan. Metrdy does not keep them.
• Stripe — takes subscription payments on its own checkout page.
• Sentry — receives crash and error reports from the mobile app, and from our servers when error reporting is on there, without your email address or other personal details.

Metrdy does not sell or rent personal information, and does not share it for advertising.

Metrdy shares data only as needed to:

• Run the app and website through the service providers above (for example, sending a label photo to Anthropic when you choose to scan one).
• Let the approved people in your lab or organization see its inventory, reservations, panels, panel runs, titrations, QC data and audit history.
• Publish what you send to TiterPubs for publication: a dataset or community report you contribute may appear on metrdy.com/titerpubs with its credits, and a community report is signed with your name, as its form says.
• Comply with legal obligations, or protect the security and integrity of the service.

Data travels over HTTPS. Roles and lab membership are checked by the Metrdy API on every request, and the database refuses direct reads of lab data from browsers and apps (Row-Level Security), so only the Metrdy backend reads it. The app's on-phone copy is encrypted, two-factor sign-in is available, and inventory changes are recorded in an audit trail. To stop spam and abuse, our servers count, in memory and for up to an hour, how many requests each network (IP) address makes to forms such as the contact form and TiterPubs uploads.

No system can guarantee absolute security. Protect your sign-in accounts, use approved devices, and tell us about any access or inventory activity you do not recognise.

Metrdy keeps lab data (inventory, reservations, transactions, panels, panel runs, titrations and their figures, QC data and attached files) for as long as needed to support lab operations, accountability, troubleshooting and recordkeeping.

Audit records are part of how inventory is controlled and traced, so they may be kept when inventory records are corrected or when a user account is deleted. Records you created stay with your lab, so the history that refers to them still reads correctly.

Photos and files sent only to be read (Scan & add inventory, Find a vial by photo, Add Inventory) are not kept after they are read. Contact-form messages and TiterPubs submissions are kept for as long as we need them to answer you, and a published TiterPubs dataset for as long as it is published. Crash reports are kept for Sentry's standard retention period. What the website keeps in your browser, and for how long, is listed above. The app's on-phone copy is removed when you sign out or delete the app.

• Accept or decline Google Analytics, and change your answer at any time with “Cookie settings”.
• Ask a lab manager or Metrdy administrator for access, or to correct your profile or lab access.
• Ask us for a copy of the personal information we hold about you, or to correct or delete it.
• Delete your Metrdy account in the mobile app (Settings → Delete account), or by emailing us from the address on your account. Deleting removes your Metrdy profile (name, email address, role and lab memberships), your Metrdy sign-in record and your place in every lab. Your Google, Apple or email account itself is not touched. If you signed in with Apple, Metrdy asks Apple to disconnect Metrdy from your Apple ID, or the app shows you how to do it yourself.

Your labs keep the vials, panels and titrations you added, so they can keep using them, and the audit trail stays complete: each entry keeps the email address and user id it was recorded under.

Metrdy is intended for use by researchers, lab personnel, administrators, and authorized organizational users. It is not intended for children.

Metrdy may update this Privacy Policy as the app, website, infrastructure, or data practices evolve. The updated version will be posted on this page with a revised "Last updated" date.

Metrdy is operated in the United States and is intended for use by research labs and institutions in the US. Metrdy does not currently direct its services at individuals located in the European Economic Area (EEA), the United Kingdom, or Switzerland.

If you are located in the EEA, the UK, or Switzerland, please contact us at richard.mcshinsky@metrdy.com before using the service so we can discuss applicable data protection requirements. Institutional customers requiring a Data Processing Agreement (DPA) may request one by contacting us at the same address.

If you have questions about this Privacy Policy or Metrdy data practices, contact:

Richard McShinsky
Email: richard.mcshinsky@metrdy.com
Or use the contact form.