Privacy

Google user data we access

When you sign in with Google at /signin, we request only what we need to sign you in and draft that email:

• Basic Google account identity (OpenID, email, and profile): your name, email, and profile image when Google provides them, kept in the session cookie so we can keep you signed in. The app shows your email. We do not keep a separate profile database.
• Google Search Console, read-only, via the webmasters.readonly scope (https://www.googleapis.com/auth/webmasters.readonly): the Search Console properties your account can open. For a site you attach, when you open its draft, we read Search Analytics for that site (queries, pages, clicks, impressions, CTR, and average position).

We call the Search Console API to list properties, and the Search Analytics API to build a draft. We do not request write access. We do not read Gmail, Drive, or other Google products besides Google Ads, if you connect it.

Google Ads data (AdsWeekly)

If you connect Google Ads at /ads, we ask Google for the adwords scope (https://www.googleapis.com/auth/adwords). That is the only scope Google offers for the Google Ads API, and Google treats it as able to make changes. We only read reporting data and never change your campaigns. Our code calls only Google Ads reporting (search) requests. It never creates, edits, pauses, or deletes anything, and never touches billing or users.

What we read, for the accounts you choose:

• Account name, currency, and the list of client accounts your manager account can open.
• Weekly totals: spend, clicks, impressions, conversions, cost per conversion, and click-through rate, for last week and the week before.
• The top campaigns by spend for those weeks, with the same numbers.
• Local Services Ads leads as counts only: lead type, status (for example booked or declined), whether the lead was charged, and when it came in. We never request lead contact details (names, phone numbers, emails, or messages), so we don’t receive or store them.

Why: only to draft the Monday client note that you review and send yourself from your own mailbox. We never email your clients.

How long we keep it: Google Ads numbers are fetched each time a draft is built and discarded once the page is built. We don’t keep a history of your Ads data. Your Google Ads access and refresh tokens are kept encrypted in an httpOnly session cookie and are deleted when you disconnect or after 30 days of no use.

Revoking access: choose Disconnect Google Ads at /ads, or remove ClientWeekly at myaccount.google.com/permissions. Either one stops new Google Ads calls.

ClientWeekly’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We don’t sell Google Ads data, use it for advertising, share it with data brokers, or use it to train AI models. People at ClientWeekly don’t read it, except with your permission for support, for security, or where the law requires.

Why we access it

We use Search Console data only to draft a weekly client status email that you review and send from your own mailbox. That is the product. We do not email your clients. We do not change, delete, or write any Search Console data. Your Google account email is also used to keep you signed in, to tie attached sites to your account, and, if you send feedback, to store and forward that message.

How long we keep tokens and data

What we keep from Search Console: the addresses of the Search Console properties you attach, and, when Google sends it, the permission level for each one. Those are stored only in a signed cookie in your browser for up to 180 days. Signing out does not clear that cookie. Detaching a site or clearing cookies removes it. That cookie also records when you attached each site. We don’t keep your Search Console numbers (clicks, impressions, CTR, position, queries, or pages). We fetch them from Google each time you open a draft and discard them once the page is built.

If you save a default for a client, the client name, greeting, and sign-off you chose are stored in a separate signed cookie in your browser named cw.prefs, for up to 180 days. That cookie does not include the site address, the draft, Search Console numbers, the searches people typed, or page addresses. It isn’t on our servers or in a database. Signing out doesn’t clear it. Detaching a site, choosing Clear saved defaults, or clearing your browser cookies removes it.

• Your session expires 30 days after you sign in, or when you sign out. Google access and refresh tokens live in that encrypted session cookie so we can read Search Analytics when you preview a draft. We do not keep a copy of those tokens on our servers.
• Signing out removes the session cookie from your browser but does not revoke the access you granted Google. To revoke it, remove ClientWeekly at myaccount.google.com/permissions.
• Because we don’t store Search Console responses or Google tokens on our servers, signing out removes the session cookie, and revoking access at Google stops new Search Console calls. Feedback that includes your Google account email is kept separately, as described below.
• Search Analytics is fetched on demand to build a draft. We do not keep a long-term warehouse of your Search Console history.
• If you join the waitlist, we store the email you submit, an optional site-count range, which button you used (waitlist vs founding), and whether the form was in the hero or the footer, so we can offer a seat. We do not run a marketing drip.
• Feedback and waitlist entries are kept for up to 24 months unless you ask us to delete them sooner. Email jake@clientweekly.com and we’ll delete them within 30 days.

Security

All traffic uses HTTPS. Google tokens are kept only in an httpOnly session cookie encrypted with a server-side secret. The attached-sites cookie and the cw.prefs cookie are signed so they can’t be altered. Both stay in your browser. We don’t keep a copy of them on our servers.

What we don’t do

• We don’t sell Google user data or client data.
• We don’t use client data or Google user data to train machine learning models.
• We don’t email your clients.
• We don’t modify Search Console data.
• We don’t change your Google Ads campaigns, budgets, or billing.
• We don’t use Google user data for advertising, and we don’t share it with data brokers.

ClientWeekly’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who else sees data

We don’t sell Google user data. We share it with Google only to authenticate you and to call Search Console and Google Ads on your behalf. Service providers process data only to run ClientWeekly. Vercel hosts the app, so Search Console responses pass through its servers in memory to build your draft. Vercel Web Analytics counts page views on our public pages only, not inside the app. If you send in-app feedback, we store your Google account email, the category you pick, your message, and any context you type in our feedback database (Supabase), and email it to jake@clientweekly.com through Resend. If you join the waitlist, we store your sign-up in Supabase and email a sign-up notice to our team through Resend. Stripe handles card payments. Card details never touch our servers, and we don’t send Stripe your Google data.

Your choices

• Sign out to remove the session cookie from this browser. That does not revoke the access you granted Google, and it does not clear attached sites or a client default saved in this browser.
• Revoke ClientWeekly under your Google Account permissions.
• Email jake@clientweekly.com to ask us to delete feedback or waitlist entries. We’ll delete them within 30 days.

Contact

ClientWeekly · https://www.clientweekly.com (https://clientweekly.com). Privacy questions: jake@clientweekly.com.