Skip to content

Third-Party Services & Compliance

Weirling integrates the services below. This document records what each is used for and the relevant terms, so operators can confirm compliant use (audit 08-8). Software licenses of bundled libraries are separate from the service terms noted here.

Service Used for Data sent Location Terms notes
Groq (Llama 3.3 70B / 3.1 8B) Summarization, topic extraction Article title + text United States Content policy prohibits certain content classes; the digest/summarization use is compliant. No cold email. Summaries are cached to limit calls.
OpenAI (optional fallback) Summarization when OPENAI_FALLBACK_ENABLED=true Article title + text United States Same content-policy considerations as Groq. Disabled by default.
Resend Digest and account email delivery (hosted) Recipient email + email content United States Transactional/user-requested email only: no cold or bulk marketing. Include a working unsubscribe (implemented) and, for bulk sending, a physical address and SPF/DKIM/DMARC on a sending subdomain.
Railway Hosting the API, workers, database and cache (hosted) All account and reading data stored by the service United States Infrastructure provider: processes data only to run the service.
Vercel Serving the web app (hosted) Request metadata (IP address, pages requested) United States No Vercel Analytics or Speed Insights: no third-party analytics run in the browser.
Lemon Squeezy / Paddle Merchant of record & subscription billing (hosted) Customer email, country, billing token United States / UK Merchant of record processes payment data directly; card details never touch Weirling servers.
Browserless / Chrome Headless rendering of JS-heavy pages Target URL Operator host Runs in the operator's own container. Fetching respects robots.txt and the honest-bot posture.

Libraries (licenses)

sentence-transformers (Apache-2.0), pgvector (PostgreSQL License), feedparser, trafilatura, BeautifulSoup, FastAPI, SQLAlchemy, Next.js, DOMPurify: all permissively licensed and compatible with the project license.

Operator responsibilities

  • Set your own API keys; when self-hosting with your own keys, you are the contracting party with those providers and their terms apply to you.
  • Keep summary caching enabled to control LLM spend and call volume.
  • Do not use Weirling email delivery for unsolicited/bulk marketing.