Short version
- Pulse analyzes authorized public audio URLs or user-provided files only to produce requested BPM, key, waveform, status, billing, and account results.
- Audio is processed for the job and is not stored as user audio after processing.
- Users must have rights, permission, lawful access, or another legal basis before submitting audio.
- Payment details are handled by Stripe Checkout. Pulse does not store card numbers.
What Pulse collects
Pulse collects the information needed to operate audio-intelligence workflows: submitted public audio URLs, selected tools, cost estimates, job IDs, job status, generated metadata, API-key account records, token balances, payment-job IDs, and basic operational logs.
For account workflows, Pulse stores account email addresses when provided, API-key records, token balances, account type, and account status. API keys should be treated as private credentials and should not be posted in public chats, screenshots, repositories, or directory examples.
Ephemeral audio processing
Pulse fetches, receives, decodes, and analyzes audio only to complete the requested job. The service is designed for ephemeral audio processing: submitted audio is processed for analysis and is not retained as user audio after the job finishes.
Pulse may retain non-expressive technical metadata needed to provide results, prevent abuse, calculate billing, support retries, cache repeated analysis, and operate the service. Examples include BPM, musical key, waveform peak data, duration, selected tools, job state, and billing status.
Public audio URLs
When a user submits public audio URLs, Pulse may request the URL and normalize supported share links, including accessible Google Drive or Dropbox-style links, so the service can determine duration and run analysis. Users remain responsible for submitting only audio they have rights, permission, lawful access, or another legal basis to analyze.
Pulse does not host, stream, redistribute, republish, or sell submitted audio.
Jobs and result retention
Pulse stores job and result metadata so users and agents can poll status, retrieve completed or partial results, display waveform exits, diagnose failed jobs, and prevent duplicate payment or webhook processing. Result access may be time-limited by the product surface even when operational records remain for accounting, fraud prevention, support, or service reliability.
Payments
Pulse uses Stripe Checkout for one-time analysis payments and token-pack purchases. Stripe handles card details and payment authentication. Pulse stores payment identifiers, payment status, amounts, refund status, and related job or token-pack metadata needed to reconcile service delivery.
MCP and agent workflows
Pulse is available as a remote MCP server. Some tools can be used without an existing account, such as cost estimation and one-time Checkout flows. API-key authentication is required for account-specific banked-token analysis, token-pack purchases, and balance checks.
Agents should estimate cost first, show the user the cost, confirm rights or lawful access, and then either analyze with an authenticated API-key account or request a one-time Stripe Checkout link.
Contact
For privacy, support, or account questions, contact support@studiosphere.space.