Privacy policy

Reading the site

CamRanks loads Yandex Metrika to measure visits: page views, referrals, and device or browser signals. Metrika may set its own cookies and may process IP addresses on Yandex’s side. See the Yandex Metrika terms. Session replay (Webvisor) is not enabled.

CamRanks loads Google Analytics 4 to measure page visits and interactions. Google Analytics uses cookies and collects browser/device information and activity on the site. See Google’s Analytics data information and its browser opt-out add-on.

CamRanks loads Microsoft Clarity for interaction analysis, heatmaps and session playback. Clarity can collect clicks, scrolls and page structure for playback; this is separate from Metrika’s Webvisor setting. See Clarity’s data collection documentation and the Microsoft privacy statement.

Besides page views, these measurement tools receive five named site events: a Visit click (the platform name and the label of the button’s position on the page), an opened FAQ question, a changed budget or currency preset in the planner, a site search submission without the search words, and a click on a follow link or button (Telegram, browser notifications or RSS, with the label of its position on the page). The search results page loads none of these three tools and is served so that Cloudflare does not add its page beacon either, so your search words are not sent to any of them.

Two of those events, an opened FAQ question and a changed budget or currency preset, are also sent from your browser to camranks.com, and our server passes them on to the tracker described below: the event name and the time it arrived, the question text or the preset, the page path, and from the request your browser string and language preferences, a device class and the country code supplied by our host. Our server passes such an event on only when the page path is one of our pages and the question or preset is one that page actually shows, so a made-up page address, question or preset is refused. Your browser string and language preferences are not checked this way: they are passed on as your browser sends them, as with every page request described below. The IP address is not passed on.

CamRanks also keeps its own log of page requests on a tracker server that we run ourselves. After our server has answered a page, it (not your browser) sends that tracker: the time of the request; what kind of request it was: a page view, a page your browser fetched in advance because you might open it next (a prefetch), a visit by a crawler or other automated client (with the crawler’s name when it is a known one, otherwise the label “other”), or a read of a page’s Markdown version by an assistant, a crawler or anyone else (with the same name or label when the client is automated); the page path without any query string, as an address on camranks.com whose path is cut to 512 characters; the response status; whether our edge cache served the page; the country code supplied by our host; the address of the referring page without its query string, also cut to 512 characters; a device class (mobile, tablet or desktop); whether your browser marked the request as a prefetch; and your browser string and browser language preferences. It does not send your IP address, and the tracker sets no cookie in your browser this way. A request for an address that no page of this site can have, such as a script or backup file that scanners look for, is not logged when it finds nothing. A search on the search results page is logged the same way as a search submission with the number of results and the length of the search text, never the words.

Our server also counts each page and Markdown request in request statistics that Cloudflare stores for us (Workers Analytics Engine) for three months: the page path without any query string, whether it was a page view, a prefetch, a Markdown read or a visit by a crawler or other automated client (with the crawler’s name when it is a known one), the country code supplied by our host, the response status class, whether our edge cache served it and the request method, but never your IP address, browser string, referring page or cookies.

You can read the guides and use the price comparisons without an account, an email address or payment details. We do not run advertising pixels beyond what is disclosed here. Affiliate Visit clicks go through our /go/ redirects.

Cloudflare hosts the site and processes requests, including IP addresses, to deliver pages and protect the service. Its handling is described in the Cloudflare privacy policy.

Cloudflare also adds a Web Analytics beacon to the public site to measure page views and loading performance. This browser measurement is separate from its hosting logs. See what Cloudflare Web Analytics collects.

Following a Visit link

A Visit link redirects from CamRanks straight to the partner. The redirect creates a random click reference and passes that reference to the partner for referral attribution. The address sent to the partner does not contain your name, email, payment details or IP address. CamRanks does not send the page address to the partner. The redirect does not wait for our click tracker.

CamRanks also sends a click notice to our own tracker. The notice can arrive after the redirect, and a failure to deliver it does not stop the partner from opening. It carries the click reference, the offer and its partner network, a label for where the link sits on the page when the link used a known placement id, the country code when the host supplied a two-letter code, the partner address the redirect sends you to (which includes the same click reference), and the browser string and browser language preferences from the request. It does not contain your name, email or payment details. Your browser is not sent to the tracker, so the tracker does not set a cookie on this visit. The CamRanks click row below is a separate record and still excludes the IP address, the browser string and language preferences.

The partner can associate that reference with activity on its own service, including a registration or purchase. Its privacy and cookie policies apply after you leave CamRanks.

When this deployment has event storage configured, CamRanks stores a click row so a later partner report can be matched to that click. The published site is configured to do this. The row contains the click reference, the fixed site tenant name, the partner network and offer, the country code supplied by the host when it is a two-letter code, the on-site page path and placement when the link used a known placement id, a source label, and the time. It does not contain your name, email, payment details, IP address or user-agent. A request that only checks the link (HEAD) is not stored. If storage is unavailable, the redirect still completes and no click row is written.

A partner can later report a registration, payment, rebill or refund for a click reference we issued. We then store, on that same click and network, the partner’s reference for the report, the event type, status, amount, currency, the event time and the time we received it. Reports for an unknown click reference are discarded. When our tracker is configured for it, each report we accept (including a repeat of one we already hold) is followed by our server sending that tracker what we then store for it: the click reference (written in another format), the event type, the status, the amount and currency, and the network with the partner’s reference for the report. Streamate reports arrive as a partner callback that must quote a click reference we created. A separate collector accepts the same kinds of reports only with a private token.

Retention: CamRanks keeps its click rows and partner reports without a fixed deletion date, for its own reporting and for partner reconciliation and disputes. No job deletes them on a schedule. They hold only the fields listed above, and none of them contains your name, email, payment details, IP address or browser string. The page log, the click notices and the forwarded partner reports on our tracker are kept for our own reporting and also have no fixed deletion date, although that server’s storage settings can remove older detailed records. To ask what we hold for a click reference, or to have a click and its reports deleted, write to us through the contact page and quote the click reference.

Editorial updates and alerts

Our RSS feed is available without registration. Your chosen feed reader retrieves it like a public page.

You can also subscribe to update notes through our Telegram bot or as browser notifications. What a subscriber gets: one confirmation message right after subscribing, and later occasional notes when a platform’s token prices, promos or card-statement labels change, at most once a week, nothing else. Sending those notes has not started yet; until it does, the confirmation is the only message. No advertising, and no message names anything explicit; a notification shows only “CamRanks” and a short plain note, because it can appear on a lock screen.

Telegram. When you send /start to @camranks_bot, we store, on our own server, your Telegram chat id, the date you subscribed, a label for the link you came from (site, footer, updates or contact; “direct” without one, “other” for anything else, never the text itself) and that the subscription is active. We do not store your name, username, phone number or your messages. Telegram processes the chat under its own privacy policy. Send /stop (or “stop”) to unsubscribe: your entry is deleted at once. Blocking the bot deletes it too, provided our bot receives Telegram’s notice of the block, which Telegram holds for 24 hours while the bot is offline. Besides the entries, the bot keeps only two running totals, of subscriptions and unsubscriptions, without any chat id.

Browser notifications. Nothing happens until you click “Browser notifications” and then “Allow notifications” on camranks.com; only then does your browser ask for permission. If you allow it, your browser creates a push subscription with its maker’s push service (Google, Mozilla, Apple or Microsoft) and sends it to us. We store, in our database at Cloudflare, the subscription address with its two encryption keys, the browser family (such as Chrome or Firefox) read from your browser string, the time you subscribed, the time of the last notification the push service accepted and a count of failed deliveries. We do not store your IP address or your full browser string. Each notification is encrypted for your browser, so the push service sees when we send and how large a message is, not its text. To unsubscribe, use “Turn off browser notifications” on the updates page in the same browser, which deletes our record at once. If you only block notifications for camranks.com in your browser settings (or clear its site data), we are not told: the record is deleted when the push service refuses our next message, and no notes are being sent yet, so until they are it stays. Use the button first.

Retention: each subscription is kept until you unsubscribe, or, for the cases above that we are not told about, until a message to it is refused. Copies: our daily backups, on our own server, include both subscriber lists and keep the last 14 daily generations (normally two weeks, longer if backup runs fail), and Cloudflare’s database keeps its own restore history for up to 30 days. A deleted entry can therefore remain in those copies for that long; nothing is ever sent from them.

Contacting us

If you email us, we receive the address and information you choose to send. Do not send card numbers, account passwords or sensitive screenshots. Use the contact page for privacy questions, including a question about a click reference, and for factual corrections.