Data, handled
with purpose.

Three different environments

The company website explains our services. Our private reporting workflow supports authorized analysis. The direct Google Ads application is being developed for reporting and authorized management. These environments have different access and processing arrangements.

The current reporting path

1. An authorized source

   A reporting request uses the read-only reporting bridge, or an authorized person supplies a Google Ads export. The requested accounts, dates and fields define the task.

2. A restricted working copy

   Source material is stored in restricted DSS working files for validation, reconciliation and analysis. A saved report remains account information; removing a name or substituting an identifier does not necessarily make it anonymous.

3. Selected reporting records

   Validated data may be entered manually into a private reporting database. It can include selected account-level facts as well as curated aggregate results. Access is scoped to the relevant client and advertiser.

4. A private report

   Authenticated internal reports read approved database outputs. Raw source files and source credentials are kept out of the public website. Any client-facing sharing needs its own appropriate access arrangement.

This is a manual workflow. The direct API service will have a separate source and permission review before its outputs can enter that reporting path.

Service providers in the workflow

The following providers are relevant to the current setup or the specifically described integration. They do not all receive the same data. Exact processing depends on the service used and the authorized task; this is not a claim that every provider has access to every account.

Google Ads and Google Cloud

The advertising system of record and the API/identity configuration for the developing integration. Cloud project creation alone does not mean an account is connected or that an execution workload is hosted.

Google Workspace

Business email and correspondence, including information a person chooses to include in an enquiry.

Supermetrics

The current reporting bridge for authorized Google Ads queries. Its use is separate from the planned direct API execution service.

Neon

Private storage of selected reporting facts and aggregate publications used by the reporting workflow.

Vercel

Hosting for this public informational website and, in a separate project, authenticated internal reporting. Private report hosting can process permitted advertiser reporting data; this public site does not.

OpenAI and Anthropic

AI assistance through tools such as Codex and Claude, and specifically authorized analysis services. Relevant prompts, report extracts, query text or drafts may be processed where that use is authorized. Provider retention and product settings matter; see AI processing.

Public research may use other tools without supplying advertiser records. Adding a provider that will receive account-related data requires review of its role, the relevant terms and any necessary notice and authorization before that disclosure.

Protection and separation

The existing reporting design uses restricted local files, account-scope validation, database access restrictions and authenticated internal reports. Credentials and raw working files are excluded from public releases. The public website has no Google Ads credentials, execution interface or reporting-database connection.

Preparation for the direct service includes separate reporting and execution identities, verified effective permissions and controls on permitted work. Those controls must be implemented and checked before production use. A descriptive page does not enforce them.

No system can eliminate every security risk. Please report a suspected exposure using the contact details in the privacy policy, giving enough context to investigate without sending passwords, tokens or unnecessary personal information.

Retention, withdrawal and deletion

Reports and working records can be retained for the engagement, historical comparisons, reconciliation, security and applicable record-keeping obligations. Retention is based on the purpose and type of record; we do not promise that every copy expires on one universal date.

Stopping account access and deleting retained data are different actions. Removing a Google Ads grant or manager link affects the relevant future access route. It does not automatically delete a previously saved report, undo campaign changes or remove data held under a provider's own retention rules.

Ask DSS to identify the applicable access paths and to return, correct or delete information within its control. The retention and request sections explain the process and limitations.