Security and data
Provkeep answers what states and federal agencies published about a product. It needs the product and the state, and nothing about the patient.
Last updated 20 November 2026. Questions: support@provkeep.com.
What we never receive
There is no field for any of these in the API, the MCP or the app.
- A patient's name, initials or signature
- A date of birth, or any date about a patient
- A street address, city, county or ZIP code: only the two letter state the order goes to
- A phone number, email address or any contact detail of a patient
- A medical record number, chart number, insurance or member ID, or Social Security number
- A diagnosis, symptom, lab result, dose history or any clinical note
- A prescriber's name, NPI or DEA number
- A photo, file or free text note about a patient
A field we do not know is dropped and counted, and its value is not kept. An order reference, line reference, product name or lot number shaped like personal information (an email address, a date, a Social Security number pattern or a phone length number) is replaced or dropped before anything is stored, and the answer says so.
What a check sends us
| Field | What it is |
|---|---|
code | Your own order or prescription reference. A value shaped like personal information (an email address, a date, a Social Security number pattern, or a phone length number) is replaced by the check ID and not kept. |
event | What happened: order_created, prescription_signed, order_shipped, order_updated. Anything else is read as order_created. |
lines | The products on the order, at most 50. Each line is described below. |
patient_state | The two letter US state the order goes to. Only the state is read: there is no field for a city, ZIP code or address, and an unknown field is dropped without its value being kept. |
prescriber_state | The two letter state the prescriber is in, when it differs. |
pharmacy_state | The two letter state the pharmacy ships from. |
pharmacy_type | How the product is dispensed, in your own words (for example 503A or 503B). Read against a vocabulary; an unknown value falls back to the account's setting. |
consult_type | How the patient was seen: in_person, video, phone, async_questionnaire. Used to match rules limited to one kind of consult. |
purpose | What the product is for, as a code: treatment, weight_management, athletic_performance, wellness, other. Never free text. |
preview | true checks the order without recording it. |
placed_at | When the order was placed. Refused if more than a day ahead. |
consent | The consent shown at checkout: the wording or its sha256 as terms_sha256, terms_version, gate (block, observe, record_only), shown_at and accepted_at. Never the customer. |
lines[].line_id | Your own line reference. Defaults to the line's position. |
lines[].peptide | The product, by any name or alias we hold. Required. |
lines[].name | The product name as you sell it, kept for your record. |
lines[].dosage_form | For example injectable, oral, nasal, topical. |
lines[].route | Route of administration, when it matters to a rule. |
lines[].blend | true when the line is a blend of more than one product. |
lines[].ingredients | A blend's or stack's ingredients, each read on its own. At most 20. |
lines[].lot_number | The lot it ships from, for your record. A value shaped like personal information is dropped. |
lines[].device_supplied | true when a device such as a pen or syringe ships with it. Kept for your record. |
lines[].quantity | How many units. A positive number. |
A check is kept as the account's record of what was asked and what we answered. How long each kind of data is kept: data retention.
How it is protected
| Tenant isolation | Every request reads the database as a role that cannot bypass row level security, with the account set for that one transaction. No account set means no rows. No request path holds a key that bypasses it. |
|---|---|
| Keys | Live API keys are stored only as a SHA-256 hash and shown once. A test key works only on the sandbox, which has its own database. Any key can be revoked in Settings, Keys, and stops working at once. |
| Sign in for apps | Apps and platforms connect by OAuth 2.1 with PKCE. They never see a password, and each connection is an ordinary key the account can revoke. |
| In transit | The API, the website and the MCP are served over HTTPS only. The application verifies the database's certificate and refuses to connect without it. |
| Webhooks | Sent only to https addresses, signed with HMAC-SHA256 in the Svix format, with a secret per address. |
| The record | Order checks, lots, certificates and consent records are append only: a correction is a new entry. Each night the day's records are fingerprinted and timestamped by two outside authorities. |
| Personal data we do hold | Account sign-in emails, and business contacts. Mail sent to a certificate address is cleared once read and deleted at 30 days. Cards are held by Stripe, never by us. |
What we do not hold
- No SOC 2 or HITRUST report. We answer a security questionnaire on request.
- No business associate agreement as a matter of course, because a check carries no patient information. Whether your organisation needs one with us is a question for your own counsel; HHS's answer for software vendors is FAQ 256.
- No legal advice. An answer reports what a rule says and who said it; a qualified person decides.
Uptime: we promise the order check API answers at least 99.5% of each calendar month, measured on the status page. How the API changes: the change policy.