Privacy Policy

This Privacy Policy explains how BeatCodex collects, uses, stores, and protects personal data through the BeatCodex website, forms, email communication, beta requests, mapping requests, and mapping submissions.

BeatCodex is currently an independent pre-launch software project. No products, subscriptions, paid downloads, paid services, voluntary support payments, donations, or crowdfunding contributions are currently sold or collected through this website.

BeatCodex does not sell personal data.

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

A complete professional identification notice will be added before any commercial release, paid product, paid download, paid service, public commercial distribution, or support-payment system is made available.

For privacy-related requests, contact hello@beatcodex.com.

You may also use support@beatcodex.com, beta@beatcodex.com, or maps@beatcodex.com.

BeatCodex only intends to collect data that is useful for operating the pre-launch project, managing beta interest, improving map coverage, handling support, and processing mapping feedback.

Depending on how you interact with the website or forms, BeatCodex may collect:

• email address;
• name or display name, if provided;
• country or region, if provided;
• operating system;
• DAW or host software;
• sampler or drum library information;
• requested drum libraries or kits;
• mapping corrections, mapping submissions, or related notes;
• uploaded mapping-related files, if voluntarily submitted;
• beta interest and communication preferences;
• support messages and related correspondence;
• technical information generated by hosting, form, email, or security services, such as IP address, browser information, timestamps, and server logs.

BeatCodex does not intentionally collect sensitive personal data.

Please do not submit passwords, license keys, private API keys, payment details, confidential third-party files, copyrighted manuals, audio samples, virtual instruments, installers, or other material that you do not have the right to share.

Beta interest and beta communication

To record beta interest, contact potential beta testers, send beta-related updates, and manage access if a beta program is opened.

Mapping requests

To understand which drum libraries, kits, DAWs, and workflows users want BeatCodex to support.

Mapping submissions and corrections

To review mapping feedback, mapping corrections, submitted files, user notes, and compatibility information.

Support and contact

To respond to questions, bug reports, support requests, compatibility reports, legal notices, or intellectual property concerns.

Product improvement

To improve BeatCodex mapping coverage, compatibility, documentation, website content, plugin planning, and pre-launch priorities.

Security and abuse prevention

To protect the website, forms, email systems, and project infrastructure from spam, abuse, security incidents, or misuse.

Legal and compliance

To comply with applicable laws, handle takedown requests, protect rights, and keep reasonable records of communications and submissions.

Depending on the situation, BeatCodex may process personal data on the following legal bases:

• Consent, when you voluntarily submit a form, join a mailing list, request beta updates, or agree to receive product communication.
• Legitimate interest, when BeatCodex processes messages, support requests, mapping feedback, security logs, or project-related communications necessary to operate and improve the pre-launch project.
• Pre-contractual steps, if you request information about future access, beta availability, or potential use of BeatCodex.
• Legal obligation, if BeatCodex must retain or disclose information to comply with applicable law or respond to lawful requests.

BeatCodex may use third-party services to operate the website, forms, email communication, mailing lists, data organization, hosting, and project management.

Current or planned services may include:

• Vercel for website hosting and technical deployment;
• Tally for beta signup, library request, and mapping submission forms;
• Brevo for email updates, beta communication, or mailing lists;
• Zoho Mail for project email mailboxes;
• Airtable or Google Sheets for organizing beta interest, library requests, mapping requests, and mapping submissions;
• GitHub for source-code hosting and project development;
• Cloudflare or another registrar/DNS provider for domain and DNS management.

These services may process personal data as service providers or independent platforms according to their own terms and privacy policies.

BeatCodex aims to limit the data sent to each service to what is necessary for the relevant purpose.

BeatCodex may send operational emails related to beta requests, support requests, mapping submissions, mapping corrections, library requests, and legal or abuse reports.

BeatCodex may also send product updates, beta news, or launch-related messages when you have requested or consented to receive them.

You can unsubscribe from marketing or product-update emails using the unsubscribe link provided in such emails, where applicable, or by contacting hello@beatcodex.com.

BeatCodex will not intentionally add users to marketing or product-update mailing lists without consent.

If you submit mapping information, corrections, notes, files, or compatibility data, BeatCodex may review, store, edit, normalize, merge, publish, or use that information to improve BeatCodex maps, taxonomy, compatibility data, plugin behavior, documentation, or website content.

Please do not submit third-party audio samples, virtual instruments, installers, proprietary presets, copyrighted manuals, logos, confidential documents, or material that you do not have the right to share.

Specific rights and permissions related to mapping submissions may be described separately in the BeatCodex Mapping Submission Terms.

Essential website functionality works without analytics consent. BeatCodex asks separately whether you want optional analytics enabled; rejecting analytics does not block navigation, accessibility, or access to forms.

If you accept analytics, the current website code conditionally loads Vercel Analytics and Cloudflare Web Analytics/Insights. Their provider-level processing, including any technical identifiers or IP handling, is governed by their own documentation and policies and is not independently controlled or fully verifiable from this repository.

BeatCodex application events are limited to page views, link actions, and form-journey context. The website does not send Tally form contents, passwords, account identifiers, advertising identifiers, fingerprints, or session recordings to its application event function.

Your analytics choice is stored locally under an essential consent preference. Optional first-party attribution, such as landing page, referrer, UTM parameters, source page, and CTA context, is stored or passed to Tally only after analytics consent. The website does not intentionally set advertising, retargeting, or marketing cookies.

Tally forms open on an external service. Tally may use its own storage, cookies, logs, and processing practices, and handles submitted information under its own privacy policy. Review Tally's notices when opening or submitting a form.

You can change your analytics choice at any time using the Privacy Settings control in the footer. The policy and consent details may change as providers or commercial services are introduced.

BeatCodex keeps personal data only for as long as reasonably necessary for the purposes described in this Privacy Policy.

Indicative retention periods are:

• beta signup data: until the end of the beta/pre-launch period, unless you ask for deletion earlier;
• mailing-list data: until you unsubscribe or request deletion;
• support messages: up to 3 years after the last interaction, unless a longer retention period is necessary for legal or security reasons;
• mapping requests and submissions: as long as needed to maintain, verify, improve, or document BeatCodex mapping compatibility;
• legal, abuse, or takedown correspondence: as long as reasonably necessary to handle the request and protect rights;
• technical logs: according to the hosting or security provider’s retention settings.

BeatCodex may keep anonymized or non-personal aggregated information for project analysis, map prioritization, and product planning.

Some services used by BeatCodex may be based outside the European Union or may process data internationally.

Where required, such transfers should be covered by appropriate safeguards used by the relevant service providers, such as standard contractual clauses, adequacy decisions, or equivalent transfer mechanisms.

BeatCodex aims to use reputable providers and limit personal data collection during the pre-launch phase.

BeatCodex uses reasonable technical and organizational measures to protect personal data against unauthorized access, loss, misuse, alteration, or disclosure.

However, no website, email system, form provider, hosting platform, or online service can guarantee absolute security.

Users should avoid submitting confidential or sensitive information through BeatCodex forms unless specifically requested and necessary.

Subject to applicable law, you may have the right to:

• access your personal data;
• correct inaccurate or incomplete personal data;
• request deletion of personal data;
• object to certain processing;
• restrict certain processing;
• withdraw consent where processing is based on consent;
• request portability of data you provided, where applicable;
• lodge a complaint with a data protection authority.

To exercise these rights, contact hello@beatcodex.com.

Please include enough information to identify your request, such as the email address used in the relevant form or message.

If you are in France, you may also contact or file a complaint with the CNIL.

BeatCodex is intended for music producers, musicians, developers, and adult users interested in MIDI drum mapping workflows.

BeatCodex does not knowingly collect personal data from children.

If you believe a child has submitted personal data through BeatCodex, please contact hello@beatcodex.com.

BeatCodex may update this Privacy Policy as the project evolves, especially if beta access, downloads, user accounts, payments, analytics, license systems, or commercial services are introduced.

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

For privacy questions, access requests, deletion requests, correction requests, or objections, contact hello@beatcodex.com.

For support questions: support@beatcodex.com.

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

For beta communication: beta@beatcodex.com.