Integrations
The read-only data connectors we build and operate for client engagements, so the reporting tools and internal assistants we deliver can answer questions from a client’s own live data. This page explains what those connectors do, and what they never do.
Where a platform’s API distinguishes read from write access, we request read-only scopes.
Each connector serves one client and one named purpose, never a shared product.
What this is
Agreeable Data is a data and AI engineering consultancy. When a client engages us to build reporting tools or an internal assistant, those tools need the client’s own numbers to be useful. So we connect a small set of the client’s data sources (a spreadsheet here, an advertising platform’s API there) and the tools answer from live data instead of stale exports.
Every connector is built for one named purpose. A connector exists to do one specific job for one specific client, such as refreshing a tracking spreadsheet or reporting on ad-campaign performance, and its access is scoped as narrowly as the platform allows. When the engagement ends, the access ends with it.
What the connectors do
Each integration is purpose-built for one client engagement. These two shapes cover most of what we build.
Spreadsheets
A client’s team already lives in a tracking spreadsheet. A connector reads the source systems on a schedule and refreshes that spreadsheet, so the numbers stay current without anyone copy-pasting.
Advertising
A connector reads campaign performance from an advertising platform’s API — spend, impressions, clicks, conversions — so the client’s reporting reflects what actually ran.
What it is not
The boundaries matter as much as the features.
A connector never creates, edits, or deletes anything in a connected account. Where a platform’s API distinguishes read from write access, we request read-only scopes.
There is no signup page and no self-serve app. Each integration is built and operated by Agreeable Data for one specific client engagement.
Data a connector reads is used only for the engagement it was built for. It is not resold, shared with other clients, or reused anywhere else.
The client grants access to a named Agreeable Data account or service identity through the platform’s own permission model, and can revoke it there at any time.
Access is always granted by the client, never taken. The client authorizes a named Agreeable Data account or service identity using the platform’s own consent and permission model, typically an OAuth grant or a role the client provisions. Credentials are stored per engagement and are not shared across clients, and the client can revoke them from their own account at any time.
Use of any data a connector reads is governed by our Privacy Policy and Terms of Service.
If you’re a client, partner, or platform reviewer with questions about a specific integration, contact us at info@agreeabledata.com.