Privacy Policy

Meridian is a private advertising management tool operated by AgentEmp for its own team and invited clients. It is not a consumer product and has no public sign-up.

When an authorised administrator connects a Meta account, we ask only for the permissions needed to read and manage that business's own advertising:

• ads_read — campaigns, ad sets, ads, creatives, targeting, budgets, and performance metrics for the connected ad accounts.
• ads_management — creating and pausing campaigns, ad sets, and ads in those accounts, only after a person approves the action in Meridian.
• business_management — the list of Business Portfolios, ad accounts, and Pages the connecting administrator already manages.
• public_profile — the connecting administrator's Meta name and user ID, used to label the connection.

We do not request, receive, or store the personal data of people who see or click the ads. We do not access private messages, friend lists, or consumer profiles.

Advertising data is used to display performance inside Meridian, to compute metrics such as cost per lead, to generate recommendations, and to carry out changes that a user has explicitly approved. Imported acquisition leads are used for internal attribution. A separately reviewed non-sensitive contact segment may be used for the explicit audience sync described below, never an insurance lead book by default.

We do not sell data or use it to train public models. The optional controlled operator test described below shares only the operator-authorized test signals with Meta.

In Tracking & Conversions, an authorized owner/admin can voluntarily submit a controlled test Lead using their own email. Only after the separate explicit choice, we normalize and hash that email and send its hash, the actual browser user agent, the Settings page URL without query data, and a test event identity/time to Meta through its Conversions API with that pixel’s Test Events code. Hashing is not anonymization. These signals are for test receipt and matching checks, not customer uploads or production optimization.

We do not sample CRM customers or send insurance, health, plan or eligibility details for this test. Raw operator email and browser signals are not stored in the test receipt. The receipt retains the operator identity, authorization time and notice version, event identity, and sanitized provider result. Uncheck the authorization choice to withdraw before sending; a completed send cannot be recalled. For later data-deletion or withdrawal requests, use the contact or data-deletion route below. Review the dataset’s restrictions in Meta Events Manager and Meta’s Business Tools Terms before testing.

An authorized administrator may explicitly sync a reviewed non-sensitive HighLevel contact segment to an exact-account Meta Customer List audience. Only normalized SHA256 email and international phone hashes are shared for audience matching and retargeting, not conversion reporting. Membership must itself be permitted; insurance survey, health, financial, eligibility and enrollment information are not eligible just because fields are removed or hashed.

Each submitted contact requires a recorded affirmative advertising choice, its time and notice version covering Meta sharing. We retain the scoped membership reference, hashes, choice evidence and sanitized batch receipts for reconciliation and explicit withdrawal removals. Hashing is not anonymization. Withdraw through the business’s original consent/contact route or the data-deletion route below; future additions are blocked, and an administrator must explicitly sync removals. There is no automatic recurring upload. Administrators must verify dataset restrictions and accept Meta’s Custom Audience and Business Tools Terms before sending.

Data is held in an access-controlled managed database. Meta access tokens are encrypted at rest and are never displayed in the interface, logs, or exports. Access is limited to the workspace that connected the account, enforced by row-level security and role-based permissions. Every change made through Meridian is recorded in an immutable audit trail.

Advertising and performance records are retained while the account remains connected and for up to 24 months afterwards for reporting continuity. Access tokens are deleted immediately when a connection is removed. Audit records are retained for accountability and may be kept longer where required.

Disconnecting Meta inside Meridian (Settings → Connections) removes the stored token at once. To have stored advertising data erased as well, follow the instructions on the data deletion page.

Meridian relies on Meta's Marketing API, a managed cloud database and hosting provider, and AI model providers used to generate written analysis. Prompts sent to model providers contain aggregated campaign metrics, not personal data. These providers act as processors and may not use the data for their own purposes.

Questions or requests about this policy, including data access and deletion, can be sent to privacy@agentemp.com.