Moderation and correspondence record

Published: 2026-07-17 Author: Jesper (JesperLive / MrSataana), developer of GRIP - Enhanced Macro Sequencer (GRIP-EMS)

Why this is a separate file

The rest of this repository has one rule: every claim is a line you can read in a shipped file, and every section tells you how to check it yourself. That rule is the reason the repository is worth anything. I am a competitor, so my framing is worthless — the files are not.

This file breaks that rule, and that is why it is not in the README.

Everything below is correspondence. Most of it you cannot verify. The CurseForge ticket is visible only to my account. The emails are in my mailbox. I am publishing it because leaving it out means the public record shows me withdrawing my weakest claim in June and says nothing about what the platform did in July, and that is a misleading picture. But you should treat it differently from the rest of the repository: this is my account of what I was told, and you are taking my word for it. Nothing in the README depends on any of it.

Names of individual support staff are removed. They were doing their jobs and none of this is about them.

A dated, ordered version of everything below — same caveats, same redactions — is in MODERATION-RECORD-TIMELINE.md.

CurseForge / Overwolf — ticket 375489

2026-06-11. I filed a moderation report against the GSE project. Two findings: the Companion’s detection, account-flagging and server-gated deletion of GRIP-EMS data, and the paid “PATRON” build. I disclosed in the report that I am a direct competitor and asked them to verify from the files rather than weigh my account against the author’s.

2026-06-16. First substantive reply. On the Companion:

“as this is distributed independently via the developer’s own website and is not hosted on CurseForge, it falls outside our enforcement scope. We also found no evidence that the CurseForge-hosted addon requires it, links to it, or triggers its download in any way.”

The remaining claims were forwarded to their moderation and community teams.

2026-06-20. I replied on the one factual point in that answer. The addon they host does link to the Companion and walks users into installing it — three lines in the free build that every user downloads: the in-game link to gse.tools in GSE_GUI/Editor_Tree.lua, the on-ramp text in GSE/Localization/ModL_enUS.lua (“Download the Companion at gse.tools. Once installed, a small bridge addon (GSE Companion Bridge) appears in your addon list, keep it enabled.”), and the built-in “Companion App” settings panel in GSE_Options/Options.lua. I asked for a decision on three items inside their scope: the paid feature-gated build, the undisclosed on-ramp, and the format funnel.

2026-06-22. “We are still looking into this. The ticket will remain open until this is resolved.”

2026-07-16, 11:20. From an Overwolf moderation agent:

“The project GSE (GnomeSequencer-Enhanced) has been taken down for changes. We apologize for the long wait. This was a complicated case that we needed to thoroughly check and confirm.”

2026-07-16, 11:39. After I asked whether to open a new ticket if anything changed:

“You can reopen this ticket if anything related to this case changes. For your information, both the companion app and the pay-gated features have been addressed in the changes request.”

What this does and does not establish

It establishes that CurseForge reviewed the report for five weeks and took the project down for changes, and that both items were in the changes request.

It does not establish what the changes request said. I have never seen it — it went to the developer, not to me. Everything past that one sentence is my inference, and inference is not evidence.

It does not establish that any particular later change was made because of it. GSE shipped Companion 0.4.23, 0.4.24 and 0.4.26 and addon 3.3.25 across 15–17 July, and those builds removed the detection, blocked the write path and removed the capture. The timing fits. Timing is not causation, and I am not claiming it is. The same goes for the CurseForge description now reading “This addon is 100% free” as of 3.3.25 on 17 July. It may be a response to the changes request. It may not be. I do not know, and neither does anyone else outside GSE and CurseForge.

I should also say the obvious thing about my own position here: a platform taking action after my report is not proof that I was right. It is proof that they reviewed it and decided something needed to change. Those are different, and I would rather state it than let the reader assume the stronger one.

Cease and desist — 2026-06-16

I sent this. Nobody has sent me one. It went to the GSE developer by Discord DM on 2026-06-16 as a PDF, after two earlier messages went unanswered.

It asked for two things:

Remove the detection, account-flagging and deletion of GRIP-EMS data from the Companion in the next release.
Confirm in writing that the enforce-gated deletion has not been and will not be activated against GRIP-EMS users.

I set a 14-day deadline. It expired on 2026-06-30 with no reply.

It also said, and I still mean it:

“To be clear, I am not contesting your right to manage your own sequences or your own users. I am asking you to stop having your software detect, flag, and delete data inside another developer’s addon, on users’ computers, without their knowledge or consent.”

Where that stands now. Point 1 has been met, on all three limbs, without any reply to me: 0.4.23 removed the client-side scan and the account flag, 0.4.24 blocked the signed engine from writing to GRIP-EMS.lua, and 0.4.26 removed the arbitrary-file capture. Point 2 has not been met. I never received an answer on any channel.

I am recording that the substance of what I asked for has happened. Whether it happened because I asked is not something I can know.

Subject access request — sent 2026-06-20, never delivered

On 2026-06-20 I sent a data subject access request to GSE, asking for the personal data held about me, specifically the value of any field recording whether I have third-party software installed — the restrictedAccount flag — and any automated decision-making applied to my account.

It bounced. Both published contact addresses rejected it at the mail server:

554 5.7.1 <admin@gse.tools>: Relay access denied 554 5.7.1 <support@gse.tools>: Relay access denied

I pasted the text into a Discord DM instead. No reply.

To be precise, because this matters and it would be easy to imply otherwise: GSE has not ignored a subject access request. GSE never received one. The addresses on their own site do not accept mail. I am not claiming a failure to respond. I am recording that there is no working written channel to the developer, which is the only reason the platform correspondence below exists.

Qik — reported 2026-06-20, replied 2026-06-22

The Companion’s account data is stored on Qik (api.qik.dev), an infrastructure platform. On 2026-06-20 I wrote to them about a customer’s use of their platform: storing a flag against each user recording whether a competitor’s addon is installed, and backing a remotely-gated routine to delete that competitor’s data. I told them I was a competitor and asked them to reach their own conclusion from the files rather than take my characterisation.

I also sent them, and the developer, a security report on 2026-06-21: the admin interface at admin.gse.tools loaded for my ordinary non-admin account, including a site-wide “Enforcement” toggle. I viewed the pages and changed nothing, and reported it privately rather than publishing it.

2026-06-22. A Qik support representative replied. In summary: Qik is an infrastructure provider, its customers build and operate their own applications on it, and Qik does not direct how they are designed. On my access request, Qik generally acts as a service provider to the customer, so they referred the request to the customer and asked them to respond. On the admin interface, that is part of a customer’s application and access to it is configured by the customer; they passed the report on. They said they would review the platform questions internally and, as a matter of policy, would not share any outcome with a third party.

They also asked this, and I am publishing it because it constrains me and the reader should know that:

“we would ask that you not access areas or data outside your own account, or carry out further testing on the application.”

I have not tested the application since.

No response to the referred access request has reached me.

Forum thread closure and account ban — 2026-06-08 to 2026-06-09

My GRIP-EMS thread on wowlazymacros.com was closed and hidden on 2026-06-08. I tried to resolve it privately by DM; the first message went through and later ones did not. I opened an on-site chat to ask about the closure. The chat was closed, and my account was banned.

I emailed the site’s support on 2026-06-09 asking for a reason. I have had no reply.

This is the weakest item here and I am flagging that myself. It is a third-party forum, it is not CurseForge, it is not GSE, and I have no evidence connecting the ban to the GSE dispute. I have one side of it — mine. I include it for completeness of the record, not because it proves anything. A reader would be right to give it no weight. [Update 2026-07-31: this item is now resolved, on the public record and not just my word. See the section immediately below.]

Update, 2026-07-31: the forum ban has been lifted, and this item is now on the public record

Everything above about the wowlazymacros.com thread and ban was my account of one side, and I said a reader should give it no weight. That has changed, and I am recording the change where I recorded the original.

On 2026-07-31 Lutechi, who owns and runs wowlazymacros.com, lifted the ban, put the GRIP-EMS thread back up, and posted publicly on his forum explaining what happened. The post is at https://wowlazymacros.com/t/on-the-grip-ems-ban/63630. You can read it in full there, and that is the point of this update: unlike the rest of this file, this item no longer rests on my word. It rests on his, in public, on his own site.

His explanation is that the ban reached him as a one line report that someone was using the forum to send people to another site, a long standing rule on WLM. He approved it without looking closely, and by his own account did not know who I was, did not know I was an addon developer, and did not know a competing addon was involved. He describes it as his own inattention rather than anything coordinated, calls it “on me”, and says the moderator who handled it is no longer on his team.

I want to be straight about what this does to the record. It closes the item I had already marked as the weakest, and it answers the open question against the more damaging reading. The ban was not part of the GSE dispute. By the account of the person who approved it, it was an unrelated moderation call on his own site that misfired. I had no evidence tying it to GSE when I wrote the original section, and he has now said in public that there was no tie.

Credit to Lutechi for how he handled it. He contacted me directly, apologised, and chose to explain it on his own forum under his own name rather than leave me as the only one telling it. He runs WLM as a hobby, had been away from all of this, and by his account only learned of the situation this week. He looked at it properly once it reached him and corrected it in the open, which is more than the situation required of him.

He also sent me a private message. Its contents stay private, and nothing here depends on it. Everything above is from his public post, at the link.

The technical findings in this repository are a separate track and are unaffected. This was always the forum item, kept apart from the Companion work on purpose. It is now closed.

The Reddit thread and the Discord bans

Some of this happened to my own account, months before any of the technical work in this repository. I paid for access to a GSE community and was banned before I posted a single message. When I tried to ask why, the message would not deliver. The one reply I got was an offer of a refund, with no reason attached. I am banned from the two GSE community Discord servers, which between them list roughly 9,600 and 4,550 members. I hold the screenshots and I am not publishing them, for the reason I publish none anywhere in this repository: a cropped image is not something you can check, and the people in them are entitled not to be posted.

In June a third party opened a thread on r/wow about GSE paywalling features and banning paying users. I did not write it. I replied to it as the GRIP-EMS developer, with my own account of the above. The operator of the GSE United community replied in public and called GRIP-EMS theft. I am recording the exchange because his comment stated, in his own words, that a paid Patreon build of the addon exists with extra “quality-of-life” features, that he had banned people across several servers for belonging to another community, and that gse.tools was built partly in response to GRIP converting GSE sequences. He also gave, in that thread, the first ban reason I ever received — “thief” — two and a half months after the refund offer and the unanswered question.

The same caveat applies as everywhere else here. This is a public forum dispute and I am one side of it. The handles are removed because none of it is about the individuals. The one claim you do not have to take on my word is the paid build, which is a documented feature you can read from the public download and which the README already covers. The rest is my account, and a person reacting to me is not proof I am right about them.

One thing I got wrong, in private, and am not hiding

My first message to the GSE developer, on 2026-06-11, asked why he was “distributing malware that edits my files.”

That was the wrong word. Nothing in this repository has ever called it malware, because the evidence does not support that characterisation and I was careful about it in every public document. I was not careful in a DM at the point I had just found the code. I am recording it here rather than leaving it to be discovered, because a record that only contains the parts that suit me is not a record.

What is not here

I hold material I am not publishing. The Qik correspondence contains my own account identifiers. The security report concerns a flaw I reported privately and have no interest in helping anyone exploit. Individual support staff are unnamed throughout.

There is more, and I would rather name the omission than hide it. I have prepared an Australian privacy complaint to the Office of the Australian Information Commissioner about the Companion’s data handling. It is not lodged — the earliest clean lodge date is 2026-07-20 — and it stays on a private regulator track in any case, because it carries my personal details, a subject access request, and forensic evidence tied to my own account.

Behind the correspondence above sits an evidence pack: the screenshots, the DM and email exports, the CurseForge report bundle, and the admin-panel security report. It stays unpublished for the reasons already given here. No screenshots, the security flaw was reported privately, and personal data runs through all of it. None of the README depends on any of this.