Privacy policy

Placeholder Legal Entity SRL is the controller of the personal data described here. You can reach us at legal@gosponsored.com. For bookings, the maker is the seller and decides about their own customer records in Stripe.

The widget sets no cookies and uses no local storage, session storage or fingerprinting.

Only aggregate counters are kept: for each slot, seat and day, how many times an ad was rendered, viewed and clicked. We keep no raw event rows; if we ever keep any, they are deleted after 30 days.

Visitor IP addresses are never stored. To filter bots and limit abuse, the edge server uses a one-way hash of the IP address and browser with a salt that changes every day, so a visitor can't be recognized from one day to the next.

A click on an ad goes through a short redirect at our edge that counts it once and forwards the visitor to the sponsor's page. Makers can repeat these statements on their own privacy pages.

Your account (name, email, and your X handle, avatar and follower count if you sign in with X), your page and properties, and your Stripe account id and status; Stripe holds your identity and bank details. If you connect a stats source, its key is stored encrypted and used only to read your stats.

When your page is published we show it, with its name, avatar, properties, open slots and prices, in the showcase on the gosponsored homepage and in Browse (gosponsored.com/browse and its category pages). You can opt out on the Page screen under Visibility.

If you sell offers, the proof of delivery you send (a link, an optional screenshot and an optional note) is stored with the order. The sponsor, you and gosponsored staff see it.

Your email, your ad (text, landing page and logo), and the Stripe customer and subscription ids of your bookings; your card details stay with Stripe. We use your email for booking emails, the weekly report (you can stop it) and your manage link.

While your ad is live, its name and logo may also appear in the "Sponsoring right now" list on the gosponsored homepage, as they already do on the maker's page. Amounts are never shown.

If you join the waitlist of a sold-out slot, we store your email address, the slot, and when you joined and when we emailed you. We use it for one thing: one email when a seat opens. The maker only sees how many people are waiting, never who. We delete the entry 90 days after that email or after you unsubscribe, or when the maker deletes the slot. To leave the waitlist, use the unsubscribe link in the email, or ask us at legal@gosponsored.com.

When you order an offer, we also store the brief you write for the maker, the maker's proof of delivery and any problem you report. The maker, you and gosponsored staff see them. Proof screenshots are stored as public files at unguessable addresses: anyone who has the address can open one, but they are not listed or linked anywhere else.

We count the steps of signing up and booking (for example "slot created" or "booking paid") from our servers, without cookies, to see where the product works and where it doesn't. Page views of gosponsored.com are counted anonymously. We don't build advertising profiles and we don't sell data.

When a sponsor drafts an ad, the public product page they enter and the ad text are sent to Anthropic (Claude) to draft and screen the ad, and the page address is checked with Google Web Risk. Our fetcher, gosponsoredbot, reads only that page.

Every night we check each maker page against the Trusted maker criteria (gosponsored.com/trust), using data we already hold: account age, page and Stripe status, connected stats, the widget's daily counters, disputes, takedowns and slot health. Numbers that look unusual are flagged for a person at gosponsored to review; a flag on its own never removes the badge.

Stripe (payments), Vercel (hosting), Cloudflare (the widget's edge and bot checks), Upstash (the edge cache), Supabase (database), Resend (email), Anthropic (AI drafting and screening), Google (Web Risk), X (sign-in), PostHog (product analytics), Sentry (error reports) and an S3-compatible storage provider (sponsor logos). Some of them process data outside the European Economic Area under the European Commission's standard contractual clauses.

Account and page data: while your account exists. Booking and invoice records: as long as tax and accounting law requires. Offer briefs, proof links, proof screenshots and problem reports: as long as the order's records. Ad drafts: 24 hours. Widget data: only the daily counters above.

You can ask us for a copy of your data, to correct or delete it, to restrict or object to its use, or to receive it in a portable format, by writing to legal@gosponsored.com. You can also complain to the data protection authority where you live or where we are established.

gosponsored.com uses only the cookies it needs: your sign-in session, your language, a 30-day cookie that remembers which maker's "via gosponsored" link brought you, and your cookie choice.

If you connect a stats source, we read only aggregate totals from it, once a day: 30-day visitors and pageviews from Plausible, Google Analytics, DataFast or PostHog; monthly recurring revenue from Stripe or Polar (never your customers' names, emails or payments); the subscriber count of your YouTube channel; the star count of your GitHub repository. Keys and tokens you give us are stored encrypted and used only for these reads; we show you only their last characters.

When you disconnect a source, we delete its key and its numbers. A number we can't refresh is marked stale on your page and stops counting as verified.

Discord: we read only the server name and the public member count of the invite link you paste, with no sign-in and no key. Because anyone can paste any public invite, the number is shown as "via invite link" and never as verified.

gosponsored uses YouTube API Services to read your channel's public subscriber count. By connecting YouTube you agree to the YouTube Terms of Service, and Google's use of the data is described in the Google Privacy Policy. We refresh YouTube data every day and delete it when you disconnect.

If you add a TrustMRR startup to a property, your page shows TrustMRR's own badge, loaded from trustmrr.com: visitors' browsers connect to TrustMRR to show it, as with any embedded content, and the numbers in it are TrustMRR's, not ours.

We will update this page when what we collect changes, and email makers and sponsors about material changes.