Access to an ad account is access to a budget. We treat it that way.
This page describes, in plain terms, the security measures Plireo applies today and the direction it is taking.
How Plireo accesses your accounts.
You authorise, on the platform's screen
The connection goes through Google's or Meta's own consent screen. You never give Plireo a password, and you can withdraw the access from your Google or Meta account at any time.
Credentials are stored encrypted
The access obtained is kept in an encrypted secret store, one entry per connection. The application's tables hold a reference only, and the value is never displayed again.
Nothing is read until an account is assigned
Signing in may reveal several accounts. Plireo reads none of them until an approver has assigned one to an advertiser; the others stay unused.
What Plireo is able to do on each platform.
| Platform | Permission requested | What limits Plireo |
|---|---|---|
| Google Ads | The single permission Google offers for an ad account; it has no read-only variant | Plireo's own design: reading is separate from writing, a change must be prepared, checked and approved, and nothing is applied without an approval |
| Meta Ads | Read-only | The permission itself: it cannot change a campaign |
| Google Analytics 4 | Read-only | The permission itself; an access that came back with editing rights would be refused |
| Google Tag Manager | Read-only | The permission itself: nothing can be edited or published |
Separation, roles and a record.
Organisations are kept apart
Which data a person may see is decided by rules enforced in the database, not only by what the screen shows. A request made outside the interface is refused the same way.
Roles decide who may approve
Reader, operator and approver. Only an approver can approve a change or assign an account to an advertiser.
A record that cannot be edited
What was prepared, checked and approved in Plireo is recorded, with its author and its reason, and cannot be rewritten afterwards.
Security questionnaires, and what comes next.
Detailed answers to security questionnaires are provided on request, from verified elements.
A separate administrator role, access limited to certain advertisers and enterprise identity management are part of the product direction; their status is shown below. By default, an approver may approve a change they prepared themselves.
The capabilities concerned.
- RolesReader, operator and approver, enforced by the serverIn progress
- Administrator roleA separate administration rolePlanned
- Access by advertiserAccess limited to selected advertisers of an organisationPlanned
- ApprovalsApproval bound to the exact change, with a written reason when a warning is openIn progress
- Audit recordAppend-only record of what was prepared, checked and approved in PlireoIn progress
- Execution by PlireoApplying approved changes, with safety controlsIn progress
- Multi-organisationSeveral organisations with strict separationPlanned
Related pages
Be among the first to use Plireo.
Plireo is in pre-launch. Request early access to be told when it opens, or apply to take part in private testing. Access opens gradually, so a request does not mean immediate access.
Paid plans open once the Google Ads, Meta, GA4 and GTM integrations are operationally validated.
Request early access