1. What Jumpr Is

Jumpr is a technical integration tool. Its purpose is to receive events sent through Meta's official API via webhooks, validate those events, normalize them, and forward them to the Odoo Online webhook configured by the user.

Jumpr is not a CRM, does not interpret business rules, does not decide whether leads should be created or updated, does not communicate with end users, and does not access complete conversation histories.

2. Information We Collect

From Jumpr administrator users, we may collect:

• Name.
• Email address.
• Profile picture.
• Google identifier.
• Session information required for secure authentication.

Jumpr uses Google OAuth for authentication. We do not store passwords.

For each configured integration, we may store:

• Integration name.
• Connected channel: Messenger or Instagram.
• Meta App ID.
• Encrypted App Secret.
• Encrypted Access Token.
• Verify Token.
• Odoo webhook URL.
• Odoo Company ID, if configured.
• Integration status.

From events received from Meta, we may process:

• Channel.
• Event type.
• Sender ID.
• Recipient ID.
• Message ID.
• Message text, when provided by Meta.
• Attachments or event metadata, when provided by Meta.
• Timestamp.
• Message echo indicator, when applicable.
• Sender name or username when Meta makes it available and the authorized permissions allow access to it.

If Jumpr cannot obtain the sender's name or username, those fields are not sent to Odoo.

3. How We Use Information

We use information only to:

• Authenticate administrator users.
• Allow integrations to be configured.
• Validate Meta webhooks.
• Verify security signatures.
• Normalize events received from Messenger and Instagram.
• Enrich events with a name or username when Meta makes that information available.
• Forward events to the Odoo webhook configured by the user.
• Record delivery status, technical errors, and attempts.
• Maintain security, auditing, and operational diagnostics.

We do not use this data for advertising, profiling, data sales, scoring, model training, surveillance, or purposes unrelated to the operation of the integration bridge.

4. Data Retention

Jumpr applies data minimization principles.

The complete payload received and forwarded may be temporarily stored in Cloudflare KV solely for debugging and operational purposes. By default, this content automatically expires after 72 hours.

Operational delivery metadata may be stored in Cloudflare D1 for technical auditing purposes, including:

• Date.
• Channel.
• Event type.
• Status.
• HTTP status.
• Number of attempts.
• Technical error, if any.

Integration credentials are retained while the integration remains active and are deleted when the user deletes the integration, unless retention is required by law or for legitimate security purposes.

Cached Meta profile information, such as a name or username, may be stored temporarily to avoid repeated requests to Meta. Jumpr does not guarantee the availability of this information and may omit it when unavailable.

5. Data Sharing

Jumpr shares data only with services required to operate the platform:

• Cloudflare — hosting infrastructure, database, KV storage, and serverless execution.
• Google — OAuth authentication for administrator users.
• Meta — source of events and provider of the official APIs used by Jumpr.
• Odoo Online — destination configured by the user.

Jumpr does not sell personal data or share information with advertisers or data brokers.

6. Security

Jumpr uses reasonable security measures, including:

• HTTPS.
• HttpOnly session cookies.
• Meta signature validation.
• Encryption of stored secrets and access tokens.
• Separation of persistent metadata and temporary payloads.
• Limited retention of message content.
• Restricted access to administrative functions.

No system is completely infallible, but Jumpr is designed to minimize the exposure of sensitive data.

7. User Responsibilities

Users who configure Jumpr represent that they are authorized to connect the corresponding Meta accounts, Pages, Instagram accounts, and Odoo webhooks.

The user is responsible for the logic implemented within Odoo Online, including the creation, updating, deletion, or processing of leads, contacts, opportunities, or other records.

8. Data Subject Rights

Individuals may request access, correction, updating, or deletion of their personal data when applicable under relevant law, including Argentina's Personal Data Protection Law No. 25,326.

For privacy or data deletion requests, contact:

[email protected]

9. Meta Data Deletion

If an individual wishes to request the deletion of data related to Messenger or Instagram processed by Jumpr, they may contact [email protected] and provide the relevant account, Page, channel, or identifier.

Jumpr will delete or anonymize applicable data that it retains, except where minimal information must be preserved for legal obligations, security, abuse prevention, or dispute resolution.

10. Changes to This Policy

We may update this Privacy Policy to reflect legal, technical, or operational changes. The current version will be published on the official Jumpr or Logic Omnipresence website.