Data Handling & Security

This page summarizes how ClarityBoard handles advertising data and secures it. It is intended to help platform reviewers, prospective customers, and partners understand our data practices. It supplements our Privacy Policy.

What data we access

With your authorization, ClarityBoard accesses advertising performance data through official platform APIs (LinkedIn Ads, Google Ads, Meta Ads). This includes campaign structure and settings, ad creatives and metadata, and aggregate performance metrics (spend, impressions, clicks, conversions/leads). We request read-only scopes wherever the platform offers them.

Why we access it

Solely to produce reporting, dashboards, and AI-assisted recommendations for the account owner and their designated team. We do not use advertising data for advertising targeting, resale, or to train third-party models.

How data flows

• Retrieval: Scheduled jobs call platform APIs using authorized tokens and pull performance data.
• Storage: Data is normalized and stored in Google BigQuery within our Google Cloud project.
• Processing: Aggregated performance data is analyzed, including via third-party LLM providers, to generate written recommendations.
• Delivery: Reports are shown on the dashboard and delivered to channels you designate (e.g. Slack).

Security measures

• Encryption of data in transit (TLS).
• Data stored within Google Cloud Platform, benefiting from its physical and infrastructure security controls.
• Access tokens stored securely and scoped to the minimum access needed; used only for data retrieval.
• Access to production data restricted to authorized personnel.
• Authentication handled by Clerk; ClarityBoard does not store user passwords.

Token and access controls

Connected-platform access tokens are used only to retrieve the data required to provide the Service. You can disconnect any platform at any time, which stops future retrieval, and you can independently revoke ClarityBoard's access from within the platform's own settings.

Data retention and deletion

We retain data while your account is active. You may request deletion at any time by contacting chandankadannar@gmail.com; upon account closure we delete or de-identify stored data within a reasonable period, except where retention is legally required.

Subprocessors

• Google Cloud Platform — hosting, storage (BigQuery), and compute.
• Clerk — user authentication.
• LLM provider(s) — generation of written analysis from aggregated performance data.
• Vercel — web application hosting.

Compliance with platform policies

Our handling of data received from each platform's API complies with that platform's developer policies. Where a platform imposes stricter handling requirements on its data, those requirements govern.

Contact

Security questions: chandankadannar@gmail.com