Production prepared · Google OAuth verified. Commercial access pending.
Data Studio Connect

Private pilot · Updated

Pilot privacy policy

Controller and scope

Owner: César Mínguez. Tax identification: ES50205318K. Professional address provided: Plaza Parroquia 18, 28025, Madrid. Contact: cesar@datastudioconnect.com. Service brand: Data Studio Connect. Domain: datastudioconnect.com.

This document describes a private connector pilot. It does not advertise a finished commercial service. The owner manages user accounts and enquiries; processing on behalf of future customers requires a defined data processing agreement before commercial onboarding.

Data we use

Registration: name, email, organisation, hashed password and memberships. Operation: sessions, authorisations, selected accounts, query references, security events and contact requests.

Meta Ads and Instagram Insights: encrypted OAuth tokens, expiry, authorised account identifiers and names, and available advertising, professional-profile, organic-content and audience statistics. Meta Ads requests ads_read; Instagram uses the read permissions for profiles, insights and linked pages required by its flow. No ads are created, no content is published and no personal data from lead forms is requested.

Stripe processes Checkout and subscriptions. The backend retains the identifiers and statuses needed to validate licences; it does not store full card numbers. Stripe LIVE infrastructure is configured, but public subscriptions remain blocked on the server until each connector’s external checks are complete. QA uses Stripe test mode and does not verify real charges.

Purposes and legal bases

We use account data to provide the requested pilot and manage the service relationship; preliminary enquiries are handled as pre-contractual steps. Security and the prevention of unauthorised access serve our interest in protecting users and systems, through proportionate checks. Records subject to legal obligations are retained according to their purpose.

OAuth authorisation enables technical read access to the selected accounts; it does not replace the obligations of the account holder or the legal basis for all processing. Report content is not used for our own advertising or for automated decisions about individuals.

Google user data: access, use and recipients

The Meta Ads and Instagram Insights connectors request only https://www.googleapis.com/auth/script.external_request from Google, to make HTTPS requests from Apps Script to our backend. They do not request permission to read Gmail, Drive, Contacts or the contents of other Google reports, and do not use Google sign-in to obtain your profile or email. SaaS registration details are provided directly on our website.

Google provides Apps Script execution and the Google Data Studio (Looker Studio) destination. Apps Script user properties retain the Data Studio Connect access and refresh tokens issued for that user, their expiry and, during OAuth initiation, the state and PKCE verifier. These are credentials for our SaaS, not Meta tokens or permission to read other Google services. They are used solely to authenticate connector requests.

To retrieve the requested report, Apps Script sends the SaaS access credential, selected connection and account, requested fields, dates, filters and query options over HTTPS to Data Studio Connect, hosted by Clouding (CLOUDI NEXTGEN, S.L.). Our backend uses and stores authorisation and configuration references and processes queries only to check identity, organisation, permissions and licence, query the official Meta API and return the authorised result. Temporary result caching is encrypted and isolated by organisation. We do not receive your Google password or a token granting access to Gmail or Drive.

Google receives the configuration, schema and requested Meta Ads or Instagram rows to display them in your Looker Studio data source and report. These rows may include account, campaign or content identifiers and names and their metrics; they originate from Meta, not Gmail or Drive. Google processes them in its services. If you share a source or report, its recipients depend on the permissions you configure in Google. Sharing does not by itself grant access to another organisation in our backend.

We do not sell or disclose Google user data for advertising, commercial profiling, data brokerage or training general-purpose AI models. Data and credentials from this connector flow are not sent to Stripe, the Meta pixel, Meta Conversions API, Google Analytics or TikTok. Meta API requests use Meta authorisation and necessary report parameters, not Google account credentials or content. Only the owner’s authorised personnel may access records necessary for support or security, with limited access; disclosure to authorities requires a valid obligation and review of legality and data minimisation.

Optional website measurement is a separate processing activity described in Cookies and security. For the owner’s internal dashboard, our backend also queries aggregate visitor and page statistics from our own GA4 property through a read-only service account; it does not query customers’ GA4 properties or connect their Google accounts. These results are processed in Clouding and shown only to the authorised administrator.

Providers and data flows

Clouding (CLOUDI NEXTGEN, S.L.) hosts our backend, database, cache, backups and mail server. It processes necessary account and operational data and the query data described in this policy to provide hosting and technical support. Clouding has confirmed that storage and backups remain in Spain. This does not guarantee Spanish residency for Google or other providers’ services.

Google provides Apps Script and Looker Studio for the flow detailed in the Google user data section. It also provides Gmail: messages you send to support are forwarded to the owner’s Gmail, so Google processes the address, subject, text and attachments you include to receive and answer them. Connector rows and credentials are not automatically sent to this mailbox; do not email passwords or tokens.

Meta provides the source APIs for Meta Ads and Instagram Insights and receives its own authorisation and the parameters needed to query assets you authorise. Stripe receives the customer and billing data necessary for Checkout, subscriptions and payments, including email and tax details provided during the process, but does not receive report rows, Meta tokens or Google connector credentials. Optional measurement recipients and their data categories are described separately in Cookies and security.

Google and other providers operate global infrastructure and may process data outside the European Economic Area under the terms and safeguards applicable to each service. We do not claim that all data remains exclusively in the EU or provide an unconfirmed list of remote-access countries. Outstanding contractual and country clarifications and platform approvals remain requirements before extending the pilot to external customers.

Retention

Pilot retention settings: one-day sessions; 30-day audit records; 14-day contact requests and completed jobs. The recently verified cache expires after 300 seconds. Cleanup runs periodically; it is not instantaneous physical deletion at the exact second of expiry.

The account is retained while in use or until its deletion is processed, separating records retained for security or legal obligations. Email verification expires after 24 hours and password recovery links after 30 minutes. Transactional messages remain encrypted in the queue until delivery or closure, after which their content is deleted. Their records are retained for up to 7 days and expired tokens are periodically purged. Encrypted backups and isolated restores have been checked; we do not advertise an external backup service or guaranteed recovery time.

Disconnection and rights

You can disconnect Meta from the dashboard: the local token is deleted, the cache is invalidated and pending jobs are cancelled. Remote revocation can be requested; if Meta does not confirm it, the service indicates this. Cancelling a subscription is not the same as completely deleting an account.

You may request access, rectification, erasure, restriction, objection and portability, where applicable, by writing to the owner’s contact address. Identity will be checked proportionately. You may lodge a complaint with the AEPD. Complete user deletion is handled manually; self-service deletion is not yet offered.

Google connector retention and withdrawal of access

The SaaS credentials in Apps Script user properties remain until connector authorisation is reset or they are deleted; they may be refreshed while authorisation remains valid. Resetting authentication first requests backend revocation and, once confirmed, deletes credentials and OAuth state from those properties. On a network or server failure it retains local credentials so revocation can be retried and reports the error; you can also ask support to invalidate server access. Backend sessions, audits, jobs and cache follow the retention and cleanup periods described in this policy.

You can withdraw authorisation in Google and request revocation or deletion of SaaS account references and data at cesar@datastudioconnect.com. Disconnecting a connector or deleting SaaS data does not automatically remove sources or reports saved in Google. Manage and, where appropriate, delete them in Google; their retention and that of Apps Script properties are subject to user controls and Google’s policies.

Cookies and security

We use necessary cookies for sessions, organisation selection and security, as well as technical cookies to remember your preferences. With your optional, separate consent, Google Analytics 4 measures visits and navigation on public pages and the Meta pixel measures advertising. Their tags remain blocked until you accept them. You can reject, configure or withdraw consent using the Cookies button. See /en/cookies for providers, purposes and retention periods. We do not send connected-account data or form fields as measurement parameters. The optional analytics cookie dsc_ga_session stores the session identifier obtained through gtag.get for 30 minutes to preserve attribution from the website to checkout after signing in. It is created only with analytics consent and removed on withdrawal; it contains no user or organisation identifiers.

We apply HTTPS, token and cache encryption, server-side organisation and licence authorisation, email verification and password recovery through single-use links. Changing a password invalidates earlier authorisations. Our own MFA is not yet available, and we do not claim security or GDPR certification for the service.

With analytics consent, commerce measurement through Google Analytics 4 Measurement Protocol may record checkout starts, purchases, renewals and refunds confirmed by Stripe. With advertising consent, Meta Conversions API may receive those operations, with refunds represented by a custom Refund event. Each channel is activated only when configured and authorised: financial events are not sent from both browser and server. Transmitted data consists of pseudonymous GA4 or _fbp/_fbc identifiers, opaque event/transaction identifiers and connector, currency, amount and VAT data. We do not send email, IP address, internal user/organisation identifiers, connected-account data or credentials. The signed-in user’s choice is recorded in the backend; context is encrypted, expires with consent (at most 180 days) and is removed on expiry. Event and delivery records default to 30 days with configurable retention. Withdrawal blocks future submissions and pending renewals without reversing data already processed. TikTok is prepared for later integration but is not active and receives no data. Only with advertising consent, we retain the browser’s real technical User-Agent string, obtained from the request header, in encrypted form. Meta Conversions API receives it only for website-originated checkout starts and the initial purchase. System-generated renewals, refunds and adjustments omit it, and our server does not send this field to GA4. It is neither fabricated nor derived from personal information. It expires with the consented context after at most 180 days and is removed when advertising consent is withdrawn; email, IP address, names and internal user or organisation identifiers are not sent.

The technical dsc_commerce_revoke cookie is HttpOnly and allows withdrawal of server measurement categories even after signing out. It only permits reducing permissions: it cannot grant them or read account data. Pseudonymous Google or Meta identifiers are encrypted and expire with consent, after at most 180 days. Minimal Checkout attribution and cumulative refund state are retained to link renewals and prevent duplicates while a subscription remains active or consent remains valid. They are purged once both purposes have ended and 180 days have elapsed since the last attribution activity; this period can be configured shorter. They contain no provider credentials and are not sent to the platforms. Event and delivery records keep their separate default retention of 30 days.