PDF export ignores user timezone setting for date macro output

Symptom

When exporting a page containing the Date macro to PDF or Word, the rendered timestamp reflects the server system timezone or UTC instead of the viewing user's configured profile timezone. The UI correctly converts UTC to the user's preference, but the export pipeline does not preserve this conversion.

Context

Confluence stores all timestamps in UTC and relies on the user profile timezone for display conversion. System-level defaults apply when a user has no explicit setting. The Date macro resolves relative dates against the server clock at render time. During PDF/Word generation, the export process runs server-side without access to the requesting user's timezone context.

Goal

Determine whether the export subsystem can be configured to apply the initiating user's timezone when rendering date macros, or if a workaround (such as pre-rendering with a specific timezone parameter) is required for consistent static output.

Specific questions:

• Does the PDF export API accept a timezone parameter that overrides the server default for macro rendering?
• Is there a supported method to inject the current user's timezone into the export context for Data Center deployments?
• Are there version-specific differences between Cloud and Data Center in how export timezone handling is implemented?