Data Use

01What we connect to

With your authorization, Adgent reads data from the platforms you connect. We request only the access the features you use require. Depending on what you connect, that includes:

• Meta & Google Ads (advertising) — account, campaign, ad set, and ad structure; budgets, bids, and settings; and performance metrics such as spend, impressions, clicks, conversions, ROAS, CPA, CPM, placements, and audiences. Where you grant execution access, we can apply changes you approve.
• Google Analytics 4 — aggregated traffic, engagement, and conversion reporting, to give your ad data on-site context.
• Google Search Console — search performance reporting such as queries, clicks, and impressions.
• Google Merchant Center — product catalogue, item issues, account status, and Shopping performance for the account you select, to diagnose Shopping campaigns against your feed. Read only; Adgent never changes anything in Merchant Center.
• Google Drive and Google Sheets — the content and metadata of files you select or create for use with Adgent, to import or export reports and provide business context. This permission does not let Adgent browse or access other files in your Drive.

02Why we access it

Every connection exists to power a feature you can see. We use the data to produce the decisions and health score you see in the product, detect anomalies, answer the questions you ask, generate the reports and audits you request, and prepare recommended changes. We do not request access to data we do not need, and we do not request access for features that do not yet exist.

03How we use it

Your connected data is used solely to provide the service back to you. It is processed — including by the AI that powers Adgent's analysis — to generate your briefs, answers, and reports, and, on your approval, to carry out changes you ask for. At the model provider that processing is transient and nothing is retained after the request; on our own infrastructure we keep a session record of the question, the answer, and the tool calls for up to 30 days to diagnose faults. We do not use one customer's data to benefit another. OAuth tokens authenticate requests to the platform you connected; they are never included in AI prompts or sent to AI model providers.

04What we never do

• We never sell your data or transfer it to data brokers or resellers.
• We never use your data for advertising, including retargeting or interest-based ads.
• We never use your data to train generalized or non-personalized AI/ML models.
• We never send your data to an AI endpoint that trains on it — we route only to inference endpoints that publish a no-training and zero-data-retention commitment, training-permitted endpoints are excluded at the account level, prompt logging is off on our account, and every request carries an explicit no-training flag.
• We never let humans read your data except with your consent, for security, to investigate abuse, where required by law, or in aggregated/de-identified form for internal operations.
• We never use your data to determine credit-worthiness or for lending.

05Google Limited Use

06Your control

• Read-only by default — Google Analytics and Search Console permissions are read-only, and Google Drive is limited to files you select. Google Ads and Merchant Center each come as one OAuth scope covering read and write, with no read-only alternative: Adgent gates every Ads write behind your approval and never writes to Merchant Center.
• You approve every change — nothing is applied to your accounts until you say go.
• Disconnect anytime — disconnect in Adgent to stop new scheduled access through that connection. To revoke the OAuth grant itself, remove Adgent from the platform's app or permission settings. Neither action deletes data already stored by Adgent.
• Delete anytime — the in-product company-deletion control closes access immediately and disconnects its platform connections. Deletion of the stored data is automated from there: verified deletion requests are picked up and processed every hour, with no manual step. You can also request removal of stored company data or your Adgent login account through our data-deletion instructions.

07Per-platform notes

Google

Adgent requests only these Google OAuth scopes:

• Google Ads — https://www.googleapis.com/auth/adwords for account, campaign, settings, and performance data. Because Google provides one scope for both read and write access, Adgent separately gates every write action behind your explicit approval.
• Google Analytics — https://www.googleapis.com/auth/analytics.readonly for aggregated reporting.
• Google Drive — https://www.googleapis.com/auth/drive.file for files you select or create for use with Adgent.
• Google Search Console — https://www.googleapis.com/auth/webmasters.readonly for authorized site-performance reporting.
• Google Merchant Center — https://www.googleapis.com/auth/content for your product catalogue, item issues, and Shopping performance. Google publishes no read-only variant of this scope; Adgent only ever reads.
• Sign-in — openid and https://www.googleapis.com/auth/userinfo.email, used only to identify which Google account granted a connection and associate it with the correct Adgent user. We do not store the email address they return.

Our use of information from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for ads, do not sell it, and do not use it to train generalized AI/ML models.

Meta

Data accessed via Meta's APIs is processed only as described here and in our Privacy Policy, and in line with applicable Meta terms and developer policies. You can revoke access in Meta and follow our data-deletion instructions at any time.