Hello,
I’m validating a Next.js Spotify Authorization Code with PKCE integration on Vercel Hobby.
On 20 October 2026, I tested a Preview deployment using only these fake values:
/api/spotify/callback?code=sme_fake_code_20261020&state=sme_fake_state_20261020
The callback correctly returned HTTP 503 because Spotify integration is disabled on Preview. Vercel reported no outgoing requests.
However, Runtime Logs → request details → Search Params displayed both fake values.
Before enabling deployed OAuth, I need to establish whether incoming authorization codes and state values can be excluded or redacted before ingestion/storage in Vercel’s platform request metadata.
Could you please confirm:
Is there a supported project or team setting for this on Hobby? If so, what exact setting?
If another plan supports it, which plan and configuration provide this?
Does the control prevent storage of the original values, or only mask them in the dashboard?
This concerns Runtime Logs request metadata. Application logging is sanitized, and Web Analytics redaction would address a different data stream.
No real authorization codes, tokens, cookies, or other credentials were used. Deployed OAuth remains disabled while this requirement is unresolved.
Environment: Next.js 16.3.6 with App Router, Node.js 24, deployed as a Vercel backend Function. The probe ran on a dev-branch Preview deployment.
Thank you.