1. Information we collect
Account information. Your email address, the way you signed up (domain preview, file upload, recorder script or Google sign-in), the company domain inferred from your email, your plan, and timestamps of sign-up and activity.
Google Ads account data. When you install the recorder script, upload an export, or connect read-only through Google sign-in, we read and store account metadata, campaign settings, keywords, search terms, placements, network and conversion metrics, conversion action definitions, change history (who or what changed what, and when), auction insight metrics, and recommendation auto-apply settings. The recorder script only ever reads; the complete list of queries it runs is published on our website and inside the script itself. We do not collect personally identifiable information about the people who clicked your ads.
Uploaded files. Exports you upload from the Google Ads interface are stored, parsed into the same record, and the raw files are deleted thirty (30) days after processing.
Usage data. Standard server logs: request timestamps, IP address, browser and device type.
Website analytics. This website loads Google Tag Manager, which we use to understand which pages people read and where they arrive from. It sets cookies in your browser and sends Google the address of the page you are on, your approximate location, and your browser and device type. We deliberately keep identifiers out of page addresses, so a link that carries a sign-in or recorder token has that token removed from the address bar before any tag runs; none of it reaches Google. Analytics never sees the contents of a report you upload or any finding produced from it. You can block it with any content blocker and every part of this site will work as normal.
2. How we use information
- To operate and secure the Service and to keep your account's record;
- To produce findings for you;
- To send transactional email: sign-in links, recorder status, alerts, and service notices;
- To respond to your questions and requests;
- To improve the Service, fix defects and prevent abuse;
- With your opt-in, to build de-identified cross-account patterns as described in section 4;
- To comply with law and enforce our agreements.
3. Legal basis (EEA and UK users)
We process your information to perform our contract with you, for our legitimate interests in operating, securing and improving the Service where those are not overridden by your rights, to comply with legal obligations, and with your consent where we ask for it.
4. We do not pool your account with anyone else's
Every finding you see is computed from your own data alone. We do not currently build cross-account patterns, benchmarks or industry aggregates of any kind, and nothing about your account contributes to another customer's findings.
One thing is shared, and it is not your data. When we classify a public string, such as a YouTube video title, a website domain or an app name, we keep the label we gave that string so the same title does not have to be classified again for every customer whose report contains it. The string is public and the label describes it, not you. Search queries are treated differently, because a query is something a member of the public typed and can contain their personal details: we store only a one-way hash of the query alongside its label, never the query itself.
If we ever build cross-account patterns, it will be opt-in, this policy will say so before it happens, and we will ask you.
5. How we share information
We do not sell your personal information or your account data. We share information only as follows:
Service providers. Amazon Web Services (hosting and storage, United States), Amazon SES (transactional email), and Amazon Bedrock. Each processes information on our behalf under contract.
What goes to Amazon Bedrock, and why. To tell a placement that fits your audience from one that does not, and to tell a search for your brand from a search for a competitor, we send short strings from your report to a Claude model running on Amazon Bedrock inside our own AWS account: placement titles, channel names, domains, app names, and the text of search queries. Nothing else goes with them, no identifier of you or your account travels with the request, and the model returns only a fixed set of classification labels. Bedrock may route the request to any of three United States regions (Oregon, Northern Virginia, Ohio); it never leaves the United States. The model is not trained on what we send.
Aggregated and de-identified data. We may publish or share aggregate information that cannot reasonably be used to identify you or your organisation, such as quarterly reports on what automation did across many accounts.
Legal requirements and business transfers. We may disclose information when required by law or legal process, to protect rights and safety, or as part of a merger, acquisition or sale of assets, in which case we will notify you.
6. Data retention
We keep the record and as little else as we can. Your account's record (daily facts, change events, settings snapshots, findings and the dashboards built from an upload) is kept for up to seven hundred and sixty (760) days, which is longer than the longest plan's memory, and is then deleted automatically. Everything that is only an input to that record goes sooner: a raw uploaded file is deleted thirty (30) days after it arrives, and the raw payload a recorder run sends is deleted after fourteen (14) days, by which time the facts have been extracted from it. Each of these is an automatic rule on our storage, not a promise someone has to remember to keep. Account information is kept while your account exists and for a reasonable period afterwards to meet legal obligations. You can ask us to erase everything at any time by emailing team@attrisight.com: that removes your uploads, findings, dashboards, recorder tokens and the daily record of any account you recorded, and it cannot be undone.
7. Your rights and choices
Depending on where you live, you may have the right to access, correct, delete, port, restrict or object to the processing of your personal information. Email team@attrisight.com and we will respond within the time the law requires. To stop the recorder, delete the script from your Google Ads account; to stop read-only access, revoke it in your Google Account settings. Either action stops new data immediately.
8. Security
Data is encrypted in transit and at rest, access is limited and logged, and the recorder script is designed so that it cannot modify your account. No system is perfectly secure; keep your sign-in credentials and recorder token private.
9. International transfers
We are based in the United States and store data there. If you use the Service from elsewhere, your information is transferred to and processed in the United States, which may have different data protection laws from your country.
10. Children
The Service is for business use and not directed to anyone under 18. We do not knowingly collect information from minors.
11. Changes to this policy
If we make a material change we will post the updated policy here with a new effective date and, where practical, tell you by email. Continued use after the effective date means you accept the change.
12. Contact
Questions or requests: team@attrisight.com.