Privacy and data use

Contact and subscription information

When you contact us about Scale or Enterprise through the pricing form, we send your email, the page you came from, your interest category, and any referral identifier to GetWaitlist so we can follow up. The Contact page sends your name, work email, organization, plan interest, message, and submission time to a Cofr-managed contact workflow. That workflow stores the submission, notifies Cofr employees by email, and creates or updates a Cofr-managed CRM record. Growth subscription checkout is hosted by Stripe, which handles payment and billing information under its own terms and privacy practices.

Contacting us does not create an account or grant access. After a Growth checkout, create your Cofr account using the same email address.

Site analytics

On the production Cofr website and app, Google Analytics loads when a page opens to measure visits and selected conversion actions. The website code limits event parameters to sanitized page paths and approved campaign values; it does not send contact form contents, skill contents, prompts, outputs, API request logs, or risk-report identifiers as event parameters.

Google Analytics may also receive technical information from your browser, such as your IP address and device details. Email hello@cofr.io with questions about Cofr's use of analytics.

Cofr uses FirstPromoter to track affiliate referrals. FirstPromoter may use browser identifiers to attribute visits; when available, its tracking ID is passed to Stripe when you start a Growth checkout.

Hosted-service information

Hosted tool calls may include user-provided input and results from connected systems. For prompt tools, Cofr stores clipped user input and output in invocation history. For connected tools, the invocation input log records argument names and string lengths rather than argument values, while output text is clipped and stored. Usage metadata is recorded separately. A prompt plugin also sends its vaulted instructions and tool input to OpenAI through its API; a connected tool calls its configured connection without that Cofr model call.

Cofr's per-tool memory write settings apply to prompt execution and default to off. Some prompt calls can read existing client and person records even when those write settings are off. Connected services may keep their own records under the specialist's configuration. See Data Processing for more detail.

Questions and requests

Email hello@cofr.io to initiate an access, correction, or deletion request. Cofr's team handles these requests manually and may need to verify your identity and identify the relevant records before taking action. If your request concerns information handled by a specialist's product, you can also contact that specialist directly.