1. Who can dispute
- Callers (or someone authorised to act for them) can contest how their calls were read, priced, labelled or flagged, or whether a channel was attributed to them.
- Anyone else can report an error they spot on any public page: a misread call, a wrong price, a wrong flag, or a missing call.
2. How to send a dispute
Email help@fenestrading.click with the subject line Dispute: <caller or token> and include:
- the Fenestra page link (
/c/…or/t/…) and the link to each original post you are disputing; - which verdict or flag you think is wrong, and what it should be;
- your evidence: for example the full post text, timestamps, the token's contract address, a price chart or data source for the relevant time, or on-chain transactions;
- if you are the caller and want a change only the caller can ask for (for example attribution or an objection to processing), proof that you control the channel or account, such as posting a short code we send you in that channel.
Do not send private keys, seed phrases or passwords. We will never ask for them.
3. What we correct
When the evidence shows we got something wrong, we correct it. That includes:
- Extraction errors: wrong token, wrong direction, misread entry, stop or targets, a post that was not a call (for example a warning or a joke) counted as one, or a real call that we missed.
- Attribution errors: a call or channel attributed to the wrong caller, or an impersonating channel listed as the real one.
- Price errors: a wrong pool, a bad or missing candle, or a wrong currency conversion that changed a label.
- Flag errors: a post flagged deleted or edited that was not, or a "late" flag based on bad price data.
- Methodology bugs: if a dispute shows that the scoring code does something different from our Methodology, we fix the code (or the page) for every caller, not only the one who wrote in.
4. What we don't change
- Correct results you dislike. If a call was read and priced correctly, its outcome stands, even if the caller sold earlier, or meant a different timeframe they did not state in the post.
- Deleted calls. Deleting a post does not remove the call from the record. It stays, with a deleted flag.
- Edits after the fact. We score the post as originally published. An edit that adds a stop or changes a target after the move does not change the verdict.
- Heuristic flags applied correctly. "Late" describes the price run-up before the call; if the run-up was real, the flag stays. It is not a claim about intent, and you are welcome to send context, which we may show alongside.
- Paid changes. No one can pay for a better score, a removed call or a higher rank.
5. Timelines
| Step | Target time |
|---|---|
| Acknowledgement of your email | Within 5 business days |
| Decision, with reasons | Within 30 days of receiving complete evidence; we will tell you if we need longer |
| Correction on the site | Within the next scoring pass after the decision (passes run about every 30 minutes), then the next leaderboard snapshot |
| Privacy requests (access, rectification, objection) | Within one month, as the GDPR requires |
These are targets, not guarantees.
6. After a decision
We reply with what we changed, or why we did not. Corrections are logged internally, with the date and reason. Because leaderboard snapshots are hashed when published, an earlier snapshot is not rewritten; the next snapshot reflects the correction. If you disagree with our decision, reply with any new evidence and a different team member will review it.
7. Privacy requests from callers
Callers have data protection rights over the personal data in their record, including correction and objection. See our Privacy Policy. We weigh each objection against the public interest in an accurate record of public market calls, and we tell you the outcome and how to complain to a data protection authority if you disagree.