How we handle your data

What we can see

When you choose Continue with Google, we ask to see only what we need to sign you in and draft that email:

• Your name and email address, so we can sign you in. The app shows your email. If Google also sends a profile photo, it stays in the sign-in cookie with your name. We don’t keep a separate profile database.
• Read-only Search Console data for the sites you pick (up to 5). We can see the sites your Google account can open. When you open a draft, we read that site’s clicks, how often it showed up in Google, how often people clicked, the average position, the searches people typed, and the pages they opened, for the latest week and the week before. We can’t change anything in your account.

What we can’t do

• We can’t read your Gmail, and we can’t send mail from your Gmail account.
• "Open in Gmail" only opens a new message in your own Gmail, with the draft already filled in, when you click it. You review it and you send it. We never send it.
• We can’t change, add, or delete anything in Search Console.
• We never email your clients.
• We don’t use your data to train an AI model.

What we keep and for how long

• Your sign-in lasts 30 days after you sign in, or until you sign out. Google’s permission to read Search Console lives in that encrypted cookie in your browser. We don’t keep a copy of it on our servers.
• The sites you attach are listed in a separate cookie in your browser for up to 180 days. That list is the site addresses you picked, the access level Google includes when it sends one, and the day you attached each site. Signing out does not clear this cookie. Detaching a site removes it. Clearing your browser cookies removes it. It is not saved in a database on our servers.
• If you check “Save as default for this client” on a draft, the client name, greeting, and sign-off you chose are stored in a cookie named cw.prefs in your browser, for up to 180 days. It is tied to that site, and it does not store the site address. It holds only those three pieces of wording. It does not include 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 the site, choosing Clear saved defaults, or clearing your browser cookies removes it.
• We never save your clients’ Search Console numbers. Each draft is pulled fresh from Google when you open it, built in memory, and discarded after the page is shown. Nothing is written to a database. We don’t send those numbers to an AI service.
• If you send feedback or join the waitlist, we keep that for up to 24 months, unless you ask us to delete it sooner. Email jake@clientweekly.com and we’ll delete it within 30 days.

Who else touches your data

We don’t sell your data.

• Google, to sign you in and to read Search Console when you open a draft.
• Vercel hosts ClientWeekly. Search Console numbers pass through its servers in memory while a draft is built, then they’re discarded. Vercel counts page views on our public pages only, not inside the signed-in app.
• Stripe handles card payments if you buy a seat. Card details go to Stripe. They never touch our servers, and we don’t send Stripe your Google data.
• Supabase stores feedback and waitlist sign-ups. Resend emails those messages to jake@clientweekly.com. Your Search Console numbers are not sent to Supabase or Resend.

How to revoke access

1. Open myaccount.google.com/permissions.
2. Find ClientWeekly in the list of apps.
3. Choose Remove access.

That stops ClientWeekly from reading Search Console. Also sign out of ClientWeekly. In the app, use Sign out in the header. Signing out removes the sign-in cookie from this browser. It does not, by itself, remove the permission you gave Google, and it does not clear the list of sites saved in this browser or a client name, greeting, and sign-off you saved for those sites.

Who’s behind it

ClientWeekly is built by Jake, the founder. Questions: jake@clientweekly.com.