Privacy Policy for Pulse AI

Stored Data

We store minimal information in our Firestore database:

• Ad Account ID: The Meta advertising account identifier you provide for analysis

Processed But Not Stored Data

When you use Pulse AI, we temporarily process but do not store:

• Meta Access Token: Used only during your session to fetch data from Meta's API
• Campaign Performance Metrics: Spend data, ROAS, CTR, CPM, CPC, reach, impressions, purchase conversions
• Campaign Structure Data: Campaign names, ad set names, ad identifiers, creation dates
• Audience Segmentation Data: Performance breakdown by audience segments and demographics

Usage Data

• Date Range Selections: The time periods you select for analysis (not stored)
• Interface Preferences: One cookie stores your sidebar display preference

Analytics Processing

Your advertising data is temporarily processed to:

• Calculate marketing metrics including ROAS, marginal ROAS, CPC, CPM, and other performance indicators
• Generate AI-powered insights about campaign performance using Google Genkit
• Provide comparative analysis between different time periods
• Create audience segment performance breakdowns

Data Storage Purpose

We store your Ad Account ID solely to enable the analytics service and associate analysis sessions with your account.

Meta Marketing API

• We retrieve your advertising data directly from Meta's Marketing API using your provided access token
• Your relationship with Meta regarding this data is governed by Meta's privacy policy
• We do not store any data retrieved from Meta

Google Genkit AI

• Used for generating insights from your campaign data
• Only processed metrics are sent to AI services, not raw campaign data
• No personal information is processed by AI services

Firebase/Firestore

• Used to store only your Ad Account ID
• Managed by Google with enterprise-grade security
• Governed by Google's privacy and security policies