Data Processing
What we collect, how we use it, and where it goes
OpenGraph+ processes as little of your data as possible. This document describes what comes in, what we do with it, and what goes out.
What comes in
The public URLs you submit, your account email, and an API key you generate. That is it. We do not collect data about your end users.
What we do
We fetch each public URL in an isolated headless browser, capture a PNG, read the Open Graph meta tags, and discard the page HTML. We do not store cookies, DOM state, or scripts from the pages we render.
What goes out
A rendered image, served over our image API and stored encrypted in object storage. The image is a picture of a page that is already public.
Public API endpoints
OpenGraph+ exposes two kinds of public image endpoints. Both serve rendered images of pages that are already public. Neither one accepts, proxies, or stores private content.
Connection image URLs (no authentication)
The URLs you place in your og:image tags, served from your-domain.ogplus.net or your own custom domain. Social platform crawlers and browsers fetch these and receive a rendered PNG of the matching public page. They carry no authentication and no personal data, because they are public images by design.
Signed image API (HMAC authenticated)
For programmatic rendering, requests go to api.ogplus.net/websites/v1/{signature}/image?url=… and are authenticated with an HMAC signature derived from your secret key. The secret key is never transmitted. Each request carries only a public page URL and its signature, and the response is the rendered image. Every request is scoped to your account, so there is no cross-tenant access.
What these endpoints do not do
They do not accept internal or private URLs, they do not proxy authenticated content, and they do not store request bodies or end-user identifiers. Server-Side Request Forgery is treated as a primary threat, so every submitted URL is validated against a blocklist of private and reserved network ranges before anything is rendered.
Retention and deletion
Screenshot images are cached according to the TTL you configure (default up to 30 days). Deleting a website removes its pages and screenshots; deleting your account permanently removes all associated data. See Security for the full retention and deletion policy, Privacy for data-subject rights, and Subprocessors for the third parties that process data on our behalf.