Data handling
Privacy & Data Handling
Foundry/API minimizes retained data and separates account, billing, product and conversion records. Payment-card details are handled by Stripe and are not stored by this application.
Last updated · 21 July 2026
Account and billing identifiers
The service can store account name, email, authentication identifier, Stripe customer and subscription identifiers, product entitlement and API-key prefix. Direct API keys are stored only as a cryptographic hash and are displayed once when generated.
Product inputs and outputs
DocuStruct, RAG-Feeder, Domain Enricher, Maps Lead Extractor and Review Sentiment records use a 30-day application retention target. TrackPulse snapshots use a 90-day target. Inputs must not contain data the customer is not authorized to process.
Conversion analytics
First-party conversion events use a pseudonymous browser token and retain no raw IP address, user agent or account identity. Their retention target is 90 days.
Processors and providers
The service uses infrastructure, payment, storage, model and data providers required to complete each selected API workflow. Customers should review the relevant product documentation before sending regulated or highly sensitive data.
Requests
Customers can use the support form to request access, correction or deletion. Some records may be retained where required for security, billing, fraud prevention or applicable legal obligations.
Professional review
This notice documents current product behavior and must be reviewed by a qualified privacy professional for the operator's legal entity, jurisdictions and customer categories.