Privacy policy
Who we are
CoFigure (cofigure.ai) is a beta of a multi-agent AI workspace, run by its owner-operator. Questions, requests, or complaints: support@cofigure.ai.
What we store
- Account data — your email address, name, and sign-in records (magic-link, Google and Apple sign-in are handled by our auth system; we do not receive your Google or Apple password).
- Conversations — everything you and the AI agents say in your rooms, plus the room and agent configuration you create.
- Context and memory — project briefs and preferences you write, bounded room summaries, source-linked notes learned from discussions, and agent participation.
- Files and artifacts — documents and images you attach, and documents agents produce for you. Stored in Cloudflare R2 object storage.
- Usage records — per-generation token counts and costs. This is how we meter the beta's spending caps.
- Feedback and operational logs — thumbs/notes you submit, support requests, and server logs (which carry ids and timings, not message content).
- Administrative records — records of account actions, including email addresses and support, ban or abuse-related notes, for support and account enforcement.
- Trial-abuse records — hashed trial identifiers derived from your email, provider sign-in identity and, when available, IP address, plus claim amounts and dates.
Who can see your rooms
Your rooms are private to your account — no other user can ever see them. Conversation content never reaches our analytics provider, never trains a model, and is never shared, quoted, or published. Room contents may be reviewed to resolve a support request you sent, to investigate abuse or a security problem, to meet a legal obligation, and — while CoFigure is in beta — to improve the product. Every access is individually logged.
Where AI processing happens
Unsent message drafts are saved on your device and periodically to your account so you can resume on another device. Draft text is not sent to AI providers until you send the message. We keep up to five recent draft versions for seven days; the current draft stays until you send, clear it, or delete its room or account.
When agents reply, your conversation content is sent to third-party AI model providers through our gateway. We route inference only to US- or EU-hosted providers, and we require no-training data policies where our router exposes them — meaning those providers agree not to train models on your prompts. Inference is never routed to PRC-hosted endpoints, including for open-weight models originally released by Chinese labs (we use US/EU hosts of those models instead). We do not train AI models on your content, and we do not sell your data.
No-training does not mean that a provider keeps no records. Provider retention depends on the model and service. Claude Fable 5.1 requires providers to retain request and response data for 30 days unless Anthropic grants an exception. Choosing Fable sends the conversation context needed for its reply under that policy.
Each request to a provider carries a one-way hashed account identifier — never your name, email or conversation content — so that a provider's safety enforcement can apply to one account rather than to every CoFigure user. For Anthropic, that identifier is registered as a per-user profile holding nothing else; the profile is deleted when your account is deleted.
We also use AI providers for occasional background summaries and learned project notes. Selected context from your account and relevant project rooms can accompany future agent replies. Project context, personal preferences and agent notes can be inspected, edited, disabled or cleared in the app; clearing context does not delete the original conversations.
Product analytics
We use PostHog for explicit product-use metrics and error counts. Session replay and automatic click-text collection are disabled. App analytics carry identifiers and reviewed product choices, not conversation content, email addresses, page-query values or raw exception messages.
We also measure whether visits from our ads lead to signup or first product use, and may report those two outcomes to the ad platform so we can understand which ads work. We do not use this to profile you or personalize ads, and do not send your name, email, or conversations.
Where your data lives
The application and database run on Railway (US region). Files live in Cloudflare R2. Sign-in emails are sent through Resend. Encrypted nightly database backups have a retention window of 14 days; removal happens through scheduled cleanup.
Your rights: export and delete
You can ask for a copy of your data or deletion of your account at any time. During the beta these requests are fulfilled by the operator by hand — email support@cofigure.ai and we will confirm within 7 days.
Account deletion removes your rooms, conversations, context and memory, account-linked support submissions and sign-in data from the live database. Attached files and generated documents are queued for deletion from object storage, with retries if storage is temporarily unavailable. Copies in database backups expire under the retention window above.
Records retained after account deletion
- Financial and usage history. We remove account links but keep amounts, token counts, dates and Stripe transaction references for accounting, refunds and payment reconciliation. Retaining transaction references means these records are not guaranteed anonymous.
- Trial-abuse history. We retain the hashed trial identifiers, claim amounts and dates to prevent repeated free-trial claims. Hashing does not make these records anonymous.
- Administrative history. We retain account-action records, including email addresses and support, ban or abuse-related notes, to handle later support requests and maintain enforcement history. This is separate from the conversations and account-linked support submissions removed above. Support requests submitted while signed out are not automatically linked to an account; identify those requests when contacting us about deletion.
These retained records do not automatically expire. You can contact us about access, correction or deletion of retained information; we review such requests against the support, abuse-prevention and financial purposes above and applicable requirements.
Changes
This is a beta and this policy will evolve. We will update this page and bump the version line when it does; material changes will be announced to active users by email.