Who we are
bidtune is an ad-revenue measurement and optimization service for publishers, offered by BuySellAds.com, Inc. (“bidtune”, “we”) at bidtune.com. Our postal address is 18 Shipyard Dr, Unit 2, Hingham, MA 02043. Privacy questions go to hello@bidtune.com.
Two relationships matter. For your account, team, and billing, BuySellAds.com, Inc. is the controller. For visitors to a site where you install the tag, you are the controller and bidtune is the processor. That processing is covered by the Data Processing Addendum and the Terms of Service.
Publisher accounts
Sign-in is Google or a one-time email link. The link is sent through Postmark, and the account is created only after it is opened. The first verified sign-in creates an approved account and an owner team. We store the email address, and for Google the name and profile image, plus an internal user id, team membership, and the sites you add (domain, display name, and the Prebid script URL you supply). Those records live in managed Postgres on ready.dev (Ready, cloud.ready.dev), which also hosts the dashboard. We do not receive a password.
While you are signed in, NextAuth keeps a session cookie on the bidtune site so the dashboard can recognize the account. An invitation link also sets an httpOnly, Secure, SameSite cookie named __Host-bidtune-invite on bidtune.com so the invitation can be accepted without putting the token in the address bar. Those cookies are not set on your readers’ browsers by the measurement tag.
If you send a message from the product, we deliver that draft and the site context through Postmark to hello@bidtune.com, with your account email as the reply address. A new account also sends a signup notice to the bidtune team through Postmark. Sign-in links and invitation email are sent from notifications@bidtune.com. Lifecycle email about a site goes through Postmark to that site’s owners and admins: install confirmation, findings, approval reminders, test start and result, trial ending, and a weekly summary. Those recipients can turn a kind of note off.
What the tag collects
You install bidtune by replacing the URL of the Prebid script you already load. The script runs on your site and sends auction and delivery events to a Cloudflare worker, which writes them to ClickHouse. A winning bid is not treated as a rendered ad. Usage billing counts observed non-empty renders.
For each event the tag can record:
- Auction facts: bidder, bid price and currency, response time, timeout, requested bidders, ad unit, size, media type, and whether a bid won, timed out, or did not bid.
- Render facts when GPT is on the page: a non-empty render, the available
hb_pbprice, and ad-server identifiers on that render (ad, advertiser, campaign, creative, and line item). These identify the ad, not the visitor. - Page context: the path only (not the query string), the referring hostname and a coarse referrer type, screen width, device class from screen width, and the local hour and daypart.
- A session id, a pageview id, and a pageview count. The session id is a random value. It is not your ad-server user id and not an advertising identifier.
- Browser family and operating system, parsed in the browser from the user agent. bidtune does not store the raw user-agent string.
- The configuration that actually applied: timeout, floors, bidder list, refresh index, experiment assignment, and cohort (holdback or optimized).
- Whether a consent API is present on the page (
tcf_present,usp_present,gpp_present, orunknown). The tag does not read the visitor’s consent choice.
The worker adds the country, city, Cloudflare data-center code, and bot score from the request. bidtune does not store the raw IP address. Cloudflare still sees the IP address and user agent while it delivers the request.
The tag can pass user-sync timing through to your existing Prebid setup. Bidder cookies and synced user ids from that process are not written to bidtune’s analytics. The tag does not write a GAM key-value or a cohort label onto the ad request. Cohort assignment stays in bidtune’s own measurement.
Identifiers on the publisher’s site
The tag does not set a cookie on the publisher’s site. It keeps a random session id in the browser’s session storage under __bidtune_session_v1, a pageview count under __bidtune_pageview_count_v1, and short-lived milestone keys under __bidtune_liveness_v1. Session storage is scoped to your site, because the script runs in your page. It clears when the browser session ends. We do not use local storage for these ids.
Your own Prebid setup, bidders, and ad server continue to set their own cookies and identifiers. bidtune does not control those.
Consent
The tag does not wait for a consent signal and does not stop collection when a consent API is missing or when a visitor refuses. You are responsible for the lawful basis for this collection, including any banner or consent mode your site already uses. Review the tag against that setup before you enable it.
The free audit
The public audit loads a page URL you submit, using Cloudflare browser rendering, and stores the configuration report in Cloudflare KV for 30 days. A multi-geography scan sends that public URL to Firecrawl. The audit describes your Prebid configuration. It is not the visitor measurement stream.
The audit worker also has a capture route that stores a submitted email address in Cloudflare KV for 365 days. The audit page on bidtune.com submits the address you enter to unlock a full report to that route; we follow up once, and nothing automated beyond that.
How we use this data
- To run your account, team, and sites, and to authenticate you.
- To measure auctions, renders, and sessions, and to show that measurement in your dashboard.
- To assign traffic to your base configuration or to a bidtune configuration, and to report the comparison.
- To count measured impressions and bill usage after the trial.
- To run research analysis when an owner or admin asks for it. That step can send aggregated statistics for the site to Anthropic. It does not send the raw event log. There is no in-product chat assistant.
- To send operational email: sign-in links, invitations, signup notices, messages you submit, and lifecycle notes to owners and admins.
We do not sell visitor data, and we do not use it to advertise to those visitors. We do not build a cross-site profile of a reader for our own marketing.
Rendered prices already on the page, including hb_pb when GPT is present, are part of the measurement. The tag does not send the visitor event stream to Google Ad Manager. A worker named bid-gam-reconciliation is still deployed. Where it is configured, it signs in to Google Ad Manager with a service account, reads a saved aggregate revenue report, and stores the daily figures. It does not receive the visitor event stream. An MCP server lets you read your site’s bid data from your own tools where it is enabled for your account. It is read-only, scoped to one site by its token, and it does not receive visitor data.
Who else handles data
These are the subprocessors the current application code uses. The deployed bid-gam-reconciliation worker, described above, reads a saved Ad Manager report. It is not a visitor-event subprocessor. ready.dev hosts both the dashboard and the managed Postgres control plane.
| Subprocessor | Role | Data it handles |
|---|---|---|
| Account sign-in | Email address, name, and profile image returned by Google sign-in. | |
| ready.dev | Dashboard hosting and managed PostgreSQL | Hosts the dashboard (Ready, cloud.ready.dev) and the managed Postgres control plane. That database holds account, team, membership, site, invitation, and billing-identifier records. The application serves the signed-in session and the publisher analytics it reads. |
| Cloudflare | Edge delivery, collection, configuration, and the public audit | Visitor requests to the tag and collection endpoint, including IP address and user agent in transit. bidtune stores the country, city, data-center code, and bot score Cloudflare supplies. Saved audit reports of a public page live in Cloudflare KV. |
| DigitalOcean | ClickHouse analytics cluster | Auction, render, and session analytics described in the Privacy Policy. |
| Stripe | Checkout, metered billing, customer portal, and webhooks | Account email, site and team identifiers, the card entered on Stripe Checkout, subscription status, and daily measured-impression counts. bidtune does not store the card number. |
| Postmark | Transactional email | Recipient email addresses and the content of sign-in links, invitations, signup notices, in-product messages, and lifecycle messages. Lifecycle mail goes to owners and admins: install confirmation, findings, approval reminders, test start and result, trial ending, and a weekly summary. |
| Anthropic | Research analysis | Aggregated auction statistics for one site when an owner or admin runs analysis: bidder, country, hour, ad unit, and experiment results. Not the raw event log and not account credentials. There is no in-product chat. The MCP server, where enabled for an account, serves read-only queries scoped to one site and does not receive visitor data. |
| Firecrawl | Multi-geography audit of a public page | The public page URL submitted for that scan. The measurement tag does not send visitor events to Firecrawl. |
How long we keep it
The analytics schema deletes rows on the following timetable. Where a table has no expiry, the schema says so and the row stays until it is deleted on request or the service ends. There is no self-serve deletion control in the product today.
| Record | Kept for |
|---|---|
| Raw auction and render events (bid_events) | 30 days |
| Session liveness events | 14 days |
| Ingest freshness, by minute | 30 days |
| Hourly bidder summaries | 90 days |
| Experiment session rows | 90 days |
| Alerts | 90 days |
| Daily rollups, experiment summaries, session summaries, session facts, analysis runs, and bidder scorecards | 365 days |
| Billing rollups, the arm ledger, and holdback comparison tables | No automatic expiry in the schema |
| Saved public-page audit reports (Cloudflare KV) | 30 days |
| Email stored by the audit capture route, if that route is called | 365 days |
| Control-plane account, team, site, invitation, and billing-identifier records | No automatic expiry in the schema |
International transfers
The providers above may process data in the United States and in other countries where they operate. For end-visitor data transferred from the EEA, the United Kingdom, or Switzerland, the Data Processing Addendum commits bidtune to the EU Standard Contractual Clauses and the UK Addendum. Executed copies are for counsel to confirm before production.
Requests
You can ask us to access, correct, export, or delete your account by writing to hello@bidtune.com. Visitors to your site should contact you first. You are the controller of that data. We will help you answer those requests as described in the Data Processing Addendum.
Depending on where you and your visitors live, you may have rights to access, correction, deletion, restriction, portability, and objection, and the right to complain to a supervisory authority. We do not sell personal information or share it for cross-context behavioral advertising.
Children
bidtune is a business service for publishers. The tag is not directed at children. Do not install it where you do not have a lawful basis to measure the audience, including on a service directed to children.
Changes
If we change this policy, we will update the date above. If a change materially affects how we process end-visitor data, the Data Processing Addendum describes how the subprocessor list is updated.
Contact
BuySellAds.com, Inc.
18 Shipyard Dr, Unit 2, Hingham, MA 02043
hello@bidtune.com