Privacy Policy

1. What we collect

When you use Briefed we collect:

• The wedding URL you submit (or the text / screenshots you paste / upload as a fallback).
• Your IP address, browser, and referrer — standard web-server logs.
• An anonymous session ID stored in your browser's localStorage under the key briefed_sid. This is generated locally; we never store anything that identifies you personally tied to it.
• If you buy Pro or Couples: your email address and Stripe payment metadata (last 4 digits of the card, brand, expiration). We do not store your full card number.
• An optional referral code if you arrived via a ?ref= link. Stored in browser sessionStorage for the duration of the visit.

2. How we use it

Submitted URLs are used to generate your brief and to write a row to the parse_events telemetry table (URL hash, domain, outcome, latency, per-field hit/miss). The submitted HTML and brief content are not persisted in the telemetry rows.

If a brief is successfully generated, the extracted fields (not the source HTML) are stored in the submissions table so the brief page can be re-rendered at /brief/:id via the share link.

If we cannot generate the brief, we write the incident to the parse_failures table (stage, error code, an 8 KB HTML snippet, and LLM request/response JSONB) for debugging. parse_failures rows are visible only to the operator.

The funnel_events table records anonymous touchpoints (landing view, paste submit, parse success at medium-or-higher confidence, checkout clicked, payment succeeded). No extracted brief content appears in this row.

3. Cookies and pixels

• Meta Pixel (FB-tr id 1942445193060227) — fires on every page load. Used to attribute paid social conversions.
• Polsia Analytics — a 1×1 pixel beacon from polsia.com/api/beacon/pixel. Used for aggregate traffic counts. No personally identifying data.
• Postmark open pixel — a 1×1 pixel inside transactional post-purchase emails so we can track which receipts were opened.
• We do not set marketing cookies. We do not use third-party retargeting cookies.

4. Third-party processors

Data is sent to the following third parties as part of operating the service:

• OpenAI (GPT-4o-mini for text extraction; GPT-4o for screenshot vision). Your submitted URL text and any pasted content are sent to OpenAI for extraction.
• ScrapingBee — hosted browser API used to fetch JS-rendered wedding sites. Your submitted URL is sent to ScrapingBee for the fetch.
• Stripe — payment processor. Your payment metadata is sent to Stripe for transaction processing.
• Postmark — transactional email delivery. Your email address and receipt content are sent to Postmark for delivery.

For EU residents: data crosses US borders as part of using these processors.

5. Retention

• parse_cache — 24 hours, then expired.
• submissions — until deleted by the operator. A successful brief page typically stays live for the lifetime of the share link.
• orders — until refunded (and then aged out per Stripe record-retention rules).
• funnel_events, parse_events, parse_failures — indefinitely, for product analytics and debugging.

6. Your choices

• Clear your browser's briefed_sid localStorage entry to reset your anonymous session ID.
• Use a different browser or incognito mode for a clean session.
• Opt out of the Meta Pixel via your Facebook ad preferences at facebook.com/ads/preferences.
• Email support@polsia.com to request deletion of any submission row tied to a specific brief URL.

7. Security

All traffic is served over HTTPS. Admin endpoints are gated by an ADMIN_SECRET query parameter. We do not store your full payment card number at any point — Stripe is the only system that does.

8. Changes to this policy

If we change this policy in a material way we will update the effective date above. Continued use of the service after that date constitutes acceptance of the updated policy.

9. Contact

Questions about your data or this policy: support@polsia.com.