SynPulse runs outbound sales for its clients: our team finds and researches companies, writes and sends messages in the client's name, answers replies and holds first meetings. Some invited customers also use the SynPulse platform themselves. To do this we use the information needed to run and protect each engagement and workspace: account details and settings, connected accounts, companies and contacts, account research, messages and replies, meeting notes, unsubscribe records, billing details, security events, and basic diagnostic information.
How we research and write
Our team researches companies with SynPulse's own software, working from business information such as company websites and job postings, and uses AI models provided by service partners to help research accounts and draft messages. A person on our team approves every message before it is sent. Research and messages made for a client are used only for that client's engagement and are never shared with another client.
If a client uses our live meeting coach, the call's audio is transcribed by a service partner and is not stored; only the text transcript is kept with that client's records.
If we contacted you
We write to people on behalf of a named client, who is the controller of that outreach; SynPulse acts as its processor. You can unsubscribe from any email we send, or reply to any message asking us to stop. We then stop and keep a suppression record so you are not contacted again for that client. You can send any request about your data to the address above, and we will act on it or pass it to the client concerned.
Support chat
SynPulse provides its own support chat on public pages and inside the application. Chat messages are stored in SynPulse so the conversation can be shown back to the same visitor or signed-in client. Before sign-in, SynPulse sets a strictly necessary support-session cookie containing a random identifier. The server stores only a SHA-256 hash of that identifier. The cookie is used to keep one browser's conversation separate from other visitors and may remain for up to 180 days.
Support messages are also sent to a dedicated SynPulse support bot on Telegram so our support administrator can respond. For visitors who are not signed in, Telegram receives the message, current SynPulse page, and an anonymous visitor reference. For signed-in clients, it can also receive the customer name, email, workspace, and current SynPulse page. Telegram replies are returned to SynPulse only when our configured administrator replies to the specific support notification. You can use support email instead if you do not want to use chat.
Identity and billing
Trusted sign-in and payment providers handle passwords, payment cards, and tax details. SynPulse keeps your account ID, plan and access status, invoice summaries, security history and, for platform customers, the usage-credit balance. We do not store full card numbers.
Connected accounts
To send in a client's name, SynPulse connects to the mailboxes and LinkedIn accounts the client's order describes. For an IMAP/SMTP mailbox, SynPulse stores its server settings and encrypted passwords and connects directly to the email provider. Google Workspace and Microsoft 365 connections use provider-specific authorization flows. These connections are used only to send, receive and manage that client's outreach.
Clients and their team members connect a LinkedIn account with the SynPulse Chrome extension. It uses the LinkedIn account you are signed in to in Chrome and sends that account's LinkedIn sign-in session and browser information directly to SynPulse over HTTPS, and again when LinkedIn refreshes the session. SynPulse encrypts the LinkedIn session and uses a revocable device token to keep the connection secure. The extension works only with LinkedIn and SynPulse, never asks for your LinkedIn password, adds nothing to the pages you visit and does not read your browsing history.
Sales data and suppression
The companies, contacts, messages, replies and suppression records of an engagement belong to the client, who can see them in their workspace. Suppression is preserved across sequences so an unsubscribe is not silently undone.
Retention and deletion
We keep account and workspace data while your engagement or subscription is active and for as long as needed for security, billing, unsubscribe protection, disputes, and legal requirements. When an engagement or subscription ends, SynPulse stops scheduled work and revokes connection tokens. A workspace owner can export data or ask us to delete it. Protected backups expire on their normal schedule.
Security and service partners
SynPulse uses trusted providers for hosting, sign-in, payments, email delivery, account connections, AI models, contact data, support communications, and monitoring. Production logs exclude message bodies, prompts, passwords, and connection secrets. Our current service provider list and data-processing addendum are published on this site.
Your controls
Authenticated workspace owners can export workspace data, export or import suppression lists, revoke account access, revoke sessions, and request account deletion. Contact privacy@synpulse.app for access or correction, deletion, restriction, portability, or objection requests. We may verify the request before acting on it.
Chrome Web Store Limited Use
Data received through the Chrome extension is used only to provide and improve the LinkedIn connection described above. We do not sell it, use it for advertising, use it for credit or lending decisions, or share it for an unrelated purpose. This use follows the Chrome Web Store User Data Policy and its Limited Use requirements.