Adgentiz Copilot

Privacy Policy

Last updated: 18 September 2026

This policy explains what personal data Adgentiz Copilot (“the Service”) collects, why it is collected, who it is shared with, where it is held and what rights you have over it. It applies to the Service at copilot.adgentiz.com and to the accounts of people invited to use it.

The Service is operated by Adgentiz (“we”, “us”). For any question about this policy or to exercise a right described below, contact privacy@adgentiz.com.

1. What the Service is

Adgentiz Copilot is a business tool used by advertising professionals to plan, authorise and record advertising activity. It is not aimed at consumers, and it is not used to build profiles of individuals or to target advertising at the people who use it. Access is by invitation only.

2. Personal data we collect

2.1 Account data

When an administrator provisions your account and you sign in, we hold: your email address, your display name, the role assigned to you in a workspace, a stable identifier issued by the authentication provider, and the time of your most recent sign-in. If you sign in with Google, we receive your email address and name from Google; we do not receive or store your Google password.

If you sign in with an email address and password, the password is handled by our authentication provider and is never stored by us in a form we can read.

2.2 Records of your activity in the Service

The Service exists to keep an accurate record of who authorised what. When you use it we record: the missions and success contracts you create or amend, the decisions you approve or reject together with your stated reason, the operations that result, and the receipts and platform responses returned. Each of these records identifies you as the person who acted.

These records form an append-only audit trail. Individual audit entries are not edited or deleted in the ordinary course of operating the Service, because their purpose is to evidence accountability for advertising spend. See section 6 on retention and section 7 on how this interacts with your rights.

2.3 Technical data

Our hosting and database providers process standard technical information needed to serve requests and keep the Service secure, such as IP address, browser user agent and request timestamps. Our application logs record the route requested, a response status, a duration and a correlation identifier; they are configured to redact credentials.

2.4 What we do not collect

We do not use advertising or analytics cookies, we do not run third-party trackers on the Service, and we do not sell personal data. We do not attempt to identify or profile you beyond what is described above.

3. Advertising data

When connected to an advertising platform such as Google Ads, the Service reads and writes campaign configuration and delivery statistics for the advertiser account your organisation has authorised. That information concerns advertising campaigns, not the individuals who see the advertising, and the Service does not receive audience lists or personal data about people who view or click an advertisement.

4. Why we process your data, and on what basis

  • To provide the Service — to authenticate you, show you your organisation’s work and act on your instructions. This is necessary to perform our agreement with your organisation.
  • To keep an accountable record — to evidence who authorised each change to advertising spend. We rely on our legitimate interest, and that of your organisation, in being able to demonstrate control over financial commitments.
  • To keep the Service secure and working — to detect misuse, diagnose faults and prevent duplicate or unauthorised changes. This is our legitimate interest in operating a reliable service.

5. Who we share data with

We use the following providers, who process data on our behalf under their own terms and security commitments. We do not share your personal data with anyone else, and we do not sell it.

  • Vercel — application hosting and delivery.
  • Supabase — database, file storage and authentication.
  • Google — sign-in with Google, where you choose it, and the Google Ads API where your organisation has connected an advertiser account.
  • Leanr — generation of advertising creative, where that integration is enabled for your organisation. Creative briefs sent to Leanr describe the advertising, not the people using the Service.

We may also disclose data where we are required to by law, or where necessary to establish or defend a legal claim.

6. Where data is held, and for how long

Application data is stored in Singapore (Supabase, region ap-southeast-1), and the application runs in the same region. Some providers may process limited technical data, such as request routing information, in other locations as part of operating a global network.

During the pilot, account records are kept for as long as your account is active. Records of advertising activity and the associated audit trail are retained for the duration of the pilot engagement and for as long as needed afterwards to evidence the advertising spend they describe. A formal retention schedule is being agreed with participating organisations as part of the pilot; if you would like to know the current position for your organisation, contact us at the address above.

When an account is withdrawn, access is revoked immediately. The person’s past actions remain in the audit trail, for the reasons given in section 2.2.

7. Your rights

Depending on where you live, you may have the right to access the personal data we hold about you, to have inaccurate data corrected, to request deletion, to object to or restrict certain processing, and to receive your data in a portable form. You may also complain to your local data protection authority.

To exercise any of these, contact privacy@adgentiz.com. We will respond within the period required by the law that applies to you.

One limit is worth stating plainly: we may be unable to delete individual entries from the audit trail described in section 2.2, because those records evidence financial authorisations made on behalf of an organisation. Where that applies we will tell you, explain why, and delete or anonymise everything we are able to.

Much of the data in the Service is held by us on behalf of the organisation that invited you. Where that is the case, we will direct a request to that organisation and support them in answering it.

8. Security

Data is encrypted in transit. Access is invitation-only: a verified Google or email identity does not by itself grant access to any workspace, and every account must be provisioned by an administrator. Credentials are held in managed secret storage, are never placed in our source code, and are redacted from logs. Every change to advertising spend requires an explicit human authorisation bound to the exact action approved.

No service can promise perfect security. If a breach affects your personal data we will notify you and the relevant authority where the law requires it.

9. Cookies

The Service sets cookies that are strictly necessary to keep you signed in and to protect the session. It does not set advertising, analytics or cross-site tracking cookies. Blocking the necessary cookies will prevent you from signing in.

10. Children

The Service is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16.

11. Changes to this policy

If we change this policy we will update the date at the top of the page. Where a change materially affects how we handle your personal data, we will tell account holders directly.

12. Contact

Adgentiz — privacy@adgentiz.com

See also our Terms of Service.