As an Amazon Associate I earn from qualifying purchases. I also earn as an eBay Partner Network affiliate and as a Darts Corner affiliate via Adtraction. No extra cost to you.

Privacy Policy

Last updated: November 2026

1. Introduction

MyDartFinder ("we", "us", "our") is a free informational website that helps dart players find darts that match their preferences. We are committed to protecting your privacy.

We do not require registration to browse the site or create visitor profiles across visits. Our hosting provider keeps short-lived technical and security logs (such as IP addresses) for its own stated periods. The personal data we receive directly is what you choose to send us through the contact form (see Section 2) and, once accounts are enabled, what you provide if you create an account to comment or to save setups (see Section 6). The third-party tools described below (analytics, affiliate networks, hosting) may process data such as your IP address or cookie identifiers, which can be personal data; this policy explains each of them.

Data controller: MyDartFinder is operated by Aki Sorvoja, a private individual based in Finland, who is the data controller for the processing described in this policy. We have not appointed a data protection officer. For any question about this policy, or to exercise the rights described in Section 9, contact us at info@mydartfinder.com.

2. Contact Form

If you contact us through our contact form, we receive the information you submit: your name, email address, the subject you choose from the list, and your message.

  • Purpose: used solely to respond to your enquiry, never for marketing, profiling, or sale to third parties
  • Processor: submissions are delivered to us by Web3Forms (web3forms.com/privacy), which acts as our processor under its Data Processing Agreement. Web3Forms operates from India and uses infrastructure and spam-filtering providers that may process data in several regions, so your submission (including your IP address and email address, which its spam filters receive) may be transferred outside the EEA and the United Kingdom. These transfers rely on the EU Standard Contractual Clauses and the UK Addendum included in that agreement.
  • Retention: Web3Forms keeps a copy of each submission for up to 3 years from the date you send it, unless we delete it earlier. We keep our own email correspondence only as long as needed to handle your enquiry, then delete it

The contact form does not set any cookies. To request deletion of past correspondence, simply contact us.

3. Analytics (after consent)

We use Google Analytics 4 to understand how visitors use our site. This helps us improve content and the finder tool.

Google Analytics may collect:

  • Pages visited and time spent on the site
  • Browser type, device type, and operating system
  • Approximate location (country or region, not precise)
  • Referring website or search query

Google Analytics uses a pseudonymous identifier stored in a cookie to tell visits apart; it does not store full IP addresses, and we do not use it to identify individual people. The reports we see are aggregated.

Consent: Google Analytics loads only after you accept analytics cookies in our consent banner. If you decline (or ignore the banner), no Google Analytics cookies are set and no data is sent to Google.

Opt-out: You can prevent Google Analytics from collecting data by installing the Google Analytics Opt-out Browser Add-on available at tools.google.com/dlpage/gaoptout.

Finder feedback context

We do not send a separate event for each Finder answer or store a new step-by-step Finder timeline. When you use the feedback control, a limited snapshot of your selected options and displayed results helps us understand the rating, even without a comment. See section 7 for the fields collected and retention. Functional answer history stays in your browser so Back and Forward work.

4. Analytics (Cloudflare Web Analytics)

We also use Cloudflare Web Analytics, a privacy-first measurement tool provided by our hosting platform. It does not use cookies, does not store any identifier on your device, and does not track you across sites: it gives us aggregate page-view and performance counts only. Because it stores nothing on your device and processes no personal profile, it runs independently of the cookie-consent banner. Details: cloudflare.com/web-analytics.

5. Affiliate Links & Tracking Cookies

MyDartFinder earns a small commission when you purchase darts through our affiliate links. This does not affect our rankings or recommendations: the finder algorithm is purely preference-based.

When you click an affiliate link, the partner's tracking network may set a cookie in your browser to record the referral. We currently participate in the following programmes:

  • Amazon Associates: links to Amazon carry our associate tag
  • eBay Partner Network: links to eBay listings are affiliate links
  • Darts Corner: tracked via the Adtraction affiliate network

When you click an affiliate link, the retailer or its tracking network may receive the following data: the referring URL (mydartfinder.com), a click timestamp, and a session or device identifier stored in a cookie. MyDartFinder does not receive personal data, purchase details, or payment information at any stage.

These cookies are set by the respective networks, not by MyDartFinder. We do not receive or store any data about your purchases, browsing history, or personal details.

Refusing affiliate cookies. Because these cookies are set by the networks only after you click a link, our cookie banner does not control them. You can refuse them by blocking third-party cookies in your browser settings, and you can delete them there at any time. You can also use the cookie and privacy settings on the retailer's own website, and the networks' privacy notices listed in Section 9 explain their own choices. Our links work the same without these cookies; the retailer may then not credit us for the referral, which costs you nothing.

Product images. Some product images are loaded directly from retailers' image servers: Darts Corner images from its own servers and its Shopify content delivery network (cdn.shopify.com), and eBay listing images from eBay's image server (i.ebayimg.com). This happens when a page showing the image loads, without any click, so those servers receive the technical data that every image request carries, such as your IP address and browser details. MyDartFinder does not receive this data.

6. User Content (Comments and Saved Setups)

This section applies once accounts are enabled on the site. Until then it has no effect.

If you create an account, post a comment or reply, or save a setup, we process the following data:

  • Your account: the identifier of your login and your email address, held by our sign-in provider (Clerk, Inc., United States; see the processor list in Section 9), and the display name you chose. Your comments, saved setups and moderation records are stored by our hosting provider (Cloudflare) in its data centres, which may include locations outside the EEA. Transfers to Cloudflare and Clerk outside the EEA rely on the EU Standard Contractual Clauses in their data processing agreements and, where the provider is certified, on the EU-US Data Privacy Framework; you can obtain a copy of these safeguards from us on request.
  • The content of your posts, their edit history, and their publication status.
  • A moderation log recording what happened to each post: whether it was published, flagged, hidden, or removed, whether the decision was made by the automated filter or by a person, and, for restrictions, the stated facts and reason.
  • Reports you submit about other users' content: the explanation, the link to the reported content, and your name and email address (required, unless the report concerns offences covered by Articles 3 to 7 of Directive 2011/93/EU, which may be reported anonymously).
  • Saved setups and your public profile: when you save a setup (from the Setup Builder, the Dart Finder or Find Setup) we store its name, your optional note, the parts or darts it lists, the tool settings needed to reopen it, when you created and last changed it, whether you marked it public and its moderation status. Private setups are not shown to other users. If you make a setup public, anyone who has the link to your profile page can see it together with your display name and the date it was last updated. Its public text (name, note and listed parts) passes the same automated filter as comments and can be reviewed, hidden or removed by a person under the same rules. The moderation log records each decision about a public setup in the same way as for posts: whether it was published, flagged, hidden, or removed, whether the filter or a person made the decision, and, for restrictions, the stated facts and reason. Unlike comments, we keep no edit history of a setup and no separate record of each automated check: we store only the current version of the setup, and the log records the decisions, not a copy of the setup. Your profile page has a random identifier that is not derived from your name or email. We ask search engines not to index your profile page, but anyone with the link can open it, so only make public what you are happy for others to see.

Automated classification. Before a post is shown publicly, its text is checked on our own server by an automated rule-based filter for indicators of spam, harassment, threats, illegal content, and other possible breaches of our content rules. The filter applies predefined rules and pattern checks; it does not use a machine-learning model and does not send the post text to any external moderation provider. Depending on the result, a post may be published, queued for human review, or temporarily hidden pending human review. A human makes the final decision on every post that the filter flags or hides. You may request human review and challenge a restriction using the procedure described in our Terms of Use.

Legal bases. Creating your account, storing and displaying your posts, and letting you edit them is necessary to provide the comment feature you asked for (GDPR Art. 6(1)(b)). The automated check and human moderation of posts rest on our legitimate interest (Art. 6(1)(f)) in keeping the site free of spam, harassment, and illegal content and in protecting other users; you can object to this processing (section 9). Writing statements of reasons, keeping the moderation log, and handling reports of illegal content are necessary to comply with our legal obligations under Articles 16 and 17 of the EU Digital Services Act (Art. 6(1)(c)). Following up a report with you, where needed, rests on our legitimate interest in handling it properly (Art. 6(1)(f)). Storing your saved setups, showing the ones you make public on your profile page, and letting you edit or delete them is likewise necessary to provide the saved-setups feature you asked for (Art. 6(1)(b)). The automated check and human moderation of public setups rest on the same legitimate interest as for posts (Art. 6(1)(f)), and statements of reasons and report handling for public setups on the same legal obligations under the Digital Services Act (Art. 6(1)(c)).

Serious offences. If a post gives us reason to suspect a serious criminal offence involving a threat to someone's life or safety, we are required to inform the police or judicial authorities and to give them the relevant information we hold, which may include the post, its edit history, the account identifiers, and related moderation records (Digital Services Act, Article 18; legal basis GDPR Art. 6(1)(c)). We keep an internal record of such a report separately from the ordinary moderation log, accessible only to the operator, until the matter is closed by the authorities and for the same 3-year period thereafter.

What you must provide. To comment you need an account (a login identifier held by our sign-in provider) and, if you want your name shown, a display name; without them you cannot comment, but you can still read everything. To report content you must give an explanation and, except in the cases named above, your name and email address; without them we cannot process the report. To save setups you need an account; to make a setup public you also need a display name, which is shown with it. Without a display name your setups stay private.

Automated decisions. The automated check described above can delay the publication of a post or hide it temporarily until a person reviews it. It works by matching the text against our content rules: low risk is published, uncertain posts are queued for review while staying visible, and high risk is hidden until a person has looked at it. Our target is to review hidden and queued posts within 7 days; this is a target, not a guarantee. A person makes every final decision. You can ask for human review, give your view, and challenge any restriction at any time using the procedure in our Terms of Use.

Retention of the moderation log. We keep the moderation log (records of what was flagged, hidden, or removed, and why) for 3 years from the decision, so that a restriction can still be reviewed or challenged after the fact. After that period, the entries are deleted or anonymised.

Reports about content. If you submit a report using the "Report" link, we keep the report, together with the moderation decision taken on the reported content, as part of the moderation records above. We use your contact details to tell you our decision and how to challenge it, and, if needed, to ask you for more information. Contact details and the free text of reports are deleted at the end of the same 3-year period.

Daily quiz: Nine Darter

Nine Darter stores the challenge date, submitted correct answers or passes, dart results, score and attempt timestamps so you can finish or recover your daily game. Incorrect free-text guesses are not retained as answer history. A random recovery secret is stored in your browser; the server stores its hash. Quiz browser storage does not contain your account session token. We process this information to provide the game you request (GDPR Art. 6(1)(b)). Cloudflare processes requests and hosts the quiz database under the service-provider arrangements described above.

Guest attempts are deleted after 30 days by scheduled maintenance. Account-linked attempts remain until you delete your account. Account deletion removes your quiz attempts and leaderboard entry. Publishing an official result is optional and off by default. If you opt in, visitors can see your chosen public name, challenge date, score and position. Your email address, account-provider identifier and private recovery secret are never displayed. Practice results are not published as official scores.

To prevent abuse, we use a daily salted hash of your network address to limit new attempts and excessive requests (GDPR Art. 6(1)(f), our legitimate interest in operating a fair, reliable game). The raw address is not stored in the quiz attempt table. Providers may retain ordinary request logs under the service and logging policies described here. Hashes associated with guest attempts are deleted with those attempts. The quiz recovery secret in browser storage is necessary to recover the game you request and is separate from optional analytics.

7. Rate Limiting & Abuse Prevention

To prevent spam and abuse, we limit how many comments an account may post and how many setups it may save in a given period, and an account can hold up to 100 saved setups. These limits are counted per account, not per IP address. For the content-report form, which works without an account, we count requests using a daily rotating IP-address hash, separate from the report itself. The security-counter retention and recovery-history periods are described in section 10.

Page feedback (thumbs up/down): the small "Was this useful?" control at the end of some pages works without an account or cookie. We store the vote, the optional comment you type, the page and the part of the page it came from, the time, and a random identifier created for that page view that links a vote to its comment. For Finder and setup advice, the vote also includes a limited snapshot of your selected preferences, the result count, up to five suggested product identifiers, match scores where available, and the site and data versions. This helps us reproduce the advice you rated. The snapshot excludes typed search descriptions, full URLs and analytics identifiers. It stays with the feedback in our database and is deleted with it; automated reports contain only aggregate counts, never individual answer snapshots. We do not store your IP address, or any hash of it, with your feedback. To cap the number of submissions we count them per IP address in a separate short-lived counter using a daily rotating hash. It is not linked to your feedback; its retention and recovery-history periods are described in section 10. Feedback rows older than 365 days are deleted when a new feedback submission is accepted. If no new submission arrives, deletion is delayed. Your browser remembers locally (localStorage, no cookie) that you already answered on a page. Comments are read by a person; do not include personal data in them.

8. Cookies Summary

Sign-in cookies (Clerk). If you sign in to an account (for comments and saved setups), our sign-in provider Clerk sets authentication cookies for mydartfinder.com, either on the site itself or on its sign-in address for our site (clerk.mydartfinder.com): __session, which holds your sign-in session so that the site knows you are signed in as you; __client, which authenticates your browser to Clerk; and __client_uat, which records sign-in freshness. Instance-specific versions can add a suffix to these names. The stored session cookie can last about one year, while its short-lived sign-in token normally refreshes every 60 seconds. Client and freshness cookies can last up to 400 days in supported browsers; Clerk can refresh their expiry. Cookie storage duration does not make an expired or revoked sign-in valid. They are set only when the sign-in software runs: on the account page, when you start signing in, and while you are signed in. If you only browse the site, they are not set. These cookies are strictly necessary for the account you asked for, so they are set without asking for your consent (EU ePrivacy Directive, Article 5(3)); they are not used for analytics or advertising and are not controlled by the cookie banner. You can delete them in your browser settings at any time; you will then be signed out.

You can change or withdraw your analytics consent at any time using the Cookie settings link in the footer of every page. Withdrawing consent deletes the Google Analytics cookies from your browser and stops new Google Analytics sends.

You can also manage or delete cookies at any time through your browser settings. Note that disabling cookies will not affect your ability to browse MyDartFinder or use its tools; only signing in to an account needs the sign-in cookies described above.

Local storage (on your device only)

Some features store data in your browser's local storage so they work across visits: your cookie-banner choice (cookieConsent), the Setup Builder's in-progress setup draft (mdf-builder-draft), the darts you select in the Compare tool together with their names (dartCompare, dartCompareNames), and which pages you already rated with the page feedback control (mdf_fb:<page>:<screen>, the value is only up or down). This data stays on your device, is never sent to MyDartFinder or any third party, and you can clear it at any time via your browser's site-data settings.

9. Your GDPR Rights

Legal bases for processing (GDPR Article 6). We rely on: your consent (Art. 6(1)(a)) for Google Analytics cookies, which run only if you accept analytics in the banner; our legitimate interests (Art. 6(1)(f)) in measuring aggregate traffic (Cloudflare Web Analytics) and in verifying affiliate referrals and in operating the page-feedback widget and the search by description (section 7), including their abuse-prevention counters, to improve the site and prevent misuse; and, for contact-form messages, processing necessary to handle the enquiry you initiate (Art. 6(1)(b), and your consent under Art. 6(1)(a)). The legal bases for user content and moderation are listed in section 6.

If you are located in the European Economic Area (EEA) or the United Kingdom, you have the following rights regarding your personal data under the GDPR and the UK GDPR:

AccessRequest a copy of personal data held about you.
RectificationRequest correction of inaccurate data.
ErasureRequest deletion of your personal data.
RestrictionRequest that processing of your data be limited.
PortabilityReceive your data in a structured, machine-readable format.
ObjectionObject to processing based on legitimate interests.

You also have the right to lodge a complaint with a supervisory authority. In Finland this is the Office of the Data Protection Ombudsman (tietosuoja.fi/en); other EEA residents may contact their local authority. If you are in the United Kingdom, you can complain to the Information Commissioner's Office (ico.org.uk).

You can exercise these rights for all processing for which MyDartFinder is the controller by contacting us, including where a service provider processes the data on our behalf (Web3Forms, Cloudflare, Clerk and, for the search by description, OpenAI). Some of the companies below process data as independent controllers (Google Analytics, the affiliate networks and retailers); requests about their own processing should be directed to them under their privacy notices. You can also withdraw a consent you gave (analytics cookies) at any time through the cookie settings. Their privacy notices:

Right to erasure and user content. If you ask us to delete your account, we remove the account link and the stored display name from your posts and from the moderation notices addressed to you; the moderation records keep only an internal reference that no longer points to an account. We then assess whether the text of a post, or its context in the conversation, can still reasonably identify you. If it cannot, the text may stay visible as an anonymous part of the discussion. If it can, it is still personal data and we erase or redact it, unless keeping it is necessary for the exercise of freedom of expression and information or for the establishment, exercise, or defence of legal claims (GDPR Art. 17(3)); we tell you if we rely on one of these. You can also ask us to erase specific posts at any time, with or without deleting your account.

Deleting your account also deletes your saved setups (private and public) and your public profile page; unlike comments, a saved setup is not part of a shared conversation, so we remove it instead of anonymising it. Moderation log entries about a public setup stay for the period in section 10, no longer linked to your account. Deleted data may remain in our hosting provider's short-term backups for up to 7 days before it is overwritten.

10. Data Retention

The separate Finder progress collection has been retired. Earlier progress records remain in our Cloudflare-hosted database for at most 30 days from receipt and are removed separately after collection stops. Its old abuse-prevention counter expires at the end of the day (UTC). Retention periods for data held independently by third-party providers are governed by their respective privacy policies. If you save a setup to your account, it is stored as described in section 6.

Page feedback (section 7): votes and comments are stored without an account, IP address or IP hash. Feedback rows older than 365 days are deleted when a new feedback submission is accepted. If no new submission arrives, deletion is delayed.

Search by description (section 7): our application does not store the text you type. OpenAI abuse-monitoring logs may retain it for up to 30 days, or longer as described in section 7. The IP-based counter stops limiting searches at the end of the hour; expired records are removed as described in section 7. Our separate cost ledger contains only random request identifiers, the calendar month and numeric cost reservations, with no search text, IP address or account identifier.

Once accounts are enabled (section 6), we retain:

  • Account and posts: until you delete your account; posts are then anonymised or erased as described in section 9, and we instruct our sign-in provider to delete your login record, subject to any security or legally required records it must keep under its own documented retention periods.
  • Moderation log and content reports: 3 years from the decision, then deleted or anonymised.
  • Saved setups: until you delete them or your account. Moderation log entries about a public setup: 3 years from the decision, as for comments, even if you delete the setup or your account earlier; they do not contain a copy of the setup.
  • Rate-limit counters: see the security-counter expiry and cleanup periods below.

Security counters and database recovery history. These counters are separate from content and usage records. They contain no raw IP addresses, email addresses or submitted answers and are not joined to usage analytics. Website account and reporting counters use D1 storage. They use daily rotating IP-derived hashes or hashed account identifiers and are removed by scheduled cleanup, normally within an hour after expiry. Service interruptions may delay cleanup. Expired counters are removed before a restored account database is reopened for writes. Page-feedback counters use KV storage. They use daily rotating IP-derived hashes and expire automatically at the UTC-day boundary or after the minimum 60-second expiry interval, whichever is later. Deleted D1 records can remain recoverable in short-term database recovery history for up to 7 days.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated date at the top. We encourage you to review this page periodically.

12. Contact

If you have any questions about this Privacy Policy, please contact us.