Privacy Policy
Last updated: 2026-09-19
Summary
betterimage.io is a social card editor for images at six platform sizes. You can use it without an account. If you create one, we store your email address, a hashed password (or your Google identifier if you sign in with Google), the templates you save, and records of the watermark-free downloads you buy. If you use the HTTP API or connect an AI assistant through our MCP server, we also store your API keys, a monthly usage count, and the apps you have connected. The only visitor statistics we look at are aggregate, cookie-free counts from Cloudflare. No advertising, no tracking pixels, and we never sell or share your data.
Who is responsible
betterimage.io is run by its operator, based in Poland, who is the data controller for everything described here. For questions or to exercise any right below, write to hello@betterimage.io.
What we collect from every visitor
-
Cookies.
A session cookie named
_og_key, which keeps your session and form security tokens together, and, only if you tick "Stay logged in", a remember-me cookie named_og_user_remember_mevalid for 14 days. Both are signed by the server, carry no personal data, and are necessary for the site to work, so no cookie banner is needed. Beyond these we set no cookies of our own. - Your IP address is used to limit how many requests one visitor can make. It is kept in memory for the duration of that window and is never written to a log or a database.
- Cloudflare. All traffic to betterimage.io passes through Cloudflare, which acts as our proxy and protects the site against abuse. Cloudflare sees your IP address and request headers and hands the IP to us for the rate limiting above. From that traffic Cloudflare gives us aggregate visit statistics (page views, referrers, countries, browser and device types) that use no cookie, store nothing in your browser, and never show us an individual visitor. On the sign-up, log-in and password-reset forms, Cloudflare Turnstile checks that you are not a bot. See Cloudflare's privacy policy.
- Pages you ask us to fetch. The link preview checker, the meta tag generator, Import from URL and the MCP tools fetch the web page at the address you give us so we can read its title, description and images. The API and the MCP tools do the same with a picture address (image_url and the other picture fields), fetching that file so it can be drawn on the card. The address and what comes back are used for that one response; a fetched picture is held in memory for ten minutes so a batch of cards over the same photo does not refetch it, and neither the address nor the file is written to our logs or our database.
- Usage counts. We count downloads (with the time, the kind of download, the layout and the size) and MCP connections and tool calls (with the tool name, the outcome and how long it took). For MCP calls we also keep a short one-way hash of the conversation or key so that distinct users can be counted; those entries are deleted after 90 days. None of these counts include an IP address, the text of your card, or the pages you fetched.
What we store if you have an account
- Your email address and password. The password is stored only as a hash; we never see it in plain text. If you sign in with Google we store the identifier Google returns for you instead of a password.
- Account records: when the address was confirmed, when you last signed in and were last active, how many times you signed in, and the account's status.
- Your saved templates: the design, the text you typed into it, any photo, logo or background you saved with it, and a preview thumbnail. The stored files are served only to you. Images you render from a template through the API, a signed og:image URL or a connected app go to whoever holds that URL or key, which is what those features are for.
- Downloads you make while signed in are counted against your account, with the time, the kind of download, the layout and the size.
- API keys, usage and subscription. For each API key: its name, its public id, its secret encrypted at rest, and when it was last used. A monthly count of clean images rendered with your keys, over the API, the MCP server, signed og:image URLs or the editor. If you subscribe, the Stripe customer and subscription identifiers, the plan and its status. Card details never reach us.
- Apps you connect through the MCP server: the app's name and registration details, the permissions you granted, when it last used them, and its sign-in tokens stored as one-way hashes, tied to an API key created on your account for that app. Tokens expire on their own and are removed by a periodic cleanup. Disconnecting the app under Account settings revokes them at once.
- Purchases. For a watermark-free download: a Stripe payment reference, the price, the design you bought, the rendered image for the 7 days the download link works, and how many times and when the file was downloaded. A checkout you start but never pay for is deleted after two days.
Images you upload
A photo or logo you add in the editor is sent to our renderer, composed into the card, and returned to your browser. It is held in server memory only briefly so that repeated previews are fast, and is stored durably only when you save a template or buy a download, as described above. Drafts of your work in progress stay in your own browser and are not sent to us.
Emails we send
Only transactional ones: account confirmation, password reset, email change, the download link after a purchase, and, if you use the API, a notice when you approach or reach your monthly quota. They are delivered by Postmark. We send no marketing or newsletter emails.
Who else handles your data
Each provider works for us for one purpose only: Stripe (payments), Postmark (email delivery), Cloudflare (proxy, aggregate statistics and Turnstile), Google (only if you sign in with Google), Hetzner (the server in Germany that runs the application and its database), Tigris (storage for the image files described above), TypeSafe (when you import a page by its link and leave "Pick a design for me" on, or ask our MCP server for a card from a page without naming a design, TypeSafe's Jev model receives that page's public title, description, site name, author and domain, nothing about you, and answers which of our designs fits it), and Sentry (error reports: when something breaks on our side, Sentry receives the technical details of the failure, which route and request id it happened on and, if you were signed in, your account number, but never your IP address, cookies, email, password, tokens, or the photos and addresses you submitted). We do not use any provider that profiles or tracks you.
Our Sentry project runs in Sentry's EU region, so error reports stay in the European Union. Stripe, Postmark, Cloudflare, Google, Tigris and TypeSafe are US-based, so the data they handle may be processed in the United States. Each relies on the safeguards the EU accepts for such transfers: the EU-US Data Privacy Framework where the provider is certified, and the European Commission's standard contractual clauses otherwise.
Why we may process this
- To provide what you asked for (performance of a contract): your account, templates, renders, purchases, API keys and subscriptions, connected apps, and the emails needed to run them.
- To keep the service secure and working (our legitimate interest, which we believe does not override yours): rate limiting, Turnstile, usage counts, Cloudflare's aggregate statistics, and periodic cleanup.
- To meet legal obligations: keeping payment records for tax and accounting purposes.
- We do not rely on consent for any of this, so there is nothing to withdraw. Signing in with Google or connecting an app happens only when you choose to.
How long we keep it
- Account data, templates, API keys, usage counts and connected apps: until you delete the account, or until we close it for abuse.
- Sign-in sessions: 14 days; app sign-ins until their tokens expire.
- Purchases: the design and the rendered images until shortly after the 7-day download window, or until you delete your account, whichever comes first; the payment record for as long as tax and accounting rules require.
- Download counts: kept as statistics; after account deletion they no longer point to anyone. MCP usage entries: 90 days.
- Your IP address: never stored.
Your rights
Under the GDPR and similar laws you can ask for access to the personal data we hold about you, have it corrected or deleted, restrict or object to its processing, and receive a copy in a portable format. From your settings you can change your email or password and delete the account yourself. Deletion cancels any active subscription, then removes your account, templates, uploaded images and thumbnails, API keys, usage counts, connected apps, and the designs and rendered files of your purchases. What stays is the payment record we must keep (the Stripe reference, price, dates and download counts), no longer linked to you, and a deletion log entry holding only the internal account number, the internal numbers of those purchases, the storage paths that were cleared, the time, and whether the cleanup had to be retried. The files are normally gone before you see the confirmation; if our storage is unreachable at that moment, the cleanup is retried automatically until it succeeds. For anything else, including a copy of your saved templates, email hello@betterimage.io and we will answer within a month. You can also complain to a data protection authority: in Poland the President of the Personal Data Protection Office (uodo.gov.pl), elsewhere in the EU the authority of the country where you live.
We make no automated decisions about you and build no profile of you.
Children
The service is not directed at children under 13 and we do not knowingly create accounts for them. If you believe a child has created an account, email us and we will remove it.
Changes
If we change how we handle data, we update this page and the date at the top. Material changes that affect existing accounts are announced by email before they take effect.
Contact
Questions, requests, complaints: hello@betterimage.io.