Account, team, and subscription
Data privacy and account security
What Ads Editor stores, how the Meta and Google connection works, and what protects each client account.
Quick answer
Your Ads Editor account (email and password, or Google, Facebook or Apple login) is separate from the ads permission. That permission opens on Meta’s or Google’s screen, the token stays encrypted on the server and is not sent to the browser. The client’s Facebook password is not requested.
What is stored
- Name, email and the id of the login you chose. Without an email the provider has confirmed, social login does not sign you in.
- The permission to call Meta and Google, encrypted with AES-256 on the server. The page only shows whether the account is connected.
- The accounts you turned on, your preferences and the actions taken in the product.
- Metrics read through the official APIs, for the screens and reports you open.
- Access logs (IP and browser). The privacy policy states a 90-day period.
What we do not ask for, and do not have access to
- The password of Facebook, Google or the client ad account. It is typed on their window. We do not have access to that password.
- The card number. Billing goes through Stripe or Asaas. We do not have access to that number.
- Data from one account does not show up inside another client account.
How the connection works
Connecting ads is not the same as signing in to Ads Editor. The login identifies you. The connection authorizes management, on Meta’s or Google’s screen.
- 1
Sign in to your account
Use your email and password, or the Google, Facebook or Apple button on the login screen. This step only proves who you are. It does not unlock any campaign.
- 2
Connect Meta
In the menu, open Connect Meta and click Connect Meta Ads. The window is Facebook’s. Log in there, choose All Pages and authorize. Back in Ads Editor, turn the accounts on under Ad Accounts (Meta). The full path is in Connect your Meta account.
- 3
Connect Google Ads
Open Connect Google and click Connect Google Ads. The window is Google’s: sign in with the email that accesses the MCC or the accounts and authorize. Then turn the accounts on under Ad Accounts (Google). Details in Connect Google Ads.
- 4
Revoke it when you want
On the connected profile, use Remove profile. Ads Editor stops using that authorization. On Facebook, the path is Settings, Apps and websites. On Google, it is the Google Account, under Third-party app access. If the Facebook password changes, the connection drops: connect again.
The client’s password stays out
Ask the client to give your profile access in their business, or to accept the MCC invitation. You do not need, and Ads Editor does not ask for, that client’s Facebook or Google Ads password.
Security of your account
- The Ads Editor password is yours, separate from the Facebook password. It is stored only as a hash, outside the profile data the screen receives.
- To raise security for the client, turn on two-factor authentication on the Meta account that manages the ads, in Accounts Center, under Password and security. In Ads Editor, each person turns on their own under My Account, with an authenticator app or an email code, and keeps the recovery codes. See Turn on two-step verification.
- The session sits in a cookie that page JavaScript cannot read. Changing the password ends the other open sessions and the remembered login in the browser. The remembered login lasts up to 60 days.
- Each team member signs in with their own email and password. Actions use the owner’s connection, which stays on the server.
Who can see what
| Who | What they can open | Limit |
|---|---|---|
| You | The accounts you connected and turned on, the reports and the automations you enabled | Another Ads Editor customer’s account does not appear for you |
| A team member | The screens and accounts you checked under Team | With no account checked, the person can use every account you turned on. The token is not sent to their browser. See Add people to your team |
| Another customer | Nothing in your account | Campaigns, lists and conversations stay in your account |
What we do on our side
- The server uses the token only for the action you take and for the rules and scaling you configured. Turn the rule off to stop the automation.
- In Copilot, the question and the context of the open account go to the model that answers that message. Another client’s account is not part of that answer, and notes stay on the account where you saved them.
- On a customer list, email, phone and name are turned into a SHA-256 hash before they go to Meta, in the format Meta requires. Fields Meta asks for without a hash follow Meta’s own rule. The list is used to create the audience you asked for.
- A request that tries to read a secret file on the server is blocked immediately and stays blocked until the team removes the block.
- The site uses TLS 1.2 or newer.
- After the account is deleted, the data is removed within 30 days, except where the law requires us to keep it. Contact [email protected]. We reply within 72 hours.
A report with a public link
If you publish a report with an open link, anyone with the link can see that report. You can put a password on the link. If you do not publish it, the report stays in your account.
How to tell you are protected
- Two-factor authentication is on for the Meta account that manages the ads and under My Account in Ads Editor.
- The Connected label is at the top of Connect Meta or Connect Google, and only the accounts you turned on appear in the picker.
- Under Team, each person has the screens and accounts you checked. With no account checked, they reach every account you turned on.
- The connection window is the Facebook window or the Google window, and the password is typed on that screen.
Frequently asked questions
Do I need my client's Facebook password to create an ad account and run campaigns?
No. You never need your client's Facebook password, and they don't need to create anything from their own profile.
Here is how it works:
- Ad account: you create it yourself, inside one of your BMs that still has a free slot (a BM has an ad account limit), or by opening a new BM for this client.
- Facebook Page: you create the company's Page, or connect one that already exists.
- Instagram: this is the only step where the client comes in: they sign in to their own Instagram account to authorize linking it to the Facebook Page (you don't need their password). It's the only step that depends on them.
- Payment: add a card, or generate a Pix payment (Brazil's instant payment method) in the ad account to add funds, and your campaigns can run.
In other words, a client without a Facebook password doesn't block anything. You set everything up and leave only the Instagram link for when the client can authorize it.
How do I connect my Meta account in Ads Editor?
To connect your Meta account (Facebook/Instagram):
- In the side menu, click Connect Meta (on mobile: More → Connect Meta).
- Click Connect Meta Ads.
- Log in to Facebook and approve access to ads and Pages.
- When you come back, turn on the ad accounts you want in the Ad Accounts panel.
Ad accounts from the Business Managers on your profile appear in that list. To use another Facebook profile, click Connect another profile.
Connect Meta is visible to the account owner. A team member sees it only when the owner grants the Connect Meta permission under Team. The member can then open the page, click Connect profile, and add the profile to the owner's Ads Editor account. The owner chooses which ad accounts that member can access.
How do I limit which Meta and Google accounts a member can see?
When adding or editing a member, use the Allowed Meta ad accounts and Allowed Google Ads accounts fields to select only the accounts that person should access. From then on, they see only those accounts across the entire system (manager, Account Center, reports and balance). If you leave the list empty, the member has access to all your accounts, with no restriction. This is how you give each team member only the clients they are responsible for and keep the other accounts out of reach.