Short version
We collect nothing from visitors. No accounts, no forms, no advertising
cookies, no tracking pixels. Our advertising software touches only our own
Google Ads account, reads only campaign and spend figures, stores those
figures privately, and shares them with nobody.
Information we collect from visitors
None. This site presents no forms, no newsletter signup, no
account creation and no comment fields. We do not ask for your name, email
address, phone number or payment details, and we have no way to receive them.
We set no advertising cookies and install no tracking pixels or analytics
scripts. Our hosting provider keeps standard technical access logs (IP address,
timestamp, requested page, user agent) for up to 30 days for security and
reliability, after which they are reduced to aggregate counts. We do not use
those logs to build profiles and do not combine them with any other source.
When you click through to a vendor
Review pages link to the vendor's own site, and those links carry a
parameter that tells the vendor's affiliate network the visit came from
dbgpicks. That is how the commission described in our
advertising disclosure is attributed.
Once you leave dbgpicks, the vendor's and the network's own privacy policies
apply, not ours. We do not control them.
The affiliate network reports transactions back to us. We deliberately
discard the buyer's personal fields — name, email address, postal address, city,
postcode and similar — before anything is written to our records. We keep only
the transaction identifier, the amount and the status, which is all we need to
reconcile payments. We never receive your payment details at any point.
Google user data
dbgpicks operates its own advertising through Google Ads, managed by our own
internal software. This section describes exactly what that software does with
Google data, as required by Google's API policies.
Whose data
The software accesses one Google account: our own, being the
Google Ads account operated by DBG IT. Access is granted by the account owner
through Google's OAuth consent flow. The software has no access to any visitor's
Google account, and no third party grants it access to theirs. We do not offer
this software to anyone else.
What it accesses and why
- Reads campaign status, delivery figures and advertising
spend, to keep spending inside a fixed budget and to stop campaigns that are
not working.
- Writes campaign creation, budget changes and pauses, to
run and stop our own advertising.
It accesses no other Google service and requests no scope beyond what the
above requires.
How it is stored
Spend and performance figures are stored in a private database on hardware
controlled by DBG IT, used solely to reconcile advertising cost against
affiliate revenue. OAuth credentials are held as secrets outside of version
control and are never written to logs, reports or published pages.
How it is shared
It is not. Google user data obtained through the Google Ads
API is not sold, rented, transferred to third parties, used to train models, or
used for advertising to anyone. It does not leave our own systems. It is used
only for the budget control and reconciliation described above.
Retention and revocation
Aggregate spend figures are retained for accounting purposes. The account
owner can revoke the software's access at any time from the Google Account
permissions page, which immediately ends all further access.
Children
This site is not directed at children and we knowingly collect no data from
anyone, including children.
Your rights
Because we hold no personal data about visitors, there is normally nothing to
access, correct or delete. If you believe we hold something about you, write to
contato@dbgit.com and we will look and
tell you what we find, including if the answer is nothing.
Changes to this policy
If this policy changes we update the date at the top of this page. Material
changes will be described here rather than made silently.
Contact
DBG IT — Brazil.
contato@dbgit.com