Privacy Policy

Gonnaclick Pte. Ltd.
Last updated: 21 August 2026 · Supersedes the version of 27 March 2026

Gonnaclick Pte. Ltd. (“Gonnaclick”, “we”, “us”) is a company registered in Singapore at 112 Robinson Road #03-01, Robinson 112, Singapore 068902. We operate a programmatic advertising system, marketed under the product brand ClickSage, together with the websites and customer portals at gonnaclick.com and clicksage.ai and their subdomains.

This policy covers two clearly separate kinds of processing. They involve different people, different data and different legal bases, so please read the part that applies to you:

Part A — Our websites and customer accounts

A1. What we collect

CategoryExamplesSource
Business contact detailsName, work e-mail, telephone number, company, job titleYou, when you contact us or open an account
Account dataLogin credentials, role and permissions, activity within the portalYou and your use of the portal
Billing dataInvoicing details, payment records, settlement historyYou and our payment processing
Server logsIP address, user agent, requested URL, timestampAutomatically, when you access our sites

A2. Why, and on what legal basis

A3. Cookies on our websites

Our public websites at gonnaclick.com and clicksage.ai set no cookies and load no third-party analytics or advertising tags. Our authenticated customer portals use strictly necessary cookies and tokens to keep you signed in and to protect against cross-site request forgery. These are exempt from the consent requirement of the ePrivacy Directive.

This is separate from Part B. In our role as an advertising vendor we set no cookies at all — see section B7.

A4. Retention

Account and contact data is kept for the life of the business relationship and for six years afterwards where required for accounting and limitation purposes. Web server logs are kept for up to 30 days.

Part B — Advertising: people who see ads served through our system

B1. Our role, and how we receive your data

We operate a server-side demand-side bidder and an ad exchange. When an app or website you are using has an advertising slot to fill, the publisher or their supply-side platform sends a bid request to our servers describing that opportunity. We decide whether to bid, and if we win we deliver an advertisement and record the outcome.

We have no direct relationship with you. We operate no consumer product, no browser tag and no mobile SDK. Every item of personal data described in this Part reaches us because a supply partner transmitted it to us in a bid request, or because an attribution provider sent us a conversion postback. We are an independent controller of that data, and our supply partners are independent controllers of the data they send us.

B2. What we receive

B3. What we do not receive or hold

We do not process precise geolocation; our systems have no field capable of storing latitude or longitude. We do not process your name, e-mail address, postal address or telephone number. We do not process hashed e-mail addresses or other authentication-derived identifiers. We do not build a cross-device graph and we do not derive probabilistic identifiers by fingerprinting your IP address and user agent. We do not process any special category of data within the meaning of Article 9 GDPR, and our contracts with supply partners prohibit sending it to us.

B4. Purposes and legal bases

PurposeTCF purposeLegal basis
Storing or accessing information on your device, in the form of the advertising identifier transmitted to usPurpose 1Consent
Selecting an advertisement using limited data, and frequency cappingPurpose 2Consent or legitimate interest
Building audience profiles for personalised advertisingPurpose 3Consent only
Using those profiles to select personalised advertisingPurpose 4Consent only
Measuring advertising performance — delivery, clicks, conversions, billing and reconciliationPurpose 7Consent or legitimate interest
Aggregated reporting for advertisers and publishersPurpose 9Consent or legitimate interest
Developing and improving our bidding, pacing and yield modelsPurpose 10Consent or legitimate interest
Detecting invalid traffic and fraud, and fixing errorsSpecial Purpose 1Legitimate interest
Delivering and presenting the advertisementSpecial Purpose 2Legitimate interest
Reading privacy choices and passing them on unaltered to downstream buyersSpecial Purpose 3Legitimate interest

We do not personalise editorial content and do not process data for Purposes 5, 6, 8 or 11. Where we rely on legitimate interest, our assessment and your right to object are set out in our Legitimate Interest Claim.

B5. Privacy signals we honour

The following are enforced in our bidding system before a bid is formed, so a suppressed opportunity produces no record at all. Every check fails closed: if a signal is present but cannot be interpreted, we suppress rather than bid.

SignalWhat we do
Limit Ad Tracking (device.lmt)We do not bid.
Do Not Track (device.dnt)We do not bid.
COPPA flag (regs.coppa)We do not bid. We never bid on child-directed traffic.
GDPR applies, but no TCF consent stringWe do not bid.
TCF consent string without Purpose 1 granted, or undecodableWe do not bid.
US Privacy string asserting opt-out of sale or sharingWe do not bid.

B6. Who we share advertising data with

RecipientWhat they receiveRelationship
Supply-side platforms and publishers whose inventory we buy — including Verve Group Europe GmbH and Smaato, Inc.Our bid response, and the win, impression, click and conversion signals needed to settle the transactionIndependent controllers. Governed by data processing agreements incorporating the EU Standard Contractual Clauses, Module One (controller to controller).
Downstream demand partners — other demand-side platforms, ad networks and advertisers to whom we forward an opportunityThe bid request, with all privacy signals passed through unaltered. Where a device-level restriction is asserted, device identifiers and the user identifier are stripped and location is truncated before we transmit it.Independent controllers, contractually required to provide protection no less protective than we owe our supply partners.
Mobile measurement partners used by our advertisersClick identifiers, so that a later install or conversion can be attributedEngaged by the advertiser; they send us postbacks.
Amazon Web ServicesHosting and storage of all of the aboveProcessor, under the AWS data processing addendum.

We do not sell advertising data to data brokers and we do not license it for any purpose outside the advertising transaction it arose from.

B7. Device storage

In our role as an advertising vendor we set no cookies and use no browser-based storage. We operate no mobile SDK. The only device-derived identifier we use is the advertising identifier that the publisher or supply partner transmits to us. Our full disclosure, in the format required by the IAB Europe Transparency & Consent Framework, is published at /tcf/device-storage.json.

B8. International transfers

We process data in Singapore and in the United States. Personal data originating in the European Economic Area, the United Kingdom or Switzerland is transferred under the European Commission's Standard Contractual Clauses, Module One (controller to controller), as annexed to our agreements with the relevant supply partner, together with the supplementary measures recorded there.

B9. How long we keep it

DataRetention
Raw host logs2 hours to 2 days
Audience segment membership30 days, garbage-collected by day 60
Frequency-capping countersDaily and hourly, expiring with the period
Bid, impression, click and conversion recordsTiered object-storage lifecycle, deleted at 365 days

B10. Your rights, and how to use them

Where the GDPR applies you have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to withdraw consent at any time without affecting the lawfulness of processing carried out beforehand. In practice, the following are the effective routes:

Because we hold no directly identifying data, we cannot find your records from your name or e-mail address. Please include the advertising identifier concerned. Under Article 11 GDPR we are not required to acquire additional information solely to identify you, and we will not ask you for identity documents we have no other reason to hold.

B11. IAB Europe Transparency & Consent Framework

We participate in the IAB Europe Transparency & Consent Framework and abide by its Specifications and Policies. We have applied for registration on the Global Vendor List; our vendor identification number will be published here once assigned. Our device storage disclosure is at /tcf/device-storage.json and our legitimate interest assessment at /legal/legitimate-interest.

Part C — Notice for California residents

This Part is provided under the California Consumer Privacy Act as amended by the CPRA. Terms have the meanings given to them in that Act.

C1. Categories of personal information collected

CCPA categoryWhat we collectSourceBusiness or commercial purposeCategories of third party disclosed to
Identifiers Advertising identifiers (IDFA, GAID), hashed device identifiers, IP address, pseudonymous user identifiers, click identifiers Supply-side platforms and publishers; mobile measurement partners Selecting and delivering advertising, frequency capping, measurement and attribution, billing and reconciliation, fraud detection Demand partners, supply partners, mobile measurement partners, cloud hosting provider
Commercial information Records of advertisements delivered, clicked and converted Generated by our systems Measurement, reporting, billing, model development Advertisers, supply partners, cloud hosting provider
Internet or other electronic network activity information The app or website in which the advertisement appeared, device and browser characteristics, interaction with advertisements Supply-side platforms and publishers Selecting and delivering advertising, measurement, fraud detection, service improvement Demand partners, supply partners, cloud hosting provider
Geolocation data (non-precise only) Country, region and city. We do not collect precise geolocation. Supply-side platforms and publishers, or derived from IP address Campaign targeting and reporting Demand partners, supply partners, cloud hosting provider
Inferences drawn to create a profile Audience segment membership Derived by us from the above Personalised advertising Not disclosed to third parties
Identifiers and professional information relating to customer contacts Name, work e-mail, telephone, company, job title, billing details The individual Account administration, billing, support Payment and accounting providers, cloud hosting provider

We collect no sensitive personal information as defined by the CPRA, and therefore offer no right to limit its use. We do not knowingly collect personal information from anyone under 16; we do not bid on traffic flagged as child-directed and we do not sell or share the personal information of minors.

C2. Selling and sharing

Our participation in programmatic advertising may constitute “selling” or “sharing” personal information for cross-context behavioural advertising as those terms are defined by the CPRA, because we forward advertising opportunities to other demand partners. The categories involved are identifiers, internet activity information and non-precise geolocation.

C3. How to opt out

You may opt out of the sale or sharing of your personal information in any of these ways:

C4. Your other California rights

You have the right to know what personal information we have collected, to delete it, to correct it, and not to be discriminated against for exercising any of these rights. We do not offer financial incentives for personal information. An authorised agent may submit a request on your behalf with written proof of authorisation. Requests go to privacy@gonnaclick.com and are actioned within 45 days, extendable once where permitted.

Security

We apply access control, encryption in transit, network segmentation and least-privilege administrative access. We hold no independent security certification such as ISO 27001 or SOC 2; our infrastructure runs on Amazon Web Services and relies on the certifications AWS holds for that infrastructure. We state this plainly rather than imply a certification we do not have. We notify affected controllers of a personal data breach without undue delay and, where the applicable agreement or law requires it, within 72 hours.

Changes to this policy

We will post any change on this page and update the date at the top. Where a change materially affects how we process advertising data, we will also update our Global Vendor List registration.

Contact

ControllerGonnaclick Pte. Ltd., 112 Robinson Road #03-01, Robinson 112, Singapore 068902
Privacy enquiries and data subject requestsprivacy@gonnaclick.com
Data protection contactFrank Huang, Chief Operating Officer — frank@gonnaclick.com. This is the contact named in our partner data processing agreements; the privacy@ address is monitored by him.
Supervisory authorityDer Hamburgische Beauftragte für Datenschutz und Informationsfreiheit — mailbox@datenschutz.hamburg.de. You may also complain to the authority in your own country of residence or place of work.