BeatMaker processes prompts and technical request information needed to generate and deliver audio. Generated files may be stored temporarily for playback or download.
When accounts are enabled, email, display name, salted password hashes, login timestamps and generation counts are stored. Guest limits use a keyed hash derived from request/network identifiers; the account store does not intentionally retain the raw IP address. Session cookies are HTTP-only. Administrator credentials are not exposed in public pages or account records. Developer-issued API keys are stored only as one-way hashes after creation. Scheduled-audio definitions, run history, and administrator-created prompts are stored in the private service state. The most recent generated WAV for a user, guest session, or API key has a private download reference that expires after about 24 hours so ordinary Cloud Run restarts do not immediately lose the download; physical object cleanup may occur later. Scheduled WAV files may be stored in the administrator's private Cloud Storage bucket until replaced or removed by the administrator.