Privacy policy
Last updated 2026-11-06.
Who we are
Bikoosh runs the trackers on bikoosh.com (Tender Watch, DataWork Watch, Race Entry Watch, Shutdown Watch and the others listed in the footer). We decide what is collected on this site and why. Contact for anything on this page: [email protected].
What we collect, and why
- Your email address, when you sign up for a digest or an alert, start a trial or sign in: to send what you asked for (with a confirm step first) and the sign-in links. Every email has a one-click unsubscribe.
- Purchase data. Gumroad is the merchant of record: it takes the payment and we never see your card. Gumroad tells us the sale (product, price, currency, time, the email used) so we can switch on what you bought, and the link parameters the checkout was opened with (for example the Google click id and your consent state, below).
- Server logs: the address a request came from, the page, the time and the browser's user agent, used to run and protect the site (rate limits, abuse, errors).
- The Google click id (gclid) and your consent state. When you arrive from a Google ad, the link carries a click id. We keep it in a first-party cookie and pass it to Gumroad with your consent state, so a purchase can be matched to the ad click (see Google Ads conversion measurement).
- Approximate location from an ad (Bid Watch US). For visitors who come from an ad, we use the approximate location the ad platform reports to sort results by state; it is not stored with you unless you sign up with that state, and our anonymous page beacons record only the two-letter state the page showed.
- Anonymous page beacons: a page view, a click on a buy button, a cookie choice. They carry the product, the event and at most our own page path, the referring site's name and your country; no name, no email, no identifier of you.
- Product data you give us: the listings, filters, keywords, domains or watchlists you set up in a product, used only to run that product.
Google Ads conversion measurement
We advertise some products on Google. To know whether an ad led to a sign-up, a trial or a purchase, pages on this site load the Google Ads tag (gtag.js) from Google. It is the only third-party script on the site, and we use no Google Analytics.
- In the UK, the EEA and Switzerland it runs only with your consent (the legal basis). Until you choose, Google's consent mode keeps advertising storage off: no advertising cookie is set and the tag sends only cookieless signals with identifiers removed.
- Everywhere else it is on by default and you can opt out at any time with the same choice (legal basis: our legitimate interest in measuring our own ads). A refusal is honoured wherever you are, including under the California opt-out rules.
- What reaches Google: that a conversion happened (sign-up, trial start, purchase and its value), the click id, the page address and your consent state. For purchases we upload the click id, time, value and consent state in a file; never your email. One exception, the Hebrew planning alerts: when you came from a Google ad and confirm the alert, a SHA-256 hash of your email goes with that one conversion (Google's enhanced conversions; see below).
Google acts under its own terms and privacy policy for this data; it does not get our email lists.
Meta ad measurement (Facebook and Instagram ads)
When you reach our pages from one of our Facebook or Instagram ads, the Meta pixel (Meta's script from connect.facebook.net) runs on those pages to tell us which ads bring visitors and sales. It runs only on our product idea pages, on a page opened from a link that carries Meta's click id, and on later pages of that same visit. It never runs on our Hebrew pages. On any other visit nothing changes.
What it sends to Meta: the address of the page; the events of the visit (page view, product viewed, time spent and scrolling past half the page, starting and finishing the designer or quiz, and the click on the buy button) with the product and its price; the click id from the ad; Meta's own first-party identifiers (the _fbp and _fbc cookies); and, only if you type an email address into a form on those pages, a hashed (scrambled) copy of it, because Meta's automatic advanced matching is on. We never put your name, your answers or the names you type into these events.
Purchases: Gumroad, which sells our products, reports its own product page views and purchases to Meta for our ads. We may also report a purchase to Meta from our server (Meta's Conversions API) with the same kind of data: the sale id, price, the page you came from, the click id, the _fbp and _fbc values, your browser's user agent, your country, and a hashed copy of the email address you paid with.
What we keep: for a visit from an ad we keep a click record for 8 days, then delete it: the time, the page, the ad identifiers in the link, Meta's click id, the _fbp and _fbc values, your browser's user agent and your country. We do not store your IP address. A design you make is saved only when you press the buy button; an unpaid design is deleted after 8 days, a paid one 37 days after payment.
Your choice: visitors from the UK, the European Economic Area and Switzerland, and visitors whose country we cannot tell, are asked first, with Accept and Decline. If your browser sends Global Privacy Control, the pixel does not run. Anyone can switch it off with the Ad measurement choices link at the foot of our product pages; that also deletes our marker for your visit. Meta's own handling of the data is described in Meta's privacy policy.
Cookies
- bk_consent: your cookie choice (accept, reject, or your settings), six months.
- bk_gclid: the Google click id from an ad, 30 days.
- bk_ab: which version of a Tender Watch UK page you see while we test a layout change, 30 days. In the UK, EEA and Switzerland it is set only after you accept cookies.
- bk_hero: which version of the top of a Tender Watch UK page you see (A or B) while we test showing live notices above the signup form, 30 days. In the UK, EEA and Switzerland it is set only after you accept cookies.
- bk_bw_st: the state you chose in Bid Watch US's Where box (or All states), until you close the browser.
- bk_twt: a random id that stops one trial click being counted twice in Google Ads, six months; set only when advertising measurement is allowed.
- bk_v: a random visitor id (16 letters and digits, nothing about you) so we can count visitors rather than page loads, one year. In the UK, EEA and Switzerland it is set only after you accept cookies, and never after you refuse.
- bk_ilad: on the Israeli planning pages, that your visit came from an ad (a short hash of the click id), 7 days, so one visit counts once in Google Ads.
- bk_iloid: on the Israeli planning pages, the signed order code of the address you checked, 30 days, so the review you buy opens for that address.
- cw_session: keeps you signed in, 30 days. bik_ref: the referral code of a shared link, 90 days. Some product pages set a short-lived unlock cookie of their own.
- Google Ads cookies (for example _gcl_au): set by Google only when advertising storage is allowed; Google sets their lifetime (about 90 days).
Change your choice at any time with the Cookie settings link in the footer of every page: it reopens the choice (Accept, Reject, or Settings with one switch for advertising measurement). Deleting the cookies in your browser also resets it.
How long we keep it
- Email addresses: while you are subscribed or a member. Unsubscribing deletes the address from that list at once; an unconfirmed signup is never mailed again.
- Server logs: 14 days, then deleted.
- Meta ad measurement click records (no IP address): 8 days, then deleted. Designs made on our product pages: saved only when you press the buy button; unpaid ones 8 days, paid ones 37 days after payment.
- Purchase measurement records (no email: hashed sale id, product, time, price, click id, consent state): up to 400 days, then deleted. Google Ads only accepts clicks of the last 90 days.
- Purchase records at Gumroad: kept by Gumroad as merchant of record under its own policy.
- Anonymous beacons: kept as counts for our statistics; they identify no one.
- Cookies: the periods listed above.
Text you type into our tools is used only to make your files and is deleted on the schedule above.
Your rights
You can ask for a copy of what we hold about you (access), for its correction or deletion, and you can object to its use, including to ad measurement at any time. Email [email protected] from the address concerned; we answer within one month. In the UK you can also complain to the Information Commissioner's Office, in the EEA to your national data protection authority.
Who else gets data
We never sell your data. Only the services that make the site run receive it: email delivery (Resend), payments (Gumroad), the network in front of the site (Cloudflare) and, as above, Google for ad measurement.
Clone Watch for rentals
- Your listing content: the photos, description and URLs of properties you register, plus mathematical fingerprints of them. This is the product: we compare the open web against these fingerprints.
- Evidence of suspected clones: screenshots and page copies of publicly visible pages that match your listings, kept as proof for takedowns. Evidence of confirmed fraud may be retained where retention is legally appropriate.
- Checker submissions: URLs submitted to the public checker, and the submitter's IP address for rate-limiting only.
To delete an account, its properties and fingerprints, email us from the account address.
מעקב תכניות בנייה (/il/plans)
כשנרשמים להתראה אנחנו שומרים את כתובת המייל, את המעקבים שבחרתם (תכנית, עיר או מילת חיפוש), את העמוד שממנו נרשמתם, ואם הגעתם ממודעה, את סוג הקליק ואת פרמטרי הקמפיין. אנחנו משתמשים בהם רק כדי לשלוח את ההתראות ולמדוד את המודעות שלנו. הסרה מהרשימה (לחיצה אחת, בכל מייל) מוחקת את הכתובת ואת כל המעקבים שלה. טקסט החיפוש שאתם מקלידים באתר אינו נשמר.
מדידת מודעות: אם הגעתם לאתר ממודעה של Google ואישרתם הרשמה להתראות, אנחנו מדווחים ל־Google Ads שהמודעה הובילה להרשמה, ומצרפים את כתובת המייל שלכם בצורה מגובבת (SHA-256, קוד חד־כיווני, ולא הכתובת עצמה), כדי ש־Google תוכל לשייך את ההרשמה לקליק על המודעה. על מבקרים שלא הגיעו ממודעה איננו מדווחים, ואיננו שולחים ל־Google פרטים נוספים.
DataWork Watch
If you subscribe to DataWork Watch updates we store your email address and, if you choose to provide them, eligibility preferences (country, work types, languages), used only to match program alerts to you. Unsubscribing (one click, in every email) deletes the address and the whole profile.
Shutdown Watch (/shutdowns)
Followers: we store your email, confirmation timestamps, the events you follow, and (for members) your tool watchlist and an encrypted copy of your license key for re-verification. Unsubscribing deletes the whole profile. Reminder emails (T-30/7/1) are sent only for deadlines you explicitly watch. Members' personal calendar feeds use an unguessable token stored only as a hash; re-activating rotates it, unsubscribing deletes it, and the token never appears in our logs.
Sponsors (Migration Slot): we store the sponsor name, link, pitch, verified transaction amounts/timestamps from Gumroad, and moderation state, kept while the placement is live and in the public bid history afterwards (amounts and relative times only). Sponsor emails are transactional (slot status), capped, and carry List-Unsubscribe; unsubscribing from marketing never blocks activation or receipt emails.
Crawling
Our monitoring only visits public pages, identifies itself, and honors robots.txt; full policy on the bot page.