Legal
Privacy policy
Defiance International keeps its data practices honest and minimal. This policy describes exactly what we collect and store today, and, just as importantly, what we do not.
Effective
At a glance
- We set strictly-necessary cookies to sign you in, protect forms, recognize the browser you sign in from for account security, hold a cart and reopen a guest order. Every cookie and browser storage item is listed under Cookies and browser storage.
- First-party analytics runs only after opt-in consent. It never records what you type or where your pointer moves, and advertising and third-party trackers are not loaded.
- Passwords are hashed; sessions live server-side and can be revoked instantly.
- Bitcoin payments go to our own bitcoin payment server, and a bitcoin payment is recorded on the public bitcoin ledger, where its address, amount and time are public and permanent. Cash App and Venmo payments are matched to orders from our business account records and confirmed by a person. Bitcoin payment and refund addresses are checked against the US sanctions list. We retain only the order and transaction information needed to complete and fulfill your order and to meet legal obligations.
- Newsletters, offers and product news go only to confirmed subscribers and to members who turned them on. Every marketing or reminder email carries an unsubscribe link.
- To use a privacy right, go to your account privacy page or use the support form (topic: Legal). A person handles every request made through the form.
Do Not Track and Global Privacy Control
If your browser sends a Global Privacy Control signal, we do not record reading measurement, even if you opted in to analytics, and you do not appear in the live view of current visitors. Page events you opted in to continue until you turn analytics off. Do Not Track does not change what the site does: optional analytics stays off until you opt in, and we load no advertising or third-party trackers.
Analytics
If you opt in, the site sends first-party events, such as a page view, a search, adding an item to your cart or a checkout step, to our own analytics endpoint. Each event holds the page path, the time and details of the action. A page view also holds how you arrived, as a category only: a campaign, a search engine, a social site, an AI assistant, another site, or directly. The address of the page you came from is never stored or sent. Certificate verification codes and links are never recorded.
When you are signed in, these events are linked to your account. When you are not, they are linked only to a keyed hash of the random analytics cookie, which expires after 24 hours.
If you allow the updated analytics, the site also measures reading: which sections of a page you reached, roughly how long each was on screen, how far you scrolled, whether you used an interactive diagram, clicks on things that are not buttons or links, form errors, how you arrived (such as a search engine or a social site), the width of your browser window as phone, tablet or desktop, and whether you use touch or a mouse. Your browser rounds these into coarse steps before sending them. They are never linked to your account, even when you are signed in. They are stored under a code made from a random cookie that expires at the end of the day and a secret that exists only for that day and only in our server’s memory, so once the day ends the code can no longer be connected to your browser.
Staff can see a live view of visitors who allowed the updated analytics and were active in the last five minutes. Each visitor appears under a random label that changes every day, with the page and section they are on, time on the page, the reading measurement above, items added to the cart and the checkout step reached. The view never shows a name, email, account, address, IP address, order, payment or anything you type, and it cannot be exported. Staff browsers are left out of all analytics. If you opt in, a random cookie that lasts 30 days lets us show you the same version of a page we are comparing, so the comparison is fair; it is removed when you turn analytics off.
A page view also holds the kind of page you first arrived on, as one of seven fixed kinds: a study record, a study topic, the study library, a verification page, an explainer, a shop page, or other. The address of that page is never stored or sent with it. We also count two steps on the verification pages: that the first look was shown, and that a sample check was completed. Neither holds a code or anything you type. The arrival record that holds the category and the kind of page stays in your browser for 30 days and is removed when you turn analytics off.
With analytics consent we also record catalog searches that return few or no results, and restock alert requests, with the search words or the size requested, so we can see demand. These are linked to your account when you are signed in, carry no email address, and are deleted after 90 days.
Analytics events are deleted after at most one year. Reading measurement is deleted after 90 days; only daily totals that hold no code or label are kept, for up to one year. You can withdraw analytics consent at any time from the Cookie settings link in the footer or your account privacy page; events and reading measurement stop at once.
Access metadata and site integrity
To operate and protect the site, we may log and review technical access metadata, including source IP address, browser or device information, request path, date and time, response status, and approximate region. We use this information to protect site integrity, prevent abuse, troubleshoot service issues, and understand site performance. We do not use it to make medical, treatment, or product-eligibility decisions. Security events kept longer than routine access logs are described under Security and fraud log.
Security and fraud log
To stop account takeover, payment fraud and automated abuse, we keep a security log of sign-ins, sign-outs, sign-ups, password resets, two-factor checks, changes to your email address or shipping addresses, requests to send order links again, orders and their acknowledgements, payments, support requests, consent changes, erasure requests, staff actions, and certificate verification requests that go over our limit. Each entry holds the IP address the request came from, the country, network operator, region, city, postal area (the first 3 characters of the postal code), approximate location to about 11 km and time zone our network provider reports for it, and a reference to the request, the time and the outcome. An entry made from a browser you signed in from also holds a keyed one-way code of that browser’s security cookie, so a change to your account from a browser you never signed in from can be flagged for review. It never holds passwords, one-time codes, payment details or the words you write to us. Our network provider is the only source of the location details an entry holds: we use no other location lookup service, and those details are deleted with the entry, never later than 90 days.
For security and fraud prevention, we look up the network your connection comes from, using public internet registry and routing data that we hold on our own servers. This covers the network operator, its country and registry, the routing prefix, and whether the network is a hosting, VPN, proxy, Tor, residential or mobile network. We may also look up the host name registered for the address, which is stored encrypted. When you sign in, we receive your browser’s time zone and language setting. We use these signals to compute a review score for possible proxy use. A person reviews any alert, and the score never blocks you on its own. This data is kept with the security event it belongs to and deleted with it, after 30 to 90 days unless a legal hold applies. Your address is never sent to a third party for these lookups.
The IP address is encrypted when the entry is written. Each entry is deleted 30, 60 or 90 days after it is written, depending on the kind of event, and never later than 90 days. An entry under a legal hold for an open payment dispute, a fraud investigation or a lawful request is kept until the hold ends, then deleted. Our encrypted backups cover only the current and the previous version of the platform, and a copy in a backup is deleted when that backup is replaced.
Only staff assigned to security review can search the log, and each search is recorded with who searched, when and why. We share entries only with a payment processor to resolve a dispute about your order, or with law enforcement when the law requires it. Every export needs a second staff member’s approval and is recorded. The log is never used for analytics, advertising or marketing, never used to follow you across the site, and never sold.
The log can lead us to refuse a request, ask for one more check, or hold an order for a person to review before it ships. Every such rule has an end date and names the staff member who set it. If you think one applies to you in error, contact support and quote the reference shown with the message.
When an account erasure completes, log entries are unlinked from the account and the rest are deleted on their normal schedule. The log is not part of the self-service data export; support can give you a summary of entries tied to your account.
Account data
Your account holds your email address, an optional username and your password. Passwords are hashed, we never store them in plaintext and cannot read them. If you turn on two-step sign-in, the account also holds an encrypted authenticator secret and hashed backup codes.
It also holds what you add or choose: shipping addresses, saved lists, reviews, recurring orders, notification preferences and consent choices. When you accept the Terms or record a consent choice while signed in, we keep the acceptance or choice with its time, a hashed IP address and your browser’s user agent, as a record of what you agreed to.
Sessions are stored server-side in our database (not as a self-contained token in your browser), which means we can revoke them instantly: signing out or changing your password invalidates the session everywhere at once. We use account data to run your account, fill and support your orders, and send the messages you choose.
Orders and payments
When you place an order we keep your name, email address, delivery address and any phone number you give, the items, prices, tax and shipping charges, the payment status and the payment reference, and the shipment and tracking details.
Bitcoin: we run our own bitcoin payment server, so no payment company receives your payment. Each order gets its own payment address and exact amount, held for a 60-minute payment window that we then keep monitoring, and we keep the address, the amount, the transaction id and the time of each payment to the order. A bitcoin payment is recorded on the public bitcoin ledger: its address, amount and time are public and permanent, and neither we nor anyone else can remove them. To follow a payment or a refund, we look up its transaction id or its address at public block explorers; a lookup sends the transaction id or the address only.
Refunds: a bitcoin refund goes to the return address you give us and confirm with a code we email you. We keep the return address, the amount, the transaction id and the time of the refund.
Sanctions screening: the addresses a bitcoin payment comes from, and every bitcoin refund address you give us, are checked against the US sanctions list. We keep the record of each check for as long as sanctions recordkeeping law requires, including after an account erasure.
Cash App and Venmo: when you pay with one of them, we match your payment to your order from our business account records, a statement or an entry we record, and a person confirms it. We import the statement and keep its parsed entries, including the amount, the time and the note; for a payment, a reversal or a refund we also keep the payer name shown on the statement and a keyed digest of the payer identifier, never the identifier itself. An entry we record by hand keeps the same details and a note of the evidence. We do not keep the statement file.
We retain only the order and transaction information needed to complete and fulfill your order, meet legal obligations, prevent fraud, and resolve disputes. We do not sell order data.
Emails we send
Service email: order, payment, shipping and delay notices, account security messages, support replies, certificate updates for lots you bought, and recall notices go to the address on the order or account. They are part of the service, not marketing.
Newsletter: if you subscribe, we keep your email address and the date you subscribed. The subscription starts only after you confirm it from the email we send to that address. Every newsletter carries an unsubscribe link.
Restock alerts: if you ask to be emailed when a size returns, we keep your email address and that size. Without an account, the alert starts only after you confirm it from the email we send. Members can turn availability alerts on or off in their account settings.
Cart reminders: if you leave checkout with items in your cart, we may send a reminder email showing them. For a signed-in member it goes to the account email address. A visitor who is not signed in receives one only after confirming the address from a confirmation email we send first. A reminder carries an unsubscribe link and is not sent once the order is placed.
Marketing email: offers and product news go only to confirmed newsletter subscribers and to members who turned on promotions or product news in their account settings. We stop marketing email to an address that unsubscribes, reports a message as spam or permanently bounces.
Delivery events: our email provider tells us whether each email was delivered, bounced or reported as spam, and, where its open and click tracking is on, whether the email was opened or a link in it was clicked. We keep those events with the message record to run and improve our email.
Support and order review
Support requests are kept as first-party tickets holding the topic, your name and email address, any order, certificate, SKU or batch reference you give, and your message.
When you contact Support or provide information for an order review, we process your contact details, relevant order or lot information, and the information you send to handle the request. Where relevant, this includes investigating an order, quality or security issue, and keeping records needed for that matter. Provide only information reasonably needed for the request. Do not send identifiable patient records, unrelated personal information, or confidential material you lack authority to share.
Who receives information
We share personal information only with the categories of service provider below, and only what each needs for the purpose stated.
Cloud hosting provider: runs the servers and the database that hold the information this notice describes.
Network security and content delivery provider: carries every request between your browser and the site, including your IP address, the pages you open and what you submit, to protect and deliver the site.
Our bitcoin payment server: creates each order’s payment address and watches the bitcoin network for the payment. We operate it; it is not a payment company.
Public block explorers: receive the transaction id or the bitcoin address of a payment or refund when we look it up, to confirm it on the public bitcoin ledger. They receive no name, email address or delivery address from us.
Sanctions list source: we download the US sanctions list from the U.S. Department of the Treasury and check bitcoin addresses against it on our own servers. No address or other information about you is sent to it.
Cash App and Venmo: when you pay with one of them, your payment and your account details go to that app under its own terms, not through us. We import our business account statement from the app to match your payment to your order, and a refund goes back through the app to the account you paid from when the app allows it; otherwise it is paid by bitcoin, bank transfer or check.
Payment processor: for as long as we are closing out card payments, receives refund requests for card orders placed in the past and supplies our records of those orders.
U.S. Census Bureau geocoder: receives the street line, city, state and ZIP code of a delivery address, and nothing else, when we need it to find the sales tax jurisdiction of the address.
Shipping and fulfillment platform: receives the recipient name, the delivery address, any phone number or email address given for delivery, and the parcel details, to buy the label and track the parcel. The postal carrier receives the delivery address to check it and to deliver the parcel.
Transactional email provider: receives your email address and the content of the order, account, support and recall messages we send you.
AI service provider: powers an assistant that only our administrator can use. We send it no customer records by design, but an administrator’s question, or the status text of the admin page in view, can include order details. Whether the provider keeps an exchange depends on the provider the administrator selects: one is told not to store it, and the others receive no such instruction. We do not claim that any provider keeps nothing.
Where a payment provider, carrier, laboratory, hosting provider or other relevant service provider needs personal information to perform the requested transaction, investigation or Platform function, we may share the information reasonably needed for that purpose, subject to applicable law and the commitments in this Notice. Their involvement does not remove our own privacy and security responsibilities. The submission permission in our Terms does not authorize public advertising use of nonpublic submissions or general-purpose model training on them.
COA verification
Verifying a Certificate of Analysis by QR or code does not create a stored scan record. To stop automated guessing, the verifier counts requests from each network address in memory only, under a key that is replaced every minute, and keeps nothing once that minute has passed. When a network address goes over that limit, one entry noting it is written to the security and fraud log, without the code entered or any result. Requests to the verifier are covered by the access metadata described above. A verification does not add an event to a lot’s chain-of-custody record.
The public verification endpoint is anti-enumeration: a forged code, an unknown product, and an unknown batch all return the same response, so it never reveals whether something exists. Third-party lab street addresses are stripped from public certificates.
A verification log records a digital event. It does not independently establish the physical custody or contents of a vial. A public certificate and a private transaction record may contain different information. Read a certificate's stated redactions and signature scope when interpreting it.
Your rights
From your account privacy page you can download a portable copy of the personal information linked to your account (never passwords or payment credentials), manage your consent choices, and request erasure. You can correct your profile and addresses in your account. Erasure runs on a 30-day cooling window: you can cancel inside that window, after which your profile, sessions, marketing records, and free-text personal details are deleted or overwritten in place. Orders, recall/exception cases, and tax records are retained, linked to the scrubbed account record, only as long as accounting and legal obligations require. Those retained records stay linked to the scrubbed account record and can still identify you; what erasure deletes or overwrites is no longer linked to your account.
For any other request, or if you have no account, use the support form with the topic Legal to ask for access, correction or deletion, or to ask about this notice. A person handles it, and we may ask you to confirm your identity before acting on it.
If your account is erased while one of your orders is still inside its recall window, we keep only that order’s email address and delivery address, use them only to reach you about a recall, and delete them when the window ends. The window ends one year after the latest expiry date among the order’s lots; where an item has no recorded expiry date, it runs at least three years from the order.
You may request access, correction, deletion or other applicable privacy rights through Support. We handle requests subject to applicable law, including its identity-verification and response requirements. An internal processing interval does not extend a legal deadline. Some transaction, quality, security or legal records may need to be retained for a lawful purpose or preservation obligation. Retention is limited to that purpose and the applicable period; a deletion request does not authorize destruction of records that law requires us to preserve. We do not describe retained identifiable records as anonymous.
Rights under state privacy laws
Depending on where you live, a state privacy law, such as California’s where it applies to us, may give you the right to know what personal information we hold about you, to access, correct or delete it, and to opt out of its sale or sharing for cross-context behavioral advertising. We do not sell personal information and do not share it for cross-context behavioral advertising. We will not treat you differently for exercising a privacy right.
To make a request, use your account privacy page or the support form. Someone you authorize may make a request for you through the support form; we verify the request before acting on it.
Children
This site is for adults. Our Terms require you to be at least 21 to use the platform, the site is not directed to children, and we do not knowingly collect personal information from anyone under 21. If you believe someone under 21 has given us personal information, tell us through the support form and we will delete it, keeping only what the law requires us to keep.
Changes to this notice
We keep a record of every version of this notice and what changed in it. The effective date at the top of this page is the date this version took effect.
We provide conspicuous notice of material changes to this Notice, with direct notice where required or appropriate. A revised notice does not by itself authorize a materially different use of information already collected. We obtain any separate consent required by law before the changed use.
Legal identity and governing law
The seller and data controller is Defiance International. These terms and policies are governed by the laws of the jurisdiction in which the seller is organized, except where applicable law requires otherwise.