Privacy

Proposed launch policy · Updated October 1, 2026. Pending final approval.

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. We skip this tracking when the browser sends Do Not Track. Global Privacy Control does not disable this internal click counter or its temporary repeat-filter identifier. 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

When enabled, a random first-party browser identifier is stored locally and changes daily at midnight UTC. The server stores a daily hash and the last activity time. Tabs sharing browser storage reuse the same identifier. “Online” estimates browser activity in the last two minutes; “visitors today” estimates distinct daily identifiers, not exact individual people.

The traffic table stores no raw IP addresses and uses no fingerprinting. Older activity rows are removed in bounded scheduled batches, usually leaving the current and previous UTC dates; cleanup backlogs can extend this period. No traffic identifier is created when measurement is disabled. Tracking is disabled in the prepared staging/production configurations pending privacy review.

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.