// Legal
Our policies for all current and future VEXNILX™ products. Last updated: April 2026.
These Terms govern your use of VEXNILX™ services, including our website, Discord community, tutorials, and all current and future products. By accessing or using anything we provide, you agree to be bound by what's written below.
By accessing VEXNILX™ services in any form — visiting our website, joining our Discord server, watching our tutorials, or subscribing to a paid plan — you agree to these Terms in full. If you do not agree, you must stop using our services immediately.
You must be at least 13 years of age to use VEXNILX™ services. If you are between 13 and 18, you must have permission from a parent or legal guardian. Users below 13 are not permitted, in line with our Safety Policy and applicable law.
Some features require an account, typically linked to your Discord profile. You agree to provide accurate information at registration and to keep it current. You are responsible for everything that happens under your account.
Keep your login credentials private. Do not share your account or sell access to it. If you suspect unauthorized access, contact us immediately in the main Discord Server. We are not liable for losses arising from credentials you failed to protect.
You may use our services for personal learning, professional development, and the lawful purposes our plans support. Business and team usage requires a Business or Vexersatie plan as described on our Pricing page.
You may not redistribute paid tutorials, scrape our content for commercial use, attempt to bypass paywalls or rate limits, harass other members, or use our services to break the law. We may suspend or terminate accounts that violate this section.
We offer multiple plans (Free, basic, standard, pro, VEXNILX™ Opus, Business, Vexersatie). Plan features and prices are listed on the Pricing page and may change over time with notice.
Paid plans are billed in advance, in the currency shown at checkout, on a recurring monthly basis unless otherwise stated. You authorize us (and our payment processor) to charge your selected method until you cancel.
Monthly plans renew automatically at the end of each billing cycle until cancelled. You can cancel at any time through Discord and your access will continue until the end of the paid period.
You may cancel a subscription at any time. Refunds follow the separate Refund Policy on this page — in short, refunds are not generally granted, but exceptions within 30 days may be considered for special cases.
The Free tier provides Discord access, public tutorials, and community channels. It does not include premium courses, priority requests, mentoring, or business features. We may change Free tier scope at any time.
Use of our Discord servers is also governed by the rules pinned within each server and Discord's own Terms of Service. Violations of either may result in removal from the server independent of any subscription you hold.
All VEXNILX tutorials, courses, written guides, code samples, graphics, and audio remain our intellectual property or that of our licensors. Your subscription grants you a limited, non-transferable license to view and use them for personal learning.
If you post messages, comments, tutorials (Business plan), code, or other content on our platforms, you remain the owner of that content but you grant us a worldwide, royalty-free license to host, display, and distribute it within our services.
The license described above is non-exclusive and lasts for as long as your content is on our platforms, plus a reasonable period afterward to handle backups, moderation, and legal obligations.
VEXNILX™ and the VEXNILX logo are our trademarks. Other marks belong to their respective owners. You may not use our marks except as described in our trademark guidelines or with written permission.
Partners with an active Partnership Agreement may use our marks in agreed contexts. All other use — implying endorsement, modifying the logo, using our marks in misleading contexts — is prohibited.
We integrate with services like Discord, Stripe, and Cloudflare. Your use of those services is subject to their own terms. We are not responsible for outages, data handling, or actions taken by third parties.
These Terms apply to any future products we release under the VEXNILX name unless we publish separate terms for them. You will be notified of any new product-specific terms before they affect you.
Some features may be released in beta. They may be unstable, may change without notice, and may be discontinued. We do not provide service-level guarantees for beta features.
We may add, modify, or discontinue any service or feature at any time. For paid features, we will provide reasonable advance notice and, where required, a pro-rata credit or refund.
We aim for high uptime but do not guarantee it for non-Vexersatie plans. Outages, maintenance, or third-party failures may cause temporary unavailability.
We may schedule maintenance with notice via our Discord server. Emergency maintenance may occur without notice when needed to protect users or systems.
We may change plan prices in the future. Existing subscribers will be notified at least 14 days before a price change takes effect on their next billing cycle. You may cancel before the change applies.
From time to time we run promotions through our Discord server. Promotional pricing applies only as described and may have eligibility requirements, time limits, and stacking restrictions.
Our referral program lets eligible Discord members earn credits when friends sign up and subscribe. Eligibility, reward amounts, and rules are described on the home page Refer popup and may change.
The Business plan grants priority requests, job board access, your own tutorial publishing, higher rate limits, and team-member additions. Use of those features must comply with the rest of these Terms.
Vexersatie organizations are governed by the separate Vexersatie Terms on this page in addition to these Terms. Where conflicting, the Vexersatie Order Form controls.
Business plan customers can post jobs and search candidates on our job board. Posts must be honest, lawful, and free of discriminatory criteria. We may remove posts that violate this section.
We provide the platform; we are not a party to any employment relationship formed through it. You and the candidate are responsible for your own contracts, taxes, and compliance.
Services are provided "as is" and "as available." We disclaim implied warranties of merchantability, fitness for a particular purpose, and non-infringement, to the maximum extent permitted by law.
To the extent permitted by law, our aggregate liability for any claim related to the services is limited to the greater of (a) the amount you paid us in the 12 months before the claim, or (b) USD $100.
You agree to indemnify and hold harmless VEXNILX™ from any claim arising out of your violation of these Terms, your misuse of our services, or your infringement of someone else's rights.
Neither party is liable for delays or failures caused by events beyond their reasonable control, including natural disasters, war, civil unrest, internet outages, or government action.
If you believe content on our services infringes your copyright, send a DMCA notice with the required information through our Discord server. We will investigate and act in line with applicable law.
If you encounter content or behavior that violates these Terms, report it in the appropriate Discord channel or by direct message to a moderator. We treat reports confidentially where possible.
We may suspend an account temporarily while we investigate suspected violations. During suspension, paid features may be unavailable but your subscription clock may continue, depending on the situation.
We may terminate accounts for repeated or serious violations. Upon termination, your right to use the services ends immediately. Surviving clauses (IP, liability, indemnity, dispute resolution) remain in force.
After termination, we retain account data for a limited period to handle disputes, comply with legal obligations, and complete backups. After that period, data is deleted in line with our Privacy Policy.
You may not use our services in violation of export controls or sanctions of your jurisdiction or ours. You confirm you are not on a restricted-parties list.
These Terms are governed by the laws applicable at the place of business of VEXNILX™, without regard to conflict-of-law principles, except where mandatory consumer-protection law of your residence applies.
Before filing any formal proceeding, you agree to attempt resolution through our Discord support channels for at least 30 days. Most disputes can be resolved that way.
If informal resolution fails, disputes will be resolved by binding individual arbitration where permitted by law. Each party bears its own costs unless the rules state otherwise.
To the maximum extent permitted by law, claims may only be brought in your individual capacity, not as part of a class action or representative proceeding.
If any provision of these Terms is held invalid or unenforceable, the rest remains in effect and the invalid provision will be modified only to the minimum extent needed.
These Terms, together with the other policies on this page, constitute the entire agreement between you and VEXNILX™ regarding the services and supersede prior agreements on the same subject.
You may not assign your rights or obligations under these Terms without our consent. We may assign ours in connection with a merger, reorganization, or sale of assets.
Our failure to enforce any right or provision of these Terms is not a waiver of that right. A waiver is only effective when made in writing by an authorized person.
Notices to you may be given via our Discord server or by an email address you have provided. Notices to us must be sent through the channels listed in the Contact section below.
We may update these Terms over time. We will indicate the date of the last update at the top of the Legal page and, for material changes, post a notice in our Discord server.
Questions about these Terms can be raised in the support channel of our main Discord Server (https://discord.gg/dNdWrru6mf). We respond as quickly as we can.
This Privacy Policy describes how VEXNILX™ collects, uses, shares, and protects your personal information across our website, Discord community, and all current and future products. We aim to collect as little as possible and to be straightforward about what we do with it.
We collect three broad categories of information: (1) information you give us directly, (2) information collected automatically when you use our services, and (3) information from third parties such as Discord.
Personal information may include your display name, Discord ID, profile picture, email address (if voluntarily provided), and country/region for tax purposes if you subscribe.
If you sign up for a paid plan, we associate your Discord account with the plan tier, billing status, and entitlements. We do not store extended profile fields beyond what is necessary.
Payments are processed by Stripe (or another regulated processor). We do not store your full card number on our servers — we only receive a token, the last four digits, the card brand, and expiration.
When you authenticate via Discord OAuth, we receive your Discord ID, username, avatar, and email if you grant the email scope. We use these only for account linking and entitlement enforcement.
We collect aggregated, mostly non-identifying usage data such as which pages are visited, click counts, and approximate load times. This helps us understand what is useful and what is broken.
When you visit the website, we receive standard request data: IP address (often truncated), user agent, referrer, and timestamps. We use this for security, anti-abuse, and analytics.
We use a small set of cookies and similar technologies as described in the Cookie Policy section. We do not use third-party advertising cookies on our website.
Aside from Discord (for OAuth) and our payment processor (for billing status), we do not buy or import personal data from third-party brokers.
We use information to provide, secure, and improve services; communicate important updates; process payments; comply with law; and prevent fraud or abuse.
Your information is used to deliver tutorial access, enforce subscription entitlements, route Discord roles, and ensure that paid features are available only to paid subscribers.
We may send transactional messages (account, billing, security) through Discord or email if provided. Marketing messages, where allowed, can be opted out at any time.
Limited promotional content is shared in our Discord server. We do not send unsolicited marketing emails. If you opt into marketing email, you can unsubscribe with one click.
We may show different content based on your subscription tier, region, or language. Personalization does not involve building behavioral advertising profiles.
Aggregated analytics help us understand which tutorials are most useful and where users get stuck. Whenever possible, this data is stripped of identifiers before analysis.
We use logs and behavioral signals to detect account takeovers, payment fraud, scraping, and abuse. We may block IPs, regions, or accounts that show signs of abuse.
We may use or disclose your information when reasonably necessary to comply with law, respond to lawful requests, or enforce our Terms.
We do not sell personal information. We share it only with service providers, with you (your own data), with authorities under lawful process, and during corporate events as described below.
We share data with vetted vendors who help us run the service — for example, Stripe (payments), Discord (community), Cloudflare (CDN, security). They receive only what they need.
Your interactions on Discord are governed by Discord's own privacy practices. We share with Discord only what is necessary to assign roles, validate subscriptions, and respond to abuse.
Stripe (or our equivalent) processes your payment under their own terms and privacy notice. We share with them only what is needed to complete and reconcile transactions.
If we ever have corporate affiliates, your information may be shared with them under privacy practices at least as protective as this policy. We will update this section if that happens.
If we go through a merger, acquisition, restructuring, or asset sale, user data may be transferred as part of the deal. We will notify users where required by law.
We respond to valid legal requests such as subpoenas and court orders. We push back on overbroad requests and notify users when we are legally permitted to do so.
We may publish aggregated statistics that do not identify any individual — for example, total members, average tutorial completion times, and similar metrics.
Depending on where you live, you may have rights to access, correct, delete, port, or restrict the use of your personal information. The sections below describe these rights in more detail.
You may request a copy of the personal information we hold about you. We will provide it within the time required by applicable law, normally within 30 days.
If your information is inaccurate, you may ask us to correct it. We will update it without undue delay once we verify the request.
You may ask us to delete your information. We will do so unless we have a legal obligation, an active dispute, or a security reason to retain it for a limited period.
You may request a copy of your account information in a machine-readable format that you can transfer to another service.
You may object to certain uses of your information, such as direct marketing or profiling, where applicable law gives you that right.
In some situations, you may ask us to limit how we use your data while a question or correction is being resolved.
Where processing is based on consent, you may withdraw it at any time. Withdrawal does not affect the lawfulness of processing that occurred before.
Our services are not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe we have, contact us and we will delete it.
We retain account data while your account is active and for a limited time afterward to comply with law and handle disputes. Logs are retained for shorter periods determined by their purpose.
Data may be stored on infrastructure operated by Cloudflare and our database providers, which may include facilities in multiple regions.
If your data is transferred outside your country, we use safeguards permitted by applicable law (such as Standard Contractual Clauses) to protect it.
We use encryption in transit, encryption at rest for sensitive data, role-based access control, and least-privilege principles to protect your information.
If a breach affects your personal data and is likely to result in significant harm, we will notify you within the timelines required by applicable law and describe the steps we are taking.
Our services may link to third-party sites or apps. Those services have their own privacy practices that we do not control.
If you are a California resident, you have specific rights under the CCPA, including the right to know, delete, and opt out of "sale" of personal information. We do not sell personal information.
If you are in the European Economic Area or UK, you have rights under the GDPR / UK GDPR including access, rectification, erasure, restriction, portability, and objection.
If you are in Brazil, you have rights under the LGPD that mirror the GDPR. You can exercise them through our Discord support channel.
If your jurisdiction grants additional privacy rights, you can exercise them by contacting us. We comply with applicable local law.
We do not currently respond to browser "Do Not Track" signals because there is no industry consensus on what they mean. Our cookie practices already minimize tracking.
You can opt out of marketing communications at any time by following the unsubscribe link in any marketing email or by leaving the relevant Discord opt-in role.
Cookie choices can be managed through your browser settings as described in the Cookie Policy section.
This Privacy Policy applies to any future products we release under VEXNILX unless we publish separate notices for them.
We may update this Privacy Policy. We will indicate the last-updated date and announce material changes in our Discord server.
Privacy questions, rights requests, and concerns can be sent through our main Discord Server in the support channel.
This Cookie Policy explains how VEXNILX™ uses cookies and similar technologies on our websites and platforms. It covers what cookies are, what we use them for, and the choices you have.
Cookies are small text files a website stores in your browser. They let the site remember things between visits — such as which language you prefer, whether you are signed in, or that you have already dismissed a banner.
We use cookies for the basics: keeping you signed in, remembering your preferences, and understanding (in aggregate) how the site is used. We do not use cookies for cross-site advertising.
Our cookies fall into a few categories: strictly necessary, functionality, and analytics. Each category is described in its own section below.
Strictly necessary cookies are required for the site to function — for example, the cookie that maintains your session after you sign in via Discord. These cannot be disabled within our site.
Functionality cookies remember choices you have made, such as theme, language, or whether you have closed a one-time announcement. They make the experience smoother but are not essential.
Analytics cookies help us understand which pages and tutorials are useful in aggregate. They do not identify you personally.
Performance cookies measure things like page load time and error rates. They help us spot regressions before users complain about them.
We do not currently use targeting or advertising cookies on our website.
We do not place third-party advertising cookies. If that ever changes, we will update this section and provide a fresh consent banner.
Session cookies expire when you close the browser. They typically hold your active sign-in state.
Persistent cookies remain after you close the browser, up to a defined expiration date. They typically hold longer-lived preferences.
First-party cookies are set directly by our domain. Most of our cookies are first-party.
Third-party cookies are set by other domains, typically loaded through embeds or scripts. We currently use a small number of these for Discord widgets and analytics.
Local storage is browser storage similar to cookies but stored differently. We use it sparingly for non-sensitive preferences such as which legal tab you last opened.
Session storage holds data only while a tab is open. We use it for transient UI state like collapsed sections.
We do not embed third-party tracking pixels in our marketing emails or pages.
We do not use browser fingerprinting techniques to identify users.
Embedded content from Discord (live widget) may set cookies for that service. Those cookies are governed by Discord's own policies.
The Discord live widget on our Community page polls Discord's API. It may set cookies for the discord.com domain. We do not control those cookies.
Stripe sets cookies during checkout for fraud prevention and session continuity, governed by Stripe's privacy and cookie notices.
Where we use analytics, we choose privacy-respecting providers and configure IP truncation and limited retention where the option exists.
We do not share cookie data with marketing partners. We also do not currently run paid retargeting.
Cookie lifespans vary from a few minutes (session cookies) to up to a year (preferences). The browser developer tools show current cookies and expirations.
If we add new categories of cookies, we will update this section and re-prompt you for consent where required by law.
Modern browsers let you block all cookies, block third-party cookies, or clear cookies for specific sites. The next sections explain how in the most popular browsers.
In Chrome: Settings → Privacy and security → Cookies and other site data. You can choose "Block all cookies" or "Block third-party cookies."
In Firefox: Settings → Privacy & Security → Enhanced Tracking Protection. "Strict" mode blocks more trackers and cross-site cookies.
In Safari (macOS / iOS): Settings → Privacy. You can prevent cross-site tracking and block all cookies.
In Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data.
Mobile browsers usually have cookie controls under Settings → Privacy. The exact path differs by app and version.
If you disable strictly necessary cookies, you will not be able to sign in or use authenticated features. Other categories degrade gracefully.
You can opt out of analytics by enabling "Do Not Track" or by blocking the analytics domain in your browser. We honor analytics opt-outs even if not legally required.
Since we do not place ads on our site, there is nothing to opt out of in this respect. If we ever introduce ads, we will provide an opt-out and a fresh banner.
Industry opt-out tools such as the NAI and DAA opt-out pages list participating advertisers. We are not part of those programs because we do not run cross-site ads.
Where required by law (mainly EU/UK and similar regions), we show a cookie consent banner that lets you accept or reject non-essential cookies.
Where granular consent is required, you can choose categories individually. Strictly necessary cookies are always on because the site cannot function without them.
You can withdraw cookie consent at any time by clearing cookies in your browser and revisiting our site, which will re-prompt the banner.
Some cookies, alone or in combination, may qualify as personal data under privacy laws. The Privacy Policy describes how we handle that data.
Under the GDPR, non-essential cookies require informed consent. Our banner is designed to meet this requirement for users in the EEA and UK.
Under the CCPA, our cookie use does not constitute a "sale" of personal information.
Our cookie banner and choices are designed to comply with the EU ePrivacy Directive in jurisdictions where it applies.
Future VEXNILX products will follow the same cookie principles unless we publish a product-specific cookie notice.
If we ever release a mobile app, that app may use platform identifiers governed by Apple or Google. We will publish a separate notice when that happens.
Server logs (separate from cookies) record IP addresses, request paths, and timestamps for security and debugging. They are kept for a short period and then rotated out.
We do not combine cookie data with offline data brokers or attempt to build advertising profiles based on cookie behavior.
Because our services are not directed to users under 13, we do not knowingly set cookies on devices used by them.
We will update this section if our cookie practices change in any meaningful way and announce the change in our Discord server.
The effective date of this Cookie Policy is the "Last updated" date at the top of the Legal page.
Cookie questions can be sent through our main Discord Server, in the privacy or support channel.
For background reading on cookies, see your browser's documentation or general resources like aboutcookies.org. We do not vouch for those external sites.
This Safety Policy outlines VEXNILX™'s commitments to creating a safe, respectful environment for all members across our website, Discord servers, and any future products.
We want VEXNILX™ to be a place where people can ask questions, share progress, and learn without fear of harassment, scams, or hostile behavior. The standards in this section apply across all our spaces.
Be respectful, assume good faith, give credit where it is due, and keep conversations on-topic in topical channels. The full Discord rules are pinned in each server's #rules channel.
Asking honest questions, providing constructive feedback, sharing your work, and helping newer members are exactly the behaviors we want.
Some behaviors lead to immediate removal: hate speech, doxxing, sexualization of minors, credible threats of violence, and attempts to defraud other members.
Slurs, dehumanizing language, and discriminatory content based on race, ethnicity, religion, gender, sexual orientation, disability, or similar characteristics are not allowed.
Targeted harassment, pile-ons, sustained negative attention, and unwelcome contact after being asked to stop are all forms of harassment we act on.
Credible threats of violence, encouragement of self-harm directed at others, and content glorifying violent extremism are prohibited and may be reported to authorities.
Our community is not an adult forum. Sexual content is not appropriate in any of our channels. Sexually suggestive direct messages to other members are prohibited and grounds for removal.
We treat the safety of minors as a top priority. Any content that sexualizes a minor, attempts to groom one, or shares CSAM in any form is reported to the relevant authorities and the account is permanently removed.
Glorification of self-harm or suicide is not allowed. We provide resource links but cannot serve as a crisis service. People in crisis should contact local emergency services or a crisis hotline.
Deliberately false information about safety-critical topics (medical, legal, financial scams) is removed. Mistakes happen — repeatedly pushing falsehoods after being corrected does not.
Mass DMs, paid-promotion spam, link bombs, and phishing attempts are removed and lead to bans. Phishing attempts are reported to Discord's Trust & Safety team.
Impersonating staff, partners, or other members — including via similar usernames or avatars — is prohibited and leads to immediate action.
Sharing someone else's private information without consent (real name, address, employer, photos) is doxxing. It is a fast-track to a permanent ban.
Don't repost paid-tier content publicly, don't share pirated material, and credit original sources when you reference them. We respond to legitimate IP claims.
Reports can be made by tagging a moderator in the report channel, by direct message to a moderator, or by using Discord's built-in report feature for severe content.
Please include the message link or screenshot, the time, and a brief description of why you think the content violates the rules. The more context, the faster we can act.
Useful items: usernames or IDs, message links, screenshots, channel name, approximate timestamp, and any prior warnings you are aware of.
We treat reports confidentially where possible. Mods may need to act on what was reported, which can sometimes reveal that something was reported, but we do not reveal who reported.
Mods review the report, check the context (often beyond just the reported message), and decide on action. Severe cases get fast-tracked; nuanced cases may take longer to resolve fairly.
Possible actions include warnings, message removal, role removal, temporary mute, temporary ban, and permanent ban, depending on severity and history.
First or minor offences usually get a warning explaining what crossed the line. We try to make warnings educational rather than purely punitive.
For repeat or moderately severe violations, we may issue a timed mute or kick. The user can rejoin or speak again after the period elapses.
Permanent bans are reserved for the most severe behaviors (CSAM, credible threats, sustained harassment after warnings) or for users who repeatedly violate after multiple chances.
Banned users may appeal once via the appeal form linked in the ban message. Appeals are reviewed by a different mod where possible. Frivolous appeals do not unlock further appeals.
Our Discord servers have additional rules pinned in #rules. Following the platform-wide Discord Terms of Service is also required.
Voice channels are for the channel topic. Earrape, soundboard spam, deliberate interruption, and recording without consent are not allowed.
Unsolicited promotional DMs, sustained DMs after "please stop," and using DMs to circumvent moderation are all reportable behaviors.
Server boosters get cosmetic perks. Boosting does not exempt anyone from the rules and does not entitle anyone to override moderators.
Mods, partners, and other roleholders are bound by all the same rules as everyone else, plus higher expectations because of their visible role.
Comments on tutorials should be on-topic, constructive, and free of self-promotion. Asking questions is welcome; advertising is not.
During live events, additional rules may apply (longer slow-mode, stricter language filter). Disrupting events leads to immediate event-time mutes.
Moderators have authority to enforce the rules. Their decisions can be appealed, but during an active incident their direction must be followed.
Moderators are held to a higher standard: no favouritism, no using mod tools in personal disputes, and no sharing of mod-channel content. Mod misconduct is investigated by senior staff.
For severe content (CSAM, credible threats), we cooperate with Discord's Trust & Safety team and provide what they request through proper channels.
We cooperate with valid legal requests from law enforcement and respond as required by applicable law. We push back on overbroad requests and notify users where legally permitted.
If you or someone else is in immediate danger, contact local emergency services first. Our staff cannot dispatch emergency help.
We may share general mental-health resource links in the appropriate channel. We are not a crisis service and cannot replace professional support.
Crisis hotlines vary by country. Channels like #resources will list a few well-known hotlines, but please verify details for your country before relying on them.
It is fine to step away from chats and tutorials. The Discord will still be there tomorrow. Burnout helps no one.
Listening, validating, and pointing someone toward proper resources is often the best a community member can offer in a hard moment. We do not expect anyone to be a therapist.
We may run occasional educational content on online safety, OPSEC for creators, and similar topics. Participation is voluntary.
Mod team and senior staff review the Safety Policy at least once a year to address new platform risks and community feedback.
Where we publish stats on moderation actions, we will do so in aggregate, without identifying individuals beyond what is necessary.
Future VEXNILX products will follow the same Safety Policy unless they publish stricter or product-specific rules.
Beta testers see early features. Sharing leaks, screenshots from private beta channels, or breaking the NDA in the beta agreement leads to removal from the beta program.
When tagging or referencing other members publicly, do so respectfully. Public callouts of named individuals for non-rule-breaking behavior are discouraged.
We do not require government ID for normal use. Limited identity checks may apply to Business / Vexersatie customers and Partner applicants.
Discord and our website use anti-bot measures (verification, rate limits). Trying to bypass these is itself a rule violation.
We will update this section when needed and announce material changes in our Discord server.
Sensitive safety issues can be raised by DMing any moderator marked as a safety contact, or by using the safety report form pinned in the appropriate channel.
This Security Policy details how VEXNILX™ protects user data, accounts, and infrastructure. Security is a continuous practice — the safeguards described here are part of an evolving program.
Security is layered: prevention, detection, and response. We aim to make attacks hard, noisy, and recoverable. No one is perfect — we plan for failure too.
All public traffic to our domains uses TLS 1.2+. We auto-redirect HTTP requests to HTTPS and enable HSTS so browsers refuse downgraded connections.
Sensitive data — credentials, tokens, billing identifiers — is encrypted at rest using industry-standard algorithms managed by our cloud providers.
Most users sign in with Discord OAuth, which means we do not store passwords for them. Where passwords are used (e.g. internal admin), we require length minimums and rotation on suspicion of compromise.
We strongly recommend MFA on Discord. For internal admin accounts, MFA is mandatory using either TOTP or hardware keys.
If you lose access, the recovery flow goes through your Discord account. We do not have a backdoor that can recover an account if Discord access is lost.
Authenticated sessions have a limited lifetime. Suspicious sessions can be invalidated server-side, forcing re-authentication.
OAuth tokens are stored encrypted, scoped to the minimum permissions we need, and rotated when scope changes.
We use Discord's standard OAuth 2.0 flow with PKCE. We request only the scopes we need and revoke tokens when no longer needed.
We rely on Stripe (or our equivalent) which is PCI-DSS Level 1. Card numbers do not touch our servers — we only see tokens and metadata like the last four digits.
Stripe handles fraud detection, 3-D Secure, and chargeback flows. We follow Stripe's integration security guidance.
Whenever you save a payment method for renewals, the actual card data is tokenized by Stripe. We store only the token reference, never the PAN or CVC.
Our origin is fronted by Cloudflare. Public traffic is filtered for known bad patterns before reaching the application.
Cloudflare provides DDoS protection, a managed WAF, bot detection, and rate-limiting at the edge. We tune the policies regularly.
Volumetric and application-layer DDoS attacks are mitigated by Cloudflare at the edge. We monitor for residual impact at the origin.
The WAF blocks common patterns like SQLi, XSS, RCE, and known CVE exploitation attempts. Rules are updated as new threats emerge.
Anomalous behavior (failed logins, sudden traffic spikes, unusual API patterns) triggers alerts to our security on-call.
We track vulnerabilities in our dependencies and infrastructure with automated scanners and a defined process for triage and remediation.
Critical patches are applied within days, high-severity within a week, and lower severities according to risk. Cloud-managed services are patched by their providers.
We perform internal security reviews regularly and may engage third-party testers for major releases.
We run a responsible-disclosure program — report security issues through our security contact in Discord. We do not pay cash bounties at our current scale, but we publicly credit good-faith finders who want it.
Please don't publish vulnerabilities before we have had a reasonable window to fix them. Don't pivot beyond proof-of-concept, don't access other users' data, and don't sell the vulnerability.
We do periodic internal audits of access controls, secret usage, and incident-response readiness. Results inform a remediation plan.
Where vendors publish SOC 2 / ISO 27001 reports, we review them as part of vendor selection and renewal.
We do not currently hold a SOC 2 attestation. Vexersatie customers can request our security questionnaire response and security controls overview.
Our infrastructure runs on cloud providers whose data centers have physical security, biometric access, and 24/7 monitoring. We do not run our own racks.
Our staff laptops use full-disk encryption, screen locks, and remote-wipe capability. Loss or theft must be reported within 24 hours.
Where required for the role and permitted by law, we conduct background checks before granting production access. Trust is matched to scope.
Access is granted by role, not by individual. Roles map to specific responsibilities and are reviewed at least quarterly.
By default, access is denied. Permissions are added only as needed and removed promptly when no longer needed (e.g. role change, departure).
Production actions on user data are logged to an immutable store. Logs are reviewed during investigations and on a sampled basis as part of audits.
Security logs are retained for the period needed to investigate incidents and to meet legal requirements, then rotated out.
Critical data is backed up on a regular schedule. Backups are encrypted and tested by periodic restore drills.
We have a documented DR plan covering region failover, data restore, and communication. We test it periodically and refine after each test.
On detection of an incident, we triage, contain, eradicate, and recover, then write a post-incident review. Severe incidents trigger user notification per legal requirements.
Where required by law (GDPR: 72 hours to authorities, etc.), we notify within those timelines. We notify affected users when their data is implicated and the law requires.
User notifications include what happened, what data was affected, what we are doing about it, and what users can do (e.g. change passwords, watch for phishing).
Severe incidents may include forensic analysis to determine root cause and extent. Findings drive remediation and policy updates.
Staff complete onboarding security training and periodic refreshers. Ad-hoc training follows incidents or new threats.
We push staff toward phishing-resistant MFA (hardware keys, platform authenticators) over SMS or TOTP where possible.
Hardware keys are issued to staff with production access and to senior staff in particular. Keys are revoked on departure.
Our APIs use TLS, authenticated tokens scoped to specific actions, and per-token rate limits. Misuse triggers automatic throttling and alerts.
Rate limits protect against scraping, credential stuffing, and abuse. Limits scale with subscription tier; abusive patterns trigger temporary blocks.
Bot defense combines Cloudflare bot management, behavioral signals, and CAPTCHA challenges where appropriate. We avoid challenges for normal users wherever possible.
All production changes go through code review. Our CI pipeline runs static analysis and dependency scans on every change.
Open-source dependencies are continuously scanned for known vulnerabilities. Affected packages are upgraded based on severity and exploitability.
We follow security advisories for the major open-source libraries we use and contribute fixes upstream where appropriate.
Future VEXNILX products inherit these baseline standards. Higher-risk products may add stricter controls (e.g. customer-managed encryption keys, dedicated tenancy).
Send vulnerability reports to the security contact described in our Discord. Please use proof-of-concept rather than full exploitation, and avoid accessing other users' data.
Security questions and vulnerability reports go through the security channel of our main Discord Server. Sensitive reports can be DMed to a designated security contact.
Refunds are generally not accepted at VEXNILX™. We may grant a refund in special circumstances within 30 days of purchase, provided you submit your request in our main Discord Server with a clear written reason. This page describes when refunds are possible, how to request one, and what we cannot refund.
Refunds are generally not accepted.
Special-case refunds may be granted within 30 days of purchase. To request one, open a ticket in our main Discord Server and provide a clear written reason for the request.
Requests without a stated reason will not be reviewed.
Refunds are not part of our standard offering. Our plans are month-to-month, easy to cancel, and the Free tier exists so you can evaluate the value before paying. Treat the first month as your trial.
We do not refund a paid month simply because you no longer want it, forgot to cancel, didn't use the content, or changed your mind after the billing date. Cancel any time to stop future charges, but the current cycle is non-refundable in the normal case.
Special-case refunds may be granted only for charges made in the last 30 days. Anything older than 30 days is outside the window and will not be reviewed regardless of the reason given.
Examples of special cases we may review: duplicate charges by us, a charge despite a successful cancellation, an unauthorized charge you reported promptly, or a serious extended outage that prevented use. Cases outside these patterns are unlikely to be approved.
Open a support ticket in our main Discord Server (https://discord.gg/dNdWrru6mf). Refund requests sent through any other channel — email, X/Twitter DMs, comments on tutorials — will not be processed.
Use the support or refund channel pinned in the server. A staff member will pick up the ticket. Please do not ping multiple staff or open multiple tickets for the same request — it slows things down.
Every request must include a clear, written reason. "I want a refund" is not enough. Tell us what happened, when, and why you believe a refund is warranted. Without a reason, the request is closed.
Include: your Discord ID, the plan you're on, the date of the charge, the last four digits of the card or the payment method, the reason, and any screenshots or transaction IDs that help.
We verify the request against our billing records. If we cannot confirm the charge, we may ask for additional details. Refunds for purchases we cannot verify are not approved.
Most reviews take up to 7 business days. Complex cases or cases involving the payment processor can take longer. We will keep you updated in your ticket.
We approve requests that fit one of the special cases above and where the verification is clean. We deny requests outside the 30-day window, requests without a stated reason, requests on Free-tier accounts (no charge), or repeat-buyer-remorse patterns.
There is no charge on the Free tier, so there is nothing to refund. If you signed up for Free and were never charged, you don't need to do anything.
basic is a low-cost monthly plan ($10.00). It is subject to the general refund stance above. Cancel before the next renewal to avoid further charges.
standard ($25.00/mon) follows the general refund stance. The 30-day window applies; the request must include a reason and meet a special-case criterion.
pro ($40.00/mon) is the Best Value tier. It follows the general refund stance. Mentoring sessions already used in the cycle are non-refundable even if a partial refund is otherwise granted.
VEXNILX™ Opus ($60.35/mon) follows the general refund stance. 1-on-1 sessions already booked or attended in the cycle are non-refundable; we may issue a pro-rata refund for the remaining cycle in qualifying special cases.
Business comes in two tiers — Business Basic ($200/mon) and Business ($1,000/mon, plus $50/mon per affiliate). Both follow the general refund stance plus team-specific rules: if seats or affiliate slots were used during the cycle, the request must explain how a refund is fair given that usage.
Vexersatie customers do not follow this Refund Policy verbatim. Refund and credit terms are described in the Vexersatie Order Form. The Order Form controls in the event of conflict.
Where a special-case refund is approved, we may issue a partial refund proportional to the unused portion of the cycle. Full refunds are reserved for clear billing errors.
Pro-rata is computed as: (days remaining in cycle ÷ days in cycle) × charged amount. We round to the nearest cent and exclude usage-based add-ons.
Charges older than 30 days are outside our window. If your bank or card issuer offers a different remedy, you can pursue that — but we will provide our records to support an accurate review.
We do not currently offer annual plans. If we add them in the future, refund handling for annual purchases will be described separately.
Charges discounted by a promo code are refundable only at the discounted amount actually charged. We do not refund the "sticker" price for a promo purchase.
If you bought during a sale or with a partner discount, the refund cannot exceed what you actually paid. The discount is not refundable as cash.
If a bundle is refunded, the full bundle is refunded as one — we don't refund part of a bundle while keeping the rest. If you've used components heavily, the request may be denied.
If you initiate a chargeback with your bank instead of contacting us, we treat it as the formal dispute path. You may lose the option of an in-house resolution while the chargeback is in progress.
Please open a Discord ticket first. Chargebacks cost everyone money and may take 30–90 days to resolve. We can usually resolve legitimate cases faster ourselves.
Accounts that file a chargeback for a valid charge — particularly after using the service — may be suspended. Future purchases from those accounts may be blocked.
Refunds are issued to the original payment method. We do not redirect refunds to a different card, account, or person. If the original method is closed, we follow the processor's guidance.
Once approved, the refund is issued immediately on our side. Banks typically post the credit within 5–10 business days. PayPal and similar wallets are usually faster.
Refunds are issued in the currency of the original charge. If your bank converted to a local currency, the refund is converted back at their current rate, which may differ slightly from the original.
Where taxes were collected on the charge and a refund is approved, the corresponding tax portion is refunded as well. Bank fees on the original charge, if any, are not refundable by us.
If a refund attempt is declined by the processor (closed card, blocked account), we will work with you in the ticket to find an alternative — typically a Discord-credit equivalent where allowed.
Duplicate charges (the same item billed twice) are refunded in full as soon as we verify the duplication. This is one of the clearest special cases.
If a charge was made without your authorization, report it within 30 days. We work with the processor to investigate. Confirmed unauthorized charges are refunded in full.
Brief outages do not normally qualify for a refund. Extended, unrecovered outages affecting a meaningful portion of the billing cycle may qualify on a case-by-case basis.
Vexersatie customers may be entitled to service credits under their SLA. Service credits are the primary remedy for SLA breaches and are typically applied to the next invoice rather than refunded.
If we terminate your account for cause (rule violations), pre-paid amounts are not refunded. If we terminate without cause, a pro-rata refund of the remaining cycle is issued.
Accounts banned for serious violations are not eligible for a refund of the current cycle. The ban is the consequence; the lost cycle is part of it.
Time lost during a suspension imposed for a rule violation is not refunded or credited.
Cancelling a subscription stops future charges. It does not, by itself, refund the current cycle. The current cycle remains active until its end date.
Most cancellations are without refund — you keep access until the end of the paid period. A cancel-with-refund only happens in approved special cases as described above.
We refund in the same currency as the original charge. We do not convert to a different currency at the user's request.
If we ever introduce gift subscriptions, refunds for them go to the buyer, not the recipient. The recipient retains access through the end of the gift cycle, even if the buyer is refunded for a duplicate or error.
We do not currently offer family plans. If we add them, refund rules for shared plans will be published separately.
Auto-renewal charges are not automatically refunded just because you forgot to cancel. "I forgot" is not a special case under this policy. Cancel as soon as you realize, and the charge will not recur next cycle.
If a renewal charge was made after a confirmed successful cancellation, that's a billing error on our side and is refunded once verified.
Notify us in the Discord ticket as soon as you spot a billing issue. Delay can move you outside the 30-day window and reduce what we can verify with the processor.
We may update this Refund Policy. Changes apply to charges made after the update date. We do not retroactively change the refund treatment of past charges to your detriment.
All refund correspondence is handled through tickets in our main Discord Server. We do not process refunds over X/Twitter, email, comments, or DMs to non-staff accounts.
These Vexersatie Terms govern the use of VEXNILX™ Vexersatie — our enterprise tier for organizations and teams. They supplement the standard Terms of Service and, where conflicting, the executed Order Form or Statement of Work controls.
Vexersatie is enterprise-tier.
These terms supplement the standard Terms of Service and apply only to organizations on a custom Vexersatie plan. Where an executed Order Form or Statement of Work conflicts with these terms, the Order Form controls.
By signing an Vexersatie Order Form or Statement of Work, the customer organization accepts these Terms in addition to the standard VEXNILX Terms of Service.
Vexersatie is intended for organizations and teams. Individuals on personal plans should use the standard tiers (basic through VEXNILX™ Opus) instead.
An Order Form must be signed by someone with authority to bind the customer organization (officer, owner, or designated procurement signatory). We may request evidence of authority.
Pricing is determined per engagement based on team size, content scope, and support level. Quotes are typically valid for 30 days unless stated otherwise.
An Order Form lists the plan, term, fees, and any custom inclusions. Statements of Work describe specific projects (e.g. custom tutorial production). Where they conflict with these Terms, the Order Form / SOW controls.
Vexersatie pricing is custom and may include base fees, per-seat fees, content production fees, and optional add-ons. The Order Form is the source of truth.
Customers are typically billed on either a monthly or annual cycle, with invoices issued at the start of each cycle. Custom cycles can be arranged on the Order Form.
We accept ACH, wire transfer, and major cards. Some plans require a non-card method due to invoice size. Banking details are exchanged through verified channels only.
Default invoice terms are Net 30. Other terms (Net 15, Net 60) can be negotiated and are recorded on the Order Form.
Past-due invoices accrue interest at the lesser of 1.5% per month or the maximum rate permitted by law. Repeated late payment may trigger service suspension.
Fees are exclusive of taxes unless stated. The customer is responsible for applicable sales tax, VAT, GST, and similar taxes, except taxes on our income.
Multi-year Order Forms may include locked-in pricing or volume commitments. Annual price escalations, if any, are listed in the Order Form.
Vexersatie terms auto-renew for an additional period equal to the initial term unless either party gives written notice of non-renewal at least 30 days before the end of the current term.
Early termination outside the cause provisions below requires payment of the remaining contract value, except where prohibited by applicable law.
If the Order Form allows termination for convenience, the notice period and any wind-down fees are stated there. By default, termination for convenience is not available mid-term.
Either party may terminate for material breach if the other party fails to cure within 30 days of written notice. Failure to pay an undisputed invoice is a material breach.
Vexersatie plans include an SLA covering uptime, response time, and resolution targets for the production environment. Specific commitments are listed in the Order Form.
Default monthly uptime target is 99.9% measured against the production user-facing surface. Scheduled maintenance, force-majeure events, and customer-caused incidents are excluded.
If we miss an SLA target, the remedy is service credits applied to the next invoice. Credits are the exclusive remedy for SLA misses, except where law provides otherwise.
Vexersatie customers get a dedicated support team with priority response. The team is reachable via private Discord channels and an escalation contact listed in the Order Form.
Each Vexersatie customer is assigned a named account manager who handles renewals, expansions, and quarterly reviews.
Onboarding includes a kickoff call, environment setup, role provisioning, and a structured handover. The standard onboarding window is 2–4 weeks; complex deployments may take longer.
Custom tutorials are produced under a separate SOW with deliverables, milestones, and acceptance criteria. IP ownership of the resulting tutorials is described in the IP section below.
Private channels are provisioned for each Vexersatie customer. Membership is managed by the customer's designated admin via Discord roles.
Limited white-label options (custom Discord branding, internal-only tutorial sections) may be available depending on the engagement. White-label requirements should be raised before signing the Order Form.
SSO via SAML or OIDC may be available depending on tier. SSO setup, user provisioning rules, and de-provisioning are documented during onboarding.
Audit logs are available for Vexersatie admins covering authentication, role changes, and access events. Compliance summaries can be exported on request.
We sign a Data Processing Agreement on request. Our standard DPA covers GDPR/UK-GDPR roles and obligations and incorporates Standard Contractual Clauses where applicable.
A current list of our subprocessors is maintained and shared on request. We notify Vexersatie customers of subprocessor changes and provide a window to object.
Each party will protect confidential information of the other with reasonable care, use it only for purposes of the engagement, and return or destroy it on request after the engagement ends.
An NDA is incorporated by reference (or attached) to the Order Form. Confidentiality obligations survive termination for at least 3 years, and indefinitely for trade secrets.
We may use subcontractors to deliver the services and remain responsible for their compliance with these Terms. Material subcontractor changes are communicated where required.
We maintain commercial general liability, cyber, and errors-and-omissions insurance with reasonable limits. Certificates of insurance can be provided on request.
Each party indemnifies the other for third-party claims arising out of its breach of these Terms, intentional misconduct, or IP infringement claims caused by its content or use.
Aggregate liability for any claim is limited to fees paid by the customer in the 12 months before the claim, with carve-outs for indemnification, breach of confidentiality, and willful misconduct.
We retain ownership of our pre-existing IP. The customer retains ownership of customer content. Custom deliverables produced under an SOW have ownership and license terms specified in that SOW.
Subject to payment, we grant the customer a non-exclusive, non-transferable license to access and use the services and tutorials within the team during the term.
The customer grants us a limited license to host and use customer content as needed to deliver the services. We do not use customer content for marketing without written consent.
Background IP (each party's pre-existing IP) is not transferred. Combinations and joint inventions, if any, are addressed in the SOW.
All Vexersatie users must comply with the standard Acceptable Use rules. The customer is responsible for ensuring its users follow them.
Plans are typically seat-based. The number of seats is listed in the Order Form. Exceeding the seat count requires a true-up amendment.
We provide usage reports to the customer admin (seat count, active users, content consumption summaries) at the cadence agreed in the Order Form.
Mid-term seat increases are processed via amendment and are typically pro-rated to the end of the current cycle. Decreases generally apply at the next renewal.
Vexersatie customers may opt into beta features. Beta features are provided as-is, may change without notice, and are not covered by the standard SLA.
Material changes to scope, fees, or seats are documented in a written change order signed by both parties. Verbal commitments are not binding without a change order.
Neither party is liable for delays or failures caused by events beyond reasonable control. The affected party will notify the other and resume performance as soon as reasonably possible.
Governing law and exclusive venue are listed in the Order Form. Where not listed, defaults from the standard Terms of Service apply.
Disputes are first escalated to the named account manager, then to senior leadership of both parties, before any formal proceeding. We aim to resolve in good faith without litigation.
If the Order Form selects arbitration, claims are resolved by binding arbitration on an individual basis. Class actions are waived where permitted by law.
Formal notices go to the contact addresses listed on the Order Form. Operational communication uses the dedicated Discord channel and named contacts.
We may update these Vexersatie Terms over time. Material changes apply at renewal. In-term changes require mutual written agreement.
This Partnership Agreement governs official partnerships between VEXNILX™ and qualifying organizations. Partnerships are only granted to companies with verified ownership, where the principal operator is at least 13 years of age, with a Discord community of more than 100 members, and active engagement in the main VEXNILX Discord Server.
Partnership eligibility (must meet ALL):
• You operate a registered or verifiable company
• Principal operator is at least 13 years of age
• Your Discord community has more than 100 members
• You are actively engaged in the main VEXNILX Discord Server
Becoming an VEXNILX™ Partner means accepting this Partnership Agreement. Approval of your application and assignment of the Partner role on Discord constitutes acceptance by both sides.
Partnerships are limited. To qualify and remain a Partner you must: operate a verifiable company, have a principal operator at least 13 years of age, run a Discord community with more than 100 members, and stay actively engaged in the main VEXNILX Discord Server.
We verify ownership of the partner organization. "Company" here is read broadly — registered businesses, LLCs, single-operator brands with consistent online presence — but we expect a clear answer to "who runs this?" with evidence.
The principal operator (the person we communicate with about the partnership) must be at least 13 years of age. Where applicable law requires a higher age for binding contracts, that higher age controls.
Your Discord community must exceed 100 members at the time of approval and over the duration of the partnership. Sustained drops below 100 members may trigger a status review.
Active engagement means the principal operator (or a designated representative) is present and visibly active in our main Discord — posting, asking questions, helping members, attending events. Lurking does not count.
Apply through the partner application form pinned in our partner channel. Applications include organization details, ownership evidence, community size, and a short rationale for the partnership.
Typical documents: business registration (where it exists), proof of domain ownership or community ownership, screenshots showing community size, and a referral from an existing Partner if available.
We may request a verification call or specific actions (e.g. posting a code from your verified company channel) to confirm ownership. Failure to complete verification ends the application.
We do a light audit of the community: rules quality, moderation activity, alignment with our Safety Policy. Communities that don't meet baseline safety expectations are not approved.
Most applications are reviewed within 14 days. Complex cases or those requiring back-and-forth take longer. We do not give exact pre-approval timelines.
Newly approved Partners enter a 60-day probation. During probation we review engagement and behavior more closely. Probation ends silently if all goes well.
Partners get a Partner role on our Discord, the Partner badge, eligible cross-promotion, and access to a private partners channel.
Approved Partners may use our "Partner" mark in agreed contexts. Co-branding cannot imply ownership, employment, or that VEXNILX endorses unrelated products.
The Partner role and badge are visible on our main Discord. They are granted on approval and removed on termination of the partnership.
Cross-promotion happens occasionally and by mutual agreement. We do not guarantee a fixed number of mentions, posts, or pin-ups per quarter.
Joint events (AMAs, workshops, tournaments) are scheduled by mutual agreement. We expect adequate notice (usually 4+ weeks) and clear roles for each side.
Where revenue share applies, attribution uses a tracked link or code provided by us. Conversions outside the tracked path may not be attributed.
Revenue share, if part of the partnership, is documented in a separate addendum with rates, payout frequency, and reporting cadence. Default is no revenue share unless stated.
Earnings are paid monthly or quarterly per the addendum, after a minimum payout threshold is reached. Payouts use the partner's preferred method from the supported list.
Partners are responsible for reporting and paying taxes on earnings. Where required, we collect tax forms (e.g. W-9 / W-8) before issuing payments.
We expect Partners to remain active in the main Discord, host healthy communities, and represent the partnership accurately. We do not expect specific volume targets unless stated.
We review partner activity once per quarter. Reviews look at engagement, moderation activity, and community health. Outcomes are communicated privately.
Partners who fall below the criteria may be demoted to a probationary status, given a written warning, or have the partnership terminated, depending on severity and history.
Partners may not: misrepresent the partnership, run scams or unlicensed paid services, harass our members, leak private partner-channel information, or use our marks in misleading contexts.
Misuse of the VEXNILX name or logo — modifying it, putting it next to off-brand content, or implying we operate the partner's community — leads to immediate review and likely termination.
What's discussed in the private partners channel stays in the partners channel. Leaks (deliberate or careless) terminate the partnership and may trigger legal action where serious.
Partners get a limited license to use our marks for partnership purposes only. The license ends when the partnership ends. All other uses require written permission.
Use our official logo files. Don't recolor, distort, add effects to, or combine the logo with other marks without permission. Maintain the minimum size and clear-space rules we provide.
Press releases or public statements that mention VEXNILX require approval before publication. We try to turn requests around quickly.
Partners may have other partnerships unless explicitly restricted. If a competing partnership creates a real conflict of interest, we discuss it openly and decide together.
Most partnerships are non-exclusive. Exclusive arrangements, if any, are documented in an addendum with the corresponding obligations on both sides.
Partners retain ownership of their content, marks, and brand. We don't acquire any rights to those beyond what's needed to deliver the partnership.
When promoting our community in your server (and vice versa), use accurate descriptions, current invite links, and respect each server's rules.
Members of either community should not be poached or aggressively recruited. Healthy overlap is fine; targeted poaching is not.
Members can report concerns about a partner's conduct in the safety channel of our main Discord. Reports are reviewed confidentially.
Disagreements between Partners (or between a Partner and us) are first handled in good-faith conversation in the partners channel. Unresolved disputes escalate to senior staff.
We may terminate a partnership for material breach (e.g. brand misuse, harassment, falling below eligibility) immediately. Where the issue is curable, we may give a short cure period first.
A Partner may exit the partnership at any time by notifying us in the partners channel. Voluntary exit is amicable; benefits and licenses end on the exit date.
On termination: the Partner role and badge are removed, mark licenses end, access to the private partners channel ends, and any pending earnings are paid out at the next regular cycle.
Confidentiality, IP, and indemnification clauses survive termination. The partnership ends; the obligations from it don't all vanish.
Partners terminated for non-serious reasons may reapply after a 90-day cooling-off period. Terminations for severe cause (fraud, harassment) bar reapplication.
Both parties must comply with Discord's own Terms of Service. A Discord-side action against a Partner (suspension, ban) may also affect their VEXNILX Partner status.
Partners must comply with the laws of jurisdictions where they and their communities operate, including consumer-protection, advertising, and tax law.
Neither side will offer or accept improper payments to influence partnership decisions. Reasonable swag and event hospitality are fine.
Neither party is liable for delays caused by events beyond reasonable control. The affected party notifies the other and resumes activities when reasonably possible.
Operational communication happens in the partners channel and via designated contacts on each side. Formal legal notices go to the contact listed on the partnership intake.
We may update this Partnership Agreement. Material changes are announced in the partners channel and apply at the start of the next quarterly review unless they involve safety or legal urgency.
Governing law follows the standard Terms of Service unless an addendum specifies otherwise.
Partnership questions go to the partner application channel for prospective partners or to your assigned contact for active Partners. We aim for timely, friendly responses.