Draft · not yet reviewed by an attorney

Privacy policy

Effective date: to be set at launch

Who we are

Keeplight is an AI operations service for small marketing teams, run by Bryce Walls in Orange County, California. This policy covers keeplight.ai, its booking chat, the support chat on the support page and the team welcome page. The client portal has its own privacy notice, and so does Keeplight Lantern. Questions go to bryce@keeplight.ai.

At a glance

This is our notice at collection: what we collect on this site, why, and how long we keep it.

Contact details

Your work email and name.

Why: to book your call and follow up. Kept: up to 12 months if we don't start a project.

Booking details

The call time, whether it was rescheduled, cancelled or went ahead, your time zone, and, if you use it, your answers in the AI audit chat in your trial portal and a short summary of them.

Why: to prepare for the call. Kept: up to 12 months if we don't start a project.

Public research on your business

What your company publishes about itself (its website, team page, own social accounts, reviews and news), and a pre-call brief about your business for Bryce.

Why: to prepare for the call. Kept: up to 12 months if we don't start a project.

How you found us

Campaign tags in the link you followed, the click ID a Google or Meta ad adds to it, the page you landed on, or the site that linked to us.

Why: to know which ads and channels bring good fits. Kept: with your booking details.

Support chat

What you type in the support chat on our support page. If it passes your question to Bryce: your email, your name if you give it, and the conversation.

Why: to answer your question and let Bryce reply. Kept: not saved unless it goes to Bryce; then up to 12 months if we don't start a project.

Device details

Your IP address and browser, seen by the services that deliver the page.

Why: to load the page and keep it secure. Kept: we don't store them ourselves, apart from a scrambled daily code for the support chat's limits, deleted after two days.

We don't sell your personal information, and we don't collect sensitive personal information. The one thing we may send an advertising company is a Google ad's click ID with whether you booked, so we can tell which ads work (see Measuring our ads).

What we collect

When you only browse, we store nothing on our side. This site has no analytics, advertising pixels or tracking cookies. To remember how you found us while you look around, the page keeps those campaign details in your browser's session storage, which is not a cookie, is never sent to us unless you enter your email, and is cleared when you close the tab. We are also testing two versions of the booking chat (one asks for your email first, the other shows open times first), so your browser's local storage keeps a note of which version you see. The note holds no identifier, is saved with your booking details only if you enter your email, and you can clear it with your browser's site data.

Measuring our ads

If you came from a Google ad and then book a call or become a client, we may upload that ad's click ID to Google Ads with the outcome (for example "call booked"), its time and its value, so Google can report which ads led to calls. We send no name, email or answers. We don't send anything to Meta: a Meta click ID is only used inside Keeplight to count which ads bring calls. If your browser sends Global Privacy Control, or you ask us by email, we leave you out of these uploads.

How we use it

Only to schedule your call, prepare for it, and follow up about working together. If you enter your email but don't finish booking, we may send you one follow-up email about the call. We don't add you to a marketing list.

The booking chat and the AI audit chat

The booking chat is an automated assistant, not a person. It follows a set script, and nothing you type in it goes to an AI provider.

After you book, your trial portal offers an optional AI audit chat. It is an AI assistant, not a person, and it says so before you start. It runs on Claude, an AI model made by Anthropic: what you type in that chat is sent to Anthropic to produce its replies and a summary for Bryce, and is saved with your booking. You can skip any question or stop anytime. Please don't share client or customer personal data, passwords, or health or financial details; the chat leaves out messages that look like ID, card or account numbers or passwords.

The support chat

Our support page at keeplight.ai/support has an AI support chat. It is an AI assistant, not a person, and it says so at the top of the chat. It runs on Claude, an AI model made by Anthropic: Keeplight sends what you type, and the earlier messages in that conversation, to Anthropic to get its answers. It answers from the support page and the policies it links to.

We don't save the conversation while you chat; your browser keeps it until you leave the page. To stop the chat being misused, we count messages per visitor per day under a scrambled code made from your IP address and a key that changes every day, and delete the counts and the key after two days, so the code can't be traced back to you after that. When the chat can't answer a question, we keep the question, reworded without names, email addresses or numbers, so we can add the answer to the support page, and delete it after 12 months.

When the chat can't answer, or you ask for Bryce, it asks for your email and tells you that sending it passes the conversation to Bryce. Only if you send your email do we keep the conversation, your email, your name if you give it, and a short summary Claude writes for Bryce. Bryce gets them by email and replies to you there. We save them with your booking details (or start a record for your email if we don't have one) and delete them on the same schedule, within 12 months if we don't start a project. Please don't share passwords, card numbers or other sensitive details in the chat; messages that look like them are left out and never sent to Anthropic.

Preparing for your call

Once you book, we look up public information about your business so Bryce comes to the call prepared. An AI tool, Claude Code by Anthropic, runs on Keeplight's own computer and searches the web for what your company publishes about itself: its website, its own team or about page, the business's own social accounts and recent posts, reviews, the tools visible on its website, and news from the last two years. To start, it gets your email's domain if it's a business address (not a personal one like gmail.com), your company website if you gave it in the AI audit chat, and your booking notes with your name, email address and phone number taken out. It never uses LinkedIn, personal social profiles, or people-search or data-broker sites, and it doesn't look up anyone beyond the names and roles your company lists on its own team page.

Claude, by Anthropic, also writes Bryce a short pre-call brief: a snapshot of your company, the workflows that look worth automating, the plan that might fit, and questions to ask. It's written from your call time, your time zone, your email's domain, the page or campaign that brought you here, your booking notes and, if you used it, your AI audit chat answers and transcript. Your name, email address and phone number are taken out before any of this goes to Claude. Bryce gets the brief and the research in one email the morning of your call. Only Keeplight sees them, and they're saved with your booking and deleted on the same schedule.

Team welcome page

If your company works with Keeplight, your team lead may send you an invite link, or ask Keeplight to email it to you (the portal privacy notice covers those invites). Our old welcome page now forwards that link to the client portal's sign-in. Your company's name, your team lead's name and your company code are written into the link after the # sign, which browsers never send to our servers; the portal reads them in your browser only, to greet you and show your company code.

Who processes it for us

These companies handle information for us as service providers, only to provide their service:

How long we keep it

We keep booking details, your trial portal login, your AI audit chat, and the pre-call research and brief while we're talking about working together, and delete them within 12 months if we don't start a project. If we do start one, your details move to your client account and the portal privacy notice applies. Ask us anytime and we'll delete them sooner.

Support chat conversations you send to Bryce are kept on the same schedule. Questions the chat couldn't answer, kept without names, email addresses or numbers, are deleted after 12 months, and the support chat's daily counts after two days.

Your privacy rights

Wherever you live, you can ask us to:

Email bryce@keeplight.ai from the address you gave us, or tell us how to reach you if you no longer use it. We'll confirm we got your request within 10 business days and answer within 45 days. We may ask you to confirm details to make sure the request is really from you. You can have someone act for you if they show us your written permission. We'll never treat you differently for using these rights.

California residents have these rights under the California Consumer Privacy Act. We don't sell personal information or use sensitive personal information. You can opt out of the Google Ads uploads described in Measuring our ads by emailing us or by turning on Global Privacy Control.

Do Not Track and Global Privacy Control

We don't track visitors across sites. If your browser sends Global Privacy Control, we save that with your booking and treat it as a request not to sell or share your information: you're left out of the Google Ads uploads described in Measuring our ads. Do Not Track signals don't change how this site works.

Security

Everything travels over HTTPS. Booking details are stored with Google Firebase, and our security rules stop visitors from reading any saved booking, including their own.

Children

Keeplight is for businesses. We don't knowingly collect information from anyone under 16.

Changes

If this policy changes, we'll update the effective date above and note what changed.