Privacy Policy

Information we process

• Uploaded audio files submitted through multipart/form-data.
• Analysis results such as BPM, beat timestamps, cut points, timing segments, request IDs, and task IDs.
• Operational metadata such as file size, content type, processing time, status code, error code, and timestamps.
• RapidAPI-related request metadata provided by RapidAPI, such as plan and request context when available.

How we use data

• We use uploaded audio and generated results to process the API request, troubleshoot failures, protect the service, and improve reliability.
• We do not use uploaded audio to train models.
• We do not sell uploaded audio, analysis results, or API request metadata.

API keys and demo usage

The demo page runs in your browser and sends your RapidAPI key directly to the RapidAPI endpoint. The BeatSync API static site does not receive or store your key. RapidAPI manages consumer API keys, subscription state, billing, and key rotation.

Retention

• Uploaded audio, request payloads, result files, and error files are kept temporarily for processing, troubleshooting, service reliability, and abuse prevention.
• Temporary processing data expires under our retention policy when it is no longer needed for those purposes.
• The exact retention period depends on the data type, operational need, security requirements, legal obligations, and whether a support or abuse investigation is active.
• Aggregated logs, billing records, and security records may be retained longer where needed for accounting, fraud prevention, legal compliance, or dispute resolution.

Security and deletion

• Public API traffic is routed through RapidAPI and BeatSync API service controls before processing.
• Access to uploaded files and operational logs is limited to service systems and operators who need it for support or maintenance.
• To request deletion assistance for a specific request, contact [email protected] with the request ID, task ID, and timestamp.