Privacy Policy

This Privacy Policy explains how Adniqo collects, uses and protects information when you visit or use our software. Adniqo is intended for business and professional users who want help generating, configuring and managing Google Ads Search campaigns.

1. Who we are

Adniqo provides software that analyses business information supplied by a user, generates Google Ads campaign configurations and, when a user chooses to connect Google Ads, can perform authorised actions in the Google Ads account selected by that user.

In this policy, “Adniqo”, “we”, “us” and “our” refer to the provider of the Adniqo service. We do not state a separate registered company name, company number or postal address here because no such verified information is currently published within the service.

2. Information we collect

The information we handle depends on how you use Adniqo and may include:

• Contact and account information: an email address submitted to the waitlist or competitor scan, any information associated with your Adniqo session, and Google Ads account names or identifiers made available after you connect Google.
• Business and campaign information: the website or domain you submit, publicly available information retrieved from that site, business details, selected services, locations, campaign goals, advertising budgets, landing pages, keywords, ad text, campaign settings, instructions and generated campaign configurations.
• Google Ads information: accessible customer account identifiers, descriptive names, manager-account status, currency, time zone, geo-target information, and campaign configuration information needed to provide and verify requested functionality.
• Payment information: payment status, amount, currency, checkout reference and campaign entitlement. Stripe processes payment-card details; Adniqo does not receive or store full card numbers.
• Technical and usage information: session identifiers, browser and request information present in server logs, IP address used transiently for abuse prevention, referral information, landing path and UTM campaign parameters. A competitor scan also stores the submitted website domain, verified service information, selected scan location, generated query count and scan count with the scan email.
• Optional advertising measurement: if you allow optional tracking, the Whop Pixel and Meta Pixel measure page views and successful funnel conversions. Meta receives leads, associated checkout starts and verified completed purchases; purchase value and currency come from the verified Stripe checkout. Adniqo does not send Meta your email address or other customer identifiers. Meta may receive browser and interaction information for attribution. Whop measures page views and successful funnel conversions, including generated campaigns, and Adniqo may send a submitted email address to Whop for matching with advertising interactions. Neither provider’s optional Pixel or conversion events are sent before you opt in.

We may collect information directly from you, from public pages on a website you ask us to analyse, from Google after you authorise access, and from service providers such as Stripe.

3. Google Account and Google Ads Data

Adniqo requests the Google Ads permission at https://www.googleapis.com/auth/adwords. This permission allows read and write access to Google Ads accounts that you are authorised to access. Google presents the requested access during the OAuth process.

Subject to the permission you grant, Adniqo may use Google Ads information to:

• identify Google Ads customer accounts accessible to you and let you select a non-manager advertising account;
• retrieve account information needed to configure campaigns, including account name, identifier, currency and time zone;
• retrieve location-target information and relevant campaign/account configuration needed to provide the service;
• create campaign budgets and Search campaigns;
• create ad groups, keywords, responsive search ads and supported advertising assets;
• configure locations, language, negative keywords, bidding and other supported campaign settings; and
• retrieve created campaign details to check that the requested configuration was applied.

Campaign actions take place only in the Google Ads account selected and authorised by you. Campaigns created directly by Adniqo are created in a paused state so that they can be reviewed before activation. Adniqo does not claim ownership of your Google Account, Google Ads account or advertising data.

Adniqo accesses Google information only as needed to provide the functionality you request. Google user data is not sold, used for advertising unrelated to providing Adniqo, or transferred to third parties except where necessary to provide the service, comply with law, protect security, or where you authorise the transfer.

Where persistent authorised access is required, Adniqo receives a Google OAuth refresh token. The token is encrypted by the application and stored server-side in the PostgreSQL-backed session associated with your browser. Access tokens are generated and used server-side as needed and are not deliberately stored in browser local storage. OAuth client credentials and developer credentials are held as server-side secrets.

Adniqo’s use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including the Limited Use requirements, where applicable.

4. How we use information

We use information where necessary to provide Adniqo, analyse a submitted website, generate campaign configurations, carry out authorised Google Ads actions, maintain sessions and campaign records, process payments and entitlements, provide support, prevent abuse or fraud, maintain security, diagnose problems, improve reliability and functionality, and meet legal obligations.

We do not currently use Google Ads data to provide performance reporting, nor do we use it to train advertising systems unrelated to your use of Adniqo.

5. Legal bases under UK data protection law

Where UK data protection law applies, our legal basis depends on the activity:

• Contract: to provide requested Adniqo functionality, campaign generation, Google Ads connection and paid campaign access.
• Legitimate interests: to secure, operate, troubleshoot and improve the service, prevent abuse, and understand how users reach Adniqo, where those interests are not overridden by your rights.
• Consent: where you choose to connect Google, join a waitlist, or where consent is otherwise legally required. You may withdraw consent, although this does not affect earlier lawful processing.
• Legal obligation: where processing is necessary to comply with applicable law, taxation, accounting, court orders or regulatory requirements.

6. How we share information

We do not sell personal information. We may share limited information with service providers acting for us, including:

• Google: authentication and Google Ads account operations requested by you.
• Stripe: checkout and payment processing. Stripe handles card details under its own privacy terms.
• Whop: optional advertising measurement and attribution through the Whop Pixel, only after you allow optional tracking. See Whop’s Privacy Policy for how Whop handles information.
• Meta: optional advertising measurement and attribution through the Meta Pixel, only after you allow optional tracking. The Pixel receives no email address or other customer identifiers from Adniqo. See Meta’s Privacy Policy for how Meta handles information.
• SendGrid: delivery of waitlist confirmation email where that service is enabled.
• Replit and PostgreSQL infrastructure: hosting the application, application secrets and server-side data storage.
• Google Fonts and jsDelivr: delivery of fonts and interface assets, which may involve your browser making requests to those providers.

We may also disclose information where required by law, to protect rights or security, in connection with a business reorganisation, or with your direction or consent.

7. International transfers

Some providers may process information outside the United Kingdom. Where data protection law requires it, we use or rely on recognised transfer mechanisms and safeguards provided by the relevant service provider, such as adequacy regulations or approved contractual protections.

8. Data storage and security

Adniqo uses server-side sessions and PostgreSQL storage for campaign, waitlist, payment-status and session information. We take reasonable technical and organisational measures designed to protect information, including HTTPS in production, server-side secret management, restricted application access to credentials, secure and HTTP-only session cookies, and application encryption of stored Google refresh tokens.

No online service can guarantee absolute security. You should protect access to your device, browser session and Google Account and notify us if you believe your connection has been compromised.

9. Data retention

We retain information for as long as reasonably necessary to provide the service, maintain security, resolve disputes, meet legal or accounting requirements and enforce agreements. Retention periods may differ by data type.

Adniqo does not currently publish fixed deletion periods for campaign, waitlist, payment-status or server-side session records. Google connection credentials should be removed or invalidated when a connection is permanently disconnected or related data is deleted, subject to legitimate legal and security needs.

10. Disconnecting Google Ads, deletion and your rights

Disconnecting Google Ads

Where the Google Ads connection screen is available, you can use Adniqo’s disconnect control. Adniqo will attempt to revoke the Google OAuth grant and will clear the Google token and selected-account information from your current Adniqo session. Disconnecting does not delete campaigns already created in your Google Ads account. You can also review or remove Adniqo’s access through your Google Account connections.

Deletion requests

Adniqo does not currently provide self-service account or data deletion. You may request access, correction or deletion through the support or contact method made available within the Adniqo service. A dedicated public privacy email is not currently published, so we do not list an unverified address here.

Your data protection rights

Depending on where you live and the applicable law, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, and withdraw consent. You may also complain to the UK Information Commissioner’s Office or another competent supervisory authority. These rights may be subject to legal exceptions.

11. Cookies and similar technologies

Adniqo uses an essential session cookie to maintain the website-analysis and campaign journey, protect forms, retain selected settings and support Google OAuth. In production it is configured as Secure and HttpOnly. Because OAuth may return from another site, it is configured with SameSite=None.

Optional advertising tracking is off by default. If you choose “Allow optional tracking”, we load the Whop and Meta Pixels to measure visits and successful funnel conversions. Meta receives leads, associated checkout starts and verified completed purchases; a purchase event includes only the actual amount paid and its currency, and Adniqo does not send Meta an email address or other customer identifiers. Meta may receive browser and interaction information for attribution. Whop continues to measure leads, generated campaigns, checkout starts and completed purchases; a submitted email address may be sent to Whop for matching with advertising interactions. Choosing “Only necessary” keeps both Pixels and their conversion events off.

We store your tracking preference in your browser’s local storage so you do not have to choose again on every page. You can change or withdraw permission using “Cookie preferences” at the bottom of website pages. Withdrawing permission reloads the page without the Whop or Meta Pixel; it does not undo events sent while permission was granted. If browser storage is unavailable, a choice applies to the current page and you may be asked again on your next visit.

Separately, Adniqo records basic referral and UTM attribution information and may maintain standard application logs for operation and security.

12. Children

Adniqo is intended for business and professional use. It is not directed to children, and users must have legal capacity to enter into an agreement and authority to manage the advertising account they connect.

13. Changes to this policy

We may update this policy to reflect changes to Adniqo, our providers or legal requirements. The “Last updated” date identifies the latest revision. Where appropriate, we will provide additional notice of material changes.

14. Contact

For privacy questions or requests, use the support or contact method made available within Adniqo. No verified public support email, legal entity name or postal address is currently published in the application, so this policy does not invent those details.