Privacy Policy
Last updated: 26 October 2026
Houndtool is a tool for working with Google Ads accounts. This page explains what Houndtool stores about you, why, and how to get it removed. Houndtool is responsible for this data. Questions or requests: sondre@houndtool.app.
Signing in
You sign in with Google. Houndtool never sees your password. Google tells Houndtool your email address, your profile picture and gives it a key (a token) to work with Google Ads, Google Sheets and the Google Drive files you pick, on your behalf. Only approved email addresses can sign in.
Your browser keeps you signed in with cookies for up to 30 days, or until you log out. The key in the cookie is encrypted. See the cookie page for details.
What Houndtool stores
- Your user record: email address, profile picture link and when you last signed in.
- Your saved login (only if you turn it on): an encrypted copy of your Google key, so a job can run after you close the page. Logging out keeps it; turn it off on the Connections page to delete it.
- Your connections (only if you create them): an encrypted Google key with Google Ads access only, its name, your Google email, its status and when it was last used.
- Shares: who you shared a connection with, their access level and the end date.
- The connection log: who did what through a connection – for example which account a report ran on, the report query, a user email that was invited or removed – and whether it worked. Changes you make with your own login are logged too.
- Saved lists: lists of account ids you save under Lists. Background jobs save the accounts they created as a list too.
- Background jobs (only if you run one): for each row the account name, currency, time zone, payment resource and the emails to invite, plus the result – the new account id, whether billing, budget and invites worked, Google's error message and how long each step took. Only you can see your jobs.
- Feature access: which release channel you are on (production, beta or alpha) and any features an admin switched on or off for you. Changes are logged.
Keys are encrypted with server secrets and are never sent to your browser. Apart from background jobs (above), Houndtool does not store your Google Ads data, report results or the contents of your sheets – those are fetched from Google when you use a tool and shown in your browser.
Some preferences (favorites, recent reports, panel settings) are saved only in your browser. They are listed on the cookie page.
Sharing a connection
If you share a connection, the person you share it with acts as your Google user in Google Ads. Their changes show under your name in Google Ads' change history. You can see everything they do through it in the log, and they can see their own actions. Your email address is shown to them. You can change or end a share at any time on the Connections page.
How long we keep it
- Saved login, connections, shares and lists: until you delete them, or ask us to.
- Your user record: as long as you have access to Houndtool, or until you ask us to delete it.
- The connection log: kept so owners can see what happened. We plan to delete entries older than 12 months automatically; until then, ask us and we delete them.
Why we use your data
Only to run Houndtool for you: to sign you in, to carry out what you ask for in Google Ads and Google Sheets, and to show owners what happened through their shared connections. We do not sell your data, use it for advertising or share it with anyone except the services below. Use of Google data follows the Google API Services User Data Policy, including the Limited Use rules.
Your rights
You can ask to see the data Houndtool has about you, have it corrected, get a copy, or have it deleted. Email sondre@houndtool.app. You can also complain to your data protection authority (in Norway: Datatilsynet).
To stop Houndtool using your Google account at all, remove Houndtool on your Google connections page. That also ends your saved login and all your connections.
Services we use
These services run parts of Houndtool. They only process data as needed to do that.
Neon
Database
Region: Frankfurt, Germany (EU)
Data: user records, encrypted keys (saved logins and connections), shares, the connection log, saved lists, background jobs and feature access.
Inngest
Runs background jobs (only when you start one)
Region: eastern United States (Ohio and Virginia) (outside the EU)
Data: the job's random id, a user number (not your email or name), timings, and each step's outcome (statuses and counts), which is encrypted before it leaves Houndtool with a key only Houndtool holds. Error messages sent to Inngest are generic. Your email, Google keys and the contents of the job (account names, emails, payment details) are never sent to Inngest – they stay in the database in the EU and are read by Houndtool's own server.
Sign-in, Google Ads, Google Sheets and Google Drive
Data: your Google account, the Google Ads accounts you work on, the sheets you open or export to, and the Drive files you pick.
Changes
When this policy changes, the date at the top changes too.