← Back to Home

Privacy Policy

Effective Date: May 22, 2026 • Last Updated: May 22, 2026

Pulse Messages ("Pulse," "we," "us," or "our") provides an AI-assisted communication widget and operator dashboard. This policy explains how we collect, process, secure, and share personal data when you interact with our platform.

Pulse Messages is operated by Zen Banez, based in Tacloban City, Leyte, Philippines.

Note to Visitors: Pulse processes messages on behalf of the businesses you chat with. If you interact with a chat widget, the respective business is the Data Controller, and Pulse acts as the Data Processor.

1. Information We Collect

1.1 From Chat Widget Visitors

• Conversational Content: Message text containing details you choose to share.
• Session Identifiers: A temporary session token held in browser sessionStorage. It is completely deleted when you close the tab. We utilize no persistent tracking cookies.
• Linked Identity: Email and display name if you choose to sign in via Google SSO.
• Connected Meta Channels: Social messaging text, page scopes (PSIDs), and profile names received via Graph APIs when you message connected Facebook and Instagram channels.

What we DO NOT collect: IP logs, precise geo-location coordinates, device fingerprints, or cross-site tracking markers.

1.2 From Workspace Operators

• Account Profiles: Hashed passwords, email addresses, and SSO tokens.
• Business Profiles: Services directories, FAQ banks, facts bases, and instruction datasets utilized to configure your AI.
• Integrations Tokens: Encrypted BYOA keys, Slack/HubSpot endpoints, and Stripe billing tokens.

2. Data Usage & AI Training Commitments

We process data to deliver secure messages, trigger Murmurs, and execute scheduled AI heartbeats. We maintain strict privacy covenants:

• No Data Monetization: We never sell, lease, or lease message records to third-party providers.
• No Model Training: Conversations processed via API wrappers (Gemini/Claude) are sandboxed and are never utilized to train underlying model weights.
• Tenant Isolation: Firestore rules rigorously isolate all read/write calls by tenant ID.

3. Message Processing Flow

1. Sanitization Moat: Inbound text is immediately stripped of scripts, HTML tags, and injection payloads.
2. Pattern Check: Murmur keywords are scanned for instant pattern-matched reply templates (free & zero-latency).
3. Urgency Classification: Unmatched logs undergo pre-label tasks to sort them by priority (Rank 1-5).
4. Heartbeat Processing: High priority (Rank 1-2) flags immediate Operator queues, while regular items wait for batch heartbeats.

4. Third-Party Subprocessors

Subprocessor	Purpose	Data Transmitted	Terms Link
Google Firebase	Edge hosting, Firestore, Functions & Tasks	All database entries and raw texts	Google Cloud
Google Gemini API	Language inference for AI Heartbeats	Sanitized message payloads	Gemini Terms
Anthropic Claude API	Language inference for Elite AI layers	Sanitized message payloads	Anthropic Privacy
Stripe, Inc.	Merchant billing and credit card handling	Secure card details (handled via Stripe SDK)	Stripe Policy
Meta Platforms	Facebook Page & Instagram Business routing	Inbound DMs, profile names, and channels tags	Meta Policy

5. Your Rights & Regulatory Compliance

5.1 Philippine Data Privacy Act (DPA of 2012)

We are fully compliant with Republic Act No. 10173 (DPA). Filipino citizens retain absolute rights to be informed, object to processing, access histories, correct records, and seek blocking or erasure of records. Direct DPA inquiries can be addressed to our privacy email below, or to the National Privacy Commission (privacy.gov.ph).

5.2 European GDPR Compliance

Pulse facilitates data portability, processing restrictions, and immediate erasure command actions.

5.3 Guest Session Ephemerality

Guest chats leverage zero permanent cookies. Active IDs exist solely inside standard browser sessionStorage and are purged automatically when the window is closed.