Privacy Policy

The short version

Adease is a desktop application backed by our secure cloud service. When you connect an advertising account, our backend holds the connection tokens and a synced copy of your campaign data, scoped to your workspace, so the app and its assistant can do their job. We do not sell that data, we do not share it with advertisers or data brokers, and we never use it to train models. Disconnecting an account or deleting your Adease account deletes it.

To run your account we also keep your name and email, your plan and billing history (card details stay with our payment processor, Stripe), what the agent has used from your allowance, and simple records of which features you use. We email you about your account, your trial and your billing; any other emails can be switched off with one click.

Who we are

Adease LTD ("Adease", "we", "us") is the data controller for the personal data described here. You can reach us at support@adease.io.

Company

Adease LTD

Company number

14743980 — England and Wales

Registered office

124 City Road, London, EC1V 2NX, United Kingdom

Contact

support@adease.io

Your advertising data

When you connect an advertising account (Google Ads, Meta, TikTok, Pinterest, LinkedIn or Shopify), the following is processed and stored on our backend, which runs on Google Cloud / Firebase, scoped to your workspace:

• Connection tokens — the OAuth tokens that let Adease act on the accounts you authorised. These are stored server-side in our database and are never placed in the desktop application or exposed to other users.
• Campaign data — a synced copy of the campaign, ad group, ad and keyword structure of your connected accounts, together with performance metrics such as spend, impressions, clicks and conversions.
• Your work in the app — assistant conversations, generated reports, and the knowledge cards you record for each client.
• Your own AI provider key — if your workspace holds a lifetime licence, you supply your own Anthropic API key so the agent can run on your Anthropic account. We store it encrypted (AES-256-GCM) and use it only to make model requests on your behalf. It is never returned to the desktop application, never shown again after you save it, never written to logs, and never shared with another workspace. You can delete it at any time in Settings › AI provider. Anthropic bills you directly for that usage; Adease does not charge for it and adds no margin to it. Workspaces on a Pro or Max subscription do not supply a key — their model usage runs on Adease's own account.
• Shopify store data — if you connect a store, the product, order and revenue figures Adease needs to report sales against your advertising.
• Studio files — product images, logos and brand details you upload to Adease Studio, the prompts you write, and the images and videos it generates for you.

The desktop application additionally keeps a local cache and any files you export; those stay on your machine until you delete them.

Your advertising accounts and store can themselves contain personal data about other people — for example customer lists in an audience, or customers' orders. For that data, you decide what is connected and we process it only on your instructions, to provide Adease to you. Business customers can ask us for data processing terms at support@adease.io.

Your account data

To run your account, your plan and the service, we process this personal data on our own systems:

• Account details — your name, email address, password (stored by our authentication provider as a secure hash, never readable by us), organisation membership and role.
• Billing and subscription records — your Stripe customer reference, plan, number of seats, invoices, renewal and cancellation dates. Card details are entered on Stripe's own pages and are never seen or stored by us.
• Free audit and free trial records — when your free audit and trial started and ended, and a record of what you agreed to at checkout (the trial terms shown beside the button). To offer one trial per payment card, we keep the card "fingerprint" Stripe provides — a code that identifies a card but cannot be turned back into the card number. To offer one free audit per advertising account, we keep the advertising account ID that used it.
• Usage records — how many agent messages and how much of your allowance you and your workspace have used, so limits and credit packs work, and whether a turn reached your ad accounts or led to an approved change, so we can tell whether Adease is working for you.
• Product analytics — which features of the app you use, described in "Analytics" below.
• Support and feedback — messages you send us, feedback you submit in the app, and paid support requests.
• Email records — which emails we have sent you, whether they were delivered, and whether you have unsubscribed.
• Diagnostics — crash reports and error traces, with device type, operating system and app version, used to fix faults.

Emails we send you

• Service emails — about your account, security, billing, receipts, your free trial (a confirmation when it starts, a reminder before the first charge, and a note if we extend it) and changes to these terms. These are part of providing Adease, so you cannot switch them off while you have an account.
• Product emails — help getting started, release notes and occasional messages from the founder about Adease. Every product email has an unsubscribe link, and unsubscribing never affects your account.

We do not send emails on behalf of anyone else.

Why we are allowed to process it

• Performance of a contract — your account details, billing and subscription records, trial records, usage records and service emails are needed to give you Adease and the plan you chose.
• Legitimate interests — keeping Adease secure and working (diagnostics), preventing abuse of free audits and trials (card fingerprints and advertising account IDs), understanding which features help people (product analytics), and telling you about Adease (product emails, which you can stop at any time). We have weighed these against your interests and kept each to the minimum needed.
• Legal obligation — keeping invoices and tax records, and records of what you agreed to when subscribing, for the periods the law requires.
• Consent — advertising cookies on this website, where the law requires consent. You can withdraw consent at any time.

Who else is involved

We use a small number of service providers, each receiving only what is needed for its role and bound by contract to use it only for us:

• Google Cloud / Firebase — hosts our backend, sign-in, database and file storage, where connection tokens, synced campaign data, Studio files and your work in the app are stored.
• Our AI model providers (Anthropic and/or Hugging Face) — when you ask the agent something, your request and the campaign context needed to answer it are processed to generate the response, and for nothing else. See "The agent" below.
• Replicate — runs the image and video models behind Adease Studio. It receives the prompt and any images you supply for a generation, and returns the result.
• Stripe — processes payments, holds your card details, screens payments and card checks for fraud, and sends receipts and trial reminders. Stripe is also an independent controller for some data, under its own privacy policy.
• Resend — sends our emails and tells us whether they were delivered. It receives your name, email address and the content of the email.
• Sentry — receives crash reports and error traces from the app.
• Google Analytics — measures use of this website and, through our servers, of the app. See "Analytics" below.
• Google Ads and Meta — measure which of our adverts lead to a signup, a trial or a subscription. See "Advertising measurement" below.
• AppSumo — if you bought a lifetime licence there, we receive the details needed to activate it.

The advertising platforms and stores you connect are not our service providers: you ask us to connect to them, and their own terms and privacy policies apply to the data they hold.

Your ad account data, campaign data and client names are never sold and never shared with advertisers or data brokers by anyone, including us. We may disclose data if the law requires it, or to a business that takes over Adease, which would remain bound by this policy.

Where your data is processed

Several of these providers are based in, or process data in, the United States. Where personal data leaves the UK or the European Economic Area, we rely on an adequacy decision (such as the UK Extension to the EU–US Data Privacy Framework, for providers certified under it) or on standard contractual clauses approved by the UK and the EU, so that it is protected to the same standard. You can ask us for details at support@adease.io.

Analytics

On this website, Google Analytics measures how many people visit, which pages they read, and which downloads they start. It records page addresses, referrer, approximate location derived from IP address, device and browser type, and download events. It sets cookies in your browser.

In the app, Adease records which features you use — for example that you connected an ad platform, generated a report, sent the agent a message, opened a pricing screen or started a trial — together with the app version and operating system. These events are sent to our own servers, which pass them to Google Analytics; the app contains no Google Analytics, Google Ads or Meta code. They are linked to a random identifier for your installation and to your Adease account number, not to your name or email address, and they never include campaign data, client names, report contents or anything you type.

You can opt out of website analytics with Google's browser add-on, or by blocking analytics cookies in your browser. To opt out of in-app analytics, email support@adease.io and we will switch it off for your account.

Advertising measurement

We advertise Adease on Google Search, and on Facebook and Instagram. When you arrive from one of those adverts, the address carries a click identifier that we store in your browser, and Google Ads and Meta each set their own cookies. If you go on to create an account, start a free trial or start a subscription, that identifier tells us which advert brought you — so we can tell which adverts are worth paying for.

What is shared with Google and Meta is the fact that a click led to a signup, a trial or a subscription, and its value. Where an email address is used to match a conversion it is hashed first, and the address itself is not transmitted. Some of these measurements are sent from our servers rather than from your browser; they carry the same information, and are sent from our systems so that they are not lost when a browser blocks the request. No campaign data, client name or connected ad account is involved at any point — this measures visits to these web pages and nothing else.

The click identifier is kept for 90 days and then discarded. You can refuse these cookies in your browser, use Google's ad settings or Meta's ad preferences to turn off personalised advertising.

The agent

When you ask the agent to do something, the request and the context needed to answer it — which can include campaign structure and performance data from your connected accounts — are processed by a hosted language model operated by Anthropic and/or Hugging Face. The model's output is returned to you and the exchange is stored in your workspace as chat history. Ad account credentials and OAuth tokens are never included in what is sent to the model, and nothing you send is used to train models.

Model training

Your ad accounts, campaigns, knowledge cards and reports are never used to train machine learning models — ours or anyone else's. There is no setting that turns this on.

Google user data

Adease connects to your Google Ads account through Google's OAuth 2.0 flow, requesting a single scope: https://www.googleapis.com/auth/adwords (the Google Ads API). This section sets out, specifically for Google user data, what we access, how we use it, who we share it with, how we protect it, and how long we keep it. Adease's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What Google user data we access

• OAuth tokens for the Google account you authorise, used solely to call the Google Ads API on your behalf.
• Your accessible Google Ads accounts — the customer IDs and descriptive names of the Google Ads accounts you can manage, so you can choose which to connect.
• Campaign structure and settings — campaigns, budgets, ad groups, ads, keywords, and their status and targeting.
• Performance metrics — impressions, clicks, cost and conversions for those campaigns.
• Keyword ideas returned by Google's keyword planning service when you research keywords.

We request no other Google scope and access no other Google service — no Gmail, Drive, Contacts, Calendar or profile data beyond the above.

How we use Google user data

Only to provide the features you see in the application:

• showing your campaigns and their performance in your dashboard and in reports you generate;
• answering questions you ask the agent about your campaigns and their performance;
• suggesting keywords while you plan a campaign;
• creating or changing campaigns, ad groups, keywords and budgets, or pausing campaigns — and only after you have reviewed and approved the specific change in the app. No change is made to your Google Ads account automatically.

We do not use Google user data for our own advertising or marketing, we do not aggregate it across customers, we do not sell it, and we do not use it to train AI or machine-learning models.

Who we share Google user data with

We do not sell, rent or trade Google user data, and we do not share it with advertisers, data brokers or other third parties for their own purposes. It is disclosed only to the processors required to run the service:

• Google Cloud / Firebase — our backend and database run there; tokens and synced campaign data are stored on this infrastructure.
• Our AI model providers (Anthropic and/or Hugging Face) — when you ask the agent a question, the campaign context needed to answer it is processed by the hosted model solely to generate the response. Tokens and credentials are never sent to the model, and the data is not used for model training.

Beyond that, we would disclose data only if required by law, or as part of a merger or acquisition in which the receiving party remains bound by this policy. Humans at Adease do not read your Google Ads data except with your permission for support, where required for security or abuse investigation, or where the law requires it.

How we protect Google user data

• All data is encrypted in transit using TLS, and encrypted at rest on Google Cloud infrastructure.
• OAuth tokens are stored server-side only — never in the desktop application, never in exports, and never visible to other users. The OAuth client secret is held server-side as a managed secret, as is any AI provider key you supply, which is additionally encrypted with AES-256-GCM before it is stored.
• Access is scoped to your workspace: every request is authenticated and authorised against your user account and organisation membership before any Google Ads data is returned.
• Internal access follows the principle of least privilege, and sensitive operations are logged for audit.

How long we keep Google user data, and how to delete it

• OAuth tokens are kept while your Google Ads connection is active and deleted immediately when you disconnect the integration in the app, when the project they belong to is deleted, or when you delete your Adease account.
• Synced campaign data and metrics are kept while the connection is active and deleted with the workspace or account they belong to.
• Agent conversations and reports that reference Google Ads data are kept until you delete them or delete your account.

You can delete everything yourself: disconnect Google Ads from the integrations screen, or use Settings › Privacy & legal › Delete account, which permanently removes your profile, workspaces, stored tokens and synced data. You can also email support@adease.io to request deletion, and you can revoke Adease's access to your Google account at any time at myaccount.google.com/permissions.

How long we keep things

• Account details — while your account is open, and deleted when you delete it.
• Ad platform tokens and synced data — as described in the Google section above, which applies equally to every connected platform.
• Billing records and invoices — for as long as tax law requires (currently six years in the UK).
• Records of what you agreed to at checkout — for three years after your subscription ends, so we can show what was agreed if a charge is ever disputed.
• Card fingerprints and advertising account IDs used to offer one free trial and one free audit each — for as long as we offer free trials and audits, then deleted.
• Usage records — while your account is open.
• Product analytics — up to 14 months in Google Analytics.
• Crash reports — up to 90 days.
• Email records — while your account is open, and your unsubscribe choice for as long as we need to honour it.

Anything held only on your machine is deleted when you delete it.

Crash reports

Crash reports describe the error, where in the app it happened, the screens visited just before, and your device, operating system and app version. They are not designed to collect your advertising data, but an error message can occasionally include the name of the item that failed, such as a campaign. They are seen only by the people who fix faults and are deleted within 90 days.

Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict how we use it, to object to our using it (including at any time to direct marketing), or to have it transferred to you or someone else. Where we rely on consent, you can withdraw it at any time. We reply within one month.

Two of these you can do yourself, without asking: Settings › Privacy & legal › Export my data writes everything out as JSON, and Delete account removes your profile, memberships and stored tokens. For anything else, email support@adease.io.

If you are unhappy with how we handle your data, please tell us first. You can also complain to the UK Information Commissioner's Office at ico.org.uk, or to the data protection authority where you live.

Children

Adease is for people aged 18 and over, and we do not knowingly collect data about children.

Changes

If we change this policy we will update the date at the top of the page, and tell you in the app or by email before a significant change takes effect.

Contact

Questions about any of this, and requests to exercise your rights, go to support@adease.io, or write to Adease LTD, 124 City Road, London, EC1V 2NX, United Kingdom.