Read-only by design.
MagneticML observes your media execution. It never changes it. This page explains what we access, what we never do, who can see what, and what stays in your control.
What MagneticML accesses
Only three things are required, and nothing beyond the scope you set.
Read-only access to the media sources in scope
A read-only connection or an agreed data feed for each media source you enroll, limited to the accounts you choose. From it we read live hierarchy, configuration, delivery, spend, creative and conversion settings, and the change evidence the source makes available.
The plan materials you already have
Decks, sheets, planning-system exports, documents, emails and messages that record what the client approved. We turn them into checks, and your team confirms what we read.
A directory of the people involved
Who owns each account, who can approve plan changes, who receives alerts, and how they prefer to receive them: Slack, Teams, email, or SMS for critical findings.
Build files, tickets and purchase orders are optional plan evidence. They are never a requirement.
What MagneticML never does
- Never changes a campaign. No budget, bid, audience, creative, status or setting is ever touched. Every correction happens in your tools, by your team.
- Never reaches beyond the agreed scope. Access is limited to the accounts you enroll, for the sources you connect.
- Never shares a finding with your client. Sharing is an explicit action by an authorized agency user, scoped to what you choose.
- Never scores individual employees. Person-level attribution is visible only to the agency roles you authorize.
Who can see what
- Findings are agency-private by default.
- Each client workspace is isolated from every other.
- Only authorized agency users can approve checks, grant exceptions or share evidence.
- When you choose to share a client-safe summary, it says which checks it covers, for which dates, how fresh the data is and what we can't check. It's about the check and the confirmed fix, not about people.
What we keep, and why
- Approved plan versions, observations, findings and re-observations are time-specific and append-only. The record of what should have been running, and what happened next, stays intact.
- Verified clear closes a finding. It does not erase spend already observed.
- Coverage records show which checks could run fully, only in part, on stale data or not at all. Missing data is shown as a gap, never as a clean result.
Access is yours to grant and revoke
You grant access, and you can withdraw it. Removing a connection stops observation for that source. The history you already have stays available to you.
Questions for your review
Security and procurement reviews usually ask about scope, access revocation, retention and who else handles the data. Bring them to the assurance review and we will answer them directly for your environment.