Privacy
Effective October 1, 2026.
Flekt Technologies Inc., a Delaware corporation in the United States, operates bid.flekt.com and is responsible for the personal information it collects for this service. Contact bid@flekt.com about privacy or your listing.
Listings and purchase records
We store submitted URLs, listing identities, optional titles/subtitles, ranking spend, timestamps and visibility decisions to operate the leaderboard. Listing information is public when visible. We also store checkout attempts, accepted terms versions, provider session/payment IDs, verified payment amounts and minimal webhook/recovery records to process payments reliably, prevent duplicate credit and investigate problems.
There are no user accounts. A private purchase reference is kept in your browser’s session storage so that browser can check its purchase status. The database stores a hash of the private token. Do not share the reference. Closing the browser does not stop a verified payment from being fulfilled.
Checkout and service providers
Checkout is hosted by Stripe. Payment details and billing information are entered there; this application does not store card numbers. Stripe and Link handle payment, tax, fraud prevention, receipts and transaction support under their own policies. Stripe privacy information.
The launch architecture uses Cloudflare Workers and D1 for hosting and records. Cloudflare processes request information for delivery, security and rate limiting. Application error logs use minimal identifiers and error categories rather than full billing data or private purchase tokens. Cloudflare may process IP addresses and other request metadata under its service and security settings. We do not claim that our hosting infrastructure processes no IP information. Cloudflare privacy information.
Favicons and shortened links
Favicon requests send a submitted hostname to Google’s favicon service through our server. Successful images are cached; retry metadata is retained briefly for failed images. We do not fetch website names or descriptions. Recognized shortened links are contacted only to resolve their destination; we do not fetch arbitrary submitted website content.
Listing clicks
We publish approximate cumulative clicks on each listing’s Visit site link. To avoid counting rapid repeat clicks, we store a random identifier in your browser’s local storage. It rotates on the next click after midnight UTC. The server stores only a daily hash of that identifier, the listing ID and the last counted time. These temporary records become eligible for removal after 24 hours; bounded five-minute cleanup can extend retention during a backlog. The cumulative total remains with the listing. We do not store IP addresses or a permanent per-person click history in this feature. The internal click counter and its temporary repeat-filter identifier do not respond to Do Not Track or Global Privacy Control signals. We do not sell or share the visitor identifier or its hash with advertisers or listed sites, or use it for targeted advertising; listed sites can see only the public aggregate count. Counts are not unique visitors or guaranteed human traffic. Cloudflare still processes requests for security and rate limiting.
Approximate visitor counters
While a leaderboard tab is open and visible, your browser keeps one WebSocket connection to our server and sends a random first-party identifier stored in local storage (it changes daily at midnight UTC). The server stores only a daily hash of that identifier, never the raw value, and one anonymous total per day. Tabs sharing browser storage reuse the same identifier. “Online” is the number of distinct identifiers connected now or that disconnected within the past 15 minutes (we keep the daily hash and the time it left for those 15 minutes only); the public visitors figure is the running all-time total of each day’s distinct identifiers (we also keep a rolling 24-hour count internally). A returning person on a later day counts again. These are visits, not exact individual people. The connection closes when the tab is hidden or closed, and that visitor then counts as online for 15 more minutes.
Each visitor’s first sighting of the day is also recorded with an approximate country (provided by our network provider, Cloudflare, from the connection) and the time. We do not store the visitor’s IP address with it, and the entry is not linked to the daily hash. The public visitors pop-up lists the most recent 200 of these entries (for example “Visitor in France, 5m”), and we keep a running count of visits per country.
This feature stores no IP addresses and uses no fingerprinting. Daily hashes are deleted after about one day; the permanent record is one number per day. No identifier is created when measurement is disabled. Cloudflare still processes requests for security and rate limiting.
Analytics and error tracking
When enabled, we use PostHog (US cloud) to understand how the leaderboard is used and to find errors. In the browser we send page views (page name only, never the query string or fragment), the referring website’s domain, campaign tags such as utm_source, approximate device, browser, operating system and screen details, and which actions happen: Outbid clicked, quote requested, confirmation opened, checkout started, load more used, and outbound listing clicks (public listing ID and rank). We also send browser errors with private values such as URLs, email addresses, purchase references and long tokens removed. On our servers we send verified placement events (new placement or increase, original USD placement amount excluding tax and currency conversion, public listing ID) after payment is verified, and reversal events after a verified refund or dispute, plus error categories for failures. These records are not net earnings.
This integration does not record sessions or screen replays, does not capture what you type, and does not use automatic click or form capture. We do not send the text you enter in the URL, title or subtitle fields, billing details, card information, private purchase tokens or purchase IDs to PostHog. The browser stores a random first-party identifier and session information in a cookie and local storage so PostHog can recognize returning visitors and measure sessions. PostHog also derives approximate location (country and city) from your IP address; like any website you contact, PostHog necessarily receives your IP address with each request, and its documentation describes how it handles it. We do not create person profiles or identify visitors, and we do not link the identifier to purchases. Analytics does not currently respond to Do Not Track or Global Privacy Control signals. Server-side payment events are not tied to a browser visitor. Counts are approximate and are not unique people, and our own click counter remains the source for public listing clicks.
PostHog processes this information as our service provider under its own terms; see PostHog privacy information. Its library may load a script from PostHog’s asset host when browser error tracking starts. Analytics records are kept under the retention settings of our PostHog project; we have not adopted a final retention period.
Support, retention and requests
If you contact support, we receive the information you send so we can handle the request. Avoid sending card details, passwords or API keys. Payment, moderation and audit records are retained for reconciliation and operational needs; we keep them for as long as needed to reconcile payments, handle disputes and complaints, prevent duplicate credit and meet applicable recordkeeping requirements. Public listing data remains while the listing and service operate, unless removed following review. Support information is kept while resolving your request and afterward where needed for follow-up, disputes or recordkeeping. We review retention according to these purposes; these records are not currently erased by an automatic fixed-date cleanup. Backups and provider logs may retain copies under their own retention settings.
Contact bid@flekt.com to request correction, access or deletion. We may need to confirm that you are authorized to make a request; this does not add a public ownership-verification or editing feature. Some records may need to remain for legitimate payment or legal reasons. Stripe/Link requests are also handled under their own policies.
Purposes and privacy rights
We use purchase and submission information to provide the service you request. Where applicable data-protection law requires a legal basis, this includes performing our agreement with you, complying with legal obligations, and our legitimate interests in securing the service, resolving complaints and maintaining reliable payment records. Measurement involving browser storage needs a separate assessment of applicable consent requirements; accepting purchase terms does not substitute for measurement consent.
Depending on where you live, you may have rights to access, correct, delete or obtain a copy of your personal information, restrict processing, object to certain processing, or withdraw consent where processing relies on consent. Contact bid@flekt.com to make a request. You may also complain to your local privacy regulator. We respond under applicable law and may retain information where a legal requirement or another permitted exception applies.
International processing and sharing
Flekt is based in the United States. Our providers may process information in the United States and other countries. Their privacy information describes their processing and transfer arrangements. We share information as needed to provide hosting and payments, handle support, comply with law, or protect the service and others’ rights. We do not sell personal information or share it for cross-context behavioral advertising. Public listing information and aggregate counts can be viewed by anyone.
Policy changes
We will post changes on this page and update its date. If a change requires new notice or consent under applicable law, we will provide it before using information for that new purpose.
Back to the leaderboard