Privacy Policy
v1 placeholder.
Independent legal review is owed before broader paid launch (scoping OQ-6). The disclosures below reflect the operational data flow of the service today; expansion or revision will arrive with that review.
Effective: 2026-05-28. Inquiries: support@producerbriefs.com.
1. What we collect
- Buyer contact information — the email you supply at order placement so we can deliver the brief and any disambiguation or refund notifications related to your order.
- Prospect identifying information — the company name, state, and any optional disambiguators (USDOT, NAICS, city) you supply so the production agent can research the prospect against public-record sources.
- Payment information — processed by Stripe. Producer Briefs does not store card numbers; Stripe handles all payment data per its own published policies.
- Operational logs — standard Cloudflare access logs, webhook event records, and internal audit logs that record the order’s lifecycle through production, QA, and delivery. These are retained for as long as the order receipt is required for accounting and dispute handling.
2. How we use it
- Fulfill the order (research and assemble the brief, deliver the PDF, handle disambiguation and refunds).
- Communicate about the order (order confirmation, disambiguation requests, brief-ready notification, refund notices, and operational support if you contact us).
- Improve the service (aggregate operational metrics and brief quality calibration; no buyer-identifying details surface in this work).
3. What we do not do
- We do not sell buyer information.
- We do not share buyer information with third parties for marketing purposes.
- We do not aggregate prospect identifying information into a third-party database.
- We do not read, request access to, or accept feeds from any buyer’s book of business, CRM, or agency management system.
4. Third-party processors
Producer Briefs operates on third-party infrastructure. The processors below handle data on our behalf under their own terms:
- Stripe — payment processing.
- Cloudflare — hosting and database.
- Resend — transactional email delivery.
- Google Workspace — the support@producerbriefs.com email account Kerry reads.
- Anthropic — the language model that runs the research and quality-grading components against the sources listed at the landing page.
Buyer information and prospect identifying information are sent to these processors only as required to fulfill the order.
5. Public-record sourcing
The brief is assembled by researching the prospect against public-record sources (FMCSA SAFER, state Secretaries of State, OSHA Establishment Search, EDGAR, PACER, county property and tax records, state licensing authority records, allow-listed trade press, official company communications, LinkedIn professional profiles). All sources cited in the brief are public; the brief itself is the buyer’s record of which sources were checked, what was found, and where the source is.
6. Retention
Order receipts and the operational logs above are retained for the duration required by U.S. tax and accounting rules. Delivered brief PDFs are stored as long as the buyer’s account requires re-access; on a documented buyer request we will delete a delivered brief and confirm the deletion. The intake-form payload submitted at order placement is retained for the same window as the order itself.
7. Buyer rights
Buyers may request: a copy of the data we hold about them, correction of any inaccurate data, and deletion of their account-level data subject to the retention obligations above. Send requests to support@producerbriefs.com; we respond within 30 days.
8. Changes to this policy
Changes are dated above (“Effective:” line) and version-bumped here. Material changes are surfaced in the order confirmation email for subsequent orders.
9. Contact
Producer Briefs · operated by Kerry Sexton · Texas, USA · support@producerbriefs.com