How BlendDuck handles product data
BlendDuck helps teams connect social accounts, create content, schedule posts, and operate AI-assisted publishing workflows. This policy explains the data we collect to provide those services.
This page is a product-facing privacy summary for BlendDuck. Enterprise agreements, data processing terms, and platform provider terms may add separate obligations.
Information We Collect
- Account details such as name, email address, avatar, authentication provider, and workspace membership.
- Connected-channel metadata such as account names, provider identifiers, OAuth scopes, token status, and publishing capabilities.
- Content data such as drafts, schedules, media references, brand knowledge, chat history, and publishing status.
- Operational data such as usage events, billing state, errors, security logs, and device or browser metadata.
How We Use Information
- To authenticate users and keep workspaces scoped to the right team.
- To generate, review, schedule, publish, and measure content across connected platforms.
- To maintain API, MCP, dashboard, billing, storage, and support workflows.
- To protect the service from abuse, debug failures, and improve reliability.
Connected Platforms
When you connect a social account, BlendDuck uses the permissions granted by that platform to perform requested actions such as reading account metadata, uploading media, scheduling posts, publishing posts, or retrieving status. You can revoke connected platform access from the platform or from BlendDuck where supported.
Service Providers and Disclosures
BlendDuck may use infrastructure, authentication, payment, email, analytics, AI, storage, and support providers to operate the service. They receive only the information needed for their role and process it under their own terms and applicable agreements.
We may also disclose information when required by law, to protect users or the service, or as part of a financing, acquisition, reorganization, or sale where the recipient assumes the applicable privacy obligations.
Storage and Retention
BlendDuck stores workspace records in the configured database and media or attachments in the configured storage backend. Operational evidence follows declared retention classes and active legal holds; account and workspace erasure removes controlled application data unless a documented legal or paid-resource exception blocks the request.
Cookies and Product Analytics
BlendDuck uses essential cookies for authentication, security, and saved product state. Optional analytics or marketing technologies are controlled through the choices exposed by the deployment and are not required for core account access.
Security and International Processing
BlendDuck uses access controls, encrypted application sessions, and encrypted provider credentials to reduce risk. No online service can guarantee absolute security, so report suspected account or token exposure promptly.
Service providers and connected platforms may process information in countries other than your own. Where required, the operator of your BlendDuck deployment is responsible for selecting appropriate providers and transfer safeguards.
Your Choices and Requests
Authenticated users can export portable account data, record optional analytics or marketing choices, review request receipts, delete owned workspaces, and request account erasure from Dashboard → Settings. A verified request has a one-calendar-month response target. Active subscriptions, communication numbers, advertising campaigns, or legal holds must be resolved before erasure can complete.
Children and Policy Changes
BlendDuck is a business service and is not directed to children. Do not create an account or submit personal information if you are not old enough to consent to online services in your location.
We may update this policy as the product, providers, or legal requirements change. The date above identifies the current version, and material changes will be presented through an appropriate product or account notice when required.