Pule
BayarPulsePayText-to-pay, IVR & portal pembayaranAIPiPRekan tim AI AndaSuaraPulseVoiceAgen suara AI agentikTagihanPulseBillPenagihan berulang & berbasis penggunaanSosialSocialCommandPublikasi sosial & JourneysEngagePulseEngageKampanye email & pesanSMSPulse SMSSMS bisnis dua arahMitraPulse DealsManajemen mitra & kesepakatanPenjadwalanPulseMeetHalaman pemesanan & catatan rapatContact CenterPulseConnectPerutean omnichannel & konsol agenKerjaPulseWorkProyek, service desk & pusat bantuanIntiInti yang AmanKeamanan & kepatuhan
KeamananMitra
Pemrosesan MerchantOnboarding Gateway
BlogStatusTentangUnduh
Login MitraMinta demo
PulsePayPiPPulseVoicePulseBillSocialCommandPulseEngagePulse SMSPulse DealsPulseMeetPulseConnectPulseWorkKeamananMitraBlogStatusTentangUnduhMinta demo
Home / Disclosures & Policies

Disclosures & Policies

The policies that govern Pulse Technologies and its products, including the Pulse platform. Choose a document below.

Last updated: June 23, 2026

These Disclosures & Policies describe how Pulse Payments LLC, doing business as Pulse Technologies (“Pulse,” “we,” “us,” or “our”), collects, uses, and protects information, and the terms that govern your use of our websites, applications, and services (collectively, the “Services”). By accessing or using the Services — including by opting in to receive text messages from us — you agree to these policies. For the detailed platform agreements, see the Terms of Service, Privacy Policy, and Data Processing Addendum tabs above.

1. Privacy

We collect information you provide (name, email, company, mobile number, billing details), information collected automatically (IP, device/browser metadata, cookies, usage), and information from authorized third parties (authentication, analytics, payment providers). We use it to provide and improve the Services, process transactions, send requested messages and updates, deliver support, personalize content, perform analytics, and secure the Services. We share personal data only with service providers acting on our behalf, and we do not sell your personal data. Depending on your jurisdiction, you may have the right to access, correct, delete, restrict, or port your data — contact legal@pulsetechnologies.ai.

2. Mobile Messaging & SMS

No mobile information or messaging consent is shared with third parties or affiliates for marketing or promotional purposes. Mobile information and SMS opt-in consent are not sold, rented, or shared for their own marketing. We share mobile information only with the service providers that help us deliver the messaging service.

  • Consent. You opt in to receive texts — for example by checking an SMS opt-in box on a web form or at the point of sale.
  • Frequency. Message frequency varies based on your activity and relationship with us.
  • Rates. Message and data rates may apply.
  • Opt-out & help. Reply STOP to unsubscribe and HELP for assistance.

3. Cookies & Tracking

We use cookies, pixels, local storage, and similar technologies to keep you signed in, measure usage, and personalize your experience. You can control cookies through your browser settings and advertising opt-out tools. Third-party analytics and advertising providers may set their own cookies, governed by their own policies.

4. Terms of Use

Use the Services lawfully and responsibly. You are responsible for safeguarding your credentials and for activity under your account. All content, logos, and software are owned by or licensed to Pulse. The Services are provided “as is,” and to the extent permitted by law, Pulse’s aggregate liability is limited to amounts you paid in the twelve (12) months preceding a claim. These terms are governed by the laws of the State of Florida, with disputes resolved in Lee County, Florida.

5. Accessibility

Pulse strives to make the Services accessible and follows recognized accessibility best practices. If you encounter a barrier, contact legal@pulsetechnologies.ai with the page URL and a description, and we will work to address it.

6. Copyright & DMCA

If you believe content on the Services infringes your copyright, send a notice to legal@pulsetechnologies.ai including your signature, identification of the work, the location of the material, your contact information, a good-faith statement, and a statement under penalty of perjury that you are authorized to act.

7. Payments & Refunds

Payments are processed by third-party payment providers; Pulse does not store raw card numbers. You are responsible for applicable taxes and fees. Refund and trial terms, where offered, are provided at the time of purchase.

8. Changes & Contact

We may update these policies; material changes are posted here with an updated date. Pulse Payments LLC (dba Pulse Technologies)
9160 Forum Corporate Pkwy, Suite 350, Fort Myers, FL 33905
General & legal: legal@pulsetechnologies.ai · Privacy & messaging: privacy@pulsetechnologies.ai

Effective date: September 24, 2026

These Terms of Service (“Terms”) govern access to and use of the Pulse platform (the “Service”), provided by Pulse Payments LLC (dba Pulse Technologies) (“Pulse”, “we”, “us”). By accessing or using the Service, the customer organization (“Customer”, “you”) and its authorized users agree to these Terms. If you use the Service on behalf of an organization, you represent that you are authorized to bind it.

1. The Service

The Service lets Customers draft, schedule, and publish social content to connected networks (LinkedIn, Facebook, Instagram, X, TikTok, YouTube, Pinterest, Threads, Google Business Profile, Bluesky, Mastodon, Discord, Telegram, Tumblr), including AI-assisted content. It also includes Pulse SMS (business messaging), Pulse Email / PulseEngage (opt-in email marketing — campaigns, automations, and signup forms — offered both within Social Command and as a standalone application at pulseengage.pulsetechnologies.ai), Pulse Voice (a business phone system and AI voice platform — inbound and outbound calling through web, desktop, and mobile softphone apps, voicemail with transcription, call recording, fax including an optional write-once fax archive, Microsoft Teams, Zoom, and Webex calling integrations, video meeting rooms with optional recording, transcripts, and AI recaps, AI voice agents built in AI Studio including the PiP phone agent, outbound AI calling, and collections and pay-by-phone calling), PulseConnect (a contact center — voice, SMS, web chat, and email queues, customer-satisfaction surveys, the Agent Console on the web and as a desktop app, and CRM connectors), PulseMeet (appointment scheduling at meet.pulsetechnologies.ai — booking pages, Google Calendar and Microsoft 365 calendar sync, Zoom meeting links, reminders, and the optional PiP Notetaker that joins and summarizes meetings), PiP for Outlook and Teams (the PiP assistant as a Microsoft 365 add-in), Pulse RFP (RFP discovery, drafting, pricing, and submission — including sending response documents for e-signature at the Customer’s direction), Pulse Deals (the Pulse Partners portal for deal registration, commissions, and partner onboarding), Pulse SSO / PulseAdmin (unified sign-in and cross-product access management), PulseBill (recurring billing and invoicing for the Customer’s own customers, including usage rating and tax calculation), PulsePay (payment acceptance — merchant processing itself is provided under separate merchant agreements with the payment processor), a public API and webhooks, native CRM connectors, a support help desk, in-product usage analytics, and native mobile apps. These Terms govern each Pulse product a Customer uses, whether accessed within the Social Command workspace or as a standalone application. Individual features may depend on third-party approvals or be offered in beta.

2. Accounts, organizations & eligibility

  • Organizations are provisioned by Pulse; an admin may invite users and assign roles (admin, editor, viewer).
  • You are responsible for all activity under your organization and for keeping credentials — including API keys and webhook secrets — confidential.
  • Users must be 18 or older and provide accurate information.

3. Customer content & license

You own the content you create or upload (“Customer Content”). You grant Pulse a limited, non-exclusive license to host, process, transmit, and display it solely to provide the Service — including sending it to the third-party platforms and AI providers you direct us to use. You are responsible for having the rights to what you upload and publish.

4. Acceptable use

You agree not to use the Service to: violate any law or a connected platform’s policies; post unlawful, infringing, deceptive, harassing, or harmful content; send spam or publish to accounts you are not authorized to manage; breach, disrupt, or reverse-engineer the Service or other tenants’ data; exceed API rate limits or circumvent security; or submit payment card numbers or sensitive data into post content (the Service screens for and blocks card numbers and detected secrets).

5. Third-party platforms & AI output

  • Connected platforms are governed by their own terms; Pulse is not responsible for their availability, decisions, or actions.
  • The AI assistant (“PiP”) and other AI features act on your instruction. PiP is an assistant, not an autonomous publisher: content it prepares is presented for your review and requires your approval before it is published or sent. You remain responsible for reviewing all content for compliance with law and platform policies.
  • AI output may contain errors and is treated as your Customer Content. Prompts and relevant content are sent to our AI provider (Anthropic) and are not used to train its models. Where a Customer selects an alternative AI model, speech-to-text, or text-to-speech provider for a feature (for example a Pulse Voice AI agent), the relevant content is sent to that provider (see the sub-processors in the Privacy Policy).

6. Business messaging, voice & email

  • Consent & your responsibility. You may only message individuals who have given you prior express consent, and are solely responsible for that consent and for compliance with the TCPA, CTIA guidelines, and A2P 10DLC registration. You are the sender of all messages you send.
  • Rates & opt-out. Message and data rates may apply; recipients may reply STOP to unsubscribe and HELP for help, handled automatically. Mobile numbers and SMS consent are not shared with or sold to third parties for their own marketing.
  • Outbound AI voice (Pulse Voice). Automated, prerecorded, and AI-generated calls carry heightened requirements. You may place these calls only with the consent required by law — including prior express written consent where applicable — and are solely responsible for TCPA compliance, calling-time windows, and do-not-call obligations. You are the caller. Pulse provides the tooling and is not a party to the call.
  • Text-to-pay. You — not Pulse — are the merchant of record. Charges are processed under your own gateway/merchant account; you are responsible for the goods or services, amounts, taxes, refunds, chargebacks, and card-network rules. Card details are entered on the gateway’s hosted page and are never received or stored by Pulse.
  • Email marketing (Pulse Email / PulseEngage). Opted-in audiences only. Every message includes a one-click unsubscribe and your postal address; the Service enforces a suppression list. No unsolicited or purchased-list email.

7. Subscriptions, fees & billing

  • Paid plans automatically renew (monthly or annually) at the then-current price using the payment method on file, until you cancel. Card details are entered on the gateway’s hosted page and never stored by Pulse.
  • Plans that include text messaging carry a $50/year A2P 10DLC registration fee; you may opt out of SMS at checkout to avoid it.
  • Free trials do not require a card and do not auto-convert. You may cancel any time from Admin → Billing; access continues through the paid period. Fees are non-refundable except where required by law. We may change pricing with at least 30 days’ notice.

8. Suspension & termination

Pulse may suspend or terminate access for breach, non-payment, or to protect the Service or third parties. You may stop using the Service at any time. On termination, Customer Content is handled as described in the Privacy Policy and DPA.

9. Disclaimers & liability

The Service is provided “as is” and “as available” without warranties of any kind. Pulse will not be liable for indirect, incidental, special, consequential, or punitive damages; its total liability will not exceed the amounts you paid for the Service in the 12 months preceding the claim.

10. Indemnification, changes & governing law

You will defend and indemnify Pulse against claims arising from your Customer Content, your use of the Service, or your violation of these Terms or applicable law. We may update these Terms; continued use after changes take effect constitutes acceptance. These Terms are governed by the laws of the State of Florida, with exclusive jurisdiction in the state and federal courts of Lee County, Florida.

11. Product-specific terms

The terms below apply in addition to Sections 1–10 when a Customer uses the product named.

Pulse Voice (phone system, fax, video meetings, and AI voice agents)

  • Recording and monitoring consent. Before recording, monitoring, transcribing, or analyzing calls or meetings, you must obtain and maintain every legally required consent — including two-party/all-party consent where required — and give callers and called parties any legally required disclosures.
  • Calling rules. For outbound calling you must also comply with robocall and caller-ID (STIR/SHAKEN) requirements and internal and national Do-Not-Call lists, and you are responsible for your AI voice agents identifying themselves as automated where the law requires.
  • Emergency calling (E911). You must register and maintain accurate emergency address information for numbers that require it. Emergency calling over the Service may be limited or unavailable; you must maintain an alternative means of contacting emergency services.
  • Protected health information. If you require processing of protected health information subject to HIPAA, a separate Business Associate Agreement (BAA) must be executed with Pulse. Absent a signed BAA, the Service must not be used to process PHI.
  • Bring-your-own credentials. You may connect your own AI-provider or carrier accounts. When you do, you authorize Pulse to use those credentials to provide the Service to you, and you remain responsible for those accounts, their terms, their fees, and the acts performed with them. Provider credentials you store are encrypted at rest.
  • Phone numbers. Numbers ordered, imported, or ported through the Service remain subject to the terms and portability rules of the underlying carrier. You are responsible for carrier and regulatory fees. On termination, numbers that have not been ported out may be reclaimed by the carrier.
  • Model training. Pulse does not use Customer Content processed through Pulse Voice to train third-party foundation models.

Social Command, Pulse SMS, and Pulse Email

  • WhatsApp and RCS. WhatsApp and RCS are delivered through Twilio and the underlying platforms (Meta/WhatsApp and Google/carriers). Where you use them, you must also comply with those platforms’ policies (including the WhatsApp Business Messaging Policy and approved message templates). Rich channels may carry an annual per-channel enablement fee and are metered against your message allowance.
  • Prohibited messaging. You may not send messages that are unlawful, deceptive, or unsolicited, or that fall within carrier-prohibited categories (including SHAFT — sex, hate, alcohol, firearms, tobacco — content) except where lawfully permitted and properly registered.
  • Anti-spam law. You must comply with all applicable anti-spam laws when sending email (including the U.S. CAN-SPAM Act and, where applicable, CASL and GDPR/PECR). Pulse Email may not be used for cold outreach or for lists the recipient did not opt into; doing so may result in suspension.
  • Blog and CMS publishing. Where enabled, Pulse drafts long-form blog posts with AI and can publish them to a content management system you connect (for example WordPress, Webflow, Ghost, Hygraph, or Medium). You are responsible for the content you publish, for reviewing AI-assisted drafts before publishing, and for the CMS credentials you provide and the account they access. The CMS is your own system or vendor; Pulse publishes on your instruction and is not the CMS provider or a records custodian.
  • Compliance capture and archiving. Regulated Customers may enable compliance capture to forward a copy of their communications (text, email, and social) to an archiving, supervision, or eDiscovery system they configure. That destination is your own system or vendor relationship: you are responsible for configuring it, for the credentials you provide, and for your retention and supervision obligations there. Pulse forwards the copy on your instruction and is not the archiving provider or a records custodian.
  • Plan limits and non-payment. Plans carry usage limits (members, connected accounts, scheduled posts, messages, AI); exceeding a limit may require an upgrade or an add-on. Fees are exclusive of applicable taxes. If a renewal charge fails, Pulse may suspend or downgrade the account until payment is resolved. Cancellation does not produce prorated refunds for partial periods.

Contact

Pulse Payments LLC (dba Pulse Technologies)
9160 Forum Corporate Pkwy, Suite 350, Fort Myers, FL 33905
pulselegal@pulsetechnologies.ai

Effective date: October 28, 2026. Last revised: November 13, 2026. Version: PRIVACY-DRAFT

This Privacy Policy explains how Pulse Payments LLC (dba Pulse Technologies) collects, uses, and protects information in connection with the Pulse platform (the “Service”) — a multi-tenant service for social publishing, business messaging (Pulse SMS), business phone, fax, team chat, video meetings, call recording, and AI voice (Pulse Voice), contact center (PulseConnect), opt-in email (Pulse Email), appointment and team scheduling and meeting notes (PulseMeet), work management and service desk (PulseWork), billing and payments (PulseBill and PulsePay), RFP and partner tools (Pulse RFP and Pulse Deals), the PiP assistant (in our apps, in Microsoft Outlook and Teams, and on our website), a public API and webhooks, and native mobile and desktop apps. It also covers our website and Pulse Secure Transfer, the secure link through which customers and partners send files to Pulse.

1. Who we are and our role

  • For account/identity data (login records of the people who use the Service), Pulse is a controller.
  • For the content and connected-account data a Customer puts into the Service, the Customer is the controller and Pulse is a processor, processing on the Customer’s behalf. See the Data Processing Addendum.
  • For information you send Pulse directly — website contact and demo requests, conversations with PiP on our website, merchant applications, and files sent to Pulse through Pulse Secure Transfer — Pulse is a controller.
  • For service and transactional email that Pulse sends about its own Service — sign-in and invitation messages, booking messages, platform notices, secure-transfer messages, and Pulse’s own invoices — Pulse is a controller, including for the open and click information described in section 2.

2. Information we collect

CategoryExamples
AccountName, email, role, organization membership, securely hashed password.
Content you createDraft and scheduled posts, captions, media, and files you upload (including items given to the AI assistant).
PiP memoryA small per-user profile of work-style preferences it infers, and — for the support assistant — short, durable support-relevant facts learned from your support conversations (e.g. the tools you use), shared across the Pulse products on your account so PiP can help consistently. Excludes sensitive data; user-clearable.
Connected accountsAccess tokens and identifiers for the social networks you connect, so the Service can publish on your behalf.
Mobile & messagingContact phone numbers/names, message content and media (SMS/MMS/WhatsApp/RCS), delivery and opt-out status, consent-event log, the org’s dedicated number, and the records tools described under Pulse SMS below (litigation holds and exports).
Email marketingContact emails, names, tags, subscription status, campaign content, verified sending domain, and per-message engagement information, such as delivery, detected opens, clicks, bounces, replies, and unsubscribes. Where open tracking is on, we use tracking pixels to detect email opens. For each detected open, we record the date and time, a broad mail-app category, indicators of possible automated or proxy loading, and a keyed hash generated from the Customer’s account identifier, the message identifier, the mail-app category, and a truncated network address. These records are linked to the recipient’s email address and help the sender estimate different opening environments. These estimates may be affected by automated image loading, privacy services, and changes in apps or networks, and do not establish who read or forwarded a message. The source IP address is processed to derive the truncated network address used in the hash; neither address is written to the detected-open records in our engagement database. Each detected-open record in that database is automatically deleted 90 days after it is recorded. Since November 13, 2026, each link-click record is also deleted 90 days after it is recorded. The opened or clicked status kept on a send record, and the time it was last updated, is linked to the recipient and is not removed by those limits. Separately, technical request logs can contain recipient email addresses embedded in tracking URLs and associated request information. These logs are used for service operation and security. A Customer can turn open tracking off for its account or for an individual journey; the account-wide setting, when off, overrides journey settings. Open tracking is off by default for journeys a Customer sends to prospects. That default describes how tracking behaves; it is not permission to send. The PulseEngage sending service may be used only to email recipients who have opted in, and a journey marked as written to prospects cannot be sent through it. In this policy, the PulseEngage sending service means email that PulseEngage delivers through Pulse’s email sending sub-processor; it does not include email sent from a mailbox through a separately configured mailbox connection. Correction (November 13, 2026). Until November 13, 2026, email sent through the sending service from one Pulse-owned marketing domain also carried the sending sub-processor’s own tracking pixel and rewritten links, and the opens and clicks that the sub-processor reported were recorded against the recipient whatever the settings described above. This affected three emails that Pulse sent to prospects on November 10, 11, and 13, 2026. Open tracking was therefore not off for those emails, although the text published here on November 11 described it as off by default for journeys sent to prospects. On November 13 we turned off the sub-processor’s tracking for that domain, applied the settings described above to opens and clicks reported by the sub-processor, and deleted the opens and clicks recorded in PulseEngage for those emails. The sub-processor holds its own records of those events. We process this information on behalf of Customers for their campaigns. For our own marketing and the associated engagement processing, Pulse is the controller.
Service and transactional emailCertain service and transactional emails sent from pulsetechnologies.ai — including sign-in and invitation messages, booking messages, platform notices, secure-transfer messages, and Pulse’s own invoices — contain tracking pixels and links routed through Resend. Resend records detected opens and clicks associated with the message and recipient and reports those events to Pulse. For a click, the report includes the link, the time of the click, the IP address, and the browser or app identifier (user agent). Pulse’s billing product uses invoice engagement information to display whether an invoice email was detected as opened, and keeps the time and number of detected opens and clicks with the invoice email record; it does not store the IP address or user agent from these reports. Detected opens and clicks can result from automated systems and do not establish that the recipient personally read the message or viewed its contents. PulseEngage’s campaign and journey tracking switches do not control this separate transactional-email tracking. Invoices that a Customer sends from its own sending domain through PulseBill carry this tracking only if tracking is enabled for that domain.
Voice / call dataCall audio, transcript, AI-agent summary and disposition, duration, and calling/called numbers for inbound and outbound calls; call recordings where recording is turned on; voicemail audio and its automatic transcript; fax documents sent and received (and, where a Customer enables the fax archive, write-once archived copies); caller name and number shown in call notifications; emergency (E911) addresses; and number-porting details. Where a Customer enables pay-by-phone, a card number keyed in by a caller passes once to the payment gateway for tokenization and authorization; Pulse keeps only the token, last four digits, and card brand, never the full card number or security code.
Compliance call recordingWhere a Customer enrolls a workspace: call recordings archived encrypted in write-once storage for the retention period in the Customer’s recording policy; the log of who accessed, exported, or held each recording; and, where the policy asks for them, speaker-labelled transcripts (card numbers detected in a transcript are masked), AI-generated summaries, action items, topics, sentiment, disclosure checks, quality-assurance scores, and reviewer notes and attestations. A Customer can also send a recording’s action items to a PulseWork desk as tickets.
Team chat (Pulse Voice)Messages, files, reactions, mentions, and search entries in the chat groups and channels of a Customer’s workspace, and requests the Customer’s users make to PiP in chat.
Video meetings & meeting notesPulse Voice meeting-room participants and, where the host turns on recording, the recording, transcript, and AI-generated recap. Where a PulseMeet user turns on the PiP Notetaker (off by default), the notetaker joins that user’s video meetings (Zoom, Google Meet, Microsoft Teams, or Webex) and captures the meeting audio, transcript, and participant names to produce AI meeting notes, which are emailed to that user. AI notes for a meeting booked through PulseMeet may also be emailed to the invitee.
Scheduling (PulseMeet)Invitee name, email, phone number, time zone, and answers to the host’s booking questions; booking times; reminders sent; AI-prepared pre-meeting briefs; for team scheduling, each teammate’s working hours and free/busy time (never event titles or attendees), shown to other members of the same PulseMeet organization, and saved groups of teammates; an organization-level audit trail of administrative changes; and the calendar information described in “Google Calendar and Microsoft 365 calendars” below.
Work management & service desk (PulseWork)Projects, work items, tickets and comments, attachments (including pasted screenshots), requester names and email addresses, customer organizations, time tracking, assets, approvals, help-center articles and satisfaction ratings, messages received from a connected Microsoft 365 support mailbox, API tokens (stored as hashes), webhook endpoints, and an administrator audit log.
Contact center (PulseConnect)Web-chat messages and attachments with the page they were sent from, inbound and outbound email threads and attachments, SMS threads, call details and (where a queue records calls) recordings, customer-satisfaction survey ratings and answers, and agent presence, schedules, and activity.
PiP for Outlook and TeamsWhen a user connects Microsoft 365, the email open in Outlook and the Teams chats, files, mail, calendar, and meeting transcripts PiP reads as that user to answer the user’s request.
Microsoft 365 contact sync (Pulse Voice, Pulse SMS)Not currently available to any customer. This row is draft text that is not in effect and does not form part of any agreement until it is published as final; it describes how contact sync is intended to work if it is made available (see “Microsoft 365 contact sync” in Section 5). It would be available only where a Customer’s administrator turns it on; contacts would be copied one way (contact sync never writes to Microsoft). Personal Outlook contacts: where a user then connects their own Microsoft account, every contact that has a phone number in that user’s main Outlook contacts folder and the folders directly inside it, including any personal, non-work contacts the user keeps there — name, company, job title, department (Pulse Voice only), one email address (the first), phone numbers, and the contact’s Microsoft identifier. These are accessible within the application only under the owning user’s login and are not added to the team’s shared contacts unless, in Pulse SMS, the user deliberately copies a single contact across. In Pulse Voice they are used for contact lookup and calling; in Pulse SMS they are used to find people and for one-to-one messaging. They are refreshed about every six hours and on demand. Microsoft directory: people in the Customer’s Microsoft Entra ID directory who have a phone number, excluding disabled accounts and guests — name, company, email address (where the person has one), phone numbers (in Pulse SMS, one phone number), the person’s Microsoft identifier, and, in Pulse Voice, job title and department. In Pulse Voice, directory contact records are visible to that Customer’s users and to Pulse workspace staff while those staff are working in that Customer’s account. In Pulse SMS, they are added to the Customer’s shared contacts with a Microsoft directory source label. In both products, contacts that come from Microsoft follow changes at the source at the next successful sync, are removed when the sync is turned off or when Microsoft reports that the permission or approval was withdrawn, and are removed after 30 days without a successful sync for any reason, including 30 continuous days of failed refreshes. In Pulse SMS they are never used for campaigns, broadcasts, message personalization, or promotional messages, and are not available to API keys, integrations, automations, or the AI tools. Synced contacts are not used to identify callers. Access to synced contacts is logged without their contents. Section 5 gives the timing and exceptions.
Website & direct inquiriesName, email, company, phone, and message from contact and demo forms; messages you type to PiP on our website; IP address for abuse prevention and rate limiting; merchant-application details (business and owner identity, tax identifiers, and bank-account details); and files and uploader email addresses sent to Pulse through Pulse Secure Transfer, which are encrypted, scanned for malware, and stored write-once.
Ecommerce store data (Shopify)If a Customer connects a Shopify store, its orders and checkouts received through Shopify webhooks — the buyer’s email and (for abandoned-checkout recovery) name, order or checkout total and currency, line items, timestamps, and Shopify’s recovery link — used for the Customer’s ecommerce automations, revenue attribution, and segmentation. Card and payment details are handled by Shopify and never received by Pulse.
Blog posts & CMS publishingThe blog posts a Customer drafts (title, SEO metadata, and body) and, where the Customer connects a content management system, that connection’s credentials, stored write-only and never shown back.
Text-to-payAmount, description, recipient, and status. Card details are entered on the gateway’s hosted page and never received by Pulse.
BillingPlan, subscription status, and a payment-gateway reference. Pulse does not store full card numbers.
PulseBill recordsA Customer’s own customers: account contacts and service addresses, invoices and usage, payment-method tokens (not card numbers), payment history, and the tax-exemption and resale certificates a Customer files (certificate number, jurisdiction, effective and expiry dates, and the document).
Agreement recordsPurpose: to keep evidence that a Pulse Voice customer accepted Pulse’s terms, an order, or the 911 advisory, and to establish, exercise, or defend legal claims about that acceptance. Fields: the signer’s name, title (if given), and email; the method and time of acceptance; the words the signer was shown and the document versions accepted; a reference to the signed file and its checksum, where there is one; and the signer’s IP address, kept only where one was provided (a paper or emailed signature has none). Retention: kept while the agreement is in effect and afterward for as long as needed to prove the acceptance and defend claims about it; a record is voided if wrongly entered, never edited or silently deleted, and it is not removed when the customer’s workspace is closed (see Section 7). Access: restricted to authorized Pulse staff; not shown to other customers.
Help & knowledge base (PulseDocs)Questions asked in the PulseDocs help panel and help center, answered by PiP from the articles the asker may read; questions that find no guide are recorded with emails, links, long identifiers, and numbers masked, cut to 200 characters, and without the asker’s name.
Support requestsThe content of support tickets and live chats — your messages, our replies, and any PiP exchange you attach — plus the status and category of the request. Pulse’s own support desk runs on PulseWork.
Developer dataAPI keys you generate (stored only as a hash) and the webhook endpoint URLs and signing secrets you configure.
Mobile app dataIf you install a native app, a device push token so we can deliver the notifications you enable.
Usage analyticsIn-product activity (which screens are used and for how long, by user and organization), used for the admin usage dashboards and to improve the Service. First-party only: stored in our own database, with no third-party advertising or analytics SDKs.
OperationalSign-in timestamps, job status, audit-log entries, rate-limit counters, and error logs.

3. How we use information

To authenticate users; generate, store, schedule, and publish content; send and receive messages and record opt-outs; orchestrate multi-channel journeys and place the outbound AI voice calls a Customer configures; route, connect, record (where turned on), archive, transcribe, and (where a recording policy asks) analyze inbound and outbound calls and voicemail, run team chat, and send, receive, and archive faxes; host video meetings and, where turned on, record, transcribe, and summarize them; run the Customer’s AI voice agents; publish booking pages, check calendar availability, create calendar and Zoom events for bookings, send booking confirmations and reminders, prepare pre-meeting briefs, and, where a user turns on the PiP Notetaker, join and summarize that user’s meetings; route contact-center calls, chats, texts, and emails to agents, run customer-satisfaction surveys, and log activity to a CRM the Customer connects; send push notifications to our mobile and desktop apps; run work-management projects and service desks; respond to website inquiries and process merchant applications; receive files sent to Pulse through Pulse Secure Transfer; send opted-in email with a working unsubscribe; measure whether certain service and transactional emails were detected as opened or clicked, including showing in our billing product whether an invoice email was detected as opened; enable text-to-pay (without processing the card itself); power AI features and the PiP assistant (which proposes, and never publishes on its own); provide API access and webhooks; screen content for sensitive data before publishing; operate support; manage billing; and secure and improve the Service with first-party analytics only.

4. Multi-tenancy & data isolation

Each organization is a separate tenant; content, connected accounts, members, and queues are segregated per organization. Contact data (names, emails, and phone numbers) a Customer imports is held in a shared per-tenant contact graph so it is available across the Pulse products that Customer uses — for example Pulse SMS and Pulse Email; it remains isolated to that Customer’s tenant and is never shared across Customers. Within the same tenant, PiP’s pre-meeting briefs may draw on that Customer’s own records of the same contact in other Pulse products (earlier bookings and meeting notes, Pulse SMS threads, and Pulse Voice call summaries). To troubleshoot, Pulse administrators may start a time-limited support session that acts within a Customer’s workspace; every such session is recorded in the audit log. Where a Customer is served through a Pulse reseller partner, that partner’s authorized administrators can enter and manage the Customer’s workspace; access runs downward only (a sub-reseller cannot reach its parent).

5. Sub-processors

We use the service providers below to run the Service, sharing only what each needs to perform its function. This is the same list published on the Sub-processors tab, which is the maintained copy.

ProviderPurpose
VercelHosting, serverless functions, media storage.
NeonManaged PostgreSQL database.
RenderHosting, managed PostgreSQL, and caching for Pulse Email and the shared contact graph, Pulse Voice, PulseConnect (including web-chat transcripts and attachments), PulseMeet, Pulse SMS, PulseBill, Pulse Deals, Pulse RFP, PulseWork, Pulse Secure Transfer, and PulseAdmin.
AnthropicAI generation and the PiP assistant — in our apps, in Outlook and Teams, and on our website — including Pulse Voice AI voice agents, meeting recaps and PiP meeting notes, pre-meeting briefs, post-call analysis of recorded calls (on card-masked transcript text, never audio) where a Customer turns it on, PiP in team chat, and email and message drafting. Inputs are not used to train models.
OpenAI, Google (Gemini), xAI, Deepgram, Cartesia (if enabled)Alternative AI models, speech-to-text, and text-to-speech that a Customer may select for a Pulse Voice AI voice agent (call audio, transcripts, and prompts). OpenAI may also be used for AI image generation and voiceover in Social Command.
fal.ai (if enabled)AI image generation.
ElevenLabsText-to-speech — spoken PiP replies, Pulse Voice AI voice agents, and voiceover (the text to be spoken).
Recall.ai (if enabled)The PulseMeet PiP Notetaker, which receives the meeting link and time of a user’s video meetings when that user turns it on, joins them, and returns the meeting recording, transcript, and participant names used to write the notes.
Connected social networksPublishing to the networks you connect — Meta (Facebook, Instagram, Threads), LinkedIn, X, TikTok, YouTube, Pinterest, Google Business Profile, Bluesky, Mastodon, Discord, Telegram, and Tumblr. Each is governed by its own terms and privacy policy.
TwilioPulse SMS — default carrier for number provisioning and SMS/MMS/WhatsApp/RCS delivery; alternative call control for Pulse Voice (if enabled).
Meta / WhatsApp (if enabled)WhatsApp Business message delivery (via Twilio) when a Customer enables WhatsApp — recipient numbers and message content, governed by WhatsApp’s terms.
TelnyxPulse SMS — alternative carrier for number provisioning and SMS/MMS delivery; the primary telephony carrier for Pulse Voice and PulseConnect — call control, softphone calling, number provisioning and porting, fax, call recordings, video meeting rooms and their recordings, and transcription of voicemail, recorded meetings, and recorded calls.
NTT (if enabled)Carrier for Pulse Voice numbers provisioned on NTT Cloud Voice — number ordering and porting, emergency (E911) service addresses, and Microsoft Teams tenant routing; call-detail records for those numbers are returned for billing.
PulseVoice (if enabled)Outbound AI voice calls, the AI agent, and video meeting rooms used by other Pulse products (for example Pulse Email journeys and PulseMeet).
Pulse SSO / PulseAdminUnified sign-in and cross-product access management — authenticates users and manages platform access grants across Pulse products; maintains an audit log of access changes.
Amazon Web Services (S3)Encrypted, write-once storage of files sent to Pulse through Pulse Secure Transfer and, where a Customer enables them, the Pulse Voice fax archive and compliance call-recording archive (the encrypted audio; transcripts and analysis are stored encrypted in the Pulse Voice database).
Apple, Google (Firebase Cloud Messaging), ExpoPush notifications to the Pulse Voice mobile apps, which may include a caller’s name and number or a message preview.
Better StackApplication logging, uptime monitoring, and the public status page — application logs from every Pulse product are sent to Better Stack for retention, search, and alerting.
OneSignal / Sentry (if enabled)Mobile push / error monitoring.
Microsoft (if enabled)Microsoft Teams sign-in, notifications, and Teams calling provisioning; Microsoft 365 calendar free/busy lookups, booking events, and event details for PiP features for PulseMeet; SharePoint and OneDrive knowledge-base connectors; PiP for Outlook and Teams, which reads the mail, chats, files, calendar, and meeting transcripts of the user who connects it; Microsoft Entra ID / Microsoft 365 sign-in for the Pulse login and for an organization’s single sign-on; and, for PulseWork, the Microsoft 365 support mailbox a Customer connects for email-in.
Google (if enabled)Google Calendar availability, booking events and, for PiP features, event details for PulseMeet; Google Calendar availability and booking events for Pulse Voice agents (see “Google Calendar and Microsoft 365 calendars” in the Privacy Policy); Google Drive knowledge-base connector; RCS Business Messaging delivery (via Twilio) when a Customer enables RCS; Google Workspace sign-in (OpenID Connect) for an organization’s single sign-on; reCAPTCHA spam protection on website forms.
Zoom (if enabled)Creating Zoom meetings for PulseMeet bookings (meeting topic and time, using the host’s connected Zoom account); the PulseSMS app for Zoom, which uses the signed-in user’s Zoom profile; and Zoom Phone provisioning for Pulse Voice.
Connected business apps (if enabled)Data exchanged with the third-party applications a Customer chooses to connect under its own account — for example CRMs (HubSpot, Salesforce, Pipedrive, monday.com, Zoho, Microsoft Dynamics 365, ActiveCampaign) for contact lookup and activity logging, Cisco Webex for message mirroring and calling, other calling and contact-center platforms, QuickBooks and Xero, Shopify, Canva, content management systems (WordPress, Webflow, Ghost, Hygraph, Medium) that receive the blog posts a Customer publishes, and, for PulseWork, Slack and Microsoft Teams channels that receive notifications, and GitHub, which sends events to PulseWork. Microsoft 365 contact sync is not currently available to any customer; if it is made available and a Customer enables it, this will also cover the Customer’s Microsoft 365 environment, from which Pulse Voice and Pulse SMS would read contacts (see the note below this list).
HubSpotPulse’s own CRM — receives website contact and demo requests.
Cloudflare (if enabled)DNS and secure proxying for Customer white-label domains, such as a Customer’s hosted SMS opt-in page.
Apollo (if enabled)Contact enrichment — appends professional data to a contact when an admin runs enrichment.
Atlassian (Jira Service Management)Support-desk ticketing. From June 2026 until October 2026, copies of Pulse’s own support-desk tickets, including tickets raised by customers of Pulse products, were mirrored to Jira Service Management. That mirroring has ended.
Accept.blueSubscription and merchant payment processing that powers the Pulse gateway; card data is handled by Accept.blue and its underlying processors (Pulse does not store full card numbers).
DM Processing (if enabled)Merchant underwriting — PulsePay merchant applications (business and owner identity, tax identifiers, and bank-account details) are sent to the payment processor for review.
ResendTransactional and opted-in marketing email delivery, including booking confirmations and reminders, meeting notes and recaps, invoices, and the PulseConnect email channel (inbound and outbound).
SignWell (if enabled)E-signature — delivering documents a Customer sends for signature (the document and each signer’s name and email), used by Pulse RFP, PulseBill quotes, and partner onboarding.
Voyage AI (if enabled)Text embeddings for knowledge-base search — documents a Customer adds to its knowledge base (Pulse RFP, Pulse SMS knowledge) are embedded for retrieval. Not used to train models.
CereTaxTelecom and sales-tax calculation and tax reporting for PulseBill. For each invoice line, PulseBill sends CereTax the service address, amount, quantity, date, product tax code, any customer tax-exemption code, and invoice number. Tax associated with issued invoices is also recorded with CereTax for tax reporting. CereTax is PulseBill’s production tax provider.

Some sub-processors are engaged only when a Customer enables the related feature (marked “if enabled”). Where a Customer connects its own third-party provider account with its own credentials (for example its own AI provider or carrier account in Pulse Voice), that provider acts under the Customer’s own agreement and is not a Pulse sub-processor for that data. Where a Customer turns on compliance capture, the archiving, supervision, or eDiscovery system it configures (for example an HTTPS/webhook endpoint, an SMTP journaling address, a Microsoft 365 / Purview mailbox, Proofpoint, or an SFTP feed to Smarsh or Global Relay) is the Customer’s own system or vendor, not a Pulse sub-processor. Microsoft 365 contact sync is not currently available to any customer, and the contact sync text in the Privacy Policy and the Data Processing Addendum is draft text that is not in effect. If it is made available and the Customer enables it, Pulse Voice and Pulse SMS will read contacts from the Customer’s Microsoft 365 environment on the Customer’s instructions. For this connection, Microsoft provides the source system under the Customer’s arrangements with Microsoft. This source-system connection is separate from any services Microsoft provides to Pulse as a sub-processor.

YouTube API Services

When you connect a YouTube channel, the Service uses YouTube API Services to upload the videos you create and read your channel name. By connecting YouTube you agree to the YouTube Terms of Service and the Google Privacy Policy. We access your data solely to provide the publishing features you request; we do not use it for advertising or sell it. We store your YouTube access and refresh tokens only while your channel is connected and delete them when you disconnect. You can disconnect the channel at any time in the Service under Admin → Connections, or revoke access from Google’s security settings at security.google.com/settings/security/permissions (also reachable at myaccount.google.com/permissions).

Google Calendar and Microsoft 365 calendars (PulseMeet)

PulseMeet, the Pulse scheduling product, lets a user connect a Google Calendar or Microsoft 365 calendar so that booking pages only offer times that are genuinely free. When you connect a calendar, PulseMeet requests: (a) free/busy information for the calendars you select, used to hide times that are already busy; (b) your list of calendars, so you can choose which to check for conflicts and which one receives bookings (for Microsoft 365, PulseMeet also reads your account email address); and (c) permission to create, update, and delete the booking events PulseMeet itself writes to the calendar you chose. For Google, event access is limited to calendars you own; for Microsoft 365, the permission Microsoft grants is read and write access to your calendars. PulseMeet reads the details of your other events (title, time, location, description, video-meeting link, organizer, and attendees) only to provide these PiP features: (i) if you turn on the PiP Notetaker (off by default; only you can turn it on), to find the upcoming meetings on your primary calendar that have a video link so the notetaker can join them; (ii) to prepare a pre-meeting brief for a booking, by finding your earlier and upcoming events with that invitee (this calendar search is on by default, and you can turn it off on PulseMeet’s Calendars page); and (iii) to answer your own questions to PiP about your meetings, including from PiP for Outlook. Event details used for these features are sent to our AI provider (Anthropic) to write the brief or notes and are not used to train its models. Access and refresh tokens are stored encrypted at rest, are used only to provide these features, and are deleted when you disconnect the calendar. Calendar data is never used for advertising, never sold, and never shared with third parties except the sub-processors that provide the Service (our hosting providers; for the PiP features above, our AI provider; and, if you turn on the PiP Notetaker, Recall.ai, which receives the meeting link and time so the notetaker can join). PulseMeet’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect a calendar at any time from PulseMeet’s Settings, or revoke access at myaccount.google.com/permissions (Google) or myaccount.microsoft.com (Microsoft).

Microsoft 365 contact sync (Pulse Voice and Pulse SMS)

Status: not currently available. Microsoft 365 contact sync is not currently available to any customer of Pulse Voice or Pulse SMS. The text under this heading is draft text: it is not in effect and does not form part of any agreement until it is published as final. It describes how contact sync is intended to work if it is made available.

If contact sync is made available, Pulse Voice and Pulse SMS will be able to copy contacts from a Customer’s Microsoft 365. The copy is one way: contact sync never writes to Microsoft. The Customer decides whether to enable contact sync. It is turned on by the Customer’s administrator, who is shown a notice linking this Privacy Policy and the Data Processing Addendum and confirms their authority to enable it, or by Pulse staff only on a recorded instruction from the Customer’s administrator; Pulse records who turned it on, when, and which version of the notice applied. Pulse processes synced contact data on the Customer’s behalf, as the Customer’s processor, and does not use it for Pulse’s own marketing, for enrichment, or to train models. The Customer is responsible for its lawful basis for importing these details and for any notice it owes to the people whose details are imported. This does not limit Pulse’s obligations as processor under the Data Processing Addendum, including helping the Customer with data-subject requests concerning synced contacts.

Personal Outlook contacts. Once the administrator allows it, each user chooses whether to connect their own Microsoft account. Contact sync requests Microsoft’s delegated Contacts.Read permission, which lets the app read that user’s contacts. In Pulse Voice, contact sync uses the user’s Outlook connection, which may also carry the calendar permissions the user approved for scheduling. In Pulse SMS, personal contact sync is not available to people who sign in only through Microsoft Teams, Zoom, or Webex. Pulse reads the user’s main Outlook contacts folder and the folders directly inside it (not deeper folders) and keeps, as contact details, only the fields listed under “Microsoft 365 contact sync” in Section 2, and only for contacts that have a phone number. To operate the sync, Pulse also reads which folder each contact is in and a synchronization marker from Microsoft that lets the next sync fetch only changes; the folder identifier and the synchronization marker are stored with the connection. Those contacts can include personal, non-work contacts the user keeps in Outlook. Synced contacts are accessible within the application only under the owning user’s login: they are not added to the team’s shared contacts unless, in Pulse SMS, the user deliberately copies a single contact across (see “Copies to shared contacts” below); Pulse support sessions use the staff member’s own identity and do not show them; and ordinary product exports and integrations do not include them. Restricted operational access by authorized Pulse personnel to production systems is governed by the security measures described under “Security” in Section 7 and in Annex II of the Data Processing Addendum. Pulse can retrieve or delete a specific person’s synced record as controlled assistance with a data-subject request under the Data Processing Addendum. In Pulse Voice, synced contacts are used for contact lookup and calling; they are not used to identify callers. In Pulse SMS, they are used to find people and for one-to-one messaging, and their names are shown on that user’s conversations. The contacts are refreshed about every six hours and on demand, and a contact deleted in Outlook is removed at the next successful sync, normally about every six hours.

Copies to shared contacts (Pulse SMS). A Pulse SMS user may copy a single synced Outlook contact to the Customer’s shared contacts. The copy carries a permanent record that it came from that user’s Outlook, which editing it, adding it to a list, or unlinking it does not change, and it stays tied to that Outlook contact: changes the user makes to the contact in Outlook replace the copy’s details at the next successful sync, and the copy is deleted when the contact is deleted in Outlook or loses its last phone number, and whenever that user’s synced contacts are removed (as described under “When synced contacts are removed”, “Recovery period after loss of access”, and “Withdrawal reported by Microsoft” below). It is shown only while the user’s connection is working and their login is active. The use restrictions below apply to it. Copying a contact does not give permission to text them, and a number that has opted out stays opted out.

Microsoft directory. Directory sync copies the people in the Customer’s Microsoft Entra ID directory who have a phone number, excluding disabled accounts and guests. In both Pulse Voice and Pulse SMS, the directory is read through a separate read-only app that the Customer’s Microsoft administrator approves specifically for directory sync, with permission to read users only; this is not the approval given for other Pulse features, such as Teams calling or the Knowledge connector in Pulse Voice. To decide whom to copy, Pulse reads whether each account is enabled and its user type; these are used only to exclude disabled accounts and guests and are not kept as contact details. Pulse also reads a synchronization marker from Microsoft that lets the next sync fetch only changes, which is stored with the connection. An email address is kept only where the person has one. A person who is removed from the directory, is disabled, becomes a guest, or no longer has a phone number is removed at the next successful sync, normally about every six hours (in Pulse SMS, when scheduled updating is not in use, the next time an administrator runs the sync and it succeeds). In Pulse Voice, directory contacts are visible to that Customer’s users and to Pulse workspace staff while those staff are working in that Customer’s account, and they are removed from Pulse’s live contact stores at once when directory sync is turned off. In Pulse SMS, directory contacts are added to the Customer’s shared contacts with a Microsoft directory source label, and each carries a permanent record that it came from the directory, which editing it, adding it to a list, or unlinking it does not change. In Pulse SMS, the removal of a person who leaves the directory deletes their directory contact together with its list memberships, including where someone at the Customer edited it or added it to a list. When a person’s name, email address, company, or phone number changes in Microsoft, the next successful sync updates their directory contact, replacing any of those details someone edited in Pulse SMS; tags added in Pulse SMS stay for as long as the contact does. A contact that someone at the Customer saved themselves and that directory sync only matched by its number holds no Microsoft data; it is not deleted, but it is no longer linked. Whenever Pulse SMS directory sync stops — because an administrator chooses Stop syncing, the Customer’s account is stopped, a different Microsoft organization is connected, Microsoft reports that the approval was withdrawn, or under the 30-day rules below — every directory contact is deleted, together with its list memberships; there is no option to keep them. Importing a person is not consent to be texted, and opt-outs are always honored.

Use restrictions (Pulse SMS). Contacts that come from Microsoft (directory contacts and copies of Outlook contacts) are never included in campaigns, including scheduled campaigns and broadcasts, and are never used for message personalization; a campaign message already queued to such a number is cancelled when it would be sent. A signed-in user of the Customer’s account can text them one to one, but never with a message marked as promotional; such a message is refused. They are not available to API keys or to the AI tools, cannot be created, changed, or deleted with an API key, and cannot be texted by API keys, integrations, or automations, except for automatic replies to a text they sent, such as an opt-out confirmation. A compliance records export can label messages with their names; this export is part of the feature, follows the same visibility rule, and each export that does so is recorded in the account’s audit log. These restrictions stay with the contact for as long as it exists.

Caller names in Pulse Voice. Pulse Voice includes a capability to show a synced contact’s name for an incoming call. It is switched off by Pulse and is not offered: synced contacts are not used to identify callers. Before offering it, Pulse would update this Privacy Policy and the in-product notice.

Copies on devices. The Pulse Voice app holds synced contacts in its working memory while it runs. Favorites a user creates from synced contacts are saved on the device. The app checks them against Pulse each time it starts or returns to the foreground and removes any whose contact is no longer synced; it clears them when the user signs out or Pulse refuses the session; and a favorite that Pulse has not confirmed for 30 days expires and is removed the next time the app runs, even without a connection. An app that is not reopened keeps those copies until it next runs, or until its local data is cleared or the app is uninstalled. The device’s own call history is separate. In Pulse SMS, synced names are held temporarily in the app’s memory and are cleared when the screen reloads.

When synced contacts are removed. Turning the sync off or disconnecting the Microsoft account immediately removes that user’s synced contacts from Pulse’s live contact stores, as does the administrator turning the feature off; in Pulse SMS this includes any copies the user made to shared contacts. When a user turns the sync off or disconnects their Microsoft account, Pulse stops reading contacts, stops using its connection for contact sync, and deletes that connection; in Pulse Voice, where the user keeps the Outlook connection for scheduling, that connection remains and Pulse stops requesting contact access on it. Turning contact sync off stops address-book syncing. If a user keeps their Outlook scheduling connection in Pulse Voice, Pulse Voice may still retrieve names and email addresses from Microsoft to suggest meeting invitees while the user searches. Those suggestions are shown only to that user and are not saved as synced contacts. In Pulse Voice, a user’s access ends when their login is deactivated, and their synced contacts are removed at the next scheduled run at the latest, normally within about six hours; if the Customer or its workspace is suspended, its synced contacts stop being shown at once and are removed at the next scheduled run, and reinstatement does not turn sync back on. In Pulse SMS, synced personal contacts and their copies are removed when the person is offboarded, when their Pulse login is suspended or removed, or when the Customer’s account is suspended or loses Pulse SMS.

Recovery period after loss of access. If refreshing a user’s Outlook connection or the Customer’s directory connection fails, a recovery period starts with the first failed refresh after the last successful one (or after the sync was turned on). During the period, contacts already synced stay available and may become out of date. Only a successful refresh ends the period; signing in to Microsoft again or approving Pulse again in Microsoft does not, and a later failure starts a new period. If refreshing continues to fail, we remove the synced contacts at the first scheduled sync after 30 continuous days of failure (in Pulse SMS, including copies to shared contacts, and for the directory every directory contact). Where a valid email address and an email service are available, we attempt a warning around day 23: for personal Outlook contacts, to the user; for the directory, in Pulse Voice to the Customer’s contact email address and its active administrator logins, and in Pulse SMS to the Customer’s account administrators. Removal does not depend on sending or receiving that warning. While refreshes are failing, the product shows the removal date; signing in again does not by itself prevent removal, which is avoided only by a successful sync before that date. Turning sync off or giving an applicable deletion instruction is handled separately and is not delayed by this recovery period; the same applies to disconnecting the Microsoft account, deactivation or removal of the user’s login, suspension of the Customer’s account, and the administrator turning the feature off. In both products, synced contacts are also deleted, in the same way and with the same warning, after 30 days without a successful sync for any other reason, for example because the feature is switched off or no longer available for the Customer’s account, the Customer’s acceptance is awaiting renewal, or, in Pulse SMS where scheduled updating is not in use, nobody runs the sync. Those 30 days are counted from the last successful sync or, if none succeeded, from when the connection was set up (Pulse SMS) or when the first contact was stored (Pulse Voice). In Pulse Voice, a user’s Outlook calendar connection is kept when their synced contacts are deleted this way.

Withdrawal reported by Microsoft. Where Microsoft reports that Pulse’s permission or approval was withdrawn (for example, the consent was revoked or declined, the app was removed or disabled in the Customer’s Microsoft organization, or the Customer’s Microsoft administrator refused the directory approval), the recovery period does not apply. The affected synced contacts are hidden at once and cannot be used. In both products, they are shown again only if, after the withdrawal, the user signs in to Microsoft again (personal Outlook contacts) or the Customer’s Microsoft administrator approves the app again (directory), and the sync is still on and allowed (in Pulse SMS, the user’s login must also still be active); a successful response using access that Microsoft issued before the withdrawal does not restore them. While they are hidden, Pulse Voice makes only the calls to Microsoft needed to verify this, and Pulse SMS reads nothing from Microsoft. Otherwise, in Pulse Voice they are deleted at the first scheduled run at or after a deadline recorded with the withdrawal, about 24 hours after it; if a scheduled run is late, deletion happens at the next run. In Pulse SMS, the contacts, including copies to shared contacts, are deleted at the first scheduled run after the withdrawal unless that fresh approval or sign-in has been recorded by then, and in any case no later than the first scheduled run at or after a deadline recorded about 24 hours after the withdrawal. Turning the sync off deletes the contacts from Pulse’s live contact stores at once, and nothing in the product restores them afterwards (copies already in a recovery point are described under “Backups” below). Pulse treats only Microsoft’s specific withdrawal signals this way; any other failure is handled under the recovery period. Microsoft may keep accepting access already issued to Pulse for a period after an approval is removed, so to stop processing at once, turn the sync off in Pulse. Pulse does not revoke the authorization on Microsoft’s side. Microsoft’s own record of the approval may expire or be revoked earlier, and otherwise remains until the user or the Customer’s Microsoft administrator removes it in Microsoft, after which Microsoft stops issuing new access to Pulse. Where the Customer’s Microsoft administrator has already approved the app for the organization, Microsoft may not show the user another approval screen; the user still chooses whether to turn contact sync on in Pulse. Turning contact sync off stops Pulse’s contact-sync reads and removes the synced contacts as described above, but does not remove Microsoft’s permission grant. A grant made for the organization is managed or removed by the Customer’s Microsoft administrator, and the user may not be able to remove it.

Access records. Pulse records access to synced contacts without recording their contents. In Pulse Voice, each read of synced contacts through the contact list, search, lookup, and sync status and sync routes writes an access record holding the user and their role, the workspace, the Customer scope, the operation, the outcome and a reason code, the number of results, a request identifier, and the time; it never holds contact names, numbers, email addresses, search terms, or tokens. Pulse Voice keeps these records for 180 days by default and then deletes them, except where a preservation hold applies. In Pulse SMS, each request that returns Microsoft-derived contacts, and each compliance export that labels messages with their names, is recorded in the account’s audit log with the actor, the scope, the route, the outcome, and the count, without contact contents or search text; sync failures, recoveries, warnings, and deletions are logged with counts. No specific retention period has yet been set for these Pulse SMS audit records.

Backups. The two databases that would hold synced contacts, those of Pulse Voice and Pulse SMS, have point-in-time recovery covering the past 7 days. Manual exports of those databases, if any are made, are kept for at least 7 days and are deleted by hand. Deletion from live systems does not remove data already in a recovery point until that point ages out. A written procedure for restoring synced contacts from a backup has not yet been approved and is not in operation. Under the procedure being considered, the data would be restored to an isolated copy with contact sync and message sending turned off, recorded deletions would be re-applied, and the copy would be checked before it is used.

6. Mobile information & SMS

Mobile phone numbers and SMS consent are not shared with, sold, or rented to third parties or affiliates for their own marketing. Mobile information is used only to deliver the messaging the Customer configured, including through Twilio. Recipients may reply STOP/HELP at any time.

7. Retention, your rights & security

We retain account and content data while the organization account is active. From Security in the app you can export your data (JSON) and delete your account. To exercise other rights, contact pulselegal@pulsetechnologies.ai; we action verified requests within 30 days. For the open and click information on service and transactional email described in section 2, Pulse keeps the detected status with the related record, such as the invoice email, and our sending sub-processor keeps its own event records under its terms; to object to this tracking or ask us to delete it, use the same contact.

Closing an account is not the same as deleting every record

Closing or deleting an account ends access to it and removes the account’s content and settings, subject to the legal and contractual exceptions in this section and the Data Processing Addendum. It does not by itself delete every record associated with the account. The records below are kept after closure, for the reasons and periods shown. If you ask us to delete data that falls in one of these categories, the request is completed when the period ends.

RecordWhy we keep itHow long, and from whenAt the end of the period
Call detail records and the call log (Pulse Voice)Telecom regulatory recordkeeping and tracing of unlawful or abusive calls.At least five years from the date of the call. This is a platform minimum; a Customer cannot set it lower. A legal hold on a workspace suspends deletion.Deleted by a scheduled sweep.
Compliance call recordings, with their transcripts and analysis (Pulse Voice)The Customer chose write-once compliance recording to meet its own recordkeeping duties. The archive is locked, so nobody — the Customer or Pulse — can delete a recording before the end of its period.The period in the Customer’s recording policy, counted from the time the recording is archived. The Customer sets it per policy: no shorter than 365 days (the default), and longer where its own obligations require. A legal hold extends it until the hold is lifted.The recording is deleted by a scheduled purge, and its transcript and analysis are deleted with it. A log entry that the recording existed and was deleted remains in the audit log.
Fax archive (Pulse Voice), where enabledThe Customer chose write-once archiving of its faxes.The period set for the Customer’s account; seven years unless the Customer sets another period. A legal hold extends it.Deleted by a scheduled purge.
Pulse Secure Transfer filesFiles sent to Pulse are stored write-once, so they cannot be deleted before their period ends.One year (General) or seven years (Regulated) from the time the file is uploaded, according to the category of the request. Deleting a request from the staff console does not shorten it.The lock lapses and the files become eligible for deletion.
Agreement recordsEvidence of acceptance of Pulse’s terms, an order, or the 911 advisory, and to establish, exercise, or defend legal claims (see Section 2).While the agreement is in effect and afterward for as long as needed to prove the acceptance and defend claims about it.Removed, after manual review, once no longer needed for those purposes.

Customers control the period for recordings and the fax archive from the settings of their workspace’s recording policy and fax archive. Pulse does not use records kept under this section for any purpose other than the reason shown.

Security

We protect data with encrypted transport (HTTPS), salted-hash passwords, httpOnly session cookies, optional two-factor authentication (which an organization can require), single sign-on (OpenID Connect or SAML 2.0, and Sign in with Microsoft) and SCIM provisioning, organization-set session limits and sign-out everywhere, server-side session checks, role-based access with tenant isolation, rate limiting, pre-publish screening, encryption of recordings, transcripts, and archived files before storage, and audit logs. The Service is for business use by adults and is not directed to children.

8. Product-specific disclosures

Pulse Voice

  • Call recording and monitoring. Pulse Voice can record, transcribe, and analyze calls where a Customer turns it on. The Customer is responsible for giving any legally required notice and obtaining any required consent from call participants. If you are a caller and have questions about a recording, contact the business you called.
  • Compliance recording. Where a Customer enrolls a workspace in compliance recording, calls are recorded as its recording policy provides. Recordings are encrypted and stored write-once, so they cannot be altered or deleted, by the Customer or by Pulse, until the retention period in the policy ends; a legal hold extends it. Transcripts and AI analysis are produced only if the policy asks for them.
  • Callers and end users. Pulse processes data about the people a Customer’s users call, or are called by, as that Customer’s processor. Please contact the relevant Customer about its handling of your data; if Pulse receives a request about such data, we refer it to that Customer.
  • Fax archive. Where a Customer turns on the fax archive, the fax documents it sends and receives are encrypted and stored write-once for the retention period set for the Customer’s account, and may be placed on legal hold.
  • Provider credentials. AI-provider and carrier credentials a Customer stores are encrypted at rest. Where a Customer connects its own provider account, that provider processes the data under the Customer’s own agreement with it.
  • No sale; no model training. Pulse does not sell personal data processed through Pulse Voice and does not use it to train third-party foundation models.

PulseMeet

  • Team availability. Members of the same PulseMeet organization can see one another’s working hours and free/busy time, never event titles or attendees.

PulseWork

  • Isolation and access. Each organization’s PulseWork data is isolated to that organization. Sessions are kept server-side (only a hash of the session token is stored) and are ended when a person signs out or is removed.
  • Email-in. Where a Customer connects a Microsoft 365 mailbox, PulseWork reads messages arriving in that mailbox to open and update tickets.
  • Pulse’s own support desk. Pulse’s support desk runs on PulseWork. From June 2026 until October 2026, its tickets were also mirrored to Atlassian Jira Service Management; that mirroring has ended.

Pulse SMS

  • Records. Account administrators can place litigation holds (a held message cannot be deleted by anyone), hand a departed employee’s lines to a successor, and export messages. These actions are recorded in an audit log.

Pulse Secure Transfer

  • Storage and deletion. Files are encrypted with per-file keys, scanned for malware, and stored write-once for a retention period set by the request’s category. Deleting a request removes it from the staff console but does not destroy the stored files, which cannot be deleted sooner than that period.

Social Command

  • Connected platform data. We access only the social accounts you explicitly authorize during connection. Access tokens are stored server-side only and never exposed to the browser. We use platform data solely to provide the posting and engagement features; we do not sell it or use it for advertising or profiling. We post only on an action initiated by an authorized user or a job that user scheduled. Disconnecting an account removes its stored tokens.
  • Cookies in the app. The Social Command app uses only strictly necessary cookies: an httpOnly session cookie that keeps you signed in and a short-lived cookie used while you connect an account. It uses no advertising or third-party tracking cookies. Cookies on our website are described in Disclosures & Policies.
  • Compliance capture. Where a Customer turns on compliance capture, a copy of its communications is forwarded to the archiving, supervision, or eDiscovery system the Customer configures and controls. That destination is the Customer’s own system or vendor, not a Pulse sub-processor.

9. Changes & contact

We may update this policy; material changes update the effective date. Pulse Payments LLC (dba Pulse Technologies)
9160 Forum Corporate Pkwy, Suite 350, Fort Myers, FL 33905
pulselegal@pulsetechnologies.ai

Effective date: October 28, 2026. Last revised: November 11, 2026. Version: DPA-DRAFT

This Data Processing Addendum (“DPA”) forms part of the agreement between Pulse Payments LLC (dba Pulse Technologies) (“Pulse”, “Processor”) and the customer organization (“Customer”, “Controller”) for use of the Pulse platform. Where Customer Personal Data is processed, this DPA applies.

1. Roles & scope

The Customer is the Controller and Pulse is the Processor of Customer Personal Data. Pulse processes it only to provide the Service and in accordance with the Customer’s documented instructions (these Terms, the Privacy Policy, and this DPA), unless required by law.

2. Processor obligations

  • Instructions: process only on the Customer’s documented instructions.
  • Confidentiality: personnel are under confidentiality obligations.
  • Security: implement the measures in Annex II.
  • Sub-processors: The Customer authorizes Pulse to use the sub-processors identified in Annex III. Pulse shall impose on each sub-processor data-protection obligations no less protective than those required by this DPA and remains responsible for its sub-processors as required by applicable data-protection law.

    Pulse shall give the Customer at least 30 days’ prior written notice before permitting an additional or replacement sub-processor to process Customer Personal Data, or materially expanding an existing sub-processor’s processing activities involving Customer Personal Data. The notice shall identify the sub-processor, the proposed change, its processing activities and locations, and the applicable safeguards, including any international-transfer safeguards. Updating a public list alone does not constitute notice.

    The Customer may object within that notice period on reasonable grounds relating to the protection of Customer Personal Data. Pulse shall consider the objection in good faith and seek a reasonable solution. While a timely objection remains unresolved, Pulse shall not implement the proposed change in relation to that Customer’s Personal Data. Existing processing unaffected by the proposed change may continue under this DPA.

    If the parties cannot resolve the objection within 30 days after Pulse receives it, Pulse shall either refrain from implementing the proposed change for that Customer or, where it cannot reasonably provide the affected Service without the change, either party may terminate the affected Service on written notice before the proposed change is implemented for that Customer. Pulse shall refund prepaid fees attributable to the unused period of the terminated Service, without an early-termination charge.

    The 30-day notice period applies to additional or replacement sub-processors appointed directly by Pulse and to material expansions of their processing activities involving Customer Personal Data.

    Where a directly appointed sub-processor proposes a change to its own sub-processors, Pulse shall notify the Customer promptly after receiving notice and before the proposed processing begins, providing the available details and the effective date. Pulse shall preserve the Customer’s opportunity to object on reasonable data-protection grounds and shall seek a reasonable resolution with the provider. If the available notice does not permit a meaningful opportunity to object, or a timely objection remains unresolved, Pulse shall not permit the proposed processing of that Customer’s Personal Data, including by suspending the affected processing where necessary. This paragraph does not limit applicable statutory or Standard Contractual Clause requirements.

    This clause does not limit any rights or obligations under applicable data-protection law or applicable Standard Contractual Clauses.
  • Assistance: help with data-subject requests, breach notification, and impact assessments.
  • Breach notification: notify the Customer without undue delay.
  • Deletion/return: on termination, delete or return within 60 days, except where retention is required by law.
  • Audits: make available information to demonstrate compliance and allow reasonable audits.

3. International transfers

Customer Personal Data may be processed in the United States. Transfers from the EEA, UK, or Switzerland to a country without an adequacy decision are governed by the applicable Standard Contractual Clauses (and the UK IDTA), incorporated by reference.

4. Special categories & HIPAA

The Customer must not submit special-category data unless its configuration and legal basis permit it. The Customer may process protected health information subject to HIPAA only under an executed Business Associate Agreement that expressly covers the relevant Pulse services and the configuration the Customer uses. Without such an agreement for a service, that service must not be used to process PHI.

Annex I — Details of processing

Nature & purpose

Hosting; AI generation and the in-app assistant (which proposes content for approval and does not publish autonomously); scheduling and publishing social content; business text messaging; opted-in email; outbound AI voice calls including processing call audio and transcripts; business phone service — routing, connecting, and (where turned on) recording inbound and outbound calls, voicemail and its transcription, fax (including the optional write-once fax archive), and the Customer’s AI voice agents; hosting video meetings and, where turned on, recording, transcribing, and summarizing them; appointment scheduling, including checking connected calendars, creating calendar and Zoom events for bookings, booking confirmations and reminders, pre-meeting briefs, and, where a user turns it on, the PiP Notetaker joining and summarizing that user’s meetings; contact-center routing of calls, web chats, texts, and emails, customer-satisfaction surveys, and activity logging to CRMs the Customer connects; PiP for Outlook and Teams reading the Microsoft 365 content of the user who connects it; where the Customer turns on Microsoft 365 contact sync (not currently available to any customer; see “Status of Microsoft 365 contact sync” below), importing, hosting, and refreshing contacts from its users’ Outlook contacts and its Microsoft 365 directory for contact lookup and calling in Pulse Voice and for finding contacts and one-to-one messaging in Pulse SMS, adding directory contacts to the Customer’s shared contacts in Pulse SMS when the Customer’s administrator activates directory sync, and copying a single Outlook contact to shared contacts where a user deliberately does so; delivering documents the Customer sends for e-signature; recurring billing and invoicing of the Customer’s own customers, including tax calculation; embedding Customer knowledge-base documents for retrieval; API and webhooks; optional compliance-capture forwarding to the Customer’s own archiving system; where the Customer connects a Shopify store, ingesting its orders and checkouts to run the Customer’s ecommerce automations, attribute revenue, and segment its customers; publishing blog posts to content management systems the Customer connects; push notifications to mobile and desktop apps; support; usage analytics; unified sign-in and cross-product access management; and user access and billing.

Data subjects & categories

The Customer’s users, SMS/voice/email recipients, callers and fax senders, meeting participants and booking invitees, contact-center customers (chat visitors, emailers, and survey respondents), the Customer’s store customers reflected in orders synced from a connected Shopify store, where the Customer turns on Microsoft 365 contact sync (not currently available to any customer), the members of the Customer’s Microsoft 365 directory (employees and other directory members) and the business and personal contacts held in its users’ Outlook contacts (external business contacts and, potentially, users’ private contacts), and individuals referenced in Customer Content. Categories include names and emails, authentication data, content and media, connected-account identifiers/tokens, a per-user assistant profile (work-style preferences and durable support-relevant facts, user-clearable), mobile numbers and message content, call audio, transcripts, and call metadata, call recordings, voicemail, and fax documents, booking details (invitee name, email, phone, and answers) and calendar event details, meeting recordings, transcripts, and AI notes, web-chat transcripts and attachments, contact-center email threads, and survey responses, email contacts and email engagement data (recipient email address; message-associated delivery, detected-open, click, bounce, reply, and unsubscribe records; detected-open timestamps; broad mail-app categories; indicators of possible automated or proxy loading; and Customer- and message-scoped keyed hashed identifiers derived from the Customer account identifier, the message identifier, the mail-app category, and a truncated source-network address (IPv4 /24 or IPv6 /48); derived data includes estimated distinct opening environments), billing and invoice records of the Customer’s own customers, synced Microsoft 365 contact data (name, company, job title, department, email address (where the person has one), phone numbers, and Microsoft object identifiers), information read only to operate that sync (for directory members, whether the account is enabled and its user type, which are used to decide what to copy and are not kept as contact details; for Outlook contacts, the identifier of the folder a contact is in; and a synchronization marker from Microsoft that lets the next sync fetch only changes; the folder identifier and the synchronization marker are stored with the connection), and records of access to synced contacts, which hold no contact contents, knowledge-base documents, developer credentials, support-ticket content, cross-product access-management records, and audit/log data. The Customer should avoid submitting special-category data (see Section 4).

Email engagement data. Email engagement data is processed for Customer-directed campaign measurement and reporting. Each detected-open record in the engagement database is automatically deleted 90 days after its recording. This period applies to the detected-open event record, including its timestamp, mail-app category, keyed identifier, and associated classification flags. It does not apply to other categories of data listed above. Deletion and return obligations under this DPA continue to apply.

Status of Microsoft 365 contact sync: not currently available. Microsoft 365 contact sync is not currently available to any customer. The contact sync text in this Annex, including the references to it above and the paragraphs below from “Synced Microsoft 365 contacts” to “Backups”, is draft text: it is not in effect and does not form part of this DPA or any other agreement until it is published as final. It describes how contact sync is intended to work if it is made available.

Synced Microsoft 365 contacts. If contact sync is made available, synced contact data will be processed, where the Customer turns contact sync on, for contact lookup and calling in Pulse Voice and for finding contacts and one-to-one messaging in Pulse SMS; it is not used to identify callers. Synced contacts follow their source at the next successful sync: a contact deleted in Outlook, or a directory member who is removed, is disabled, becomes a guest, or no longer has a phone number, is removed, normally within about six hours (for the Pulse SMS directory when scheduled updating is not in use, the next time an administrator runs the sync and it succeeds), and in Pulse SMS this includes directory contacts that someone at the Customer edited or added to a list, and copies of Outlook contacts in shared contacts. Changes to a person’s name, email address, company, or phone number in Microsoft replace those details at the next successful sync. A user’s synced Outlook contacts are removed from Pulse’s live contact stores at once when the user turns the sync off or disconnects their Microsoft account or the Customer’s administrator turns the feature off. Directory contacts in Pulse Voice are removed from those stores at once when directory sync is turned off. In Pulse Voice, a user’s access ends when their login is deactivated, and their synced contacts are removed at the next scheduled run at the latest; if the Customer or its workspace is suspended, its synced contacts stop being shown at once and are removed at the next scheduled run, and reinstatement does not turn sync back on. In Pulse SMS, synced personal contacts are removed when the person is offboarded, when their Pulse login is suspended or removed, or when the Customer’s account is suspended or loses Pulse SMS. Copies held by the Pulse Voice app are limited to its working memory and to favorites created from synced contacts, which the app reconciles with Pulse each time it starts or returns to the foreground, clears on sign-out or when Pulse refuses the session, and removes, even without a connection, the next time it runs once Pulse has not confirmed them for 30 days; an app that is not reopened keeps those copies until it next runs or its local data is cleared, and the device’s own call history is separate. The Customer is responsible for its lawful basis for importing these details and for any notice it owes to the individuals concerned; this does not limit Pulse’s obligations as Processor under this DPA, including helping with data-subject requests concerning synced contacts.

Microsoft-derived contacts in Pulse SMS. Directory contacts and Outlook contacts that a user copied to the Customer’s shared contacts carry a permanent record of their Microsoft origin that editing, list changes, or unlinking do not change. A copied Outlook contact stays tied to its Outlook contact: it is updated from it, deleted when it is deleted in Outlook or loses its last phone number, and deleted whenever the copying user’s synced contacts are removed. A contact that the Customer’s team saved themselves and that directory sync only matched by its number holds no Microsoft data and is not deleted, but is no longer linked. Whenever Pulse SMS directory sync stops (an administrator stops it, the Customer’s account is stopped, a different Microsoft organization is connected, Microsoft reports the approval withdrawn, or under the 30-day rules below), every directory contact is deleted, including edited or listed ones, with its list memberships; there is no option to keep them. These contacts are never included in campaigns (including scheduled campaigns and broadcasts), used for message personalization, or sent a message marked as promotional; they are returned only to signed-in users of the Customer’s account, can be texted one to one by those users, are not available to API keys or the AI tools, and cannot be texted by API keys, integrations, or automations except for automatic replies to a text they sent. A compliance records export can label messages with their names under the same visibility rule, and each such export is recorded in the account’s audit log. Importing a person is not consent to be texted, and opt-outs are always honored.

Recovery period after loss of access. If refreshing a user’s Outlook connection or the Customer’s directory connection fails, a recovery period starts with the first failed refresh after the last successful one (or after the sync was turned on). During the period, contacts already synced stay available and may become out of date. Only a successful refresh ends the period; signing in to Microsoft again or approving Pulse again in Microsoft does not, and a later failure starts a new period. If refreshing continues to fail, Pulse removes the synced contacts at the first scheduled sync after 30 continuous days of failure. Where a valid email address and an email service are available, Pulse attempts a warning around day 23 (for personal Outlook contacts, to the user; for the directory, in Pulse Voice to the Customer’s contact email address and its active administrator logins, and in Pulse SMS to the Customer’s account administrators). Removal does not depend on sending or receiving that warning, and only a successful sync before the removal date avoids it. Turning sync off or giving an applicable deletion instruction is handled separately and is not delayed by this recovery period; the same applies to disconnecting the Microsoft account, deactivation or removal of the user’s login, suspension of the Customer’s account, and the Customer’s administrator turning the feature off. In both products, synced contacts are also deleted, with the same warning, after 30 days without a successful sync for any other reason (for example because the feature is switched off or the Customer’s acceptance is awaiting renewal), counted from the last successful sync or, if none succeeded, from when the connection was set up (Pulse SMS) or the first contact was stored (Pulse Voice).

Withdrawal reported by Microsoft. Where Microsoft reports that Pulse’s permission or approval was withdrawn, the recovery period does not apply, and the affected synced contacts are hidden at once and cannot be used. In both products, they are shown again only if, after the withdrawal, the user signs in to Microsoft again or the Customer’s Microsoft administrator approves the app again, and the sync is still on and allowed (in Pulse SMS, the user’s login must also still be active); a successful response using access issued before the withdrawal does not restore them. Otherwise, in Pulse Voice they are deleted at the first scheduled run at or after a deadline recorded with the withdrawal, about 24 hours after it, or at the next run if a run is late; in Pulse SMS they are deleted at the first scheduled run after the withdrawal unless that fresh approval or sign-in has been recorded by then, and in any case no later than the first scheduled run at or after a deadline recorded about 24 hours after the withdrawal. Turning the sync off deletes them from Pulse’s live contact stores at once, and nothing in the product restores them afterwards (see “Backups” below). Only Microsoft’s specific withdrawal signals are treated this way; any other failure is handled under the recovery period. Microsoft may keep accepting access already issued to Pulse for a period after an approval is removed; turning the sync off in Pulse stops processing at once.

Organization-wide Microsoft approval. Where the Customer’s Microsoft administrator has already approved the app for the organization, Microsoft may not show a user another approval screen; each user still chooses whether to turn personal contact sync on. Turning contact sync off stops Pulse’s contact-sync reads and removes the synced contacts as described above, but does not remove Microsoft’s permission grant, which the Customer’s Microsoft administrator manages or removes where it was granted for the organization.

Caller names and access records. Showing a synced contact’s name for an incoming call in Pulse Voice is switched off by Pulse and is not offered; before offering it, Pulse would update this DPA and the in-product notice. Pulse records access to synced contacts without their contents: in Pulse Voice, access records are kept for 180 days by default and then deleted, except where a preservation hold applies; in Pulse SMS, reads that return Microsoft-derived contacts are recorded in the account’s audit log, for which no specific retention period has yet been set.

Backups. The two databases that would hold synced contacts, those of Pulse Voice and Pulse SMS, have point-in-time recovery covering the past 7 days. Manual exports of those databases, if any are made, are kept for at least 7 days and are deleted by hand. Deletion from live systems does not remove data already in a recovery point until that point ages out. A written procedure for restoring synced contacts from a backup has not yet been approved and is not in operation. Under the procedure being considered, the data would be restored to an isolated copy with contact sync and message sending turned off, recorded deletions would be re-applied, and the copy would be checked before it is used.

Annex II — Security measures

  • Encryption of data in transit (HTTPS/TLS).
  • Passwords, one-time tokens, and API keys stored only as hashes; reset/invite tokens expire automatically.
  • httpOnly, Secure session cookies; optional 2FA and SSO; role-based access control within each organization.
  • Tenant isolation — each organization’s data is segregated and scoped.
  • Third-party access tokens stored server-side only.
  • Rate limiting on authentication and AI endpoints; pre-publish screening that blocks card numbers and secrets.
  • Signed webhooks (HMAC-SHA256); audit logging of sensitive actions, including support sessions; error monitoring; production access limited to authorized personnel.

Annex III — Approved sub-processors

The sub-processors below are those Pulse engages as a processor of Customer Personal Data. The maintained list, including providers Pulse uses only for its own controller data, is on the Sub-processors tab.

Sub-processorPurposeLocation
VercelHosting, functions, media storageUnited States
NeonManaged PostgreSQL database.United States
RenderHosting, managed PostgreSQL, and caching for Pulse Email and the shared contact graph, Pulse Voice, PulseConnect, PulseMeet, Pulse SMS, PulseBill, Pulse Deals, Pulse RFP, PulseWork, Pulse Secure Transfer, and PulseAdminUnited States
AnthropicAI generation and the assistant (PiP), including AI voice agents, meeting recaps and notes, pre-meeting briefs, and post-call analysis of recorded calls (card-masked transcript text) where turned onDetermined by the provider
OpenAI, Google (Gemini), xAI, Deepgram, Cartesia (if enabled)Alternative AI models, speech-to-text, and text-to-speech selected by the Customer for Pulse Voice AI voice agents; OpenAI image generation and voiceover in Social CommandUnited States
fal.ai (if enabled)AI image generation.United States
ElevenLabsText-to-speech for PiP, AI voice agents, and voiceoverUnited States
Recall.ai (if enabled)PulseMeet PiP Notetaker — receiving the meeting link and time of a user’s video meetings, joining them, and returning the recording, transcript, and participant namesUnited States
Connected social networksPublishing to networks the Customer connectsVaries
TwilioSMS/MMS/WhatsApp/RCS delivery (default carrier); alternative Pulse Voice call control (if enabled)United States
Meta / WhatsApp (if enabled)WhatsApp Business message delivery (via Twilio)United States
TelnyxSMS/MMS delivery (alternative carrier); primary telephony carrier for Pulse Voice and PulseConnect — call control, number provisioning and porting, fax, call recordings, video meeting rooms, and voicemail, meeting, and recorded-call transcriptionDetermined by the provider
NTT (if enabled)Carrier for Pulse Voice numbers on NTT Cloud Voice — number ordering and porting, E911 addresses, Teams routing, and call-detail recordsUnited States
PulseVoice (if enabled)Outbound AI voice calls, the AI agent, and video meeting rooms used by other Pulse productsUnited States
Pulse SSO / PulseAdminUnified sign-in and cross-product access managementUnited States
Amazon Web Services (S3) (if enabled)Encrypted, write-once storage for the Pulse Voice fax archive and compliance call-recording archiveUnited States by default; a Customer may select another region for its recording archive
Apple, Google (Firebase Cloud Messaging), ExpoMobile push notifications for the Pulse Voice appsUnited States
Better StackApplication logging, uptime monitoring, and status pageUnited States
OneSignal / Sentry (if enabled)Push notifications / error monitoringUnited States
Microsoft (if enabled)Microsoft Teams sign-in, notifications, and calling provisioning; Microsoft sign-in and single sign-on; PulseWork support-mailbox email-in; Microsoft 365 calendar availability, booking events, and event details for PiP features for PulseMeet; SharePoint/OneDrive knowledge connectors; PiP for Outlook and TeamsDetermined by the provider
Google (if enabled)Google sign-in for organization single sign-on; Google Calendar availability, booking events and, for PiP features, event details for PulseMeet; Google Calendar availability and booking events for Pulse Voice agents; Google Drive knowledge connector; RCS Business Messaging delivery (via Twilio)Determined by the provider
Zoom (if enabled)Zoom meetings for PulseMeet bookings; the PulseSMS app for Zoom; Zoom Phone provisioning for Pulse VoiceUnited States
Connected business apps (if enabled)Exchanging data with third-party applications the Customer connects under its own account (CRMs, Cisco Webex, other calling and contact-center platforms, accounting, e-commerce, design tools, content management systems, and chat, code-hosting, and ticketing tools connected to PulseWork); reading contacts from the Customer’s Microsoft 365 environment where the Customer enables Microsoft 365 contact sync, once that feature is made available (it is not currently available to any customer; see the note below this list)Varies
Cloudflare (if enabled)DNS and secure proxying for Customer white-label domainsUnited States
Apollo (if enabled)Contact enrichmentUnited States
Atlassian (Jira Service Management)Support-desk ticketing (mirroring ended October 2026)Determined by the provider
Accept.blueSubscription and merchant payment processing (card data handled by Accept.blue and its underlying processors)United States
ResendTransactional and opted-in marketing email, booking and meeting emails, and the PulseConnect email channelUnited States
SignWell (if enabled)E-signature delivery for documents the Customer sends for signatureUnited States
Voyage AI (if enabled)Text embeddings for knowledge-base searchUnited States
CereTaxTax calculation and tax reporting for PulseBill invoices; CereTax is the production tax providerUnited States

Some sub-processors are engaged only when a Customer enables the related feature (marked “if enabled”). Where a Customer connects its own third-party provider account with its own credentials (for example its own AI provider or carrier account in Pulse Voice), that provider acts under the Customer’s own agreement and is not a Pulse sub-processor for that data. Where a Customer turns on compliance capture, the archiving, supervision, or eDiscovery system it configures (for example an HTTPS/webhook endpoint, an SMTP journaling address, a Microsoft 365 / Purview mailbox, Proofpoint, or an SFTP feed to Smarsh or Global Relay) is the Customer’s own system or vendor, not a Pulse sub-processor. Microsoft 365 contact sync is not currently available to any customer, and the contact sync text in the Privacy Policy and the Data Processing Addendum is draft text that is not in effect. If it is made available and the Customer enables it, Pulse Voice and Pulse SMS will read contacts from the Customer’s Microsoft 365 environment on the Customer’s instructions. For this connection, Microsoft provides the source system under the Customer’s arrangements with Microsoft. This source-system connection is separate from any services Microsoft provides to Pulse as a sub-processor.

Contact

Pulse Payments LLC (dba Pulse Technologies)
9160 Forum Corporate Pkwy, Suite 350, Fort Myers, FL 33905
pulselegal@pulsetechnologies.ai

Last updated: October 29, 2026

To deliver the Pulse platform — Social Command, Pulse SMS, Pulse Email / PulseEngage, Pulse Voice, PulseConnect, PulseMeet, PiP for Outlook and Teams, PulseBill and PulsePay, Pulse RFP, Pulse Deals, PulseWork, Pulse SSO / PulseAdmin, and our mobile and desktop apps — Pulse Payments LLC (dba Pulse Technologies) engages the third-party sub-processors below. This is the single list for every Pulse product; the Privacy Policy (Section 5) and the Data Processing Addendum (Annex III) show the same list. Sub-processors are engaged under terms no less protective than the Data Processing Addendum, and Pulse gives Customers prior written notice of an additional or replacement sub-processor, or of a material expansion of an existing sub-processor’s processing, and prompt notice of a change a sub-processor makes to its own sub-processors, with a right to object, as described there.

October 2026 update. Beginning October 22, 2026, PulseBill uses CereTax as its production provider for telecom and sales-tax calculation. For invoices issued on or after November 1, 2026, tax associated with issued invoices is also recorded with CereTax for tax reporting.

Changes in the October 28, 2026 update. This update changes how the list is described; it is grouped here by kind of change. A provider is engaged only for the products and features named in its row.

  • Newly engaged: CereTax, as described in the October 2026 update above (processing began October 22, 2026). No other provider is newly engaged in this update.
  • Expanded uses of existing providers: Telnyx transcribes recorded calls; Amazon Web Services (S3) stores the write-once compliance call-recording archive; and the AI provider (Anthropic) analyzes recorded-call transcripts (card numbers masked, never audio) and answers PiP requests in Pulse Voice team chat, where the Customer turns the feature on (PiP in team chat is available to a workspace’s users without a separate setting). These recording features were first used in production in October 2026. Atlassian (Jira Service Management) received copies of Pulse’s own support-desk tickets from June 2026 until October 2026, when that mirroring ended, and, for PulseWork, a Customer can connect Slack and Microsoft Teams notifications and GitHub events under its own account.
  • Corrections describing processing that was already in place before this update: Pulse RFP, PulseWork, and Pulse Secure Transfer are hosted with Render; Microsoft and Google provide sign-in and single sign-on for the Pulse login and for an organization’s own identity provider; and, for PulseWork, a Customer can connect a Microsoft 365 support mailbox for email-in.

Revision history. November 13, 2026 (second update): correction and disclosure in the Privacy Policy — (1) a dated correction that, until November 13, 2026, three emails Pulse sent to prospects carried our sending sub-processor’s own open and click tracking despite the settings described, with what was changed and deleted; (2) a definition of the PulseEngage sending service; (3) link-click records are deleted after 90 days, and the opened or clicked status on a send record is not covered by that limit; (4) a new description of open and click tracking on service and transactional email sent from pulsetechnologies.ai, including Pulse’s own invoices. Earlier versions are preserved. November 13, 2026: clarification to the Privacy Policy (email marketing) — the open-tracking default for journeys sent to prospects describes a control and is not permission to send, and the PulseEngage sending service may be used only for recipients who have opted in. November 11, 2026: substantive disclosure and control update to the Privacy Policy (email marketing) and the Data Processing Addendum (Annex I) — email open tracking in PulseEngage is described in full: what is recorded for each detected open, that these records are linked to the recipient’s email address, the 90-day deletion of detected-open records in the engagement database, technical request logs, and the account and journey controls. This replaces a shorter description published earlier the same day. A further correction later that day removed from Annex I a reference to retention arrangements for other records that had not yet been specified, placed the email engagement retention terms in their own paragraph, and stated in the Privacy Policy that Pulse is the controller for its own marketing. October 29, 2026: accuracy corrections to this page, the Privacy Policy (Section 5), and the Data Processing Addendum (Annex III) — the Atlassian (Jira Service Management) support-ticket mirroring, which ran from June 2026 to October 2026, is described as ended; processing locations for Anthropic, Telnyx, Microsoft, Google, and Atlassian are stated as determined by the provider; the Amazon Web Services (S3) entry covers encrypted call-recording audio only; the PulseWork connected-tools description was corrected; and retention wording for Pulse Secure Transfer files and agreement records was clarified. October 28, 2026: the update described above. Earlier versions of this page are retained. A revision date is not a statement of when any change took effect.

ProviderPurposeLocation
VercelHosting, serverless functions, media storage.United States
NeonManaged PostgreSQL database.United States
RenderHosting, managed PostgreSQL, and caching for Pulse Email and the shared contact graph, Pulse Voice, PulseConnect (including web-chat transcripts and attachments), PulseMeet, Pulse SMS, PulseBill, Pulse Deals, Pulse RFP, PulseWork, Pulse Secure Transfer, and PulseAdmin.United States
AnthropicAI generation and the PiP assistant — in our apps, in Outlook and Teams, and on our website — including Pulse Voice AI voice agents, meeting recaps and PiP meeting notes, pre-meeting briefs, post-call analysis of recorded calls (on card-masked transcript text, never audio) where a Customer turns it on, PiP in team chat, and email and message drafting. Inputs are not used to train models.Determined by the provider
OpenAI, Google (Gemini), xAI, Deepgram, Cartesia (if enabled)Alternative AI models, speech-to-text, and text-to-speech that a Customer may select for a Pulse Voice AI voice agent (call audio, transcripts, and prompts). OpenAI may also be used for AI image generation and voiceover in Social Command.United States
fal.ai (if enabled)AI image generation.United States
ElevenLabsText-to-speech — spoken PiP replies, Pulse Voice AI voice agents, and voiceover (the text to be spoken).United States
Recall.ai (if enabled)The PulseMeet PiP Notetaker, which receives the meeting link and time of a user’s video meetings when that user turns it on, joins them, and returns the meeting recording, transcript, and participant names used to write the notes.United States
Connected social networksPublishing to the networks you connect — Meta (Facebook, Instagram, Threads), LinkedIn, X, TikTok, YouTube, Pinterest, Google Business Profile, Bluesky, Mastodon, Discord, Telegram, and Tumblr. Each is governed by its own terms and privacy policy.Varies
TwilioPulse SMS — default carrier for number provisioning and SMS/MMS/WhatsApp/RCS delivery; alternative call control for Pulse Voice (if enabled).United States
Meta / WhatsApp (if enabled)WhatsApp Business message delivery (via Twilio) when a Customer enables WhatsApp — recipient numbers and message content, governed by WhatsApp’s terms.United States
TelnyxPulse SMS — alternative carrier for number provisioning and SMS/MMS delivery; the primary telephony carrier for Pulse Voice and PulseConnect — call control, softphone calling, number provisioning and porting, fax, call recordings, video meeting rooms and their recordings, and transcription of voicemail, recorded meetings, and recorded calls.Determined by the provider
NTT (if enabled)Carrier for Pulse Voice numbers provisioned on NTT Cloud Voice — number ordering and porting, emergency (E911) service addresses, and Microsoft Teams tenant routing; call-detail records for those numbers are returned for billing.United States
PulseVoice (if enabled)Outbound AI voice calls, the AI agent, and video meeting rooms used by other Pulse products (for example Pulse Email journeys and PulseMeet).United States
Pulse SSO / PulseAdminUnified sign-in and cross-product access management — authenticates users and manages platform access grants across Pulse products; maintains an audit log of access changes.United States
Amazon Web Services (S3)Encrypted, write-once storage of files sent to Pulse through Pulse Secure Transfer and, where a Customer enables them, the Pulse Voice fax archive and compliance call-recording archive (the encrypted audio; transcripts and analysis are stored encrypted in the Pulse Voice database).United States by default; a Customer may select another region for its recording archive
Apple, Google (Firebase Cloud Messaging), ExpoPush notifications to the Pulse Voice mobile apps, which may include a caller’s name and number or a message preview.United States
Better StackApplication logging, uptime monitoring, and the public status page — application logs from every Pulse product are sent to Better Stack for retention, search, and alerting.United States
OneSignal / Sentry (if enabled)Mobile push / error monitoring.United States
Microsoft (if enabled)Microsoft Teams sign-in, notifications, and Teams calling provisioning; Microsoft 365 calendar free/busy lookups, booking events, and event details for PiP features for PulseMeet; SharePoint and OneDrive knowledge-base connectors; PiP for Outlook and Teams, which reads the mail, chats, files, calendar, and meeting transcripts of the user who connects it; Microsoft Entra ID / Microsoft 365 sign-in for the Pulse login and for an organization’s single sign-on; and, for PulseWork, the Microsoft 365 support mailbox a Customer connects for email-in.Determined by the provider
Google (if enabled)Google Calendar availability, booking events and, for PiP features, event details for PulseMeet; Google Calendar availability and booking events for Pulse Voice agents (see “Google Calendar and Microsoft 365 calendars” in the Privacy Policy); Google Drive knowledge-base connector; RCS Business Messaging delivery (via Twilio) when a Customer enables RCS; Google Workspace sign-in (OpenID Connect) for an organization’s single sign-on; reCAPTCHA spam protection on website forms.Determined by the provider
Zoom (if enabled)Creating Zoom meetings for PulseMeet bookings (meeting topic and time, using the host’s connected Zoom account); the PulseSMS app for Zoom, which uses the signed-in user’s Zoom profile; and Zoom Phone provisioning for Pulse Voice.United States
Connected business apps (if enabled)Data exchanged with the third-party applications a Customer chooses to connect under its own account — for example CRMs (HubSpot, Salesforce, Pipedrive, monday.com, Zoho, Microsoft Dynamics 365, ActiveCampaign) for contact lookup and activity logging, Cisco Webex for message mirroring and calling, other calling and contact-center platforms, QuickBooks and Xero, Shopify, Canva, content management systems (WordPress, Webflow, Ghost, Hygraph, Medium) that receive the blog posts a Customer publishes, and, for PulseWork, Slack and Microsoft Teams channels that receive notifications, and GitHub, which sends events to PulseWork. Microsoft 365 contact sync is not currently available to any customer; if it is made available and a Customer enables it, this will also cover the Customer’s Microsoft 365 environment, from which Pulse Voice and Pulse SMS would read contacts (see the note below this list).Varies
HubSpotPulse’s own CRM — receives website contact and demo requests.United States
Cloudflare (if enabled)DNS and secure proxying for Customer white-label domains, such as a Customer’s hosted SMS opt-in page.United States
Apollo (if enabled)Contact enrichment — appends professional data to a contact when an admin runs enrichment.United States
Atlassian (Jira Service Management)Support-desk ticketing. From June 2026 until October 2026, copies of Pulse’s own support-desk tickets, including tickets raised by customers of Pulse products, were mirrored to Jira Service Management. That mirroring has ended.Determined by the provider
Accept.blueSubscription and merchant payment processing that powers the Pulse gateway; card data is handled by Accept.blue and its underlying processors (Pulse does not store full card numbers).United States
DM Processing (if enabled)Merchant underwriting — PulsePay merchant applications (business and owner identity, tax identifiers, and bank-account details) are sent to the payment processor for review.United States
ResendTransactional and opted-in marketing email delivery, including booking confirmations and reminders, meeting notes and recaps, invoices, and the PulseConnect email channel (inbound and outbound).United States
SignWell (if enabled)E-signature — delivering documents a Customer sends for signature (the document and each signer’s name and email), used by Pulse RFP, PulseBill quotes, and partner onboarding.United States
Voyage AI (if enabled)Text embeddings for knowledge-base search — documents a Customer adds to its knowledge base (Pulse RFP, Pulse SMS knowledge) are embedded for retrieval. Not used to train models.United States
CereTaxTelecom and sales-tax calculation and tax reporting for PulseBill. For each invoice line, PulseBill sends CereTax the service address, amount, quantity, date, product tax code, any customer tax-exemption code, and invoice number. Tax associated with issued invoices is also recorded with CereTax for tax reporting. CereTax is PulseBill’s production tax provider.United States

Some sub-processors are engaged only when a Customer enables the related feature (marked “if enabled”). Where a Customer connects its own third-party provider account with its own credentials (for example its own AI provider or carrier account in Pulse Voice), that provider acts under the Customer’s own agreement and is not a Pulse sub-processor for that data. Where a Customer turns on compliance capture, the archiving, supervision, or eDiscovery system it configures (for example an HTTPS/webhook endpoint, an SMTP journaling address, a Microsoft 365 / Purview mailbox, Proofpoint, or an SFTP feed to Smarsh or Global Relay) is the Customer’s own system or vendor, not a Pulse sub-processor. Microsoft 365 contact sync is not currently available to any customer, and the contact sync text in the Privacy Policy and the Data Processing Addendum is draft text that is not in effect. If it is made available and the Customer enables it, Pulse Voice and Pulse SMS will read contacts from the Customer’s Microsoft 365 environment on the Customer’s instructions. For this connection, Microsoft provides the source system under the Customer’s arrangements with Microsoft. This source-system connection is separate from any services Microsoft provides to Pulse as a sub-processor.

Payment card data is entered only on the payment gateway’s hosted pages or passed once to the gateway for tokenization, and is never stored in full by Pulse. To ask about this list, contact pulselegal@pulsetechnologies.ai.

Pule

Produk

PulsePayPiPPulseVoicePulseBillSocialCommandPulseEngagePulse SMSPulse DealsPulseMeetPulseConnect

Solusi

Unduh aplikasiAplikasi & integrasiPusat bantuanBayar via telepon & text-to-payAgen suara AIContact center sesuai PCIPembayaran white-labelPenagihan berbasis penggunaanAlternatif StripeAlternatif SquareIndustri

Perusahaan

MitraKeamanan & KepatuhanBlogTentang kamiKontak

Akses

Login MitraMinta demoAjukan pemrosesan pembayaranOnboarding gatewayPengungkapan & Kebijakan
© 2026 Pulse Payments LLC dba Pulse TechnologiesSertifikasi validasi PCI DSS SecurityMetrics
(850) 80-PULSE · contact@pulsetechnologies.ai