Privacy policy
This policy explains what Soldpage collects, why, and for how long. We are the controller of our customers’ account data, and a processor of the data of the people who visit and buy from our customers’ pages.
On soldpage.app (this site and the app)
- Account: your e-mail address, the workspace you create, your plan and purchases (processed by Stripe; we never see card numbers).
- Sign-in uses a strictly necessary session cookie (
__session, HttpOnly, 5 days). - If you follow one of our links with a discount code, we keep that code in a cookie (
sp_promo, HttpOnly, up to 3 days) so it can be applied when you check out. It holds only the code, nothing about you, and is removed when you return from a completed checkout. - If you open our Portuguese pages or pick a language, we remember that choice in a strictly functional cookie (
sp_lang, HttpOnly, 180 days). It holds only “en” or “pt” and picks the language and whether we offer prices in reais. - Hackathon traffic tracker. Soldpage is built in public for a hackathon whose rules require a traffic tracker on this site and the app. It records page views (page address, referrer, browser type and approximate location derived from the IP) for the organizers’ public leaderboard. It does not run on our customers’ pages.
- Free previews: if you keep a preview with your e-mail and don’t publish it, we send one reminder about 2 hours before it expires. It is the only e-mail about that preview, and its “Don’t remind me” link stops these reminders for your address. We remember that choice as a keyed hash of the address, not the address itself, for one year.
- Meta Pixel checker: the address you check is fetched once from our servers to read its public HTML. We don’t store the address or the report, and we never run the page’s scripts.
- Anti-abuse: the free page generator uses Cloudflare Turnstile and counts requests per IP; we store only a keyed hash of the IP, never the IP itself.
Advertising pixels for Soldpage’s own ads
We advertise Soldpage on TikTok and Meta (Facebook, Instagram). To know which of our ads bring people who sign up or buy, we use the TikTok Pixel with TikTok’s Events API and the Meta Pixel with Meta’s Conversions API, under the same rules.
- Where. Only on our home page and the free page generator (
/create). Never on the sign-in pages, inside the app, or on our customers’ pages. - Consent. In the EU, the UK and where we cannot tell, a notice asks first, with “Reject” and “Accept” equally easy; nothing loads before you choose. Elsewhere the pixel loads by default and you can turn it off below. Your choice is kept in your browser (local storage and a
sp_ads_consentcookie). - In your browser (after consent): the pixels record page views, a view of our home page and the creation of a free preview, and set first-party cookies (TikTok’s
_ttp, Meta’s_fbpand_fbc). Like any script loaded from TikTok or Meta, they also send that company your IP address, your browser’s user agent, the page address and the referring page, and basic page details and clicks on buttons. Before it loads we remove the product link you typed from the page address. We keep automatic advanced matching on both (which reads e-mail or phone fields on the page) turned off. If you arrived from a TikTok ad, we keep its click id (ttclid) in a first-party cookie for up to 28 days. - From our servers (only if you allowed ad cookies, or none were required where you are): when you create an account, start a checkout and complete a purchase, we send TikTok and Meta the event, a SHA-256 hash of your e-mail address, a SHA-256 hash of your account id, the click id and the
_ttp/_fbpvalues, and for sign-up and checkout your IP address and browser user agent. For purchases we add the amount, currency and the name of the pack or plan. The click id travels with your Stripe checkout session so the payment can be credited. IP and user agent are stored encrypted for at most 7 days while the event is delivered. Refunds are not reported. - Opt out. Use the buttons below, clear this site’s data in your browser, or use TikTok’s or Meta’s ad settings. Turning ads off removes our ad cookies from this browser and stops new events from it. Events already on their way are still delivered, and a purchase can still be reported for a checkout you started before turning ads off.
On our customers’ pages (*.soldpage.page and custom domains)
- Visits and clicks: the campaign tags in the link (utm_*), the referring site, a keyed hash of the IP (to count unique visitors), and your cookie choice. Kept 90 days.
- Cookies. In the EU, the UK and where we cannot tell, a notice asks first; “Reject” and “Accept” are equally easy. Only after “Accept” (or where no notice is required) do we read the Meta cookies
_fbpand_fbc, keep ad click ids (fbclid, gclid, ttclid) and load the Meta Pixel if the page owner connected one. Your choice is stored in your browser’s local storage on that page’s domain. - When you click the buy button, with consent, we store your IP address and browser user agent encrypted (AES-256-GCM) for at most 7 days, only to send them to Meta with the purchase so the page owner’s ad is credited. They are deleted once Meta accepts the purchase.
- When you pay on Stripe, the page owner’s Stripe tells us the amount and a SHA-256 hash of your e-mail. We never receive your card or the e-mail in clear.
- If you rejected cookies, nothing about your visit or purchase is sent to Meta.
Sub-processors
Google Cloud / Firebase (hosting, database, sign-in; us-east4), Stripe (payments), Resend (e-mail), Anthropic (writing page copy from public product pages), Cloudflare (DNS, Turnstile), TikTok (our own ads, with consent where required), and Meta (when a page owner connects their pixel, and for our own ads if we turn them on).
Your rights
You can ask for a copy, correction or deletion of your data at privacy@soldpage.app. If you bought from one of our customers, write to them first; we help them answer. EU/UK residents may complain to their data protection authority.
Security
Customer keys and tokens are encrypted; the database is reachable only from our servers; visitor IPs are hashed or encrypted and deleted on schedule.