Privacy Policy

Effective Date: 2026-09-04

This policy explains how Daoco ("Daoco," "we," "us," or "our") processes information when you use daoco.org and the related application (the "Service").

Information we collect

• Account and workspace data: name, email address, authentication identifiers, workspace and membership records, roles, and account preferences.
• Customer content: prompts, messages, uploaded files and media, brand information, generated content, drafts, campaigns, and feedback you submit or create.
• Connected-service data: account identifiers, authorization credentials, imported content, and publishing results from services you choose to connect.
• Operational and usage data: IP address, browser and device information, timestamps, page and feature interactions, diagnostics, security events, and, inside the authenticated product, session recordings.
• Billing data: plan, usage, subscription, and transaction information. Payment card details are handled by our payment processor and are not stored by Daoco.

How we use information

• Provide, secure, support, and troubleshoot the Service.
• Generate, store, and publish content at your direction.
• Authenticate users and enforce workspace access controls.
• Process subscriptions, meter usage, and prevent abuse.
• Understand product performance and improve the Service using operational and product analytics.
• Comply with law and enforce our agreements.

AI processing and training

An AI request may include your prompt, relevant conversation and brand context, files or images, and generation settings needed to produce the requested output.

• Text and multimodal model requests are routed through OpenRouter to a selected model endpoint. Current model families may be operated by OpenAI, Anthropic, or Google.
• Daoco sends request-level OpenRouter controls that require a zero-data-retention endpoint and deny routing to providers that may collect request data. The no-retention claim applies only when OpenRouter private input/output logging and the separate Inputs/Outputs use setting are both disabled.
• Image and media inference may be processed by fal. Daoco disables storage of fal request and response JSON and requests a one-hour expiration for generated media on fal's CDN. Media copied into Daoco storage is then governed by Daoco's retention rules.
• Daoco does not use Customer Content to train, fine-tune, or evaluate shared AI models unless you give separate, explicit written permission. Product feedback and de-identified operational metrics may be used to improve the Service.

Product improvement and your choice

Workspace owners and admins decide whether Daoco may use the workspace's prompts, generated outputs, and agent activity to improve the Service. The Help improve Daoco setting in Workspace settings is on by default and can be turned off at any time.

• On: we may review prompts, outputs, tool activity, and ratings from the workspace to diagnose problems, evaluate quality, and improve how the product plans and executes marketing work. This data stays inside Daoco and its infrastructure providers; it is not sold or shared as a dataset.
• Off: diagnostics keep only identifiers, timings, token counts, decisions, and error classes. Prompts, outputs, and tool arguments are not captured. We still record that an error happened, in which runtime and when, so that we can support you.

This setting does not change how OpenRouter requests are made. Daoco asks OpenRouter for a zero-data-retention endpoint and denies routing to providers that may collect request data.

Anonymized agent data after deletion

When you delete a brand, a workspace, or your account, you can choose to let Daoco keep an anonymized record of the agent's work. The choice starts from your workspace's Help improve Daoco setting and is shown on every deletion confirmation. If you keep it, Daoco keeps two things under a random key that is not linked to you, your brand, or your workspace:

• How the agent worked: which runtime handled a request, which tools ran and in what order, how the run ended, and any rating you gave. Titles, notes, and references to your content are cleared.
• A redacted copy of the conversation: messages exchanged with the agent after a redaction pass that removes the brand and product names, the names and emails of workspace members, connected-account handles, and anything matching an email address, link, @handle, phone number, IP address, long number, or credential. Tool inputs and outputs are not kept, only the names of the tools used. If a conversation cannot be read and redacted, it is deleted instead.

Redaction is deterministic and versioned, and each retained record says which rules produced it. It reduces but does not eliminate the chance that a free-text sentence describes a person or business in a way that could be recognised; we treat retained records as confidential and use them only to improve the Service. Leave the option off and this data is deleted with everything else.

Service providers

Our current core subprocessors and their functions are:

• WorkOS: authentication, sessions, users, workspaces, and memberships.
• Convex: application database, server functions, scheduled work, and file storage.
• OpenRouter, with selected endpoints operated by OpenAI, Anthropic, or Google: AI inference.
• fal: image, vision, and media inference.
• Cloudflare: object storage and media delivery.
• Browserbase and Firecrawl: web browsing and extraction that you request.
• PostHog: product analytics, session recording, diagnostics, and error monitoring.
• Autumn and Stripe: billing, subscriptions, and payments.
• Resend: transactional email.

A connected social, commerce, productivity, or publishing service is also a recipient when you ask Daoco to read from or write to that service. We may update this list when our processing changes and will update the effective date for material changes.

Messaging platform assistants

If you connect a Daoco assistant to a messaging platform such as Slack, Discord, Telegram, Microsoft Teams, or WhatsApp, we process the messages directed to that assistant so it can respond and carry out the work you ask for. This can include the message content, the sending account's identifier and display name, and the channel or conversation identifier. We use this data to run the requested work in your workspace and to report results back to you in that conversation, and we store it with your workspace so you can review the resulting threads. Disconnecting the channel stops future access. You can request deletion of stored assistant conversation data by contacting support@daoco.org.

Google user data

When you connect a Google account, Daoco accesses only the Google data covered by the permissions you approve. Depending on the connection, this may include Gmail messages and drafts, Drive files and Google Docs, Calendar lists and events, Google Analytics and Search Console reporting data, YouTube channel data, and basic Google account profile information used for sign-in. Daoco accesses this data when you connect the account and when you ask the Service to use a connected Google feature.

We use Google user data to provide the features you request, such as finding and summarizing messages or files, composing Gmail drafts, creating or editing files and Google Docs, checking calendar availability and events, and preparing analytics and search reports. Google user data included in your prompts, tool results, or saved work may be stored with your Daoco account so you can review and continue that work. OAuth credentials are retained while the connection is active. You can stop future access by disconnecting the Google connection or revoking access in your Google Account. You can request deletion of stored account data by contacting support@daoco.org.

We do not sell Google user data, use it for advertising or credit decisions, or allow people to read it except with your explicit consent, when needed to investigate security or abuse, or when required by law. We share Google user data only with service providers acting on our behalf when needed to deliver the feature you requested, operate and secure the Service, or comply with law. Those providers may not use the data for their own purposes.

Daoco does not use Google Workspace data to create, train, or improve generalized or shared artificial intelligence or machine-learning models. Daoco's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. See the Google API Services User Data Policy.

Reddit data

If you register a public Reddit post or comment with Daoco, or ask Daoco to monitor public Reddit conversations about your brand, we may use Reddit's approved, read-only API access to retrieve those specific public threads, their engagement metrics, and public replies. We use this information only to provide post analytics, mention monitoring, and reply notifications for content you registered or topics you asked us to watch. Daoco does not use Reddit API data to vote, post, comment, send private messages, target advertising, build user profiles, infer sensitive characteristics, or train machine-learning or AI models.

We store only the identifiers, metrics, and limited reply excerpts needed to provide these features. Public reply excerpts are retained for no more than 30 days. We remove stored Reddit-derived content sooner when you delete the associated Daoco data, or when Reddit reports that the content is unavailable, and we delete it when our authorized access ends. Reddit content may be processed by infrastructure providers acting on our behalf solely to operate the Service; it is not sold, licensed, or redistributed as a dataset.

Retention and deletion

• Account, workspace, and Customer Content remain in active Daoco systems while your account or workspace is active, unless you delete a record or submit a verified deletion request.
• A brand deletion starts an asynchronous deletion of the Daoco-controlled brand records and files in the schema-audited active-system registry. Workspace and account owners can also start verified deletion from the data deletion page. The receipt records workflow status, rows deleted, rows anonymized, and explicit exceptions; it is not proof that a third party has physically erased its security, billing, or backup records.
• Anonymized agent data is kept after deletion only when you choose to keep it, as described above. Account deletion also removes your product-analytics profile and its events; if the analytics provider's deletion API is unavailable at the time, the receipt records that as an exception and we complete it by hand.
• Daoco configures PostHog and Convex operational log retention for up to 30 days. Logs are minimized and scrubbed, but may contain identifiers, event metadata, and diagnostic details.
• Billing, fraud-prevention, security, audit, and legal records may be retained after a deletion request where required for legitimate business or legal purposes. Access to those records is restricted.
• Provider backups and immutable logs cannot always be selectively erased. They age out under the provider's applicable retention schedule and are not restored to active use after deletion.

Brand deletion does not automatically delete your WorkOS identity, shared workspace, billing history, analytics history, or records held by a connected service. See the data deletion page for scopes, limitations, and self-service account or workspace deletion.

Cookies and analytics

We use cookies and similar storage for authentication, security, preferences, and analytics. On our public pages — the home page, blog, legal pages, and the sign-in, invite, and connection hand-offs — we record page views only: no session recording and no automatic capture of clicks or form interactions.

Inside the authenticated product we capture product events, automatic interaction events, and session recordings, and we use them to troubleshoot problems and improve the Service. Recordings mask the text you type: all form input values, the chat transcript and message box, and brand context and brand document fields are replaced before the recording leaves your browser. Other on-screen text and images are recorded. Do not enter sensitive personal information that is not needed to use the Service.

The Help improve Daocosetting governs whether we keep and review the workspace's prompts, outputs, and agent activity. It does not switch this product analytics off. To stop analytics collection entirely, use your browser's tracking controls or email support@daoco.org.

Security

We use access controls, encryption in transit, service-provider security controls, and monitoring intended to protect information. No system is completely secure, and we cannot guarantee absolute security.

Your choices and rights

Depending on your location, you may have rights to access, correct, export, restrict, object to, or delete personal information. Workspace owners and admins control the Help improve Daoco setting and the deletion choices for Customer Content submitted through their workspace. Submit a request through our data deletion process or email support@daoco.org. We will verify your identity and authority before acting.

Changes and contact

We may update this policy as our Service changes. We will post the revised policy here and update the effective date. Questions can be sent to support@daoco.org.