Forge privacy and data handling
This page summarizes how Forge handles account, workspace, source, and reviewed knowledge data. Use only approved, low-risk business documents unless a separate written handling path is in place.
Account and workspace data
Forge stores account identity from the authentication provider, workspace membership and role data, invite/request records, and account-activity records needed to run the service.
Source and knowledge data
Forge stores source records, source hashes, extracted text when allowed, evidence quotes, reviewed knowledge, processing history, usage events, and export records.
Raw file posture
Forge is not a long-term raw-document vault by default. Uploads can be removed after processing, and external/customer-controlled source references can remain the system of record.
Operational logs
Forge records lightweight usage and account-activity events for upload, processing, review, export, access denial, rate-limit, provider failure, invite, signup-request, and deletion activity.
Deletion
Users can delete individual documents from the app. Document deletion removes extracted text, knowledge items, evidence, review tasks, and processing history tied to that document; account-activity and deletion records may remain.
Third-party services
Forge may use Clerk for authentication, Vercel for hosting, Neon/Postgres for data storage, Stripe for billing, and AI providers for optional processing paths.