Privacy policy
Current privacy baseline for scoretransposer.com
This policy describes how ScoreTransposer handles account data, uploaded music PDFs, generated Jianpu outputs, and support records for the current production release.
Information collected
Account data such as email address, password hash, activation status, and entitlement dates.
Uploaded PDF files, generated preview text, output PDFs, and draft bundles required to fulfill conversions.
Operational metadata such as upload timestamps, job status, file names, and support contact records.
How data is used
To authenticate users, verify paid access, and deliver the requested staff PDF to Jianpu workflow.
To retain source files and generated results for the signed-in user to review and download inside the app.
To investigate failed jobs, respond to support requests, and improve heuristic conversion quality.
Retention and deletion
Account and entitlement records are retained while the account remains active and for follow-up support when needed.
Uploaded source files and generated outputs are retained to support download, review, and service troubleshooting.
Deletion requests should be handled through manual support review until a self-service deletion flow is released.
Data sharing
Customer files are not sold.
Operational vendors may process traffic, hosting, DNS, storage, logging, and deployment data as part of delivering the service.
Data may be disclosed when required by law or to protect the service from abuse, fraud, or security incidents.
Security baseline
Access to the conversion tool is gated by user authentication and activation-based entitlement checks.
Production access should be limited to authorized operators, and secrets should be managed in the hosting platform instead of source control.
Users remain responsible for avoiding unlawful or unauthorized uploads and for verifying musical correctness before publication or performance.
Contact and policy changes
If you need account deletion, data export, or policy clarification, route the request through your published support channel and confirm the account identity before taking action.
Material changes to hosting, storage, analytics, payment handling, or account workflows should trigger an immediate policy update before the new flow goes live.