Privacy Policy

1. Introduction

Construct Computer (“Construct,” “we,” “us,” or “our”) operates a cloud-based work platform where each user receives an isolated workspace powered by an AI agent. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website at construct.computer, use our platform at beta.construct.computer, interact with your agent through Slack, Telegram, Discord, or the native agent inbox, or use any of our related services (collectively, the “Services”). By using the Services, you consent to the practices described in this policy.

2. Information We Collect

2.1 Account Information

When you create an account or join our waitlist, we collect:

• Your email address and name (provided directly or via Google OAuth)
• Google profile information if you sign in with Google, including your profile ID and avatar URL
• Any additional information you voluntarily provide, such as responses on our waitlist form

2.2 Workspace & Agent Data

When you use the Construct platform, the following data is created and stored within your isolated virtual environment:

• Workspace files - any files, documents, code, or other content you upload or that the AI agent creates on your behalf, stored in per-user Cloudflare R2 storage
• Chat & session history - conversations between you and your agent across supported surfaces (web desktop, Slack, Telegram, Discord, and agent inbox), stored in your per-user Cloudflare Durable Object
• Agent memory - long-term memory containing source episodes, versioned assertions, temporal context, and related entities. You can inspect, search, correct, forget, or restore memories from the Memories app
• Workflows - reusable procedures, published versions, run state, step results, and retry information
• Scheduled jobs - one-time and recurring agent tasks or workflow runs stored with their schedule and execution state
• Calendar - scheduled jobs, recurring rules, and run status used to coordinate background work
• Agent email inbox - each agent gets its own address at <agentname>@agents.construct.computer; incoming messages, threads, and sent replies are retained to provide thread state
• Activity history - agent, tool, system, delegated-work, and error events with timestamp, source, status, and reasons when available
• Access-control records - per-platform inbound policy, trusted-user list, and the approval queue for non-trusted senders

2.3 Integration Credentials

If you connect third-party services to your Construct environment, we store the credentials needed to maintain those connections:

• Composio connected accounts - OAuth tokens for any of the 1,000+ SaaS apps you connect via Composio (Google Workspace, Gmail, Slack, Notion, Linear, Jira, HubSpot, GitHub, Airtable, Dropbox, and more). Connection management, scopes, and refresh are handled through Composio.
• Direct integrations - Slack, Telegram, and Discord credentials and any OAuth tokens issued directly to Construct
• App Registry credentials - per-app auth (OAuth2, API key, Bearer, or HTTP Basic) for any app you install from the public Construct App Registry
• Bring-Your-Own-Key (BYOK) API keys - optional model provider keys (for example, OpenRouter) that you choose to use instead of our bundled provisioning

All integration credentials and BYOK API keys are encrypted at rest using AES-256-GCM (Web Crypto) and injected scoped per-call.

2.4 Billing & Subscription Data

If you subscribe to a paid plan, we store the subscription state (tier, status, period) and a customer identifier from our payments processor. Payment method details (card numbers, bank info) are never stored by Construct - they are handled entirely by our processor, Dodo Payments. We also record per-call usage (service, model, token counts, latency, and real dollar cost via Cloudflare AI Gateway) so you can view usage history and we can enforce plan and per-session limits.

2.5 Technical & Usage Data

• IP address (used for rate limiting and security purposes)
• Browser type and operating system
• Authentication tokens (JSON Web Tokens stored in your browser’s local storage)
• Aggregated analytics via PostHog, including per-LLM-generation events (token counts, latency, cost) used for observability and product improvement

3. How We Use Your Information

• Providing the Services - to operate your agent and sandbox, maintain your workspace, route inbound messages across surfaces, and facilitate the integrations you connect
• Authentication - to verify your identity via Google OAuth or magic-link email and manage your session
• Personalization - to enable your agent to remember preferences, context, and prior interactions across sessions and platforms
• Communication - to send you transactional emails (magic-link sign-in, usage notifications at 50/75/90/100% of budget, subscription events) and, with your consent, product updates
• Billing - to process subscriptions, meter usage against plan caps, and reconcile BYOK vs bundled cost
• Security & abuse prevention - to enforce rate limits, verify webhook signatures (Slack HMAC-SHA256, Telegram, Dodo Payments), detect unauthorized access, and protect infrastructure
• Improvement - to diagnose technical issues, monitor model behavior via aggregated analytics, and improve the Services

4. Third-Party Services & Data Sharing

We do not sell your personal information. Your data may be shared with or processed by third parties only in the following circumstances:

4.1 Services You Connect

When you choose to integrate third-party services with your Construct environment, data is exchanged with those services as necessary to provide the integration:

• Google - if you sign in with Google or connect Google Workspace tools, your account data, calendar events, and files are exchanged with Google’s APIs as needed
• Composio - manages OAuth and executes tool calls against 1,000+ SaaS apps you connect. Prompts, parameters, and returned results for tools you invoke are processed by Composio on your behalf
• Slack, Telegram & Discord - if you connect these services, messages, files, and metadata are processed to enable communication with your agent
• Model providers - prompts and conversations are sent to the model provider serving your plan. If you provide a BYOK OpenRouter key, model traffic is routed through OpenRouter - see OpenRouter’s privacy policy
• Composio Browser - powers interactive browser tasks. Target URLs and task inputs relevant to browsing are processed by Composio and streamed back to the work desktop
• Construct inbox - inbound messages, drafts, sent mail, and thread metadata are stored to provide native agent email
• Custom MCP and workspace apps - tool parameters and permitted network requests are processed according to each app's manifest and configured connection

4.2 Platform & Infrastructure

Construct runs on Cloudflare (Workers, Durable Objects, D1, R2, Sandbox SDK, AI Gateway). Data-at-rest and in-transit for platform state is handled by Cloudflare. Aggregated product analytics flow to PostHog. Application logs flow to Cloudflare Logs for observability.

4.3 Email & Payments

We use Resend to deliver transactional emails (magic-link sign-in, usage alerts). We use Dodo Payments to process subscriptions; Dodo holds payment-method data and sends us signed webhooks for subscription lifecycle events. Your email address is shared with these providers solely for these purposes.

4.4 Legal & Safety

We may disclose your information if required by law, regulation, or legal process, or if we believe in good faith that disclosure is necessary to protect the rights, safety, or property of Construct Computer, our users, or the public.

4.5 Business Transfers

In the event of a merger, acquisition, reorganization, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change.

5. Data Storage & Security

We take the security of your data seriously and implement the following measures:

• Per-user isolation - each user runs on a dedicated Cloudflare Durable Object with its own SQLite state and a dedicated Cloudflare Sandbox (Docker) container. Workspace data is separated at the storage layer, not at the application layer
• Encryption at rest - OAuth tokens, BYOK API keys, and app credentials are encrypted with AES-256-GCM (Web Crypto) before being written to D1, and decrypted only at call-time
• Resource & budget limits - each container has CPU, memory, timeout, monthly, and per-session limits based on the active plan
• Rate limiting - authentication endpoints, app calls, and API routes are rate-limited to prevent brute-force and resource-abuse attacks
• Webhook verification - Slack HMAC-SHA256 signatures with a 5-minute replay window, Telegram bot-token verification, and signed Dodo Payments events
• JWT authentication - sessions are managed via signed JSON Web Tokens with configurable expiration
• Role & access control - inbound senders on Slack, Telegram, and Discord are tagged OWNER, TRUSTED, GUEST, or BLOCKED before the agent ever sees the message, and non-trusted senders go to an approval queue

Despite these measures, no system is completely secure. We cannot guarantee absolute security of your data.

6. Metered Usage and Bring Your Own Key

Construct supports two billing modes, which you can mix per request:

• Bundled (default) - your plan includes model usage subject to monthly and per-session limits. Usage is metered and is visible in your account’s usage history
• BYOK - on Pro, you may provide your own API keys (e.g. OpenRouter). BYOK traffic is billed directly by the provider, does not count against your bundled budget, and is used solely to make requests on your behalf. We do not monitor, log, or retain the content of provider responses beyond what is needed to display results and maintain conversation context

7. Data Retention

We retain your data as follows:

• Account data - retained for as long as your account is active. You may request deletion at any time
• Virtual desktop data - workspace files, agent memory, chat history, Activity history, Calendar, and agent email persist for as long as your account is active and are deleted when your account is closed
• Voice audio - not retained; only the transcript is saved to the conversation
• Webhook event IDs - retained briefly for idempotency and replay protection, then pruned
• Waitlist data - email addresses and responses are retained until you are granted access or request removal

8. Cookies & Local Storage

The Construct platform does not use cookies for user session management. Authentication tokens are stored in your browser’s local storage. We do not use third-party tracking cookies. An HTTP-only session cookie is used only for administrative access to internal dashboards and does not apply to regular users.

9. Your Rights

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you
• Correct inaccurate or incomplete data
• Request deletion of your account and all associated data, including your sandbox container, workspace files, memory, audit log, and agent email
• Inspect, search, and delete individual memories at any time from the Memory app
• Object to or restrict the processing of your data
• Withdraw consent for optional processing at any time
• Request a portable copy of your data
• Disconnect third-party integrations (Composio connections, direct OAuth, App Registry apps) through your account settings, which revokes stored credentials

To exercise any of these rights, please contact us - see our Support page.

10. Children's Privacy

The Services are not directed to individuals under the age of 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected data from a child under 13 without parental consent, we will promptly delete that information and terminate the associated account.

11. Autonomous Browsing & Third-Party Links

Our website and your workspace may contain links to third-party websites. The AI agent may also navigate to third-party websites on your behalf via the remote browser, extract content, or submit forms. We are not responsible for the privacy practices or content of those websites, and you are responsible for tasks you delegate to the agent. We encourage you to review the privacy policies of any third-party service you connect or visit.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page with a revised “Last updated” date. Your continued use of the Services after any changes constitutes your acceptance of the updated policy.

13. Contact Us

If you have any questions about this Privacy Policy or wish to exercise your data rights, please contact us at: support@construct.computer.