Privacy policy
In short
Fortress HQ is an internal tool. It is operated by one marketing agency, for that agency's own staff, to manage advertising and analytics accounts that clients have explicitly granted the agency access to. It is not offered to the public, it has no other users, and it sells nothing and shares nothing.
Who operates this application
Fortress HQ is built and operated by Digitl, a marketing agency based in Niš, Serbia, trading atdigitl.me. Digitl is the sole data controller for everything described here. Questions go toluka@digitl.rs.
What the application does
Digitl manages paid advertising and web analytics for its clients. Doing that well means looking at the same accounts every day: what campaigns spent, whether conversions are still being recorded, whether a tracking container changed overnight, whether organic search traffic moved.
Fortress HQ does that reading automatically. It connects to the Google accounts a client has granted us access to, copies the reporting data into our own database, and produces pacing summaries, alerts and briefings for our team. Where an optimisation is approved by a member of our team, it can also apply that change back to the advertising account.
Google user data we access
We only ever access accounts where the account owner has explicitly added us as a user through Google's own permission screens. We cannot reach any account that has not granted us access, and the owner can remove that access at any time without involving us.
| Scope | What it lets us do | Why we need it |
|---|---|---|
auth/adwords | Read campaign, ad, keyword and search-term structure and performance. Create and modify campaigns, budgets and negative keywords. | Reporting and budget pacing, and applying optimisations our team has reviewed and approved. |
auth/analytics.readonly | Read traffic, key events and landing-page performance from Google Analytics 4. | To check advertising conversions against analytics, so we can tell a tracking failure apart from a genuine drop in demand. |
auth/webmasters.readonly | Read search performance and sitemap status from Google Search Console. | To see organic search performance next to paid, and to spot queries we are paying for that we already rank well on. |
auth/tagmanager.readonly | Read the configuration of Google Tag Manager containers. | To audit measurement setup and detect when a container changed, which is the most common cause of conversion tracking silently breaking. |
We request the narrowest scope that does the job. Where a read-only scope is sufficient, we use the read-only scope.
Limited Use
Fortress HQ's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
How we use the data
- To produce internal reporting, budget pacing and performance alerts for accounts we manage.
- To diagnose measurement problems, such as conversions that stopped recording.
- To prepare the monthly performance report we deliver to the client whose account the data came from.
- To apply advertising changes that a member of our team has explicitly reviewed and confirmed.
What we never do
- We do not sell Google user data, and we never have.
- We do not transfer it to advertising platforms, data brokers, or any third party for advertising, resale or profiling.
- We do not use it to train generalised machine-learning or AI models.
- We do not combine one client's data with another's, or use one client's data to benefit a competitor of theirs.
- We do not allow humans to read the data except where it is necessary to operate the tool for the account owner, to resolve a fault, or where the law requires it.
- We do not access any account we have not been explicitly granted access to.
Artificial intelligence
The tool uses a large language model to draft written summaries of the data it has already collected. All figures are calculated by our own code before the model sees anything, and the model is used to describe them, never to compute them. Data sent for this purpose is not used to train the model. No automated action is taken on an advertising account without a member of our team confirming it first.
Storage and security
- Data is stored in a private PostgreSQL database that is not publicly reachable.
- Access credentials and tokens are encrypted at rest with AES-256-GCM, and decrypted only in memory at the moment a request is made.
- Access to the application and its database is restricted to Digitl staff who need it, over authenticated connections.
- Where possible we authenticate using a Google service account, so that no long-lived user credential needs to be held at all.
How long we keep it
Reporting data is retained for as long as we manage the account it came from, plus up to twelve months, so that year-on-year comparison remains possible. When an engagement ends, the account's data is deleted on request immediately, and otherwise within twelve months. Credentials are deleted as soon as an engagement ends.
Sharing
We do not share Google user data with third parties, with two narrow exceptions. The first is the client the data belongs to, who receives it in their own reports. The second is the infrastructure providers that host the database and run the application on our behalf, who process it only on our instructions and never for their own purposes. We disclose data to a public authority only where we are legally compelled to.
Revoking access and requesting deletion
Access can be withdrawn at any time, and you do not need our cooperation to do it. Remove our user or service account in Google Ads, Google Analytics, Search Console or Tag Manager, or revoke the application atmyaccount.google.com/permissions. Access stops immediately.
To have data already collected deleted, emailluka@digitl.rs. We action deletion requests within 30 days and confirm in writing when it is done.
Changes to this policy
If this policy changes materially, the date at the top of this page changes with it. Because the application has no public user base, there is no mailing list to notify; the current version is always the one published here.
Contact
Digitl · Niš, Serbia
luka@digitl.rs