Privacy Policy

Outcomesy OÜ, registry code 17093201, Sepapaja tn 6, Lasnamäe linnaosa, 15551 Tallinn, Harju maakond, Estonia. Contact for privacy matters: support@outcomesy.com.

• Account data: email address, login credentials (passwords are hashed; we never see them in plain text).
• Waitlist / contact data: email address and, for consultation requests, the website and message you submit.
• Customer Data from connections and uploads: advertising performance and configuration records from connected Meta and Google accounts (including copies of your ads’ images and text), and order and product records from connected Shopify stores (e.g. spend, revenue, orders and product names). It also includes what you write in the service: recorded changes and their verdicts, proposals, and Brand Brain notes. Optional store exports can supply historical store data; advertising spreadsheets are not accepted. These are business records of the brand you operate; provide or authorise access only to data you are authorised to process.
• Usage and technical data: basic logs needed to run and secure the service (timestamps, request metadata, error logs).
• Bot-protection data: our public forms use Cloudflare Turnstile, which processes technical browser signals to distinguish humans from bots.

• Providing the service you request — recording advertising changes, measuring and grading recorded changes, and supplying store-first figures for briefings and reports (performance of contract).
• Managing the waitlist and responding to consultation requests (legitimate interest / pre-contractual steps).
• Securing the service against abuse (legitimate interest).
• Communicating service messages such as invites and account emails (performance of contract / legitimate interest).
• We do not sell personal data and do not use your Customer Data for advertising.

Where a processing feature uses Google’s Gemini API, relevant Customer Data is processed by Google acting as our processor. Recommendation generation is switched off; this does not remove the disclosure for retained processing paths. Data sent to that API uses a paid tier, and we rely on Google’s published terms for that tier, which state that submitted data is not used to train Google’s models. That is a commitment we depend on rather than one we can enforce ourselves. What is in our own control: we do not use your data to train any model of ours, outputs are generated for your workspace only, and we do not pool your data across customers.

AI assistants you connect yourself. Outcomesy offers a connector (MCP) that you can add to an AI assistant you use, such as Claude by Anthropic. When you do, the assistant reads the workspace data you ask it to read, signed in as you and limited to the workspaces you can see. That data then goes to the assistant’s provider under your own agreement with that provider; the provider is not our sub-processor, and we send it nothing unless you ask your assistant to read it. Through the connector an assistant may propose a record, which counts for nothing until you apply it in Outcomesy; it cannot apply, edit or delete a record, and it cannot change your advertising or store accounts. You can remove the connector in your assistant’s settings at any time.

When you connect your Shopify store, Outcomesy reads order and product data via Shopify's Admin API to generate aggregate analytics. Customer personal fields (name, email, phone, address) are never queried or stored. The queried non-personal order payloads and order-line records are retained to reconcile refunds and edits, alongside derived daily aggregates. Uninstalling the app ends our access at once; when Shopify sends its redact request 48 hours later, we delete the store’s data and our copy of the access token. GDPR data-request and redact webhooks are implemented.

We use a small set of infrastructure providers to run the service:

Some providers may process data outside the EEA; where they do, we rely on appropriate safeguards such as EU Standard Contractual Clauses as implemented by those providers.

• Account and Customer Data: retained while your account is active. Deleting a workspace removes its data, stored ad images and access tokens at once. Deleting your account keeps a 7-day window in which you can undo it; after that everything is permanently deleted, except billing records we must keep for legal reasons. Routine infrastructure backups held by our hosting provider are overwritten on the provider’s own schedule.
• Waitlist data: retained until the beta programme ends or you ask us to remove you.
• Logs: retained for a short rolling window for security and debugging.

You may request access to, correction of, deletion of, or a portable copy of your personal data, object to or restrict certain processing, and withdraw consent where processing is based on consent. Write to support@outcomesy.com. You may also lodge a complaint with a supervisory authority — in Estonia, the Data Protection Inspectorate (Andmekaitse Inspektsioon), or the authority in your country of residence.

The service uses only cookies and local storage strictly necessary to operate (such as keeping you signed in). We do not currently use advertising or third-party analytics cookies. If we introduce analytics (e.g. Google Analytics), this policy will be updated and a consent banner added first.

Data is encrypted in transit; access is scoped per workspace with row-level security; public forms are protected against automated abuse. No system is perfectly secure — if we become aware of a breach affecting your data, we will notify you as required by law.

Requests from public authorities: if a public authority asks us for personal data, we check that the request is lawful and challenge it if it is not, disclose only the minimum the law requires, and keep a record of each request, our response and the legal basis. Where the law allows, we tell the affected customer first.

The service is for business use and not directed at anyone under 18.

When you connect a Google Ads account, Outcomesy requests a single OAuth scope — https://www.googleapis.com/auth/adwords — and nothing wider. We use it to read aggregate performance figures for the advertising accounts you select: campaign and ad group names and settings (such as budgets and bidding), spend, impressions, clicks, conversions and conversion value, conversion action settings, network, device and product splits, product feed status, asset performance and search terms. Search terms are summed per term and are not linked to any person.

We do not retrieve or store end-consumer personal data from your advertising accounts: no customer match lists, no audience membership, no contact details, no advertising identifiers, no cross-app or cross-site browsing data.

We never use advertising data to train a model. Data obtained through the Google Ads API is used solely to provide your workspace's advertising records, measurements and figures. We do not use it to train, fine-tune, retrain or otherwise improve any machine-learning model of ours; we do not pool it with other customers’ data for model development; and we do not sell, license or share it for advertising purposes. Where it is processed by Google’s Gemini API through a retained processing feature, we rely on Google’s paid-tier terms, which state that submitted data is not used to train Google’s models.

Access and refresh tokens are held encrypted in a dedicated secret store, are never exposed to the browser, and are deleted when you disconnect. Disconnecting Google Ads affects only that connection — your Shopify store connection is unaffected. Deletion routes and timelines are documented on our data deletion page.

When you connect a Meta ad account, Outcomesy asks for the ads_read permission and uses Facebook Login only to identify who is connecting. We read the ad accounts you select: campaign and ad names, statuses and budgets; spend, impressions, clicks, adds to cart, purchases and purchase value; copies of your ads’ images and text; and spend split by age band, gender, placement and region, summed across many people.

We do not retrieve or store data about individual people from your Meta accounts: no custom audiences, no customer lists, no contact details, no identifiers. We never create, edit or delete anything in your ad account.

We never use Meta data to train a model. Meta Platform Data is used solely to provide your workspace’s records, measurements and figures; it is not sold, licensed or shared for advertising, and not pooled with other customers’ data. Tokens are held encrypted in a dedicated secret store and deleted when you disconnect or delete the workspace. You can also remove Outcomesy in your Facebook settings; Meta then notifies us, and we revoke the connection and delete its access token at once. Meta figures already in your workspace are deleted when you delete the workspace or ask us to, as described on our data deletion page.

We will post updates here and, for material changes, notify you before they take effect.