Privacy Policy

Last updated: 15 November 2026

Who we are

Impulsis is developed and owned by CLEVER DEVELOPMENT LLC, a limited liability company incorporated in the state of New Mexico, USA (“Clever Development”, “we”, “our”, “us”).

Impulsis is a multi-channel campaign and messaging platform for WhatsApp, Email, and SMS, fully embedded in Zendesk. It allows Zendesk teams to launch campaigns, send proactive notifications, manage templates, automate outreach, and communicate with customers directly from the Zendesk agent workflow.

1) Scope & Roles

Scope

This Policy covers personal data processed when you use Impulsis within Zendesk, including campaign management, sidebar messaging, automations, template-based messaging, delivery tracking, and related support or billing communications.

Controller vs. Processor

For end-customer data connected to your Zendesk account, campaigns, tickets, contact lists, or messaging activity, you, the Zendesk account owner or organization using Impulsis, are the controller and Clever Development acts as your processor.

This may include data such as contact information, message content, campaign metadata, ticket references, delivery status, template variables, tags, notes, and operational logs.

For our own business records, such as billing, subscription management, product support, security, and account administration, Clever Development acts as the controller.

2) Data We Process

Inside Impulsis, as your processor

  • Contact and recipient identifiers: We may process customer names, phone numbers, email addresses, external IDs, Zendesk user IDs, Zendesk ticket IDs, tags, segments, and other identifiers required to send WhatsApp, Email, or SMS messages.
  • Contact base: Every message Impulsis sends on your behalf creates or updates a contact in your workspace: the recipient’s phone number or email address, their name when Zendesk or the WhatsApp profile provides one, their Zendesk user ID when the message was sent from a ticket, how the contact first reached the workspace (the panel, a spreadsheet, a campaign or an import), when it was first and last contacted, and how many messages it received by channel. The contact’s communication history is built from the messages themselves: what was sent, when, and what happened to it (delivered, read or opened, clicked, replied, bounced or failed). Nothing enters the contact base unless a message is sent to that person or you import them. An import, through Impulsis’s own template or through Clever Merge, can create contacts who have never received a message from you.
  • Imported contacts: Your workspace can import a spreadsheet through Impulsis’s own template, which only creates contacts. When your workspace and your company’s Clever Merge workspace are linked on the same Zendesk account, a Clever Merge admin, or an Impulsis manager through Clever Merge, can also import any spreadsheet or your Zendesk end users into your contacts. Only the columns mapped to contact fields are written: name, phone number, email address, external ID and the custom fields your workspace defines, including new ones created while mapping. An import through Clever Merge can also update contacts you already have, filling in what is empty or replacing values, as the person importing chooses; a name set by hand in Impulsis is not replaced. Each contact it creates records that import and the file’s name. As with any import, the legal basis for processing those people’s data is yours. A workspace admin can switch the link with Clever Merge off at any time in Settings › Connections, and a Clever Merge admin can do the same on their side; either stops imports at once, and contacts already written stay.
  • Zendesk as a source: Clever Merge can read your Zendesk end users with its own authorization, filtered by the tags, organization or user fields you choose. It reads name, email address, phone number, external ID, organization, tags and user fields, and never the `details` or `notes` fields. Those values are held under the time limits of the import (section 5). The contact keeps the Zendesk user ID.
  • Zendesk sync: When your workspace is linked with Clever Merge and the Zendesk sync is on (it is on by default when your plan includes it), Clever Merge forwards the changes to your Zendesk end users: users created, edited, merged or deleted, with their Zendesk user ID, name, email address, phone number and external ID. Impulsis applies them to the matching contacts under your workspace’s settings, which also say whether new end users become contacts; agents and admins are left out. When a Zendesk user is deleted, its contact loses the Zendesk user ID, keeps the rest and is marked with that user’s ID and the date of the deletion, and a workspace admin can delete the contacts so marked from the Contacts screen; a contact left without a phone number, email address or external ID is deleted.
  • Normalization: An import changes how a value is written (a phone number’s format, a lower-case email address), and may suggest a correction to an email address’s domain, but never changes a domain unless someone accepts the suggestion.
  • Probable duplicates: Impulsis lists contacts that are probably the same person, and nothing is merged until someone in your workspace merges them. A merge keeps one contact and takes the others out, keeping them whole for the undo (section 5); their phone numbers, email addresses, contact IDs, Zendesk user IDs and external IDs stay as aliases of the contact that stayed, so a later message or import to an old number or address lands on the same person instead of recreating the duplicate. When the merged contacts were two or more Zendesk users and your workspace is linked with Clever Merge, the group goes to Clever Merge as a suggestion, with each user’s Zendesk user ID, name, email address and phone number, why they were grouped and the name of the person who merged them; nothing changes in Zendesk until a Clever Merge admin confirms it.
  • Base cleanup through Clever Merge: When your workspace is linked with Clever Merge, a Clever Merge admin can read your contacts to propose three kinds of fix: a Brazilian phone number saved without its country code, a mistyped email domain, and a name that is only a phone number, which is removed. Only the fixes the admin reviews and applies are written, each only if the field still holds the value that was read. The old phone number or email address becomes an alias of the same contact, as in a merge.
  • Custom fields in a send: If you point a column of a spreadsheet send at a contact’s field, that value is kept on the contact until you change or delete it. Every other column stays in the send only.
  • Checking a send’s file: Before a spreadsheet send, Impulsis reads the file once more to count repeated and invalid numbers, numbers without their country code, Brazilian landlines, and numbers Meta reported as not on WhatsApp in your workspace’s own sends of the last 90 days; for email, it counts repeated and invalid addresses and asks Impulsis’s own email service which ones are suppressed. Only the counts are stored, with the file. If you choose to leave some of those rows out or to add the missing country code, the send stores that choice and how many rows it left out or corrected.
  • Tags, lists and segments: Tags and lists are names stored in your workspace, and each contact holds the IDs of its own; deleting a tag or a list takes it off every contact and deletes nobody. A saved segment stores its name and its filter, never a list of people, and is resolved again when a send uses it.
  • Communication facts: Each contact also keeps, per channel, the dates of the last message it was sent, had delivered, and read or replied to (WhatsApp) or opened and clicked (email), and the names of the last 20 templates it was sent, with their channel and date, so a segment can look further back than the 30 days message records stay in the active database. They are kept on the contact for as long as it exists.
  • Sends to a list or segment: A send to a list, a segment or a filter turns the matching contacts into a recipient file in the format of a spreadsheet send, with the values the template needs read from each contact, and a spreadsheet missing one of the template’s columns can be copied with that column filled from each row’s contact. Contacts left out for lack of a value go into a second file, with the values they have, for you to complete and send later.
  • Template variable bindings: A WhatsApp template’s variables can be bound to a field of the contact, the requester, the ticket or the organization. The binding stores the field’s name, never a person’s value, which is read when the message is sent.
  • Campaign data: We process campaign names, audience segments, scheduling information, templates used, message variables, sender/channel configuration, execution history, campaign status, and audit logs.
  • Message content: We process the content of WhatsApp, Email, and SMS messages, including dynamic template variables, customer-specific personalization fields, and messages sent from campaigns or directly from Zendesk tickets.
  • Template data: We process template names, template bodies, variables, approval/status information where applicable, and template usage history.
  • Zendesk ticket and workflow data: We may process Zendesk ticket IDs, ticket metadata, customer context, internal notes, tags, event logs, conversation references, and other Zendesk-related data required to provide the embedded Impulsis experience.
  • Delivery and engagement metadata: We process timestamps, sender and recipient information, message status, delivery status, failure reasons, retry attempts, channel provider responses, and other technical metadata needed to track and troubleshoot message delivery.
  • Automation and operational data: We process automation rules, triggers, execution logs, queue events, rate-limit controls, retries, and system events required to operate campaigns and proactive messaging reliably.
  • Operational logs: We maintain minimal technical logs to provide, secure, monitor, debug, and improve the service. These logs are never used for advertising.

Where content ultimately resides

Final conversation records, ticket context, notes, tags, and related customer data may reside in Zendesk or Zendesk Sunshine, depending on your Zendesk configuration.

Delivery copies and message metadata may also exist with the relevant communication providers, such as WhatsApp Business providers, email infrastructure providers, SMS providers, or telecommunications carriers, under their own policies and contractual obligations.

We do not disclose message content, contact lists, campaign data, or customer data to other companies for their own independent purposes, except where required by law or where service providers process data on our instructions to operate Impulsis.

Our business operations, as controller

We may process:

  • Account and billing details, such as company name, contact email, subscription status, plan information, payment status, and invoice records.
  • Support communications, including emails sent to [email protected] or other support channels.
  • Technical diagnostics, API logs, authentication events, and security logs used to maintain, protect, and troubleshoot Impulsis.
  • Administrative data related to product usage, onboarding, customer success, and service communications.

3) Lawful Bases

As a processor, we process customer and Zendesk-related data only on your documented instructions, in accordance with Article 28 of the GDPR and equivalent obligations under applicable data protection laws, including Brazil’s LGPD.

For our controller activities, we rely on:

  1. Contractual necessity, to provide and manage your subscription and access to Impulsis.
  2. Legal obligation, for billing, accounting, tax, and compliance purposes.
  3. Legitimate interests, for security, fraud prevention, service monitoring, support, debugging, and product improvement.

We do not sell personal data. We do not use customer message content, contact lists, Zendesk data, or campaign data for advertising.

4) How We Share Data

We only share data with vendors and service providers that help us operate Impulsis, such as:

  • Cloud hosting providers.
  • Database and infrastructure providers.
  • Logging, monitoring, and observability tools.
  • Email, WhatsApp, and SMS delivery providers.
  • Authentication, billing, support, and communication tools.

Each vendor is required to process data under confidentiality obligations and appropriate data processing terms aligned with GDPR, LGPD, and other applicable laws.

We may also disclose data if required by law, regulation, court order, government request, or where necessary to protect our rights, users, systems, or legal interests.

5) Storage & Retention

Data processed inside Impulsis is retained for as long as needed to provide the service, maintain campaign history, support auditability, troubleshoot delivery issues, and comply with your configuration, retention preferences, or contractual requirements.

Campaign records, message metadata, delivery history, template usage, execution logs, and Zendesk-related references may remain in your Impulsis workspace until deleted, exported, or otherwise managed according to your retention settings or instructions.

Contacts stay in your workspace until you delete them. A workspace admin can delete a contact at any time from the Contacts screen. The contact leaves every screen at once and cannot be restored; for a contact with many messages, unlinking it from those messages finishes in the background. The messages themselves stay in your workspace’s sending records, as described below, and a later message to the same phone number or address creates a new contact. Deleting a custom field, or removing an option from one, erases its values from your contacts in the background; it isn’t immediate, and it takes longer on a large base.

Message records are kept in the active database for 30 days. After that they move to a compressed archive in our storage provider, from which your exports and reports keep reading them. Aggregated counts used by your dashboards are kept separately and contain no personal data.

Spreadsheets for sends: The spreadsheet you upload to send messages is kept in our storage provider with that send’s records. It is not currently deleted automatically, and it is not changed when a person is removed from your sending records (section 8).

Files built from lists and segments: The recipient file a send to a list, segment or filter builds, the copy of a spreadsheet with a column filled from your contacts, and the file of contacts left out for a missing value are kept in our storage provider with that send’s records, like a spreadsheet you upload, and are not currently deleted automatically. While you prepare such a send, its counts are kept for 24 hours; the file of contacts missing a value that it offers for download stays in our storage provider and is not currently deleted automatically either.

Imports through Impulsis’s template: The file stays in our storage provider only until the import ends; if the import is waiting behind another one in your workspace, the file waits with it, and otherwise it is deleted within 3 days at most. The rows that weren’t imported go into a file you can download, which holds those rows’ values and is deleted after the number of days set for your workspace (2 by default, 30 at most).

Imports through Clever Merge: To show what changes on each contact, Clever Merge receives what the contacts matching the file hold today (name, phone number, email address, external ID, custom fields and Zendesk user ID) and keeps it with the import’s rows, under Clever Merge’s privacy policy: the rows are deleted within 72 hours, not counting any time the import waits behind another one on the same account, or sooner if a Clever Merge admin deletes the import. When an Impulsis manager starts an import through Clever Merge, their name goes to Clever Merge and stays in its import history for a year.

Import summaries and undo: Impulsis keeps a summary of each import for a year: the file’s name, who ran it, its phase and its counts, never its rows. While an import runs, and for 7 days after, we keep each row’s number, what happened to it and the contact’s ID, so a restart writes nothing twice; a row refused by a template import keeps its reason, and no values, in that record. To give values back if you undo an import, we keep what an import replaced on each contact for 72 hours after the import ends, and at most 7 days from when it was written. Each undo is recorded with who ran it, when and how many contacts it restored, and no data about the contacts themselves.

Contact exports are generated as CSV files in our storage provider, downloadable through a link that expires after 24 hours, and deleted after 2 days, or a longer period of up to 30 days if one is agreed with you.

Zendesk sync: Each batch of changes Clever Merge forwards, with the users’ details in it, is kept for 7 days so that the same batch is never applied twice, and then deleted. The sync’s daily counts hold numbers only and are deleted after 40 days. The mark left on a contact whose Zendesk user was deleted stays until the contact is deleted or linked to a Zendesk user again.

Merged duplicates: The contacts a merge took out are kept whole, with the contact that stayed as it was before the merge, for the 30 days in which the merge can be undone, and deleted one day later. Aliases have no time limit, because a later message or import to an old number or address must keep landing on the same person: they stay while the contact that stayed exists, and go when it is deleted or when the merge that wrote them is undone. Deleting the contact that stayed also deletes what was kept of the contacts merged into it. Clever Merge offers a suggestion it received for 30 days for a Clever Merge admin to confirm, and deletes its details 60 days after it arrived at the latest, under Clever Merge’s privacy policy.

Base cleanup through Clever Merge: For each fix applied, Impulsis keeps the field’s value before and after it for 30 days, plus one day, so the cleanup can be undone; an undo puts back only the fields that still hold the fixed value, and then deletes those records. To find the fixes, Clever Merge receives each contact’s ID, name, phone number, email address, external ID and custom fields, under Clever Merge’s privacy policy: that copy is deleted as soon as the fixes are listed, and the list of fixes, with each contact’s name and the old and new value, is kept for 30 days for the review, or for as long as the applied cleanup can be undone.

Operational logs are retained only for as long as reasonably necessary for security, monitoring, debugging, and compliance.

Billing, tax, accounting, and support records are retained for as long as required by applicable law, typically five years in Brazil, unless a longer period is required to establish, exercise, or defend legal claims.

6) International Transfers

Impulsis may be hosted and operated using reputable cloud providers and infrastructure services located in different countries.

When personal data is transferred outside Brazil, the European Union, or the European Economic Area, we rely on appropriate safeguards, such as Standard Contractual Clauses, contractual protections, adequacy decisions where applicable, or equivalent mechanisms required by applicable law.

7) Security

Impulsis implements industry-standard technical and organizational security measures, including:

  • Encryption in transit.
  • Access controls and authentication safeguards.
  • Role-based access where applicable.
  • Infrastructure monitoring.
  • Logging and auditability.
  • Queue-based processing for reliable message handling.
  • Rate-limit controls to support compliance with messaging provider policies.
  • Automatic retries for delivery failures where appropriate.
  • Operational monitoring and incident response procedures.

We regularly review our security posture and update safeguards to address emerging risks.

8) Your Rights

For data we process on behalf of your organization inside Zendesk or Impulsis, please contact your Zendesk administrator or the organization that controls your data. That organization is responsible for responding to requests from end customers and data subjects.

For data where Clever Development is the controller, such as billing, support, account administration, and business communications, you may contact us to request access, correction, deletion, portability, restriction, or objection to processing, subject to applicable law.

We will respond to valid requests in accordance with applicable privacy laws, including LGPD and GDPR.

Access and deletion requests. As the controller, you answer a person’s request, and Impulsis gives you the tools: the Contacts screen exports your contacts and each contact’s sends (including archived months) as CSV, and a workspace admin can delete a contact for good. Deleting a contact does not remove the person from your sending records. To do that, a workspace admin contacts our support: on your instruction, we remove the person’s phone number, email address, spreadsheet row, message variables, replies and clicked links from every send of your workspace, including archived months, together with the delivery events and the copies of their details in Impulsis’s ticket records. The sends themselves stay, without the person, so your reports and billing remain correct. A send to that person that is still scheduled or queued must be cancelled first. The spreadsheets you uploaded for sends are not changed (section 5), and the ticket in your Zendesk account is yours to manage there. If a person writes to us directly, we pass the request on to you.

9) Customer Consent and Messaging Compliance

Impulsis is a business messaging platform. You are responsible for ensuring that your use of Impulsis complies with applicable laws, messaging rules, platform policies, and consent requirements.

This includes, where applicable:

  • Obtaining valid consent or another lawful basis before sending WhatsApp, Email, or SMS messages.
  • Respecting opt-outs, unsubscribe requests, and communication preferences.
  • Using approved templates where required by WhatsApp or other messaging providers.
  • Ensuring campaign content complies with applicable laws and provider policies.
  • Maintaining accurate contact lists and segmentation rules.

Clever Development provides the infrastructure to process and send messages according to your instructions, but you remain responsible for the legality of your campaigns, contact lists, message content, and communication practices.

10) Children’s Data

Impulsis is intended for business use only and is not directed to children under 13.

You must not knowingly use Impulsis to collect, process, or send communications to children in violation of applicable laws.

11) Contacting Impulsis

If you have questions about this Policy or want to exercise rights related to data for which Clever Development is the controller, please contact us at:

Email: [email protected]

We may request proof of identity or authorization before acting on your request.

12) Changes to This Policy

We may update this Policy from time to time to reflect changes in law, our service, our subprocessors, or our data practices.

When we update this Policy, we will post the revised version with a new “Last updated” date. Where required by law or where changes are material, we may provide additional notice.

13) Contact

CLEVER DEVELOPMENT LLC

1209 Mountain Road PL Ne
Albuquerque, NM 87110
USA

Email: [email protected]