Control stays with the agent.

Private workspace actions require a signed-in user. The application checks the caller before reading or changing a listing, generated output, seller proof, team record, or workspace setting.

Data tables use workspace-scoped access rules, and the server verifies ownership when a service-side action needs broader access to render or publish an output.

• Property sites publish only after an explicit agent action.
• Unpublishing stops an AlpenGlow-hosted listing site from being served at its agent-branded address.
• Generated copy, print files, social material, and seller proofs remain reviewable; AlpenGlow does not post to social networks, email recipients, submit to an MLS, or sign documents for the agent.

The Creative Director works from the current workspace context and records each run, its selected model, and its source trail. It does not autonomously write permanent memory, approve facts, publish a listing, make legal guarantees, or submit material outside the workspace.

Requests are limited in length and frequency at the application layer. Agents should still review all generated content, facts, disclosures, and compliance requirements before use.

AlpenGlow currently uses Supabase for authentication, workspace data, and file storage; Vercel for application hosting and runtime delivery; and Anthropic for requested AI-assisted generation and Creative Director responses. We do not currently process card payments inside AlpenGlow.

If you believe your workspace may have been accessed improperly, or discover a security issue, contact support@usealpenglow.com with the account email, affected listing if applicable, and a safe way to reach you. Do not include passwords or access tokens.