Uploads and posts
We store content you upload or create, including tracks, images, posts, comments, messages, events, reports, profile intro tracks, stories, and forum content.
We collect the data needed to run accounts, music tools, safety systems, and the community. This page explains the basics in normal language.
Last updated: May 31, 2026
We may collect account details such as username, display name, email address, password hash, verification state, profile information, avatar or profile media, social links, settings, security preferences, and account status.
Public profile information, posts, events, comments, forum activity, charts, and selected uploads may be visible to other users or visitors depending on the feature.
We store content you upload or create, including tracks, images, posts, comments, messages, events, reports, profile intro tracks, stories, and forum content.
Studio projects, loop metadata, user-uploaded loops, saved project JSON, names, timestamps, and related settings may be stored so the DAW can reopen and manage your work.
PULSATRAX Studio voice recording relies on your browser's microphone permission. Your browser controls the permission prompt. PULSATRAX does not receive microphone audio unless you choose to use a recording feature and save or upload the result.
Recorded vocals may be stored as user audio assets, included in studio projects, or processed for playback depending on the workflow you choose.
PULSATRAX uses essential cookies or session storage for login, CSRF protection, account security, preferences, and keeping the app working. See the Cookie Policy.
PULSATRAX may load Google AdSense verification or advertising scripts. If ad placements are enabled, advertising partners may process browser, device, page, and interaction signals under their own policies. Ad slots are configured separately from core account features.
We may store reports, moderation decisions, rate-limit events, login/session signals, blocked words, admin actions, IP-related security records where available, device or browser signals, and other logs needed to detect spam, scams, abuse, copyright issues, or attacks.
Direct messages are intended to be private between users, but may be reviewed when reported or when needed to investigate abuse, safety, legal, or security issues.
Posts or profiles may include links or embeds from services such as YouTube or other external sites. Those services may collect data under their own policies when you load, click, or interact with them.
Email delivery, hosting, push notification, anti-abuse, or infrastructure providers may process data on behalf of PULSATRAX where needed to operate the service.
Users may create or upload AI-assisted music, artwork, text, or profile content. PULSATRAX may store and display that content like other user-generated content. Users are responsible for making sure AI-assisted content does not violate rights, impersonate people deceptively, or mislead collaborators and listeners.
Data is used to operate accounts, show content, power PULSATRAX Studio, deliver notifications, support messages, handle reports, protect the platform, enforce rules, debug issues, and improve launch stability.
We keep data as long as needed for the service, legal obligations, safety, backups, abuse prevention, disputes, or account operation. Some deleted content may remain in backups or logs for a limited period.
Depending on where you live, you may have rights to access, correct, delete, export, object to, or limit use of certain personal data. You can also request account deletion through available account tools or by contacting us.
For privacy requests, contact [email protected]. For broader legal or moderation issues, use Contact / Support.