Privacy policy

In short

• datty is a small program that runs on your own computer. Your AI app (for example Claude Desktop) starts it there.
• datty is read-only. It never creates, changes, pauses or deletes ads, campaigns, budgets or orders.
• There is no datty server and no datty database. The datty team does not receive your logins, tokens or account data.
• datty runs on your computer and does not send your account data or tokens to datty-operated servers. Results you ask for are shared with the AI assistant you choose (for example Claude or ChatGPT) and are subject to its policies.
• The only thing this website asks you for is the beta list form: your email and, if you want, a connector name, stored by our website host Netlify (see Beta list).
• You can remove datty at any time: delete its files on your computer and remove its access at Google, Meta or Shopify (see Remove datty and your data).

How datty works

datty is a local MCP server (MCP, the Model Context Protocol, is an open standard that lets an AI app use outside tools). It talks to your AI app on your computer only; it opens no network port of its own. The one-time Google login helper, which you run yourself, briefly listens on your own computer (127.0.0.1) for Google's sign-in reply. When you ask a question, datty asks Google Ads, Meta Ads or your Shopify store for the data it needs, calculates the answer with code and gives the result to your AI app.

With the built-in sample data (the default mode), datty opens no network connection at all.

What data datty reads

datty reads only the fields below, and only from the accounts you connect yourself.

Google Ads (Google user data)

datty asks for one permission, the Google Ads scope (https://www.googleapis.com/auth/adwords). Google offers no read-only version of it, so datty limits itself in code: it only runs read-only report queries with Google's search method and has no code that changes anything. It reads:

• Account: customer.id, customer.currency_code, customer.time_zone.
• Spend: campaign.id, campaign.name, campaign.status, segments.date, metrics.cost_micros (cost per campaign and day).

Meta Ads

datty sends only read (GET) requests to three places: your ad account, its campaign list and its insights. It reads:

• Ad account: account_id, currency, timezone_name.
• Campaigns: id, name, status.
• Insights: spend per campaign and day (with campaign_id, campaign_name) and per day for the whole ad account, with date_start, date_stop, account_id and account_currency.

Shopify

datty refuses to work with a Shopify app that has any write permission; it needs only read_orders. It reads:

• Shop: currency and time zone.
• Orders: id, created time, cancelled time, test flag, currency, order total and refunded total (in the shop currency).

datty does not read customer names, emails, phone numbers or addresses, ad texts, keywords, search terms, audiences, customer lists or billing details.

On your computer

datty reads the settings your AI app starts it with and the login files you name there: a Google token file and OAuth client file, a Meta token file and a Shopify credentials file (only the ones you set up).

How datty uses it

Only to answer the question you ask: totals, spend per campaign, change against the previous period and revenue against spend (ROAS). Every result says which account, dates, currency and time zone it used.

datty does not use this data for advertising of any kind, does not sell it, does not give it to data brokers or information resellers, does not use it to judge credit or for lending, does not build databases from it and does not use it to train AI or machine learning models.

Who receives it

• Google, Meta and Shopify receive datty's read requests and your login for that platform, because the requests go to them. When it answers questions, datty contacts only these hosts: accounts.google.com and googleads.googleapis.com (Google Ads), graph.facebook.com (Meta Ads) and your own store's myshopify.com address (Shopify). The one-time Google login helper also opens Google's sign-in page in your browser and sends the sign-in code to the token address named in your OAuth client file (in files downloaded from Google, oauth2.googleapis.com).
• Your AI app and its provider receive the results you ask for, as part of your chat (for example Anthropic for Claude, OpenAI for ChatGPT). Their policies decide how they keep and use your chats. Many AI apps let you turn off model training in their settings.
• Nobody else. The datty team receives nothing: no telemetry, no analytics and no crash reports are sent.

What is kept, where and for how long

• Ad and order data: not saved to disk by datty. It is held in the computer's memory only while datty answers your question.
• Account details in memory: while datty is running, it keeps each account's id, currency and time zone in memory so it does not ask again for every question. They are gone when your AI app stops datty.
• Short-lived access tokens: in memory only (for Shopify, a token that lasts up to 24 hours), never written to disk.
• Login files: on your computer, in a folder you choose (we suggest ~/.config/datty). On macOS and Linux, datty refuses a Google token file, Meta token file or Shopify credentials file that other users of the computer can read. It refuses Meta and Shopify files inside a git folder and never writes the Google token file into one. The Google OAuth client file is not checked by datty: keep it private yourself. datty does not encrypt these files; use your computer's disk encryption.
• Status file: ~/.config/datty/status.json on your computer, with the newest 20 error kinds only (time, mode, platform, kind), no account ids, names or amounts. You can switch it off.
• Logs: datty writes error kinds and masked account ids (for example ******7890) to its log, which your AI app may save in its own log files on your computer.
• Chats: results stay in your AI app until you delete them there.

How it is protected

• Read-only by design, checked by automated tests in datty's build checks: only Google's search method for Google Ads, only three read paths with GET for Meta, only two named read queries for Shopify.
• Connections to Google, Meta and Shopify use TLS. For Meta and Shopify, datty always checks the server certificate and never turns the check off.
• Text from your accounts, such as campaign names, is passed to your AI app as data and labelled as not being instructions.
• The support report (python -m datty.doctor) hides tokens, secrets, home folder paths and full account ids. We never ask you to send us a token or login file.

Remove datty and your data

Because datty keeps nothing on our side, there is nothing for us to delete. To remove everything on your side:

1. Remove datty from your AI app's settings (in Claude Desktop, its entry in claude_desktop_config.json) and restart the app.
2. Delete datty's login files and its status file, or the whole datty folder. A running datty stops using a deleted login file at the next question.
3. Google: remove datty's access in your Google Account at myaccount.google.com/permissions (Google's help page). After that, a copy of the old login cannot be used.
4. Meta: delete the token file. Meta documents an API call to make a system user token unusable at once (Meta's system user page).
5. Shopify: delete the credentials file, then in the Shopify Dev Dashboard rotate the app's client secret and revoke the old one (Shopify's page).
6. Delete chats that contain datty results in your AI app, if you want them gone.

Removing access (at Google, Meta, Shopify) and deleting files are separate steps: do both. Questions: hello@datty.ai.

Google API Services User Data Policy

datty's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

datty uses Google user data only to give you the answers described above. It moves results to another app only when you ask, and only to the AI app you run datty in.

This website

This website has no analytics, no cookies, no ads and no third-party code. It is hosted by Netlify, which serves the pages at https://datty.ai. Like any web host, Netlify receives the technical details your browser sends when it loads a page (for example your IP address and browser type); what Netlify records and for how long is set by Netlify's own policies, which we have not reviewed in detail yet.

Beta list

• What we collect: the email address you type in the beta list form and, if you fill it in, the connector you ask for. Netlify Forms receives and stores the entry for us. Netlify may store technical details with it, such as your IP address and browser type.
• Why: only to tell you when datty opens and to see which connectors people want. We do not sell it, and we do not add you to other mailing lists.
• Spam checks: Netlify checks each entry for spam with Akismet before it reaches us. A hidden field also catches automated sign-ups; an entry that fills it is rejected by Netlify and does not reach us.
• Who sees it: the datty team, in Netlify's dashboard and in notification emails Netlify sends us about new entries.
• How long: until you ask us to remove it, or until we stop running the beta list, whichever comes first. Netlify's documentation does not state a fixed retention period of its own.
• Remove it: write to hello@datty.ai from the same address and we delete your entry in Netlify.

Children

datty is a tool for businesses and is not meant for children.

Changes to this policy

When datty starts reading, using, keeping or sharing data in a new way, we update this page and the date at the top before the change takes effect, and tell the people using datty that we know of, for example through the release notes.

Who runs datty

datty is run by ESS & LABS LLC, a Florida limited liability company. Address: 2164 Platinum Rd, Ste C, Apopka, FL 32703, United States. ESS & LABS LLC uses the name datty for this product; datty is not registered as a fictitious name yet.

Contact

Questions or requests about privacy: hello@datty.ai. Please never send us your token, login or credentials files.