Legal · العربية
Connected Ad Accounts & Platform Data
Version: 1.2
Addendum to the Aylah Privacy Policy and the Aylah Terms of Use
Effective date: 26 October 2026 (effective from publication)
Last updated: 26 October 2026
This page is published in English and Arabic. If there is any conflict between the two versions, the English version prevails. Where this page is more specific or more protective than the Privacy Policy, this page applies to Platform Data.
This page explains how EUPPORIA IT SOLUTIONS L.L.C ("Aylah", "we", "us") accesses, uses, protects, shares and deletes data from advertising accounts that you connect to the Aylah Service, and what you authorise when you connect an account. Words defined in our Terms of Use and Privacy Policy have the same meaning here.
1. Who we are and how this page relates to our other terms
1.1 Aylah is operated by EUPPORIA IT SOLUTIONS L.L.C, a limited liability company established in Dubai, United Arab Emirates (trade licence No. 1325954), with its registered address at Office No. 13, Riggat Al Buteen, Dubai, United Arab Emirates.
1.2 This page supplements the Aylah Privacy Policy (in particular its sections 5.5 and 6.6) and section 13A of the Aylah Terms of Use. It covers only data from connected advertising accounts ("Platform Data"). In all other respects, the Privacy Policy and the Terms of Use govern. If this page and the Privacy Policy conflict on Platform Data, this page applies.
1.2.1 Aylah reads your past ad performance to tailor its recommendations to your account. We never use imported ad history to train any AI model.
1.3 Platform Data means any data we receive from an advertising platform through an account you connect. This includes account identifiers, campaign and ad identifiers and settings, performance results, the access tokens or keys that keep the connection working, and any data that is aggregated, anonymised or derived from that data.
1.4 Our role. For Platform Data, we act on your instructions to provide the features you choose. Where data protection law uses these terms, we act as your processor (or "service provider") for personal data contained in Platform Data, and you remain responsible for that data as the advertiser. We are the controller of your Aylah Account data, of the records of the consents you give us, and of our security logs, as described in the Privacy Policy.
2. Which platforms, and what is available
2.1 Connection is optional. You can use the Service without connecting any advertising account.
2.2 Availability depends on each platform. Each integration depends on that platform's own review, approval and permissions, which the platform may grant, limit or withdraw. Connecting is offered only for platforms shown as available in the app. The table in section 2.3 is the only place on this page that states which platform and which feature is available. Nothing on this page, in our other terms or in the app means that any platform has approved, certified, endorsed or partnered with Aylah.
2.3 Availability table. "Available" means the feature is switched on for customers in the app. "Pending platform approval" means we have not received, or have not yet switched on, the access needed, and the feature cannot be used. "Not offered" means we do not offer it.
| Key | Platform (connectable service) | Read: reporting in Aylah | Managing campaigns (publishing and budget changes, section 3.3) | Learn from my results (section 6.2) | Platform Data sent to AI providers (section 6.3) |
|---|---|---|---|---|---|
| meta | Meta (Facebook and Instagram) | Pending platform approval | Pending platform approval | Not offered | Not offered |
| google-ads | Google Ads | Pending platform approval | Pending platform approval | Not offered | Only with your separate consent (section 7) |
| microsoft-ads | Microsoft Advertising | Pending platform approval | Pending platform approval | Not offered | Not offered |
| snapchat | Snapchat | Pending platform approval | Pending platform approval | Not offered | Not offered |
| Pending platform approval | Pending platform approval | Not offered | Not offered | ||
| tiktok | TikTok | Pending platform approval | Pending platform approval | Not offered | Not offered |
| Pending platform approval | Pending platform approval | Not offered | Not offered | ||
| x | X | Pending platform approval | Pending platform approval | Not offered | Not offered |
| openai-ads | ChatGPT ads (OpenAI) | Pending platform approval | Pending platform approval | Not offered | Not offered |
Each cell shows one of: Available, Pending platform approval, Not offered. If the app and this table ever differ, the more limited of the two applies.
2.4 You always connect your own advertising account, or one you are authorised to connect. You remain the advertiser of record and you pay the platform directly. Aylah never holds your advertising funds, and Aylah credits are never used for ad spend. We never place ads for more than one customer in the same advertising account.
2.5 We add a platform to the table in section 2.3 before you can connect it.
3. What we access and what you authorise
3.1 How you connect. You connect an account through the platform's own authorisation screen (OAuth). Where a platform does not offer OAuth, you connect using an access key that you create in that platform's settings for your own account. Before the platform's screen, Aylah shows you a separate connect screen for that platform, which says what we will read and what we will not do. We request only the permissions needed for the features shown as available for that platform.
3.2 Read access. With your authorisation, we read:
(a) ad account information, such as account name, identifier, currency, time zone and status;
(b) campaign structure, meaning your campaigns, ad sets or ad groups, ads, creatives, budgets and settings; and
(c) performance results, such as impressions, clicks, spend, conversions and other results the platform makes available for your account.
3.3 Managing campaigns (only where shown as Available in section 2.3). Aylah Autopilot, our AI ad agent, is being built to read your results, suggest changes and, if you allow it, make them within the cap you set. It is coming as each ad platform approves our access. Where managing campaigns is shown as Available for a platform, and only after you have given the separate write consent for that specific ad account (section 3.5), you may authorise Aylah to create, edit, pause and resume campaigns, ad sets or ad groups, ads and creatives in that ad account, upload creatives you made in Aylah, and change budgets and schedules, subject to all of the following:
(a) Approve-first by default. Every change is shown to you first, with its budget or spend impact, and is made only after you approve that change. An approval applies only to the change shown and does not carry over; if a change fails or its details change, we ask again.
(b) Autopilot is a separate choice. Only if you separately switch on Autopilot for a campaign, and accept the Autopilot consent shown at that time, may Aylah make the kinds of changes you chose for that campaign without asking each time, always within your spending cap. Autopilot never deletes campaigns. You can switch Autopilot off at any time; this stops future Autopilot actions and does not undo actions already made.
(c) Spending cap. Before any change that can affect spend, you set a daily spending cap for that ad account. The default is USD 20 per day (or the equivalent shown in the app in your ad account's currency). There is no "unlimited" option. To set a cap above USD 20 per day you must type the amount in yourself. We enforce the cap on our servers for each connected ad account, and, where the platform allows it, also set a matching limit at the platform. Any increase of the cap needs your new approval.
(d) No rounding up. If a platform's minimum budget is higher than your cap, we refuse the change and tell you. We never round a budget up above your cap.
(e) New campaigns start paused. Every campaign and ad we create starts in paused status, and goes live only when you approve its activation (or, where Autopilot is on for that campaign, within the limits you set for it).
(f) Stop at any time. A Pause or Stop control is always available in one click for each campaign and for Autopilot. Stopping takes effect for all future actions straight away.
(g) Failures. If an action that affects spend fails, we tell you and do not retry it silently.
(h) Ad spend. All ad spend is billed to you by the platform under your agreement with it.
(i) Your responsibility. You remain responsible for your advertising accounts, budgets, targeting, ad content, landing pages and compliance with each platform's terms and policies and with the law, as set out in section 13A of the Terms of Use.
3.3A Approved changes for Meta. Where you switch on approved changes for a Meta ad account, Aylah prepares proposed changes and shows each one with the values before and after and the effect on daily spend. Nothing is sent to Meta until you approve that exact change. Aylah can only create campaigns and ad sets in paused status, edit paused items it created, and pause items it created. Aylah never turns delivery on, never deletes anything, and never changes payment methods, account users, billing or the Meta account spend cap. Budgets stay within the daily limit shown in Aylah (by default the equivalent of USD 20 per day) and Aylah never raises a budget. You can withdraw this permission or disconnect at any time.
3.4 Permissions that include write access. Some platforms grant read and write permissions together. Where this is the case, our systems block every write action until managing campaigns is shown as Available for that platform and you have given the write consent for that ad account and approved the action (or switched on Autopilot under section 3.3(b)).
3.5 Your consents, one by one. Each of the following is a separate choice, shown on its own screen or checkbox, unticked or off by default, and never bundled with sign-up or with each other:
(a) the connect screen for each platform (section 3.1);
(b) for Google Ads, the consent to send Google Ads data to AI providers (section 7.4);
(c) where offered, "Learn from my results" for each platform (section 6.2);
(d) where managing campaigns is Available, the write consent for each ad account (section 3.3); and
(e) where offered, the Autopilot consent for each campaign (section 3.3(b)).
For each consent we record the exact text you were shown, its version, a fingerprint (hash) of that text in the language you saw, your Account, the platform and ad account concerned, and the date and time. You can withdraw any of them at any time in Settings › Connected ad accounts (section 9). If we change the text of a consent in a material way, we ask you again before relying on it.
3.6 We do not access your advertising accounts for any purpose other than those described on this page.
3.7 Activity log. Every change you approve for a connected ad account is recorded in your workspace's activity log: who approved it, when, the action, the values before and after, the platform's reference number, and the proposal and approval references. You can view and export it in Settings › Activity log. We keep activity-log entries for 24 months, then delete them, unless the law requires us to keep them longer. Withdrawing a permission or disconnecting does not delete earlier entries; deleting your account does, except where we must keep a record by law.
4. Purpose limitation
4.1 We use Platform Data only to provide the features you ask for in your own Aylah Account, which are visible in the app, including:
(a) reporting on your campaigns and ads;
(b) suggestions for your account;
(c) drafting ads for your account; and
(d) where shown as Available, managing campaigns as described in section 3.3.
4.2 We do not:
(a) build advertising, marketing or user profiles of individual people from Platform Data;
(b) sell, rent, license or resell Platform Data;
(c) use Platform Data to serve, target or personalise advertising, including our own advertising;
(d) use Platform Data to benefit any other customer;
(e) use Platform Data to make eligibility decisions about people (such as for credit, housing, employment or insurance) or for surveillance; or
(f) use Platform Data for any purpose unrelated to the features you asked for.
4.3 We use Platform Data in line with the terms and policies of the platform it comes from. If we plan to use Platform Data in a new way, we will tell you first and, where the platform or the law requires it, ask for your consent before we do so.
5. Separation of each customer's data
5.1 Separate store. Each customer's Platform Data is kept separately and linked only to that customer's Account.
5.2 No pooling. We never pool, combine or aggregate one customer's Platform Data with another customer's data. This also applies to aggregated, anonymised or derived data.
5.3 Opt-ins do not change this. No setting, consent or opt-in allows Platform Data to be pooled or shared with other customers. The optional learning in section 6.2 stays inside your own Account.
5.4 Platform-specific reporting. Where a platform's policies require it, we report that platform's data separately from data from other platforms. For example, Google Ads data is always available separately from non-Google data.
5.5 No sale or sharing for advertising. We do not sell Platform Data. We do not share it for cross-context behavioural advertising or targeted advertising.
6. Artificial intelligence
6.1 As stated in our Terms of Use, we never use your Customer Content, Outputs or Platform Data to train, fine-tune or improve any artificial intelligence model that is shared with other customers or offered by a third party. The only learning from Platform Data is the optional learning for your own Account described in section 6.2.
6.2 Learning only from your own results, only for you. If you switch on "Learn from my results" for a connected platform, where it is offered (section 2.3), the Service uses that platform's results for your own campaigns, together with your own creative history in Aylah, to tailor the suggestions it shows in your own Account. This learning is kept separately for each Account. It is never pooled or combined with other customers' data, never used to train or improve any artificial intelligence model that is shared with other customers or offered by a third party, and never used to build profiles of individual people. It is off unless you switch it on, separately for each platform, when you connect or later in Settings › Connected ad accounts, and you can switch it off at any time there. When you switch it off, disconnect the platform or delete your Account, we stop this learning and delete what was learned from that platform's data within 30 days. We do not offer this learning for platforms whose terms do not allow it, and never for Google Ads.
6.3 AI providers. Some features use artificial intelligence technology providers that process data only on our instructions and only to produce your output. We send them Platform Data only where section 2.3 shows this for the platform and, where the table or section 7 says so, only after you have given the separate consent for it. We send only the Platform Data needed for the output you asked for, and we use only providers whose terms do not allow them to use it to train their models or for their own purposes. These providers never receive anything learned under section 6.2 for their own use.
6.4 Chat history. When you use the AI ad agent, earlier results from connected ad accounts are removed from the chat history before it is sent again to an AI provider, unless the consent in section 6.3 applies to that data.
6.5 Automated suggestions and decisions. Suggestions and, where you allow them, Autopilot actions are made by automated systems and can be wrong. They concern your campaigns, not decisions about individual people. You can always review, refuse or reverse a change in your ad account, and you can ask for a person to review how an automated action was taken by writing to support@aylah.ae.
7. Google
7.1 Limited Use. Aylah's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
7.2 Our access to and use of Google Ads data also complies with the Google Ads API Terms and Conditions and the Google Ads API policies.
7.3 Human access. Aylah has no internal tool that shows your Google user data to our team; it is shown only to you, in your Account. We do not look at it unless you ask us to for specific data (for example, in a support request about a specific account), it is necessary for security purposes such as investigating a bug or abuse, or the law requires it.
7.4 Transfers. We transfer Google user data to others only: (a) when it is necessary to provide or improve the features you use in Aylah, including to our hosting and infrastructure providers, which process it only on our behalf to run Aylah, and to AI providers only after you have given the separate consent on the Google Ads AI screen; (b) for security purposes; (c) to comply with the law; or (d) as part of a merger, acquisition or sale of assets, only after getting your explicit prior consent.
7.5 We do not use Google user data to serve, target or personalise advertising to you or anyone else, including retargeting and personalised or interest-based advertising, and we do not transfer or sell it to advertising platforms, data brokers or information resellers. We do not use it to determine credit-worthiness or for lending purposes. "Learn from my results" (section 6.2) is never offered for Google Ads, and we do not use Google user data to train any artificial intelligence model. This section applies in place of section 6.4 of the Privacy Policy for Google user data.
7A. Meta
7A.1 When you connect a Meta ad account, we request permission to read your ad accounts and results to show your reporting in Aylah and, only where managing campaigns is shown as Available for Meta in section 2.3, permission to manage campaigns as described in section 3.3. We use Meta Platform Data only for your own Account, in line with Meta's Platform Terms and Developer Policies, keep each customer's Meta data separate, do not sell or license it, and report Meta campaign data separately from other platforms.
7A.2 We share Meta Platform Data only with our service providers who need it to provide the Service to you and who have agreed in writing to process it only for us, on our instructions; where you expressly direct or consent to it; or where the law requires it.
7A.3 Deleting Meta data. You can remove Aylah in your Meta Business settings under Business integrations (or in your Facebook settings under Apps and websites) or disconnect in Aylah (section 9). To ask us to delete Meta data, follow section 8.7.
7B. Our duties for Meta data
7B.1 We use Meta Platform Data only for you, to provide the features you switch on for your own ad accounts. We do not use it for our own purposes, for any other customer, or to train or improve our own or anyone else's AI models.
7B.2 We keep each customer's Meta data separate from every other customer's.
7B.3 We do not sell or license Meta Platform Data. We do not share it with anyone for their own use. The hosting and infrastructure providers that run Aylah for us process it only to provide the service.
7B.4 You can ask us at any time to delete your Meta data or to disconnect, by using Disconnect in the app or writing to support@aylah.ae. We also delete it when Meta or the person the data is about asks us to. Section 8 explains what is deleted and when.
7B.5 If Meta sends us a request or notice that concerns your data, we will pass it on to you, unless the law forbids us.
7B.6 You may use Meta data shown in Aylah only for your own advertising, and you must follow Meta's Platform Terms and advertising policies. You are responsible for having authority over the ad accounts you connect and for the ads you approve. Political, election and social-issue ads are not allowed in Aylah (Terms 8.1).
8. Retention and deletion
8.1 While connected. We keep Platform Data while the connection is active and only for as long as needed to provide the features you use.
8.2 When you disconnect. When you disconnect an account, we stop accessing it straight away, and within 3 business days we revoke the access tokens or keys at the platform where the platform allows it, and delete them. We delete that account's Platform Data, and anything learned from it under section 6.2, within 30 days.
8.3 When you switch off learning. When you switch off "Learn from my results" for a platform, we stop the learning straight away and delete what was learned from that platform's data within 30 days.
8.4 When you delete your Account. When you delete your Aylah Account, we disconnect all connected accounts, revoke and delete their tokens or keys, and delete all Platform Data and anything learned from it within 30 days.
8.5 Earlier deletion and inactive data. If a platform's terms require earlier deletion, we delete the data within the time those terms require. We also delete Platform Data that is no longer needed for the features you use.
8.6 Backups and legal exceptions. Deleted Platform Data may stay in encrypted backups until they are overwritten on our rolling backup schedule. We do not restore or use Platform Data from backups except to recover the Service after an incident, and if we do, we delete again any data that should have been deleted. We keep Platform Data longer only where the law requires it, and only for as long as it requires. Records of the consents you gave and of the actions taken in your ad accounts are kept as the Privacy Policy describes for consent and acceptance records; they contain the minimum needed to prove what was agreed and done.
8.7 How to ask for deletion (data deletion instructions). You can ask us to delete Platform Data at any time, without deleting your Aylah Account:
(a) In the app: go to Settings › Connected ad accounts and choose Disconnect for the account. This starts the deletion in section 8.2.
(b) By email: write to support@aylah.ae with the subject "Privacy request" from the email address of your Aylah Account, naming the platform and ad account. We confirm receipt, give you a reference number and tell you when deletion is complete. We complete deletion within 30 days of your request.
(c) On the platform: remove Aylah's access in the platform's settings (section 9.2). Where the platform tells us that you removed Aylah or asked for deletion, we treat it as a request under this section.
(d) Whole Account: delete your Aylah Account in Settings, or write to support@aylah.ae with the subject "Privacy request"; section 8.4 applies.
If we cannot delete some data because the law requires us to keep it, we tell you which data and why.
9. Revoking access and withdrawing consent
9.1 In Aylah. You can disconnect any account, switch off "Learn from my results", withdraw the Google Ads AI consent, withdraw a write consent for an ad account or switch off Autopilot at any time in Settings › Connected ad accounts, or by emailing support@aylah.ae. Withdrawing a consent stops the related processing for the future; it does not affect what was done before.
9.2 On the platform. You can also remove Aylah's access directly in each platform's settings, usually in the section for connected, authorised or third-party apps. When you revoke access on a platform, we can no longer read or change that account, and section 8 applies. Disconnecting or revoking access stops all further read and write actions straight away. It does not pause or delete campaigns already running in your account. You manage those on the platform.
10. Security
10.1 We protect Platform Data with technical and organisational measures appropriate to the risk, including:
(a) access tokens and keys encrypted at rest, stored in a restricted, access-controlled store for each customer and never written to logs;
(b) encryption in transit using TLS;
(c) least-privilege permissions: we request only the scopes needed for the features shown as available, and block write actions until they are available and you have approved them;
(d) access to Platform Data limited to authorised staff who need it to provide or support the Service;
(e) an audit record of every action we take in your advertising accounts, including who or what approved it;
(f) server-side enforcement of your spending caps; and
(g) checks that each customer's data stays separate.
10.2 No system is completely secure. If you suspect unauthorised access to your Aylah Account or a connected account, tell us immediately at support@aylah.ae and revoke access as described in section 9. To report a security vulnerability, write to support@aylah.ae with the subject "Security".
11. Your rights and contact
11.1 Your rights over personal data in Platform Data, including access, correction, deletion, objection and withdrawal of consent, are set out in sections 10 and 10A of the Privacy Policy. You exercise them as described there. Where we act as your processor (section 1.4) and someone asks us directly about personal data in your campaigns, we pass the request to you or help you answer it.
11.2 Contact:
Questions about this page: support@aylah.ae
Privacy and deletion requests: support@aylah.ae (with the subject "Privacy request")
Security vulnerabilities: support@aylah.ae (with the subject "Security")
EUPPORIA IT SOLUTIONS L.L.C, Office No. 13, Riggat Al Buteen, Dubai, United Arab Emirates
12. Changes to this page
We may update this page, for example when a platform's availability changes in section 2.3 or a new feature becomes available. We will publish the updated version with a new "Last updated" date. For material changes, we will notify you by email at least 14 days before they take effect, unless a change is required sooner by law or by a platform. A change that only makes a feature less available (for example, a platform declining or withdrawing access) can take effect straight away. Before we use Platform Data in a new way, we will tell you and, where required, ask for your consent (section 4.3).
13. Trademarks
Platform names on this page and in the app are used only to identify the services you can connect. They are trademarks of their respective owners. Aylah is not affiliated with, endorsed by or sponsored by any of them.
Change log
1.2 (26 October 2026). New section 3.3A (approved changes for Meta: paused-only, approve each change, daily limit, never raises a budget), new section 3.7 (activity log, kept 24 months) and new section 7B (our duties for Meta data; 7B.3: we do not share Meta data with anyone for their own use, and the hosting and infrastructure providers that run Aylah for us process it only to provide the service). The availability table is unchanged: managing campaigns for Meta stays "Pending platform approval". Section 7B is shown in English on the Arabic page until the translation is checked.
1.1.1 (26 October 2026). Contact address changed to support@aylah.ae (one mailbox; subjects "Privacy request" and "Security"); availability table (section 2.3) corrected. No other changes.
1.1 (26 October 2026): version number added; availability table (section 2.3) replaces the platform list and the permissions table; Pinterest removed from the list of connectable platforms; ChatGPT ads (OpenAI) added, pending approval; section 3.3 now describes approve-first changes, the separate Autopilot choice and the spending cap (default USD 20 per day, no unlimited, no rounding up), available only where shown in section 2.3; new section 3.5 on separate, recorded consents; section 6.1 clarified and new optional per-Account learning in section 6.2 (off by default, never for Google Ads); new sections 6.4 and 6.5; Google transfers (section 7.4) and Meta sharing (section 7A.2) set out in full; deletion of learned data and new data-deletion instructions (sections 8.2 to 8.7); tokens encrypted at rest (section 10.1); our role as processor for Platform Data (section 1.4); security contact; trademark line (section 13); English version prevails. Effective from publication.
Version 1.2 · 26 October 2026 · SHA-256 469ffbcbc86c4da6