Privacy Policy
Last updated: Wed, Oct 28, 2026
This policy explains what personal data AI Meta Ads Operating System ("the service") collects, why, who it is shared with, how long it is kept and how to have it deleted. The service is operated by Haroun Bayoudh, Téboulba, Monastir. For any question about this policy or your data, write to harounsouper@live.fr.
1. What we collect
Your account
- Your name and email address.
- Your password, stored only as a one-way hash that we cannot read.
- If you turn on two-factor authentication: its secret and your recovery codes, stored encrypted.
If you sign in with Google
When you choose "Continue with Google", Google sends us:
- your name;
- your email address, and whether Google has verified it;
- the identifier of your Google account.
We ask Google for nothing else. We do not receive your Google password, and we have no access to your contacts, your emails, your files, your calendar or any other content of your Google account.
If you connect a Meta account
When a member of your organization connects Meta, on Meta's own screen, we receive and store:
- the name and identifier of the Meta account that was connected;
- an access token issued by Meta, stored encrypted, and the list of permissions that were granted or declined;
- the businesses, ad accounts, Pages, Instagram accounts, pixels and catalogs that this account can use: their names, identifiers, and for ad accounts their currency, timezone and status;
- as the features that use them become available, the campaigns, ad sets, ads and performance figures of the ad accounts your organization selected.
We never see, ask for or store your Facebook password.
Your organization and your team
- The name of your organization, its members, their roles and what each may do.
- The email addresses of the people you invite.
Security and technical data
- For each device signed in to your account: its IP address, browser and system, and the time of its last activity.
- An audit log of sensitive actions (signing in, changing a password, inviting or removing a member, connecting Meta, changing a budget), with who did it, when, and from which IP address and browser.
- Technical logs kept to diagnose errors. Passwords, access tokens and API keys are masked before anything is written to them.
- The country of the IP address you sign in from, looked up on our own server in a copy of the DB-IP country database, to show amounts in your currency until you choose one in Settings → Currency. The address is not sent to anyone for this, and only the currency found is kept, for the length of your session.
2. How we use it
- To create your account, sign you in and keep it secure.
- To provide the service: show and manage the advertising of the Meta ad accounts your organization selected, at the request of its members.
- To send you the emails the service needs: verifying your address, resetting a password, an invitation to join an organization.
- To detect and investigate misuse, and to keep a record of sensitive actions for your organization.
We do not sell personal data. We do not use it for advertising of our own, and we do not build profiles of you for other parties.
Legal bases
Under the EU General Data Protection Regulation (GDPR), we process your data:
- to provide the service you or your organization signed up for (Article 6(1)(b));
- to meet our legal obligations, such as keeping records the law requires (Article 6(1)(c));
- for our legitimate interest in keeping the service and your account secure: the audit log of sensitive actions and the technical logs (Article 6(1)(f)).
Your organization's data
The advertising data of an organization (its ad accounts, campaigns, figures, creatives and what its members write in the service) is processed on behalf of that organization, which decides what it is used for. For this data we act as its processor, under a data processing agreement (Article 28 GDPR) that an organization can ask us for.
Data received from Google
What we receive from Google is used only to create your account and to sign you in. It is not used for advertising, not sold, not transferred to others except as needed to provide the sign-in itself, comply with the law or protect the security of the service, and not used to train artificial intelligence models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
AI-assisted features
The service is designed to offer AI-assisted recommendations about your advertising. When your organization uses such a feature, the campaign data needed to answer the request is sent to the AI provider configured for it. Your sign-in data, your password and your Meta access token are never sent to an AI provider.
3. Who we share it with
Only with the providers we need to run the service, and only what each needs:
- Our hosting provider, which stores the database and runs the application.
- Brevo, which delivers the emails of the service. It receives the recipient's email address and the content of the email.
- Stripe, when your organization subscribes: it takes the payment, keeps the card, and issues the invoices. It receives the organization's name, the billing e-mail and the billing details entered on its pages; the service never sees the card.
- Google, when you sign in with Google.
- Meta, when your organization connects a Meta account: the requests made on its ad accounts are sent to Meta's API.
- An AI provider, when your organization uses an AI-assisted feature, as described above.
We may also disclose data when the law requires it. Inside the service, your organization's data is visible only to its members, within what their role allows.
Meta, Google, Stripe and some AI providers are based in the United States or transfer data there. Data sent to them leaves the European Economic Area under the safeguards the GDPR provides for: the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise the European Commission's Standard Contractual Clauses.
4. Cookies
The service uses only the cookies it needs to work:
- a session cookie, which keeps you signed in, and a token that protects forms against forgery;
- a "remember me" cookie, if you tick that box when signing in;
- two preference cookies, for the light or dark appearance and for the state of the sidebar.
There are no advertising cookies and no third-party analytics cookies.
5. How long we keep it
- Your account data: until you delete your account.
- The data of an organization: until the organization is deleted, with these limits:
- the daily figures copied from Meta: 1125 days, as long as Meta keeps them itself;
- what was sent to an AI provider and what it answered, and the conversations of Ask AI: 365 days;
- notifications: 180 days.
- The Meta access token and connection: until someone in your organization disconnects Meta, the person who connected it removes the app from their Facebook settings, or the organization is deleted.
- Sessions: until you sign out or they expire.
- Audit log entries: 730 days. The IP address and browser they record are removed after 90 days. They are kept after an account is deleted, for the security of the organization they concern, but no longer point to the deleted account.
- Invitations and shared reports: deleted 30 days after they expire, are accepted or are revoked.
- Invoices: kept by Stripe for as long as the law requires (in Germany, up to ten years under § 147 AO and § 257 HGB).
6. How we protect it
- All traffic is encrypted in transit (HTTPS).
- Passwords are hashed. Access tokens and other secrets are encrypted at rest, with a key kept apart from the database.
- Secrets are never sent to your browser and are masked in logs.
- The data of an organization is isolated from the others, and what a member can see depends on their role.
- Two-factor authentication is available to every user.
No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.
7. Your rights
You can ask to see the personal data we hold about you, to have it corrected, to receive a copy, to restrict or object to its use, and to have it deleted (Articles 15 to 21 GDPR). You can download a copy yourself at any time: sign in and open Settings → Profile → Download my data. You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live or work (Article 77 GDPR). To use any of these rights, write to harounsouper@live.fr.
8. How to delete your data
- Your account: sign in and open Settings → Profile → Delete account. Your account, your sessions and your sign-in data are deleted at once.
- The data of an organization: what belongs to an organization (its Meta connection and the data copied from Meta, its secrets, campaigns, creatives and audit log) stays with the organization when one of its members leaves. Its owner deletes it all at once in Settings → Organization → Delete the organization; Meta is then asked to take back the permissions it granted.
- The Meta connection: a member who manages integrations opens Settings → Meta connection → Disconnect. The access token is deleted at once. You can also remove the app from your Facebook settings, under Business integrations, or ask Facebook to have your data deleted: Meta tells us, the connections you made and their tokens are deleted in every organization, and Facebook shows you a confirmation code and the status of the deletion.
- The link with Google: remove the app from the third-party access page of your Google account. Deleting your account here also deletes the Google identifier we stored.
- By email: write to harounsouper@live.fr from the address of your account, and we will delete your data within 30 days.
9. Children
The service is meant for businesses and is not directed to anyone under 18. We do not knowingly collect data from children.
10. Changes to this policy
When this policy changes, the new version is published on this page with its date. If a change matters for how your data is used, we will tell you by email or in the service before it applies.
See also our Terms of Service.