Privacy Policy

We collect the information needed to run your account, projects, integrations, and publishing workflow. This can include your name, email address, authentication details, project names, project websites, account settings, connected social account metadata, API key metadata, content payloads, media URLs, publish destinations, delivery status, and operational logs.

When you sign in with Google or connect a social platform, we receive the account information and permissions that platform makes available for the connection you approved. We do not ask for permissions that are unrelated to receiving, preparing, or publishing content through zedgad.

We use account and project data to authenticate you, create workspaces, receive content from your websites or backend systems, display publishing history, route content to connected channels, troubleshoot failed posts, prevent abuse, and improve the reliability of the service.

We may use aggregated, non-identifying usage patterns to understand which product areas need better performance, documentation, or safeguards. We do not sell your personal information.

Project API keys are secrets. Full keys are shown once at creation, then stored in a protected form for verification. Keep them in server-side environment variables and rotate them if they are exposed.

Webhook payloads may contain titles, summaries, article bodies, images, videos, links, tags, categories, or other content fields supplied by your system. You are responsible for making sure the content you send to zedgad is lawful and appropriate for the platforms where you publish it.

zedgad stores the tokens and metadata required to publish to social accounts you connect, such as Facebook Pages or other supported destinations. We use these connections only to provide the publishing features you request, show connection status, and diagnose platform errors.

You can disconnect a social account from zedgad, revoke access from the social platform itself, or remove a project when you no longer want zedgad to use that connection.

When you sign in with Google or connect a Google-owned service such as YouTube to zedgad, we may receive the Google user data that you authorize through the Google OAuth consent screen. This may include basic account profile information for sign-in and YouTube channel information, permissions, access tokens, refresh tokens, and related metadata for YouTube publishing integrations.

We use Google user data only to provide the features you request, authenticate your account, maintain your Google or YouTube integration, publish content to destinations you connect, show connection status, troubleshoot platform errors, maintain security, and operate the relevant zedgad services.

zedgad does not sell Google user data. We do not share, transfer, or disclose Google user data to third parties except to trusted service providers that process data on our behalf only as necessary to operate zedgad and subject to confidentiality and security obligations; at your direction when you explicitly instruct zedgad to perform an action that requires sending data to a connected service or destination; or when required by applicable law, legal process, or when reasonably necessary to protect the security, rights, and integrity of zedgad, our users, or others.

Google user data is not used for advertising purposes and is not shared with third parties for advertising, profiling, or unrelated marketing purposes.

Our use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including the Limited Use requirements.

We keep account, project, content, and publish log data for as long as needed to provide the service, maintain security, resolve disputes, and comply with legal obligations. Some diagnostic records may be retained after deletion where they are necessary for abuse prevention, auditability, or platform compliance.

We retain Google user data only for as long as necessary to provide the requested integration, maintain security, comply with legal obligations, resolve operational issues, or support platform compliance.

If you want account or project data removed, contact us with enough detail to identify the account and project. We may need to verify ownership before completing a deletion request. You may also disconnect your Google or YouTube account from zedgad or revoke zedgad's access through your Google Account settings.

We use reasonable technical and organizational safeguards to protect account access, API keys, integration tokens, and publishing records. No internet service can guarantee perfect security, so you should use strong passwords, protect your email account, and limit API key access to trusted server environments.

If you believe your account, API key, or connected social account has been compromised, rotate the affected credentials and contact us promptly.

We may update this policy as zedgad adds features, integrations, billing, or operational safeguards. When the changes are material, we will make the updated policy available on this page and may provide additional notice inside the product or by email.