Analytics dashboard
Meta Assets Insights Viewer
Connect your Meta account to view Pages, ad accounts, engagement, and campaign insights in one place.
Privacy Policy
AnalyticsPH Privacy Policy
This Privacy Policy explains how AnalyticsPH, available at analyticsph.com, collects, uses, stores, and deletes data when advertisers connect their Meta account to analyze advertising performance.
Last updated: April 29, 2026
Who We Are
AnalyticsPH is operated by the AnalyticsPH team, which is responsible for the Meta Assets Insights Viewer application on analyticsph.com. The application helps authorized advertisers and business users analyze reporting data for Meta assets they already manage. The Meta App ID for this application is 1304907574836461.
Privacy contact: [email protected].
Data We Receive From Meta
When a user signs in with Meta Login and grants the requested permissions, AnalyticsPH may receive and process only the Meta data needed to provide the reporting dashboard. This may include:
- Basic Meta profile information returned by Meta Login, such as user ID and display name.
- Facebook Pages the user manages, including page ID, page name, category, fan count, follower count, and engagement fields returned by the Graph API.
- Ad accounts available to the user, including ad account ID, account name, currency, and account status.
- Campaign-level ad insights for selected ad accounts, including campaign name, impressions, clicks, spend, CTR, CPC, date preset, and related reporting metadata.
- Operational sync records, such as the type of sync action, completion status, timestamp, selected asset, and number of records fetched.
AnalyticsPH does not ask for permission to create ads, modify campaigns, or publish content. The application uses Meta data for reporting and analytics display only.
How We Use Data
We use the data described above to:
- authenticate the user and keep their session active;
- list Pages and ad accounts the authenticated user is allowed to access;
- let the user explicitly select a Page or ad account for analysis;
- fetch live or recently synced reporting data from the Meta Marketing API and Graph API;
- display advertising performance metrics in the user dashboard;
- store sync history so the user can verify when data was last loaded.
We do not sell Meta data, use it for third-party advertising, or share it with data brokers.
Storage And Security
Access tokens and reporting data are stored server-side and are not stored in browser cookies. Session cookies contain only the information needed to connect the browser session to the server-side authentication record.
We use reasonable technical and organizational safeguards to limit access to Meta data to authorized application operators and to protect it from unauthorized access, alteration, or disclosure.
Retention
AnalyticsPH keeps Meta access tokens while the user account remains connected or until the token expires, is revoked, or is deleted upon request. Reporting snapshots and sync history are retained only as long as needed to provide the dashboard, support the user, debug sync activity, or meet legitimate operational requirements.
Users may request deletion of their Meta data at any time by following the instructions on our Data Deletion page.
User Choices And Deletion
Users can revoke AnalyticsPH access from their Meta account settings. After access is revoked, AnalyticsPH cannot fetch new Meta data for that user.
To request deletion of stored Meta data, email [email protected] from an address that can be used to verify your request. Please include your name, the Meta user or business context connected to AnalyticsPH, and the data you want deleted.
Third-Party Services
AnalyticsPH connects to Meta APIs only after the user authorizes access through Meta Login. Meta's own processing of user information is governed by Meta's terms and privacy policies. AnalyticsPH does not transfer Meta data to unrelated third-party services for resale or independent marketing use.
Changes To This Policy
We may update this Privacy Policy when the application, legal requirements, or Meta platform requirements change. The updated version will be published at this URL with a new "Last updated" date.