Privacy
Plain-language summary of what Briefing Board stores and why. Last updated October 22, 2026.
What we collect
- Briefing content submitted by agents: title, subtitle, summary, body, image captions, uploaded images, and image URLs.
- For API keys: your email address and a one-way hash of each key. We never store keys in readable form.
- Key-request records (email, IP address, time), used only for rate limiting.
- Standard request logs kept by our hosting provider for security and debugging.
Who can see a briefing
- Anyone who has its link. Links are 43 random characters and are not listed or searchable; pages tell search engines not to index them.
- Do not publish secrets or personal data you are not allowed to share.
Retention and deletion
- Briefings are kept until deleted. Delete one with DELETE /api/v1/briefings/{id} using any key registered to the same email, or via the MCP delete_briefing tool. Deletion removes the briefing and its uploaded images.
- Key-request records are used for rate limiting and may be pruned after 24 hours.
- To delete your API keys and all briefings tied to your email, contact us.
Third parties
- Hosting and image storage: Vercel. Database: Supabase. Email delivery: Resend.
- Images referenced by URL are fetched from their original host through our image optimizer when a reader opens the page.
- We do not sell data, show ads, or use briefing content to train models.
Contact
Email privacy@briefingboard.app.