Portfolio
A selection of documents, policies, and community materials I've written across my roles.
Madium
9 of 9Terms of Service & Software Agreement
Drafted the full ToS covering permitted use, IP ownership, reselling rules, acceptable-use conduct, update-chain behaviour disclosures, and the antivirus/defamation policy.
End-User License Agreement (EULA)
Wrote the license grant, single-device/HWID allocation terms, automated-update consent language, and reverse-engineering restrictions.
Software License, Copyright & Legal Notice
Authored the proprietary IP notice, commercialisation/reselling rules, service-availability disclaimer, and the defamation & false-claims policy.
Privacy Policy & Data Collection Notice
Documented exactly what data is and isn't collected (HWID hashing, server logs, diagnostics) and how it's stored, retained, and used.
DMCA & Copyright Takedown Policy
Set out the formal notice-and-takedown process for IP claims, plus enforcement terms for unauthorized re-uploads and cracked distribution.
Official Reseller Agreement & Guidelines
Defined authorization requirements, vendor responsibilities, and grounds for reseller termination for parties distributing license keys.
Security & Vulnerability Disclosure Policy
Wrote the responsible-disclosure process, scope definitions, reporting protocol, and safe-harbor terms for security researchers.
Staff Moderation Guidelines
Internal handbook standardising staff conduct: warning/escalation mechanics, role-based leniency, a full violation-to-action enforcement matrix, and evidence-logging requirements.
Registrar Abuse & Security Escalation Report
Filed a registrar abuse complaint against an impersonating domain that copied Madium's branding and UI and funnelled users through a deceptive redirect chain toward an unaffiliated Discord server. Built out the evidence package — screenshots, a continuous unedited screen recording, and a clear requested-action list — while carefully distinguishing confirmed facts from suspected ones.
Bloxflip
2 of 2Subreddit FAQ
Wrote the community FAQ covering support routing, rakeback, provable fairness, the affiliate program, community events, and VIP tiers to cut down repeat questions.
Subreddit Welcome & Verification Post
Authored the pinned welcome post: how to verify the official subreddit against impersonators, community quick links, age requirement, and account-safety reminders.
RoStake
2 of 2Structured Escalation Reports
Built a consistent escalation format for issues that need management review — user details, chat link, a clear description of the problem, action already taken, and a specific requested action — instead of ad hoc messages that are easy to lose track of.
Support Macros for the Team
Wrote a set of canned-response macros for common support scenarios so the wider team can reply faster and more consistently instead of drafting the same explanations from scratch each time.
Case studies
3 deep divesMadium
Standardising staff moderation from scratch
Situation
Disciplinary actions were being handled case-by-case by individual staff, with no shared reference for what action fit what violation — inconsistent, and hard to review after the fact.
Approach
Wrote a full staff handbook: a violation-to-action enforcement matrix covering everything from spam to zero-tolerance categories, role-based leniency rules for trusted community roles, and a mandatory evidence-logging requirement tied to the bot's automated-notification system.
Outcome
Staff now action reports against a single documented reference instead of individual judgement calls, and every disciplinary action has a required evidence trail to review.
Bloxflip
Cutting repeat support questions with a self-serve FAQ
Situation
The same handful of questions — where to get support, how rakeback works, whether the games are fair — kept surfacing on the subreddit, taking up moderator time that could go to actual issues.
Approach
Wrote a structured FAQ covering support routing, rakeback mechanics, the provably-fair system, the affiliate program, community events, and VIP incentives, then pinned it as the first stop before posting.
Outcome
Gives moderators a direct link to point to instead of re-answering the same questions, and sets clear expectations up front about what subreddit mods can and can't help with.
RoStake
Turning a stuck withdrawal into a trackable escalation
Situation
A user was missing $200 from a card withdrawal after nearly two months of waiting, with no clear path to get it in front of management — the kind of issue that's easy for a plain chat message to get lost.
Approach
Documented the case in a structured format: user and chat-link reference, exact payment method and missing amount, what had already been explained to the user, and a specific, actionable list of what management needed to do next (verify the transaction history, manually process the withdrawal, follow up with a status update).
Outcome
Gave management a self-contained report they could act on without back-and-forth, and gave the user a documented case instead of an open-ended wait — the format has since become the standard way the team escalates payment issues.