How Crawl Foundry handles access and customer data.

The authenticated application uses Clerk for identity and session management. Protected application access requires an authenticated user.

Workspace data is protected by organization and workspace access checks. In signed-in product flows, public database functions derive organization context from authenticated access instead of accepting a client-provided organization ID as proof.

Organization and workspace roles determine what a member can read or change. The server performs the decisive checks; hiding or showing an interface control is not treated as access control.

Uploaded documents and derived content are assigned to a workspace. Access to them is subject to the same workspace boundaries as the surrounding product data.

AI features run through a controlled internal layer that binds every call to user, organization, and workspace context and makes scope and cost traceable. Feature code does not talk to models directly.

Crawl Foundry uses contracted infrastructure and service providers to operate authentication, storage, databases, billing, analytics, and selected product data workflows. Categories and purposes are listed in the privacy policy.

Credentials and API keys are kept server-side. The shared logging layer is configured to redact sensitive fields. The contact route records delivery status, topic, and errors, but not the message body.

The repository treats changes to authentication, permissions, billing, and public interfaces as security-sensitive work. Those changes require focused review and tests that match the risk of the affected boundary.