Privacy Policy

How BrandGuard uses personal data on our website and in the service.

Effective 16 September 2026

Controller: Clean Digital Limited
Contact: [email protected]
Website: https://usebrandguard.com

1. Who We Are

BrandGuard is operated by Clean Digital Limited, trading as BrandGuard. We are the data controller for the personal data described in this notice unless we say otherwise.

Registered office: Clockwise Offices, 84 Commercial Street, Edinburgh, Scotland, EH6 6LX
Company number: SC428397
VAT number: VAT status will be confirmed on customer invoices
Privacy contact: [email protected]
DPO or privacy lead: Privacy requests can be sent to [email protected]
ICO registration: ICO registration details will be published where required

2. The Personal Data We Collect

We collect information that we need to run BrandGuard, manage customer accounts, provide support, improve the product, keep the service secure, and meet legal obligations.

Identity and contact details, such as name, email address, login method, profile information, and workspace role.
Account and organisation information, such as workspace names, invited users, permissions, billing owner details, plan information, and subscription status.
Integration data, including Google account identifiers and profile details, Google Ads account names and hierarchy, campaign settings and selections, keywords and negative keyword lists, targeting and landing-page information, performance and spend metrics, monitoring configuration, and authorization credentials where you connect Google Ads.
Optional browser usage data, where you allow it, such as pages viewed, features used, reports opened, feature evaluations, browser diagnostics, and session information.
Service activity, operational, and security records, such as authenticated settings changes, authentication events, workspace audit logs, monitoring and report job status, billing actions, abuse prevention signals, and server-side failures.
Payment and billing records, such as Stripe customer IDs, subscription IDs, invoice status, plan changes, and billing support messages.
Website and device data, such as IP address, browser, device type, approximate location, cookie identifiers, consent choices, and analytics events.
Support and communication data, including messages you send us, attachments, feedback, and records of our replies.

3. How We Use Personal Data

Purpose	Examples	Lawful basis
Provide and manage BrandGuard	Create accounts, authenticate users, manage workspaces, run monitoring, produce reports, and provide requested features.	Contract and legitimate interests.
Provide integrations	Connect Google Ads, refresh access, read account data, show campaign options, monitor selected terms, and apply user-approved automation.	Contract and legitimate interests.
Take payment and administer plans	Process checkout, manage subscriptions, invoices, cancellations, upgrades, downgrades, and plan limits.	Contract, legal obligation, and legitimate interests.
Optional product improvement	Measure browser usage, evaluate product changes, diagnose browser errors, and review session recordings where you enable each purpose.	Consent.
Operate and secure the service	Keep audit records, run monitoring and report jobs, investigate incidents, prevent misuse, and record server-side failures.	Contract, legal obligation, and legitimate interests, depending on the record and purpose.
Communicate with you	Send service messages, support replies, billing notices, security notices, and product updates.	Contract, legitimate interests, consent where required, and legal obligation.
Comply with law	Keep required records, respond to lawful requests, resolve disputes, and enforce our terms.	Legal obligation and legitimate interests.

Provide and manage BrandGuard

Examples: Create accounts, authenticate users, manage workspaces, run monitoring, produce reports, and provide requested features.
Lawful basis: Contract and legitimate interests.

Provide integrations

Examples: Connect Google Ads, refresh access, read account data, show campaign options, monitor selected terms, and apply user-approved automation.
Lawful basis: Contract and legitimate interests.

Take payment and administer plans

Examples: Process checkout, manage subscriptions, invoices, cancellations, upgrades, downgrades, and plan limits.
Lawful basis: Contract, legal obligation, and legitimate interests.

Optional product improvement

Examples: Measure browser usage, evaluate product changes, diagnose browser errors, and review session recordings where you enable each purpose.
Lawful basis: Consent.

Operate and secure the service

Examples: Keep audit records, run monitoring and report jobs, investigate incidents, prevent misuse, and record server-side failures.
Lawful basis: Contract, legal obligation, and legitimate interests, depending on the record and purpose.

Communicate with you

Examples: Send service messages, support replies, billing notices, security notices, and product updates.
Lawful basis: Contract, legitimate interests, consent where required, and legal obligation.

Comply with law

Examples: Keep required records, respond to lawful requests, resolve disputes, and enforce our terms.
Lawful basis: Legal obligation and legitimate interests.

4. Google Ads and Google API Data

Google sign-in

When you choose Sign in with Google, we receive your Google account identifier, name, email address, and profile picture where provided. We use this information to create or identify your BrandGuard account, authenticate you, and display your profile. We do not receive your Google password. Signing in does not by itself connect your Google Ads accounts.

Google Ads access and automation

Connecting Google Ads is a separate authorization. With your permission, we access the advertiser and manager accounts available to your Google identity, including account identifiers, names, and hierarchy. For connected accounts and selected campaigns, we may access campaign names, status, budgets, bidding and targeting settings, landing-page URLs, keywords, negative keyword lists, search terms, and performance information such as impressions, clicks, and spend.

We use this data to let you discover and select accounts and campaigns, configure monitors, review reports and savings estimates, check connection health, and carry out the automation you enable. This includes managing negative keyword lists and attaching or removing them from selected campaigns according to your configured rules. BrandGuard uses Google user data only to provide or improve these user-facing features.

Storage and ongoing access

We store the account and campaign information needed for your workspace, monitoring configurations, and reports in our service databases. Google Ads authorization credentials are held in protected server-side storage with restricted access. We use these credentials to obtain access tokens so that the monitoring and automation you authorize can continue while you are signed out. Google Ads refresh tokens are stored in an encrypted managed credential store and are not displayed to workspace members.

Sharing and use restrictions

Google Ads account information, monitoring results, and reports may be visible to the workspace owners, organisation administrators, agency managers, and invited users you authorize, according to their roles and permissions.
Service providers may process Google user data on our behalf only as needed to deliver or improve the features you authorize, subject to confidentiality and data-protection obligations. We may also disclose it where necessary for security or to comply with applicable law. These limits apply to the recipients listed in section 6.
Our personnel may access Google user data with your affirmative agreement for specific support needs, where necessary to investigate security issues or abuse, or to comply with applicable law. Aggregated data may be reviewed for internal operations in accordance with applicable privacy law.
We do not sell Google user data or transfer it to data brokers or information resellers. We do not use or share it to target or personalize advertisements to individuals, including retargeting or interest-based advertising. The campaign-management actions described above are performed only to provide the BrandGuard features you authorize.
We do not use Google user data for creditworthiness or lending decisions, or to develop, improve, or train general-purpose or non-personalized AI or machine-learning models.
These restrictions also apply to data derived from Google user data, including aggregated or anonymised data.

Our use of Google user data follows the Google API Services User Data Policy including its Limited Use requirements.

Disconnecting and deleting Google data

You can revoke BrandGuard's authorization in your Google account connections. In BrandGuard, open Google Ads, unlink the advertiser accounts using a connection, then open Google connections to disconnect the Google identity. Unlinking an advertiser pauses its BrandGuard monitors; it does not revoke the Google identity's authorization or erase historical reports.

Disconnecting a Google identity disables that connection in BrandGuard. A completed disconnection removes its stored Google Ads refresh token. If credential removal fails, the connection remains disabled and BrandGuard asks you to retry removal. Disconnecting in BrandGuard does not replace revoking authorization in your Google account.

Disconnecting or revoking access does not automatically delete previously collected account information, monitoring records, or reports. Their retention is explained in section 8. To request deletion of your Google user data or BrandGuard account, email [email protected]. We will verify your authority to make the request and delete the relevant data unless continued retention is required by law or necessary for a legitimate security or dispute purpose. We will explain any such exception when responding.

5. Cookies and Analytics

We use essential cookies and similar technologies to provide the website and application, keep users signed in, protect accounts, remember preferences, and support OAuth and security features.

Optional browser analytics, error diagnostics, and session recordings start only after you allow them. You can control each separately and change your choices at any time in cookie preferences. These features may use cookies or similar browser storage.

We also keep server-side records of service activity to operate, secure, and improve BrandGuard. These records are separate from optional browser collection and use the lawful bases described above.

7. International Transfers

Some providers may process personal data outside the UK. Where this happens, we use appropriate safeguards where required, such as adequacy regulations, UK international data transfer agreements, UK addenda to EU standard contractual clauses, vendor data processing terms, and security controls.

8. How Long We Keep Personal Data

We keep personal data only for as long as we need it for the purposes described in this notice, then delete, anonymise, or aggregate it unless we need to keep it longer for legal, accounting, security, or dispute reasons.

Data type	Typical retention
Account and workspace data	For the life of the account, then normally up to 24 months after closure unless a longer period is needed for disputes, security, tax, accounting, or legal obligations.
Google Ads authorization credentials	Retained while the Google connection is active. A completed disconnection removes its stored refresh token; if removal fails, the disabled connection remains pending cleanup until removal succeeds.
Google Ads and monitoring data	While needed for an active Google Ads connection or monitoring configuration, then normally up to 24 months after disconnection. Historical reports and audit records may be retained where still needed for an active workspace or a legal, accounting, security, or dispute purpose; they remain subject to the use restrictions in section 4 and deletion requests in section 9. Authorization credentials are handled separately as described in section 4.
Billing and invoice data	Normally up to 7 years after the relevant transaction or invoice for tax, accounting, and audit obligations.
Support data	Normally up to 24 months after the support request is closed unless it relates to an active account, dispute, or legal obligation.
Security and audit logs	Normally up to 24 months from collection unless needed to investigate abuse, fraud, security incidents, or legal claims.
Analytics and diagnostic data	Analytics and diagnostic data is retained only while needed to improve, operate, and maintain the service. Optional browser analytics, diagnostics, and session replay follow your saved choices. We review retention and respond to deletion requests under applicable data protection law.
Consent records	Consent choices and changes are retained as compliance records while needed to demonstrate and honour those choices and to resolve related legal claims.

Account and workspace data

Typical retention: For the life of the account, then normally up to 24 months after closure unless a longer period is needed for disputes, security, tax, accounting, or legal obligations.

Google Ads authorization credentials

Typical retention: Retained while the Google connection is active. A completed disconnection removes its stored refresh token; if removal fails, the disabled connection remains pending cleanup until removal succeeds.

Google Ads and monitoring data

Typical retention: While needed for an active Google Ads connection or monitoring configuration, then normally up to 24 months after disconnection. Historical reports and audit records may be retained where still needed for an active workspace or a legal, accounting, security, or dispute purpose; they remain subject to the use restrictions in section 4 and deletion requests in section 9. Authorization credentials are handled separately as described in section 4.

Billing and invoice data

Typical retention: Normally up to 7 years after the relevant transaction or invoice for tax, accounting, and audit obligations.

Support data

Typical retention: Normally up to 24 months after the support request is closed unless it relates to an active account, dispute, or legal obligation.

Security and audit logs

Typical retention: Normally up to 24 months from collection unless needed to investigate abuse, fraud, security incidents, or legal claims.

Analytics and diagnostic data

Typical retention: Analytics and diagnostic data is retained only while needed to improve, operate, and maintain the service. Optional browser analytics, diagnostics, and session replay follow your saved choices. We review retention and respond to deletion requests under applicable data protection law.

Consent records

Typical retention: Consent choices and changes are retained as compliance records while needed to demonstrate and honour those choices and to resolve related legal claims.

9. Your Rights

Under UK data protection law, you may have rights to access, correct, delete, restrict, object to processing, receive a portable copy of your data, and withdraw consent where we rely on consent.

To make a request, contact [email protected].
You can change or withdraw optional analytics permissions at any time through the cookie preferences page.
You can revoke Google OAuth access through your Google account.
You can complain to the UK Information Commissioner's Office if you are unhappy with how we handle your data.

10. Security

We use technical and organisational measures designed to protect personal data, including access controls, authentication safeguards, encrypted connections, audit logs, vendor controls, and secure handling of integration credentials. No online service can be guaranteed to be completely secure.

11. Children

BrandGuard is not directed at children. Users must be at least 18 or otherwise authorised to use the service on behalf of a customer.

12. Changes to This Notice

We may update this notice from time to time. If we make material changes, we will take reasonable steps to notify users through the website, application, email, or another appropriate method.

Before accessing additional Google user data or using Google user data for a new purpose that was not previously disclosed, we will update this notice, explain the change, and obtain your consent.