← Back to BeatCodex

BEATCODEX

Beta Terms

Last updated: 1 June 2026

1. Introduction

These Beta Terms govern access to and use of any BeatCodex beta program, beta signup list, preview build, test build, private download, experimental plugin version, experimental map, or pre-release material.

By requesting, accepting, downloading, installing, testing, or using any BeatCodex beta material, you agree to these Beta Terms.

If you do not agree with these Beta Terms, do not request, download, install, test, or use BeatCodex beta materials.

2. Current Project Status

BeatCodex is currently an independent, pre-commercial software project.

No products, subscriptions, paid downloads, paid services, paid support, voluntary support payments, donations, or crowdfunding contributions are currently sold or collected through this website.

BeatCodex is in a pre-launch phase. Beta materials may be experimental, incomplete, unstable, inaccurate, undocumented, or subject to change.

3. No Guarantee of Beta Access

Joining the beta list, submitting a form, requesting access, or communicating with BeatCodex does not guarantee beta access.

BeatCodex may accept, refuse, delay, pause, revoke, or limit beta access at any time and for any reason, including technical capacity, compatibility focus, project priorities, abuse prevention, or lack of fit with the current test phase.

BeatCodex may close, pause, or end the beta program at any time.

4. Experimental Nature of Beta Materials

Beta materials are provided for testing, validation, feedback, and pre-launch evaluation only.

They may contain bugs, crashes, incorrect mappings, incorrect note names, broken exports, stuck MIDI notes, host compatibility issues, performance issues, incomplete features, missing documentation, or other errors.

Beta materials are not intended for critical, commercial, live, production, paid-session, or time-sensitive use.

You should not rely on beta materials for professional work unless you have independently tested them and accept the risk.

5. User Responsibility and Backups

You are responsible for your own testing environment and for any consequences of installing, opening, importing, exporting, or using BeatCodex beta materials.

Before using beta materials, you should back up:

  • DAW projects;
  • sessions;
  • templates;
  • presets;
  • MIDI files;
  • drum maps;
  • plugin settings;
  • sampler patches;
  • any files that may be affected by testing.

You should test BeatCodex beta materials on copies of projects, not on your only working version of an important project.

6. No Warranty

Beta materials are provided “as is” and “as available.”

BeatCodex makes no warranty that beta materials will be accurate, complete, stable, secure, compatible, uninterrupted, error-free, or suitable for any particular purpose.

BeatCodex does not guarantee that beta materials will work with any specific DAW, plugin host, sampler, operating system, drum library, MIDI file, workflow, or hardware setup.

To the maximum extent permitted by applicable law, BeatCodex disclaims all warranties, whether express, implied, statutory, or otherwise.

7. Limitation of Liability

To the maximum extent permitted by applicable law, BeatCodex will not be liable for indirect, incidental, consequential, special, punitive, or economic damages arising from beta access or use of beta materials.

This includes, without limitation:

  • lost DAW projects;
  • corrupted sessions;
  • lost MIDI files;
  • lost presets;
  • lost plugin settings;
  • lost income;
  • studio downtime;
  • production delays;
  • failed live use;
  • compatibility problems;
  • incorrect MIDI conversion;
  • incorrect mapping exports;
  • stuck notes or MIDI playback issues;
  • damage caused by relying on incomplete or inaccurate beta information.

Nothing in these Beta Terms excludes liability where such exclusion is not permitted by applicable law.

8. No Paid Product, License, or Future Benefit

Beta access is not a sale, paid license, subscription, preorder, commercial product, support contract, or professional service.

Receiving beta access does not grant:

  • ownership rights;
  • intellectual property rights;
  • voting rights;
  • revenue share;
  • guaranteed support priority;
  • guaranteed future access;
  • a free future paid license;
  • a discount on a future paid product;
  • access to future paid maps, packs, builds, or services.

If BeatCodex later offers paid products, licenses, subscriptions, mapping packs, or services, those will be governed by separate commercial terms.

9. Feedback

BeatCodex may invite testers to provide feedback, bug reports, compatibility notes, mapping corrections, feature suggestions, screenshots, logs, or other test information.

By providing feedback, you allow BeatCodex to use, edit, adapt, combine, publish, implement, and commercialize that feedback without payment, attribution, or obligation, unless a separate written agreement says otherwise.

Feedback may be used to improve the website, maps, taxonomy, documentation, plugin behavior, compatibility data, public materials, or future commercial products.

Do not submit confidential information, third-party proprietary content, private license keys, passwords, API keys, audio samples, installers, copyrighted manuals, or material that you do not have the right to share.

10. Mapping Feedback and Submissions

If you submit mapping corrections, mapping files, drum-library information, compatibility notes, or related data, those submissions may also be governed by the BeatCodex Mapping Submission Terms.

BeatCodex may review, normalize, edit, merge, publish, or use mapping-related feedback to improve BeatCodex maps, taxonomy, compatibility data, plugin behavior, website content, documentation, or future products.

11. Third-Party Products and Compatibility

BeatCodex is an independent MIDI mapping and remapping project.

Third-party company, product, library, software, DAW, sampler, and trademark names are used only to identify compatibility, source mappings, target mappings, user-requested drum libraries, or relevant workflows.

BeatCodex is not affiliated with, endorsed by, sponsored by, approved by, or officially connected with Native Instruments, Toontrack, GetGood Drums, XLN Audio, Steven Slate Drums, BFD, UJAM, IK Multimedia, Ableton, Steinberg, PreSonus, Cockos, Image-Line, Apple, Avid, or any other referenced third-party rights holder.

All trademarks, product names, company names, and library names remain the property of their respective owners.

Users must own or lawfully access any third-party drum library, sampler, DAW, plugin, or software used with BeatCodex beta materials.

12. No Third-Party Audio Content

BeatCodex beta materials do not include third-party audio samples, virtual instruments, installers, proprietary presets, copyrighted manuals, or proprietary drum-library content.

BeatCodex works with MIDI mapping information, compatibility metadata, and independently curated mapping structures.

You must not upload, share, or submit third-party audio samples, virtual instruments, installers, proprietary presets, copyrighted manuals, confidential files, or material you do not have the right to share.

13. Restrictions on Beta Materials

Unless BeatCodex gives written permission, you must not:

  • redistribute beta builds or private download links;
  • resell beta access;
  • publish private beta materials;
  • represent BeatCodex beta materials as official third-party integrations;
  • use beta materials to mislead users about compatibility or endorsement;
  • attempt to bypass technical limits, access controls, or download restrictions;
  • use beta materials for unlawful, harmful, or infringing purposes.

Additional restrictions may apply to specific beta builds, download links, license files, or private test groups.

14. Public Discussion and Screenshots

Unless BeatCodex states that a beta build or test phase is confidential, testers may discuss their general experience with BeatCodex.

However, BeatCodex may ask testers not to publish screenshots, videos, private download links, internal notes, unreleased features, or sensitive compatibility details for specific test phases.

If a specific beta invitation says that the build is private or confidential, you must follow that instruction.

15. Security, Abuse, and Revocation

BeatCodex may suspend or revoke beta access if it detects abuse, spam, redistribution of private builds, harmful behavior, security concerns, misuse of forms, infringement risk, or conduct that damages the project or other users.

BeatCodex may also revoke or limit access if a beta build is outdated, unsafe, technically broken, or no longer supported.

16. Privacy

Personal data collected through beta requests, beta communication, support messages, forms, mapping submissions, or testing feedback is handled according to the BeatCodex Privacy Policy.

BeatCodex does not sell personal data.

17. Changes to Beta Terms

BeatCodex may update these Beta Terms as the project evolves, especially if beta access, plugin downloads, license systems, user accounts, commercial releases, support systems, or mapping workflows change.

The updated version will be published on this page with a new “Last updated” date.

18. Contact

For beta-related questions: beta@beatcodex.com.

For support questions: support@beatcodex.com.

For mapping-related questions: maps@beatcodex.com.

For legal, privacy, or general questions: hello@beatcodex.com.