Privacy Policy
Last updated: November 2026
RegDataLab is operated by Wasatch Crest Holdings LLC.
1. Information We Collect
1.1 Information You Provide
- Account registration details (name, company, email address)
- Payment information processed through Stripe (we do not store card numbers)
- Communications you send to us (support emails, feedback)
- Pilot applications and free supplier snapshot requests (name, work email, company, and the supplier names you enter)
1.2 Information Collected Automatically
- Tool-call records, described in section 1.4 (tool name, arguments, time, credits, and the other fields listed there)
- The IP address recorded for a tool call. On the shared demo key, an IPv6 address is stored as its /64 network and an IPv4 address is stored in full
- Failed sign-in attempts, as described in section 1.4
- Device and browser information for bot protection (via Cloudflare Turnstile)
- Website usage data (pages viewed, referring site, browser, device type, approximate location derived from your IP address, and actions such as clicking a signup link or completing signup), collected by the analytics services described in section 6
1.3 Information from Third Parties
- Bot verification results from Cloudflare Turnstile
- Payment status and subscription data from Stripe
1.4 AI connectors, sign-in, and tool-call logs
ChatGPT apps, Claude connectors, Grok connectors, and other MCP clients call the same hosted server at https://www.regdatalab.com/mcp. A call is billed to one RegDataLab account whether the client sends that account’s API key or an OAuth access token for that account.
Claude and ChatGPT can sign in with OAuth. The consent page names Claude or ChatGPT when the redirect host is claude.ai or chatgpt.com, which are the default trusted hosts. You approve by pasting the API key once, or, for an account with a verified email or a key emailed at checkout, by opening an email sign-in link in the same browser. The connector then uses its own access and refresh tokens. Grok is not one of those named hosts. A Grok connector or any other MCP client uses the same endpoint with the account’s API key, sent in the Authorization, x-api-key, or x-auth-token header. The server accepts API keys only in those headers. It refuses a request that puts a key in the URL query string and does not use that key. OAuth for any other client works when that client’s redirect is one the server accepts. OAuth sign-in is served only when the server has it enabled.
The account row stores:
- The name, email, company, and role entered at signup
- The SHA-256 hash of the API key, and the key’s first 8 characters
- Plan, credit balance, rate limit, and billing status
- The Stripe customer identifier, and the Stripe subscription identifier while a paid plan is active. Card numbers are not stored
- The signup referrer and UTM parameters when the browser had stored them
- Email verification time and last-used time
- Whether you asked for product update emails, when, and whether at signup or on the account page
OAuth sign-in stores:
- For a dynamically registered client: client id, client name, redirect URIs, and the IP address of the registration. A client that never receives an authorization code or a token is deleted one day after registration
- A signed sign-in request lives in the browser flow until you approve or deny it. The request expires after 15 minutes. On approve or deny, the server stores the client id, client name, redirect URI, scope, resource, PKCE challenge, and the client’s state value, under the SHA-256 hash of the request token. That row is deleted one day after the request expires
- Authorization codes as SHA-256 hashes, with the account id, client id, redirect URI, scope, resource, PKCE challenge, the API key hash at approval, and expiry. A code expires after 5 minutes. The row is deleted one day after it expires. Unused codes are deleted when the API key is rotated
- Access tokens and refresh tokens as SHA-256 hashes, with the account id, client id, scope, resource, the API key hash at issue, expiry, and revocation time and reason when a token is revoked. Access tokens expire after one hour and refresh tokens after 30 days, unless those durations are changed in server configuration. The token row is deleted seven days after it expires. During refresh, an encrypted copy of the replacement refresh token can remain on the row for about ten minutes and is then cleared
- Email sign-in rows as hashes of the email address, the sign-in request, the browser cookie, and the link token, plus the account id when the email matches an account, and the pending request sealed with a key derived from the emailed token. The email address itself is not stored on that row. The link expires after 15 minutes. The row is deleted one day after it is created
A tool call that debits credits writes one usage row, used for billing and the per-minute rate limit. The row contains the tool name, the time, the credits consumed, the balance after the debit, the MCP session id, the IP address described above, how long the call took, whether it succeeded, an error message when it failed, whether the call used an API key or OAuth, and, for OAuth, the client id. The arguments sent to the tool are stored with the row. An argument whose name contains api_key, apikey, token, secret, password, or auth is left out. In the other arguments, email addresses, API keys, and other credentials are replaced with a placeholder, and very long values are shortened. The rest is stored as sent, including company names, FEI numbers, product names, and date ranges. The stored arguments are cleared 90 days after the call, as described in section 7. A call refused for lack of credits or for the per-minute limit does not add a usage row. A call refunded for invalid input or a server error keeps the row, with the credits on that row set to zero.
A rejected API key is written to a failure log with the failure reason, the first 8 characters of the key, the IP address, the user agent, and the request path. The rest of the key is not stored in that log, and neither is the key’s hash. A failed OAuth consent that included a pasted key is recorded the same way. A recorded email-link failure stores a short reason code in place of the email address or the link. An unknown link, or a link opened in a different browser, is written to the application log with the reason only. Application request logs use the path and leave off the query string. If a client puts a key in the URL anyway, the request is refused, but the full URL, key included, can still appear in the host’s access log. The application log records that the request was refused, with the first 8 characters of that key and the user agent.
2. How We Use Your Information
- Provision and maintain your API access
- Process payments and manage subscriptions
- Enforce rate limits and prevent abuse
- Send transactional emails (key issuance, billing, security alerts)
- Send product update emails, about once a month, only if you ticked the box at signup or turned them on in your account. Each one has an unsubscribe link, and you can turn them off on the account page
- Send RegDataLab Weekly, a weekly email of new FDA data, only if you signed up for it and confirmed your address through the link we emailed you. Each issue has an unsubscribe link. We keep the address only to send that email
- Improve service reliability and performance
- Comply with legal obligations
- Respond to support requests
3. Third-Party Service Providers
- Heroku — Cloud hosting for the API and MCP service (United States)
- Vercel — Website hosting and Vercel Web Analytics
- Google — Google Analytics 4 website analytics
- Sentry — Error monitoring and diagnostics
- Stripe — Payment processing
- Cloudflare — Bot protection (Turnstile) and CDN
4. Disclosure of Information
We may disclose your information in the following circumstances:
- To service providers who assist in operating our platform
- To comply with legal obligations, court orders, or government requests
- To protect our rights, safety, or property
- In connection with a merger, acquisition, or asset sale
- With your explicit consent
5. Sale of Personal Data
We do not sell, rent, or trade your personal information to third parties.
6. Cookies, Analytics and Tracking
6.1 Analytics
We use two analytics services on regdatalab.com to understand which pages are used and whether signup works:
- Vercel Web Analytics records page views with the page address, referring site, browser, operating system, device type and country. It does not set cookies. Vercel identifies a visit with a hash of the request that is discarded after 24 hours and is not used to track you across sites.
- Google Analytics 4 records page views and events such as signup clicks, documentation clicks and completed signups. It sets first-party cookies (for example
_ga) and sends data, including your IP address, to Google, which processes it under its own terms. We do not send your name, email address or API key to Google Analytics. You can opt out with the Google Analytics opt-out browser add-on or by blocking cookies for this site.
6.2 Cookies and local storage
- The account page signs in with an email link. That sign-in sets an HttpOnly cookie named
__Host-rdl_accountfor 14 days (rdl_accounton plain HTTP). The server stores a SHA-256 hash of the cookie value, the account id, and the API key hash from sign-in. The cookie is cleared on sign-out. It does not authorize MCP tool calls. Looking up an account with an API key still sends the key on the request. The key is not written to browser storage - OAuth email sign-in sets an HttpOnly cookie named
__Host-rdl_oauth_browserfor one hour. It ties the sign-in link to the browser that requested it. The server stores a hash of that cookie value on the email sign-in row - For signup attribution, the UTM parameters and referring site (its address only, without the page path or search terms) of your first visit that came from another site or an ad are kept in your browser’s local storage for 90 days (key
rdl_first_touch), plus session storage for the current tab. An ad click is recorded only as “google / cpc”; the ad click id is not stored. Nothing is sent to us unless you submit a form - Google Analytics cookies as described above
- We do not use advertising pixels, and we do not use analytics data for advertising
7. Data Retention
The server does not delete tool-call rows or failed sign-in rows on a schedule. Account email sign-in link rows and the rows that count sign-in requests are deleted one day after they are created. An account sign-in session row is deleted one day after it expires. A tool-call row remains until the account row it belongs to is removed, but the daily cleanup (05:00 UTC) clears the tool arguments stored on it 90 days after the call. Removing that account row also removes the usage rows, OAuth tokens, authorization codes, and email sign-in rows that reference it. A failed sign-in row that pointed at a removed key keeps the rest of its fields and drops the key id. Billing event rows stay, with the key id cleared.
OAuth housekeeping does run. The daily cleanup (05:00 UTC) deletes closed sign-in requests and authorization codes one day after they expire, token rows seven days after they expire, and email sign-in rows one day after they are created. It also deletes a registered client that never received a code or a token, one day after registration.
Stripe customer and subscription identifiers stay on the account until the account row is removed. Cancelling a paid plan clears the subscription identifier and returns the account to the free plan. The account row and its tool-call log stay.
8. Children’s Privacy
Our service is not directed at individuals under the age of 13. If we become aware that we have collected personal information from a child under 13, we will delete it promptly.
9. International Users
Our services are hosted in the United States. By using our service, you consent to the transfer and processing of your data in the United States. We do not guarantee compliance with data protection laws outside of the United States.
10. Account deletion
The account owner deletes the account on the account page. The owner key confirms by typing DELETE. Deletion is irreversible. When a Stripe subscription id is stored on the account, or on supplier monitoring for that account, the server cancels that subscription in Stripe before it removes the account row. Cancellation stops later charges. It does not refund a charge already paid. The Stripe customer record stays in Stripe. Card numbers are not stored.
Removing the account row removes the API keys, the tool-call log, OAuth tokens, authorization codes, and email sign-in rows that reference those keys. A failed sign-in row that pointed at a removed key keeps the rest of its fields and drops the key id. Billing event rows stay, with the key id cleared.
An inactive key cannot delete the account. Email hello@regdatalab.com from the account email to ask for that deletion, or to ask about the account information on this page.
Email sign-in leaves your API key in place and does not revoke OAuth grants. Lost-key recovery emails a one-time link. The link expires in 24 hours and works once. Using it rotates the API key. The old key stops working. It revokes OAuth grants for that account. Recovery disconnects the account's OAuth connections (such as Claude or ChatGPT), so you'll need to reconnect them with the new key. Unused authorization codes are deleted. The account page sign-in ends. Request a new email link, or paste the new key. It leaves the account row and the tool-call log in place. Manage billing on the account page opens Stripe’s billing portal. Cancelling there ends the paid plan. It does not delete the account.
11. Security Measures
- All data transmitted via TLS/HTTPS
- API keys are stored as SHA-256 hashes. The first 8 characters are stored for display
- OAuth access tokens, refresh tokens, and authorization codes are stored as SHA-256 hashes
- Access controls and role-based permissions for internal systems
- Automated monitoring for unauthorized access
12. Do Not Track Signals
Our service does not currently respond to Do Not Track browser signals.
13. Changes to This Policy
We may update this policy from time to time. Continued use of the service after changes constitutes acceptance of the revised policy.
14. Contact Information
Wasatch Crest Holdings LLC
Email: hello@regdatalab.com
Web: regdatalab.com