One agreement. Published, versioned, not negotiated.
Everything that forms part of a CLEO subscription lives on this page, together with the policies that apply to this website and to the platform. It is the Legal Page that the Master Subscription Agreement refers to.
1.Agreement documents
What governs a CLEO subscription
Every subscription is governed by the CLEO Master Subscription Agreement (the Agreement) and an Order Form. The Agreement is a standard form. We publish it here, we version it, and we do not negotiate it, redline it or vary it for individual customers (clause 2.3). What changes from one customer to the next is only what the Order Form is designed to record: the plan, the site, the term, the fees, the approvers and a small number of elections.
| Document | Version | Effective | Where to find it |
|---|---|---|---|
| Master Subscription AgreementWith Schedule 1 (Services, plans and support), Schedule 2 (Standard Service Terms), Schedule 3 (Data Processing Terms) and Schedule 4 (Content Approval Matrix and Restricted Topics) | 1.1 | 11 September 2026 | Download PDF |
| Plan ScheduleThe published plans, prices, allowances, inclusions and add-ons. Versioned; the version identified on your Order Form governs it and is appended to your countersigned Order Form (Schedule 1 and clause 3.11). | 1.0 | 10 September 2026 | regencleo.ai/pricing; PDF: Download PDF |
| Sub-processor ListForms part of the Agreement under term S3.7 and clause 18.11. | 1.0 | 11 September 2026 | Section 4 of this page |
| Privacy NoticeApplies to account, billing, usage and contact data, and to this website. | 1.0 | 11 September 2026 | Section 6 of this page |
| Cookie notice and website terms | 1.0 | 11 September 2026 | Sections 7 and 8 of this page |
Which version applies to you
The version stated on your Order Form governs that Order Form for its Initial Term. We may apply a newer version from the start of a Renewal Term by giving at least thirty days' written notice. If you object, you may terminate the affected Order Form with effect from the date the new version would have taken effect, and the earlier version applies until then (clause 2.5). Changes required by law or by the terms of a third-party platform may take effect on shorter notice.
The Plan Schedule is versioned separately. The version identified on your Order Form sets your plan's allowances and inclusions. When we increase an allowance or add an inclusion, every subscriber on that plan receives it from the new version's effective date. A reduction or withdrawal applies to an existing Order Form only from the start of a Renewal Term and on at least thirty days' written notice (clause 3.11).
Copies
The version you accepted is sent to you with your countersigned Order Form and remains available on request. Earlier versions are available on request to info@itsregen.com.
Order of precedence
If the documents conflict, Schedule 3 prevails on the processing of personal data, then the body of the Agreement, then Schedule 2, then Schedule 1, then Schedule 4, and then the Order Form, which prevails only in respect of the fields it is designed to record (clause 2.4). Text added to an Order Form outside those fields has no effect.
2.Version history
Every version, with its date and what changed
| Version | Effective | What changed |
|---|---|---|
| 1.1 | 11 September 2026 | Plan Schedule introduced as the single, versioned source of plans, prices, allowances and add-ons (new definition; Schedule 1 Part A rewritten; clause 3.11 added on how later versions apply). The Order Form no longer carries page scope or allowance adjustment fields; Enterprise page scope is the Plan Schedule figure (term S2.15.1). Trial marked in the Plan Schedule (clause 3.7). Scoped hosting or file access for root-level files such as robots.txt and llms.txt where the CMS cannot write them (clause 4.1; new term S2.2.5). Orders are placed on the Website and accepted by email confirmation; the Order Form is withdrawn (clauses 2.2, 2.4, 2.7). Payment by bank transfer against monthly invoice, card by payment link only where Provider requires (clause 7.2). Start Date chosen by the customer within thirty days; Initial Term is the Plan Schedule minimum (clause 8.2). Plan changes and second domains in the platform (clause 3.12). Hosting in Mumbai with disaster recovery in New York stated as fact; the data residency election and pilot terms are removed (S2.15.2, S2.16, S3.14). No change to liability, termination or data terms. |
| 1.0 | 6 September 2026 | First published standard form. One Agreement for every plan, with Schedules 1 to 4 and a two-page Order Form. Introduces electronic acceptance, the published Sub-processor List, per-item content approval as the default on every plan, and the Content Approval Matrix as the only route to autonomous publication. |
Version 1.0 is the first published version. Drafts issued to individual prospects earlier in 2026 were never published and have no successor. An agreement signed before 6 September 2026 continues to be governed by its own terms.
A change to commercial, liability or termination terms is a new major version (2.0). Clarifications, Schedule updates and changes required by law or by a third-party platform are minor versions (1.1). Each is listed here with its effective date, and the notice rules in clause 2.5 apply to both.
3.Accepting the Agreement
How a subscription comes into existence
Who can accept. The Services are supplied to businesses for business purposes only (clause 2.8). The person who accepts confirms that they have authority to bind the business.
How you accept. An Order Form becomes binding on the earliest of three events (clause 2.2): signature of the Order Form by both parties, including electronic signature; clicking to accept the Agreement in the platform or in an electronic signature workflow; or using the Services after receiving the Order Form. Electronic signatures, click-acceptance records and platform audit logs have the same effect as handwritten signatures, consistent with the ADGM Electronic Transactions Regulations 2021 (clause 2.6).
The order portal. After a conversation with us you receive a personal link. It shows the full Agreement, which is also published above, lets you choose a plan from the published menu, takes your company details, and generates your Order Form for review. You accept by confirming your authority, accepting the Agreement and the Order Form, and typing your name as your signature, after verifying your email address with a one-time code. We countersign, and the completed document is emailed to both parties with an acceptance certificate. No document is edited by either side; a wrong field means a new Order Form.
What we record. The Order Form and the full text of the Agreement it references, the name, title and verified email address of the person who accepted, the statements they accepted, the date and time, the IP address and client, a cryptographic hash of the document as accepted, and the same details for our countersignature. We keep this record for the life of the subscription and for at least six years afterwards.
Our acceptance. We may decline any Order Form, trial request or customer, and we are not obliged to give reasons. No subscription exists until we have countersigned the Order Form or confirmed acceptance in writing (clause 2.7). During the first thirty days we may also end an Order Form if we judge that the site, sector, content requirements or working relationship are not suited to the Services, in which case we refund all fees paid under it (clause 8.5).
Purchase orders and supplier forms. We are happy to quote your purchase order number on invoices. Terms contained in a purchase order, vendor onboarding form, supplier portal or cover email are rejected and have no effect, even if we sign or process the document (clause 2.3).
Nothing on this page is legal advice. Take independent advice before you accept.
4.Sub-processor List
Who processes customer data on our behalf, and where
A sub-processor is a third party that processes personal data contained in Customer Data on our behalf in delivering the Services. This is the Sub-processor List referred to in Schedule 3 of the Agreement. Platforms that you connect through your own accounts, and the AI engines we query to measure your visibility, are listed separately in section 5: they process data under their own terms and are not our sub-processors, except where term S3.8 says otherwise.
Notice of changes and your right to object
We add a new sub-processor, or move an existing one to a new location, at least fifteen days before it starts processing Customer Data. We do that by updating this list and by emailing every customer that has registered for notice. To register, email info@itsregen.comwith the subject line Sub-processor updates and the domain of your Customer Site.
Within that fifteen-day period you may object in writing on reasonable data protection grounds. If we cannot resolve the objection, you may terminate the affected Order Form with a pro-rata refund of prepaid fees for the period after termination, as your sole remedy (term S3.7). We impose data protection obligations on every sub-processor that are in substance no less protective than Schedule 3, and we remain responsible to you for their performance.
Where we process data ourselves
| Party | Role | Location |
|---|---|---|
| REGENAI CLEO | Provider. Controller of account, billing, usage and contact data; processor of Customer Data. | Abu Dhabi Global Market, Abu Dhabi, United Arab Emirates |
| RegenAI Group Holding Ltd | Parent company of the Provider (Abu Dhabi Global Market Registration No. 31710). It does not process Customer Data. | Abu Dhabi Global Market, Abu Dhabi, United Arab Emirates |
| Provider personnel | Delivery, support and engineering staff and contractors, bound by confidentiality (term S3.5), with access limited by role to what the Services require (term S3.6). | The United Arab Emirates, the United Kingdom, the United States, Singapore and India |
Sub-processors
Transfers to a sub-processor outside a jurisdiction recognised as adequate by the ADGM Commissioner of Data Protection, or outside the EEA or the UK where those laws apply, rely on the standard contractual clauses incorporated by term S3.9. The plans column shows which subscriptions the sub-processor is used for; where it names a feature, the sub-processor is used only when that feature is enabled for the Customer.
| Sub-processor | Purpose | Customer Data processed | Location of processing | Plans |
|---|---|---|---|---|
| A. Platform infrastructure | ||||
| Amazon Web Services (AWS) | Hosting of the platform, its primary databases, file storage, queues and logs | All Customer Data | Asia Pacific (Mumbai), India, with encrypted replicas and backups in US East (N. Virginia), United States | All plans |
| MongoDB Limited (MongoDB Atlas) | Managed document database for site analyses, crawl data, keyword history, generated content and connected-account tokens | All Customer Data held in that database | AWS Asia Pacific (Mumbai), India | All plans |
| Amazon Web Services (AWS) and MongoDB Atlas | Encrypted backups and disaster recovery | All Customer Data | Asia Pacific (Mumbai), India, and US East (N. Virginia), United States | All plans |
| Amazon Web Services (AWS): Amazon CloudFront and Amazon Route 53 | Delivery of the platform web application, domain name service, and protection against attacks and abuse | Request metadata, IP addresses, credentials in transit | Global points of presence; data at rest is not stored at the edge | All plans |
| Okta, Inc. (Auth0) | Sign-in, sessions and password reset for the platform | Names, email addresses, login identifiers, IP addresses, roles | United States | All plans |
| Microsoft Corporation (Microsoft 365) | Transactional email from the platform (invitations, approval requests, reports, notices and billing emails), and the Provider's own email, documents and calendar | Named Approver and user names and email addresses; content sent for approval; report PDFs; communications with the Provider; Order Forms | India | All plans |
| Alibaba Cloud | Application telemetry: hosting of the Provider's self-managed Sentry and Langfuse | Technical identifiers and error context; prompts and responses of AI model calls | Hong Kong | All plans |
| B. AI model providers, generation and analysis | ||||
| OpenAI OpCo, LLC | Generating, editing and analysing content; knowledge base embeddings; image generation; answering monitored prompts for the ChatGPT engine | Customer Content, brand inputs, monitored prompts and their results, page content of Customer Sites | United States | All plans |
| Anthropic, PBC | Researching, writing and refining long-form content; brand voice profiling; strategy recommendations; done-for-you planning; answering monitored prompts for the Claude engine | Customer Content, brand inputs, monitored prompts and their results, page content of Customer Sites | United States | All plans |
| Google Cloud EMEA Limited (Vertex AI) | Generating and analysing content; image descriptions; article and social images; the autonomous technical optimisation agent; answering monitored prompts for the Gemini engine with Google Search grounding | Customer Content, brand inputs, monitored prompts and their results, page content of Customer Sites | United States (us-central1) or Google's global endpoint | All plans |
| Perplexity AI, Inc. | Answering monitored prompts for the Perplexity engine | Monitored prompts and their results | United States | All plans |
| SpaceXAI LLC (xAI) | Answering monitored prompts for the Grok engine | Monitored prompts and their results | United States | Enterprise |
| Meta Platforms, Inc. (Meta Model API) | Answering monitored prompts for the Meta AI engine | Monitored prompts and their results | United States | Enterprise |
| Hangzhou DeepSeek Artificial Intelligence Co., Ltd. | Answering monitored prompts for the DeepSeek engine, where the Customer selects it | Monitored prompts and their results | People's Republic of China | All plans, optional engine |
| Beijing Zhipu Huazhang Technology Co., Ltd. (GLM) | Generating page elements such as headings, meta tags and redirect pages during technical optimisations; an optional chat model | Page content of Customer Sites; Customer Content where the model is selected | People's Republic of China | All plans |
| HeyGen Technology, Inc. | Avatar presenters, digital twins and voice clones for reels (term S2.9) | Scripts, templates, and likeness material supplied with documented consent | United States | Enterprise |
| BytePlus Pte. Ltd. (ModelArk) | AI video clips for reels | Scripts, brand inputs and reference images | Malaysia, Indonesia or the European Union (Asia Pacific Southeast endpoint) | Enterprise |
| Amazon Web Services (AWS): Amazon Polly | Narration voice for reels | Narration scripts | United States (N. Virginia) | Enterprise |
| OLIVE WORKS LLC (ZeroGPT) | Scoring draft text for signs of machine writing before it is refined | Draft article text | United States; the vendor also reports hosting in Germany | All plans |
| OpenAI, Anthropic, Google, Perplexity, Meta and BytePlus are engaged on terms that prohibit the use of Customer Content to train their generalised models (clause 9.6 and term S3.8); xAI gives the same commitment subject to disclosed account settings. DeepSeek and Zhipu AI, which are based in the People's Republic of China, may use submitted data to improve their models: DeepSeek receives monitored prompts only where a Customer selects that engine, and Zhipu AI receives page content for the technical optimisation tasks listed above. HeyGen may use content submitted on its self-serve plans to improve its models; likeness material is submitted to HeyGen only with the documented consent required by term S2.9. Amazon Polly receives narration scripts only. | ||||
| C. Visibility monitoring and crawling | ||||
| DataForSEO OU | Collecting Google search results and AI answers, ChatGPT answers, Google Maps listings, backlink data, and reviews from Trustpilot and Tripadvisor | Monitored prompts and keywords with a country code; Customer Site and competitor domains; public reviews | Estonia; processing on servers in Germany and the United States | All plans |
| Apify Technologies s.r.o. | Collecting Bing AI answers and search results; public posts and mentions on LinkedIn, Reddit, X and Instagram; reviews from G2, Capterra and TrustRadius | Monitored prompts; Customer and competitor handles and public posts; public reviews | Czech Republic and the United States | All plansSocial and review monitoring: Social bundle and Enterprise |
| Bright Data Ltd. | Keyword rank tracking | Keywords, country and language | Israel | All plans |
| Kundi d.o.o. (Nightwatch) | Keyword rank tracking | Keywords and locations | Slovenia | All plans |
| SerpApi, LLC | Collecting Bing AI answers | Monitored prompts with a country code | United States | All plans |
| Serper.dev | Search results for off-page and social discovery | Search queries containing brand terms | Not published by the operator | All plans |
| Exa Labs, Inc. | Web search for off-page discovery, buyer-intent research and in-app web search | Search queries containing brand terms | United States | All plans |
| AlphaAI Technologies Inc. (Tavily) | Web research for the content pipeline | Research queries | United States | All plans |
| SideGuide Technologies, Inc. (Firecrawl) | Crawling and extracting Customer Site and third-party pages | Customer Site URLs and page content | United States | All plans |
| Jina AI GmbH | Extracting text from rendered pages for analysis and brand voice sampling | Customer Site URLs and page content | Germany, with web services in the United States | All plans |
| Seranking Ltd. and SER Acquisition Inc. (SE Ranking) | Technical site audit of the Customer Site | Customer Site domain and pages | United Kingdom and the United States; processing on servers in Germany and Luxembourg | All plans |
| Web Scraping Guy LLC (ScrapeCreators) | Reddit mentions | Brand terms and public posts | United States | Social bundle and Enterprise |
| Nokia of America Corporation, dba Rapid (RapidAPI) | Medium follower statistics | Medium account handle | United States | Social bundle and Enterprise |
| Google LLC (PageSpeed Insights, Custom Search, Google Ads keyword data and YouTube Data APIs) | Page speed measurement, search results, keyword volumes, and public YouTube data | Customer Site URLs, keywords, public YouTube channels and videos | United States | All plans |
| D. Business systems holding account data | ||||
| HubSpot, Inc. | Customer relationship records, contract records and sales correspondence | Names, work email addresses, company details, communications with the Provider | European Union (EU data hosting) | All plans |
| Stripe Payments Europe, Limited | Card payments and invoicing. Card numbers are entered directly with the processor and are not stored by the Provider | Billing contact name and email, billing address, transaction records | Ireland and the United States | Card billing |
| Rewardful Inc. | Attribution of referrals and affiliate commissions | Referral code, sign-up and subscription events | Canada | All plans |
| E. Website protection and lead identification | ||||
| Cloudflare, Inc. (Turnstile) | Protecting the forms on this website against automated abuse | IP address and browser signals of a visitor submitting a form | United States | This website |
| Artia International S.R.L. (ip-api.com) | Country lookup of an IP address, for abuse prevention on this website and for the sign-in location shown to administrators | IP addresses | Romania | This website and all plans |
| Elaunira SARL (Ipregistry) | Company lookup for visitor IP addresses | Visitor IP addresses | France; may transfer to the United States | Leads feature |
| Leadpipe LLC | Lead identification | Visitor company and contact details | United States | Leads feature |
| Defastra Tech Inc. (Prospeo) | Contact enrichment | Names and companies | United States | Leads feature |
| Adyntel | Advertising intelligence lookups | Company domains | Not published by the operator | Leads feature |
Data residency regions
Where an Enterprise Order Form records a data residency region, Customer Data at rest is stored in the platform's primary database for that region. Residency does not cover data processed transiently by third-party platforms, AI engines, sub-processors, crawlers, monitoring tools or content delivery networks, which may process data in other locations (term S2.15.2).
| Region | Data centre location | Note |
|---|---|---|
| Mumbai | Amazon Web Services (AWS), Asia Pacific (Mumbai), India, with encrypted replicas and backups in US East (N. Virginia), United States; MongoDB Atlas on AWS in the same region | India. Transfers to India and the United States rely on the standard contractual clauses in term S3.9. |
Changes to this list
| Date | Version | Change |
|---|---|---|
| 11 September 2026 | 1.0 | List first published. |
5.Connected platforms and AI engines
The third-party platforms the platform connects to or measures
This is the current list published under clause 15.2 of the Agreement. You authorise each connection through your own accounts, and each platform processes data under its own terms, which you must comply with (clause 15.1). We may add, suspend or withdraw support for any platform or AI engine where its terms, APIs, pricing, policies or availability change (clause 15.2). Charges levied by a platform are not included in the fees (clause 15.4). Anything not listed here is not supported, including TikTok and Google Business Profile.
| Category | Platforms | Plans | Notes |
|---|---|---|---|
| Content management systemsTechnical optimisations and publishing | WordPress, Wix, Shopify, Sanity, and sites built on React, Next.js, Vue and Astro | All plans | On any other platform the scan and measurement still run; the deploy step hands recommendations to your team. |
| Search and analytics | Google Search Console, Google Analytics 4 | All plans | Connected during onboarding through your own Google account. |
| AI engines monitoredPrompts checked six days a week | ChatGPT (OpenAI), Google AI (Google), Bing AI (Microsoft), Perplexity (Perplexity AI), Gemini (Google), Claude (Anthropic), DeepSeek (DeepSeek, China), Grok (xAI), Meta AI (Meta) | Seven on self-serve plans Nine on Enterprise | Up to four engines run at a time. Grok and Meta AI are available to select on Enterprise only. The monitored prompts you configure, which normally contain your brand and product terms, are sent to these engines directly or through the monitoring providers in section 4C, and the responses and citations are stored to report your visibility. Do not include personal data in monitored prompts. |
| Social platforms monitored | X, LinkedIn, Reddit, Medium, YouTube, Quora, Bluesky | Social bundle and Enterprise | Public posts and mentions only. |
| Posting from inside the platform | X, LinkedIn (personal profiles only), Bluesky, Mastodon; YouTube on Enterprise | Social bundle and Enterprise | Through your Connected Accounts. LinkedIn company pages are not supported. |
| Reels | X, Bluesky, LinkedIn, YouTube | Enterprise | Term S2.9 applies to synthetic media and likeness. |
| Long-form publishing | Medium, LinkedIn | Social bundle and Enterprise | Through your Connected Accounts, drawing on the article allowance. Publishing only; no outreach (term S2.10). |
| Review platformsPerception | G2, Capterra, Trustpilot, TrustRadius and Tripadvisor | Enterprise | Up to five connected. Monitoring, reply drafts and tools to invite your own genuine customers to review. No review is written, posted or solicited in any name by the Provider (term S2.8). |
6.Privacy Notice
How we handle personal data
6.1 Who we are
REGENAI CLEO, registered in Abu Dhabi Global Market under number 33929, Sky Tower, Al Reem Island, Abu Dhabi, United Arab Emirates (we, us). We operate the CLEO platform and this website. For anything in this notice, emailinfo@itsregen.com with Privacy in the subject line. Our lead regulator for data protection is the ADGM Office of Data Protection.
6.2 Who this notice covers, and the role we play
- Visitors to this website, including anyone who runs the free Presence Scan, books a conversation or contacts us. We are the controller.
- People at our customers: administrators, Named Approvers, billing contacts and anyone who uses the platform or corresponds with us on a customer's behalf. We are the controller of your account, billing, usage and contact data (clause 14.2 of the Agreement).
- People at our prospects and suppliers, and anyone who corresponds with us. We are the controller.
- Individuals whose data appears in a customer's content, sites, accounts or monitoring, for example a customer's own customers, website visitors, and people who post or review publicly about a customer's brand. Here the customer is the controller and we are its processor under Schedule 3 of the Agreement. Section 6.5 explains what that means for you.
6.3 What we collect as a controller
| Category | Examples | Where it comes from |
|---|---|---|
| Identity and contact | Name, work email address, job title, company, phone number where you give it | You, or your employer when it sets up the account |
| Account and access | Login identifiers, roles, approver designations, Connected Account authorisations, security settings | You and your employer |
| Contract and billing | Order Forms, acceptance records, invoices, payment status, billing address. Card numbers are entered with our payment processor and are not stored by us | You, your employer, our payment processor |
| Communications | Emails, support tickets, approval replies, meeting notes, feedback | You |
| Usage and technical data | Features used, actions taken, approval decisions, timestamps, IP address, browser and device information, logs | Generated by the platform and this website |
| Presence Scan inputs | The domain you enter and the public pages we read to produce the scan; the name, work email address, company name and, if you choose to give it, phone number you provide to receive the report | You and the public web |
| Marketing preferences | Subscription status, opt-outs, interactions with our emails | You and our email systems |
We do not ask for special category data, government identifiers, payment card data or data about children, and we ask customers not to place them in the platform (clause 14.4 of the Agreement).
6.4 Why we use it, and the legal basis
| Purpose | Legal basis under the ADGM Data Protection Regulations 2021 |
|---|---|
| Providing the platform and the Services, onboarding, approvals, reports and support | Performance of our contract with the customer. Where you act for a customer that employs you, our legitimate interest in performing that contract. |
| Billing, collections and keeping financial records | Performance of the contract; compliance with legal obligations. |
| Securing the platform, preventing fraud and abuse, and enforcing the Agreement | Our legitimate interests in running a secure service and protecting our customers and ourselves. |
| Improving the platform, benchmarking and product analytics | Our legitimate interests. We use aggregated or de-identified data for this wherever possible (clause 9.6 of the Agreement). |
| Responding to enquiries, running the Presence Scan and booking conversations | Steps taken at your request before entering into a contract; our legitimate interest in responding to you. |
| Sending business marketing about CLEO to people who have enquired or subscribed | Our legitimate interest in promoting our services to businesses, with your right to object at any time; consent where the law that applies to you requires it. |
| Sanctions screening, legal compliance, disputes and regulatory requests | Compliance with legal obligations; our legitimate interests in establishing, exercising or defending legal claims. |
| Naming a customer as a reference (name and logo) | The election the customer makes in its Order Form (clause 9.8 of the Agreement). |
You are not required by law to give us personal data. If you do not, we cannot provide the Services to your business, run a scan for you or respond to you.
6.5 Data we process on behalf of customers
When a customer subscribes, the platform processes personal data contained in the customer's content, sites, Connected Accounts and monitoring. The customer decides what the platform processes and why; we process it only on the customer's documented instructions, which are the Agreement, the Order Form, the Content Approval Matrix and the settings the customer configures (term S3.3). The data involved is described in term S3.2, our sub-processors in section 4, and the platforms the customer connects insection 5.
Monitoring covers public content only: search results, AI engine responses, public posts, reviews and mentions that refer to a customer's brand. We do not attempt to identify individuals beyond the public name or handle shown, and we do not build profiles of individuals for our own purposes.
If your personal data appears in a customer's content or monitoring and you want to exercise your rights, contact that customer. If you contact us instead, we will pass your request to the customer and help it respond (term S3.10).
6.6 Who we share data with
- The sub-processors and business systems listed in section 4, on contractual terms that restrict what they may do with it.
- The platforms and AI engines listed in section 5, when a customer connects them or instructs monitoring; each processes data under its own terms.
- Our group companies, for engineering, delivery and support.
- Our payment processor, banks, auditors, accountants, lawyers and insurers, to the extent they need it.
- Courts, regulators and law enforcement, where the law requires it or to protect our rights.
- A buyer or successor, if our business or the platform is sold or reorganised, on terms that protect your data.
We do not sell personal data and we do not share it with advertisers.
6.7 International transfers
We are established in the ADGM. Our sub-processors process data in the locations shown insection 4, and an Enterprise customer may choose a data residency region there. Where a transfer from the ADGM goes to a jurisdiction that the ADGM Commissioner of Data Protection has not recognised as adequate, we rely on the standard contractual clauses adopted under section 42 of the ADGM Data Protection Regulations 2021, or another safeguard those Regulations permit. Where the GDPR or the UK GDPR applies to a transfer, we rely on an adequacy decision where one exists and otherwise on the European Commission's standard contractual clauses or the UK International Data Transfer Addendum (term S3.9). You may ask us for a copy of the safeguard that applies to your data.
6.8 How long we keep data
| Data | Retention |
|---|---|
| Account, contract and acceptance records; communications with a customer | For the life of the subscription and six years afterwards, so that either side can rely on the record if a claim arises. |
| Invoices and financial records | For as long as ADGM company law and applicable tax law require. |
| Customer Data we process as processor | Exportable during the thirty-day Export Window after the subscription ends; deleted within ninety days after the Export Window; removed from routine backups within twelve months (term S3.12). |
| Platform logs, change logs and audit records | Up to twenty-four months after the subscription ends (term S2.13.3). |
| Trial accounts that do not convert | Deleted within ninety days after the trial ends. |
| Enquiries, Presence Scan results and prospect records | Until you ask us to stop, or twenty-four months after our last contact with you. |
| Website analytics | As set out in the cookie table in section 7. |
We keep data for longer where the law requires it or where it is needed for a claim, and we delete or de-identify it when the reason for keeping it ends.
6.9 Security
We encrypt data in transit and at rest, limit access by role, require multi-factor authentication for our personnel, log and monitor access, follow secure development practices, take regular backups and review these measures periodically (term S3.6). A summary of current measures is available to customers on request. No system is perfectly secure; if a personal data breach affects Customer Data we notify the customer without undue delay and in any event within seventy-two hours after becoming aware of it (clause 14.3).
6.10 Your rights
Subject to the law that applies to you, you may ask us to: give you access to your personal data and a copy of it; correct it; delete it; restrict how we use it; give it to you or another provider in a portable form; and stop using it where we rely on legitimate interests, including for marketing. Where we rely on consent, you may withdraw it at any time without affecting what we did before. You may also ask us not to make decisions about you based solely on automated processing.
To exercise a right, email info@itsregen.com withPrivacy in the subject line. We may need to verify your identity. We respond without undue delay and within the period the applicable law allows: one month under the GDPR and the UK GDPR, and two months under the ADGM Data Protection Regulations 2021, each extendable where the law permits. There is no charge unless a request is manifestly unfounded or excessive.
If you are not satisfied with our response you may complain to theADGM Office of Data Protection. If you are in the EEA or the UK, you may also complain to your local supervisory authority.
6.11 Marketing
We send business marketing about CLEO to people who have enquired, run a scan, booked a conversation or subscribed. Every message includes an unsubscribe link, and you may opt out at any time by using it or by emailing us. We do not send marketing to a customer's approvers or users about anything other than the service they use, unless they have asked for it.
6.12 Automated decision-making and AI
The platform uses artificial intelligence to generate and edit content, to analyse pages, prompts and results, and to recommend actions. Content is published only after a Named Approver at the customer approves it, or under a Content Approval Matrix the customer has completed (clause 5 of the Agreement). We do not make decisions about individuals that produce legal or similarly significant effects by automated means alone. We do not use customer content to train generalised foundation models, and we require our AI sub-processors not to do so (clause 9.6).
6.13 Children
The platform and this website are for businesses. We do not knowingly collect personal data from anyone under eighteen, and we ask customers not to place children's data in the platform.
6.14 Changes to this notice
We update this notice when our processing changes and record the version and date at the top of this section. Where a change materially affects customers we also notify them by email. The version history for the Agreement is in section 2.
8.Website terms
Using regencleo.ai
Information only. The pages of this website describe our services and prices. They are not an offer that you can accept by conduct; a subscription comes into existence only in the way described insection 3. Prices and plan contents may change, and the Agreement records how changes affect existing subscriptions.
The Presence Scan. The free scan reads publicly available pages of the domain you enter and returns an indicative score. It is not an audit, a warranty, a ranking prediction or professional advice, and it may be incomplete or out of date. Use it for domains you own or represent.
Content and marks. The text, design, software and data on this website belong to us or our licensors. CLEO, CLEO Orbit, Quill and Perception are names we use for our products. You may read and share pages for your own information. You may not copy, scrape, crawl or reproduce the site by automated means, except for indexing by a public search engine or AI engine that respects our robots directives, and you may not use our names or marks to suggest an endorsement.
Third-party links. Links to other sites are provided for convenience. We do not control them and are not responsible for their content or their handling of your data.
No liability for the website. To the extent the law allows, this website is provided as it is and we exclude liability for loss arising from reliance on it. Nothing on this website excludes liability that cannot be excluded by law. Liability under a subscription is governed by the Agreement, not by this section.
Law and courts. These website terms are governed by the laws of the Abu Dhabi Global Market, and the ADGM Courts have exclusive jurisdiction over any dispute about them.
9.Notices and contact
Where to send what
| Purpose | Channel |
|---|---|
| Legal notices under the AgreementBreach, termination, objection to a new version or sub-processor | Email info@itsregen.com with Legal Notice in the subject line (clause 18.1). A notice is deemed received on the next Business Day after sending unless a delivery failure is received. |
| Registered office | REGENAI CLEO, Sky Tower, Al Reem Island, Abu Dhabi, United Arab Emirates. Abu Dhabi Global Market Registration No. 33929. |
| Day-to-day contact | apoorva@itsregen.com |
| Privacy requests and questions | info@itsregen.com, subject Privacy |
| Sub-processor update notices | info@itsregen.com, subject Sub-processor updates, with your domain |
| Security concerns | info@itsregen.com, subject Security |
| Support | In-platform tickets. Response targets and hours are in Schedule 1, Part C of the Agreement. |