AutoPulse Privacy Policy

This Privacy Policy explains how AutoPulse ("AutoPulse", "we", "us", or "our") processes information when a monday.com account installs or uses the AutoPulse app. AutoPulse helps teams monitor important monday.com workflows and create incident records when expected work is missing.

AutoPulse is operated by Khalil Oueslati. If AutoPulse is later submitted under a company or other legal entity, this policy will be updated to match that entity.

Who this policy applies to

This policy applies to monday.com users and accounts that install or use AutoPulse, website visitors, and people who contact AutoPulse support. If you use AutoPulse through your employer or organization, that organization may also control how your monday.com data is used.

Information AutoPulse processes

AutoPulse processes only the information needed to provide the app:

• monday.com account, user, board, column, item, webhook, and feature identifiers.
• Rule settings, such as source board, trigger column, trigger value, target board, match column, delay, severity, incident board, and notification recipients.
• Limited board data needed to run a check, such as item names and selected column text used to find a matching item.
• Incident data, including summary, severity, status, occurrence count, timestamps, check result, and related monday.com item references.
• Support information you choose to send us, such as your name, email address, account details, screenshots, and support messages.
• Technical logs needed to debug service issues, such as request timestamps, app errors, account identifiers, and non-sensitive diagnostic events.

Information AutoPulse does not need

• AutoPulse does not need monday.com passwords.
• AutoPulse does not collect payment card details. Marketplace payments are handled through monday.com billing.
• AutoPulse does not use customer data for advertising.
• AutoPulse does not currently use AI or large language models to process customer data.
• AutoPulse does not send direct outbound email alerts in the initial marketplace version.

How AutoPulse uses information

We use information to:

• Create, pause, resume, test, and delete watchdog rules.
• Receive monday.com webhook events for configured source boards.
• Run delayed checks and confirm whether the expected matching item exists.
• Create and update monday.com incident board items.
• Send monday.com notifications to selected recipients.
• Show dashboard health, recent incidents, and weekly digest information.
• Enforce subscription limits and provide customer support.
• Protect the app, debug errors, prevent duplicate incidents, and maintain service reliability.

monday.com access and OAuth scopes

AutoPulse requests only the monday.com permissions needed to operate the app. The exact scopes shown during install may depend on the app version, but they are used to read board metadata, read relevant item data, create and update incident items, create webhooks for configured rules, and send monday.com notifications. AutoPulse does not use those permissions to access unrelated boards except where the user selects boards in the app.

Storage and hosting

The production app is designed to run on monday Code and use monday-compatible storage for account data, rules, pending checks, incidents, settings, and digest state. Local SQLite storage is used only for development. Production secrets are stored as monday Code environment variables or secrets, not in client-side code.

Tokens, secrets, and access controls

AutoPulse validates monday session tokens for app requests and isolates data by monday.com account. monday.com API tokens, signing secrets, and client secrets must be stored server-side. AutoPulse does not expose those secrets in browser code. Access to production configuration should be limited to authorized maintainers.

Third-party services

AutoPulse currently uses:

• monday.com APIs, monday Code hosting, monday SDK, and monday marketplace billing to provide the app.
• The public website host or CDN used to serve this website and legal pages.

If future versions add transactional email, analytics, or other third-party services, this policy will be updated before those services process customer data.

Cookies and tracking

The AutoPulse website does not require tracking cookies for core pages. The AutoPulse monday.com app uses monday.com session token authentication for app requests. If analytics or tracking cookies are added later, they will be disclosed and handled according to applicable consent requirements.

Data sharing

We do not sell personal data. We share information only as needed to provide AutoPulse, comply with law, protect the service, process support requests, or work with service providers that help operate the app.

Retention and deletion

AutoPulse keeps rule, check, incident, settings, and diagnostic records while needed to provide the service, maintain account history, and support customers. Users can delete rules and resolve or ignore incidents in the app. If AutoPulse is uninstalled or deauthorized, deletion or retention will follow monday.com marketplace requirements, applicable law, and any explicit agreement with the customer.

Security practices

AutoPulse uses account isolation, server-side token verification, webhook idempotency keys, input validation, HTTPS-only deployment, and server-side secret storage. See the Security page for more detail.

Your privacy choices

Depending on your location, you may have rights to request access, correction, deletion, export, or restriction of personal data. To make a request, contact support@autopulse.solutions. We may need information to verify the request and identify the relevant monday.com account.

Children

AutoPulse is intended for business use and is not directed to children.

Changes to this policy

We may update this Privacy Policy as AutoPulse changes. The "Last updated" date will show when the latest version was published.

Contact

Email: support@autopulse.solutions
Website: https://www.autopulseapp.com/