Privacy Policy

Last updated: 19 September 2026 · Effective: 19 September 2026

This policy explains what data the Vested Systems platform collects, why we collect it, who we share it with, how long we keep it, and how it is deleted. It covers data obtained from Google APIs in detail in section 4.

1. Who we are and who this covers

Vested Systems operates a hosted software platform on which an organisation's staff ask questions about that organisation's own business data and receive answers, reports and summaries produced by AI agents.

The platform is sold to organisations under contract; there is no public self-service sign-up. If you use Vested Systems through your employer or client, that organisation administers the account, chooses which external systems are connected, and controls who within the organisation may see what. In data-protection terms that organisation is the controller of the business data it brings, and Vested Systems is its processor. Vested Systems is the controller of the account and operational data described in section 2.

2. What data we collect

We collect only the categories below. We do not buy personal data, we do not operate advertising, and we do not run tracking or advertising cookies on this site.

2.1 Account and identity data

• Name and work email address of each user in an organisation.
• Organisation and department membership, and the role that determines what a user may access.
• Authentication records: sign-in times and session tokens.
• Where an administrator connects a Google account, the Google account's email address and basic profile, obtained from the openid, email and profile scopes, shown so an administrator can tell which account is connected.

2.2 Connection credentials

• OAuth refresh and access tokens, or API keys, for the external systems an administrator has connected.
• The identifier of the specific resource selected for that connection — for example the single Google Analytics property the organisation chose to report on.

2.3 Business data from connected systems

• Records read from a connected system in order to answer a question. For Google Analytics this is aggregated reporting data — sessions, users, channels, events, revenue, product and search-term performance — and never individual end-user identities.
• Structural metadata about connected systems, such as available properties, report dimensions and currency and timezone settings, used to build valid queries.

2.4 Conversations and generated content

• The questions users ask, the answers produced, and any reports, files or charts generated from them.

2.5 Operational and security data

• Application and audit logs: which user invoked which agent or tool, when, against which connection, and whether it succeeded or was refused.
• Technical diagnostics such as error traces and performance timings.
• IP address and user agent of requests, used for security and abuse investigation.

3. How and why we use it

Purpose	Data used
Authenticate users and enforce who may see what	2.1
Connect to an external system on the organisation's instruction	2.2
Answer a question the user asked, and build the requested report	2.2, 2.3, 2.4
Show an administrator which accounts and properties are connected	2.1, 2.2
Keep an audit trail of access to connected systems	2.5
Diagnose faults, maintain reliability, investigate abuse	2.5
Bill the organisation and meet legal obligations	2.1, 2.5

We do not use any of this data for advertising, we do not sell or rent it, and we do not profile individuals.

4. Google user data — what we access and why

If an administrator connects a Google account, Vested Systems requests read-only access to the specific Google products that organisation wants its agents to report on. Each scope and its exact use:

Scope	What we read	Why
analytics.readonly	The list of Google Analytics properties the connected account can access; the currency and timezone of the chosen property; and report data from the Analytics Data API.	So an administrator can pick which property this workspace reports on, and so users can ask for traffic, channel, e-commerce, product and search-term reports about their own property.
adwords	Campaign, ad group and keyword performance from the Google Ads API.	To answer questions about advertising performance. Read-only use; we never create, modify or pause campaigns and never spend on your behalf.
content	Product and listing data from Merchant Center.	To report which products are disapproved or missing attributes. We never submit or modify products or feeds.
webmasters.readonly	Search performance data from Search Console — queries, pages, impressions, clicks, position.	To answer questions about organic search performance. The read-only scope is used deliberately: we never submit sitemaps or change property settings.

We request no write scope for any Google product, and nothing in your Google account is created, changed or deleted by Vested Systems. Access is requested only for the products your organisation enables, and offline access is requested so scheduled reports can run when you are not signed in.

Concretely, this means data obtained through Google APIs is used only to provide and improve the user-facing features your organisation enabled; is never sold or transferred for advertising, credit-scoring or any similar purpose; is never used to develop, improve or train generalised artificial intelligence or machine learning models; and is accessed by our staff only where you have asked us for support, where required for security, or where the law requires it.

5. Processing by AI model providers

Producing an answer generally requires sending the relevant excerpt of your data — the part needed to answer the specific question asked — to a third-party large language model provider, which processes it and returns the answer. This happens only in response to a request from a user in your organisation.

We use such providers under business terms that prohibit them from using submitted data to train their models, and we configure their APIs accordingly. Providers act as our sub-processors; the current list is available to customer administrators on request. We do not send connection credentials to model providers.

6. Who we share data with

• AI model providers — as described in section 5.
• Infrastructure providers — the hosting, storage and network providers on which the platform runs.
• Your own organisation — administrators can see audit records of who used which connection.
• Legal and safety — where required by law, or to investigate abuse and protect the service and its users.

We do not sell personal information, and we do not share it with advertisers or data brokers. We do not transfer Google user data to any third party except as set out above.

7. Retention and deletion

• Connection credentials — held until the connection is removed. Disconnecting an account deletes the stored credential immediately and stops all further access at that moment.
• Business data and conversations — retained while the organisation's account is active, so users can revisit past answers.
• Operational and audit logs — retained on a rolling basis for security and troubleshooting, then discarded.
• On termination — when an organisation leaves, its data is deactivated immediately and permanently deleted after a retention window of 30 days, which exists so an accidental termination can be reversed.

You can revoke Vested Systems' access to your Google account at any time, independently of us, at Google account permissions. Revoking there stops all further access immediately.

8. Security

• Traffic is encrypted in transit with TLS.
• Credentials for connected systems are encrypted at rest. When a credential is passed to a connector to make a call, it is additionally encrypted specifically for that organisation and that connection, so a credential cannot be read in another organisation's context.
• Each organisation's data is isolated from every other organisation's at the database level as well as in the application.
• Every use of a connected system is recorded in an audit trail.
• Administrative access to production is restricted to named personnel.

9. Your choices and rights

Depending on where you live you may have the right to access, correct, export, restrict or delete your personal data, and to object to certain processing. Because your organisation controls its account and the data within it, please direct such requests to your organisation's administrator; if you contact us directly we will refer the request to them and support them in answering it.

The platform is not intended for children and is not offered to consumers.

10. Contact

Questions about this policy, about what we hold, or about a data request: [email protected].

If we make a significant change to this policy we will update the date at the top and notify organisation administrators.