Privacy Policy

This Privacy Policy describes how ChangelogGuard (“we”, “us”, “our”) collects, uses, and shares information when you visit our website or use our services (the “Service”). If you have questions, contact us at [email protected].

1) What ChangelogGuard does (context)

ChangelogGuard monitors public, official change signals for the WhatsApp Business Platform and turns them into structured alerts. Those alerts can be delivered to destinations you configure such as Slack, Jira, Email, or a Webhook endpoint.

Important: ChangelogGuard is not affiliated with Meta. We don’t require access to your repositories, and we do not ingest your WhatsApp message content to operate.

2) Information we collect

2.1 Information you provide

• Account details (such as name, email, company) when you sign up or contact us.
• Billing details (processed by our payment provider; we do not store full card details).
• Support communications (messages you send to us, including attachments/links you share).

2.2 Configuration data

To deliver alerts, we store configuration data such as:

• Alert destinations (e.g., Slack webhook URL, email recipients, Jira settings, webhook endpoint).
• Preferences (what alert categories you want, severity thresholds, routing rules).

2.3 Usage and technical data

Like most services, we collect basic technical information to keep the Service stable and secure:

• IP address (often in logs), device/browser type, and approximate location (derived from IP).
• Diagnostics and performance data (e.g., error logs).
• Event metrics (e.g., “alert sent” counts) for reliability and billing.

2.4 What we do not collect

• We do not scan your source code or require access to private repositories.
• We do not ingest WhatsApp message content (no chat text, no media payloads).
• We do not sell personal data.

3) How we use information

We use the information we collect to:

• Provide, operate, and maintain the Service (including sending alerts to configured destinations).
• Respond to support requests and communicate with you.
• Prevent abuse, fraud, and security incidents.
• Improve reliability, performance, and user experience.
• Process payments and manage subscriptions (through a third-party payment processor).

4) How we share information

We share information only in a few cases:

• With service providers that help us run the Service (hosting, email delivery, analytics, payments).
• With your configured destinations (Slack/Jira/webhook/email). This is the point of the Service: we send alert payloads and metadata to the endpoints you choose.
• For legal reasons if we are required to comply with a lawful request or protect rights/safety.

When we send alerts to your destinations, the content includes structured change information, timestamps, and a link to the official source. We do not include WhatsApp message content because we do not collect it.

5) Data retention

We retain information for as long as needed to provide the Service, comply with legal obligations, and resolve disputes. Typical examples:

• Account and configuration data: kept while your account is active.
• Alert history: retained based on plan limits and operational needs.
• Security logs: retained for a reasonable period to detect and investigate abuse.

6) Security

We use reasonable administrative, technical, and physical safeguards to protect information. No system is perfect; if you believe your account is compromised, contact us immediately.

If you store a Slack webhook URL or a webhook endpoint, treat it like a secret. Anyone with access could post messages to your channel/endpoint.

7) Your choices

• Access/Update: You can request access to or correction of your account information.
• Delete: You can request deletion of your account (subject to legal/operational retention requirements).
• Marketing: You can opt out of non-essential emails at any time.

8) Cookies and analytics

We may use cookies or similar technologies to operate the site and understand usage. If we use analytics, we aim to keep it privacy-conscious and avoid collecting unnecessary personal data.

9) International users

If you access the Service from outside the country where our servers are located, your information may be processed in that country. We take steps to protect information regardless of where it is processed.

10) Children’s privacy

The Service is not directed to children and we do not knowingly collect personal information from children.

11) Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we’ll update the “Last updated” date and, where appropriate, provide additional notice.

12) Contact

If you have questions or requests related to privacy, contact:

• Email: [email protected]
• General: [email protected]