Affreedom Research

Everything in the workspace is about a business and its public offer. It holds no personal data about consumers.

• Affiliate programmes — brand, merchant website, commission rate, cookie duration, the regions where promotion is permitted, and whether deep linking is allowed. Read from each affiliate network's own API using the operator's credentials.
• Merchant websites — which affiliate platform a store runs on, its public customer review score, and the deals it publishes.
• Traffic estimates — a third-party estimate of monthly visits, used only to tell a large merchant from a small one. An estimate, not a measurement, and labelled as such wherever it appears.
• Advertising records — which advertisers have publicly disclosed ads pointing at a merchant's site, read from public sources.
• Keyword demand — search volume and bid ranges for terms related to a merchant, from the Google Ads API.

Where a source does not publish a field, the field stays empty rather than being guessed. Where a value is derived rather than published, it is marked as inferred.

1. 1. Connect the operator's own affiliate network accounts and pull in the programmes approved for them.
2. 2. Compare them on commission, cookie duration, permitted regions and merchant size, and shortlist the ones worth advertising.
3. 3. Research keyword demand for a shortlisted merchant, then write the ad copy and landing page by hand.
4. 4. Create and manage the Google Search campaign.

Steps 1 and 2 read affiliate network APIs. Steps 3 and 4 are where the Google Ads API comes in.

The workspace requests the https://www.googleapis.com/auth/adwords scope for three purposes, and nothing else:

• Keyword research — search volume, competition and bid estimates for a merchant's terms. In place.
• Reporting — performance of campaigns, keywords and search terms, and spend against daily budgets. Being built.
• Account management — creating and adjusting Search campaigns: budget, targeting, keywords, negative keywords and ad text. Being built.

Only Google Ads accounts the operator owns are accessed, linked under the operator's own manager account. There is no second user and no mechanism to add anyone else's account.

Use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

These are binding commitments, and they hold regardless of build state.

• Never move money. No payment initiated, no payment method changed, no billing setup edited. There is no billing or payment code in it at all. Spend figures are read-only.
• Never start spending on its own. Campaign management, once built, will create every campaign paused; enabling one, raising a budget, or removing a campaign or keyword will each need an explicit confirmation. No write operation will run on a schedule.
• Never create Google Ads accounts, and never attempt to work around policy review.
• Never resell or publish Google Ads data. It is read for the operator's own accounts and stays on a private server.

Which safety mechanisms are already in the code, and which arrive with the features they protect, is listed openly at affreedom.org/safeguards.

Data stays on a private server with no public interface. Credentials are encrypted at rest and are never returned to the browser in any form, not even masked — the interface can only ask whether a credential exists, not what it is.

The operator drives the workspace by describing what is wanted in plain language; an assistant (Anthropic Claude) translates that into calls. Aggregated account metrics and campaign settings are therefore processed by that assistant. No consumer personal data is sent to it.

Full detail, including retention periods and how to make a data request, is in the privacy policy.

Login only. Accounts are created by hand by the owner, and a new account sees nothing until it is approved. There is no public sign-up and no way to request one here.