Privacy Policy

Last updated: October 17, 2026

The short version

LyteKeepr connects to your Google account only when you choose to connect it. It can read your Gmail messages and your primary Google Calendar, create or delete a meeting in that calendar when you ask it to, and send an email from your Gmail account only after you approve that email.
We use Google data only to provide LyteKeepr's features to you. We do not sell it, use it for advertising, or use it to train AI models.
When you use LyteKeepr's AI features, relevant text from your emails, calendar events, call transcripts or leads is sent to OpenAI to produce the answer (see section 5).
You can disconnect Google at any time, and you can ask us to delete your data (see section 7).

Who we are
Google user data we access
Other information we collect
How we use information
Where it is stored and who processes it
Security
Retention, disconnecting and deletion
Your choices
Children
Changes to this policy
Contact

1. Who we are

LyteKeepr ("we", "us") is an independent B2B relationship software product available at lytekeepr.xyz. It helps you keep track of conversations with leads and customers across LinkedIn, Instagram, email and your calendar, and reminds you when to follow up. It is currently offered through early access. This policy applies to the LyteKeepr website and the LyteKeepr application.

2. Google user data we access

Google access is optional and starts only when you sign in with Google and approve the permissions shown on Google's consent screen. We request the following permissions (scopes):

Google service and scope	What we read or do	Why
Gmail `https://www.googleapis.com/auth/gmail.modify`	Your Gmail address; the messages Gmail returns for the period we sync (sender, recipients, subject, date, labels, message body); and attachments of the messages we process. We send an email from your account only when you press "Send now" on a draft.	To find messages that look relevant to your relationships, let you review and keep them, search and summarize them, read attached documents, and send replies that you approve.
Google Calendar `https://www.googleapis.com/auth/calendar.readonly`	Read-only access to events on your primary calendar, from about 30 days in the past to about 6 months ahead: title, start and end time, description, location and meeting link. All-day events are ignored. This permission cannot change your calendar.	To show your meetings next to your tasks and follow-ups, let you add your own notes and meeting status in LyteKeepr, and create a follow-up reminder 24 hours after a conference call you mark as completed. While connected, the calendar refreshes automatically about once an hour.
Google Calendar events `https://www.googleapis.com/auth/calendar.events`	Creates a meeting in your primary calendar when you press Save on a new meeting in LyteKeepr (title, time, length, notes, the people you chose to invite and, if you ask, a Google Meet link), and deletes a meeting when you press Delete meeting. Google then emails the invitation or cancellation to the people invited. We do not change or delete any other event.	So you can schedule calls with your contacts from LyteKeepr and have them recorded and linked to the right contact.

The Gmail permission is Google's "modify" scope. In the LyteKeepr application we use it to read messages and to send messages you approve; the application does not delete, trash or relabel your Gmail messages. (The only other write is a separate import tool run by the operator, which can add historical messages to the operator's own mailbox. It is not part of the application screens.)

You can also sign in to LyteKeepr with Google. For that we receive only your email address and name (the openid, email and profile scopes), to know which account is signing in.

Google API Services User Data Policy. LyteKeepr's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Other information we collect

Early-access requests. If you submit the form on our website we receive your name, work email, company and the CRM you use. The submission is saved to a file on our server and emailed to us through our mail server and its outbound email-delivery provider (Brevo).
Things you add to LyteKeepr. Lead lists you import (for example names, profile handles and links, and notes), your own tasks, meetings and reminders, the notes and meeting statuses you add, and the status of each lead.
Call transcripts, if you connect Fathom. If you paste your own Fathom API key in LyteKeepr, we fetch your recorded calls from Fathom about once an hour: the meeting title and time, the people invited, the link to the recording in Fathom and the transcript. These are saved in your workspace's database and linked to your contacts by email address. A summary or follow-up email is written only when you press Summarize or Draft follow-up. Your Fathom key is saved on our server in a file only the application can read; Disconnect removes it.
Your account. The email address and name you sign in with, the people you add to your team and their access level, and, for the operator, plan and billing settings. Each customer account's data is kept in its own separate workspace. A team member can connect their own Google Calendar (calendar permissions only, never Gmail); its meetings are visible to them, to the account's admin and to team members the admin gave access to everything.
Your assistant conversation. So that a page refresh or a new sign-in doesn't lose it, the most recent 100 messages of your conversation with the LyteKeepr assistant are saved in the application's database. The "Clear chat" button deletes them.
Web server logs. When you visit lytekeepr.xyz our web server records your IP address, the time, the page requested and your browser type. These logs are kept on the server and not shared; we do not currently delete them automatically.
A sign-in cookie. If you sign in to the LyteKeepr application, we set one cookie that keeps you signed in for up to 30 days. It is a signed, HTTP-only cookie sent only over HTTPS and only to the application pages.
No analytics or advertising. Our website does not use analytics, advertising or tracking scripts or cookies. Its pages load fonts from Fontshare (fontshare.com), so your browser contacts that service, which may see your IP address.

4. How we use information

We use the information above only to provide and operate LyteKeepr for you: to show your messages and calendar, search and summarize them, track which leads need a follow-up, create reminders, draft and (when you approve) send replies, respond to early-access requests, keep the service running and secure, and meet legal obligations.

Limited Use of Google data.

We use Google user data only to provide or improve the user-facing features described in this policy.
We do not sell Google user data, and we do not use or transfer it for advertising, including personalized, retargeted or interest-based advertising.
We do not use Google user data to develop, improve or train generalized AI or machine-learning models.
We do not allow people to read Google user data, except with your consent for specific messages, where needed for security or to investigate abuse, or to comply with the law. The person who operates a LyteKeepr installation can access the data stored in it.
We transfer Google user data to others only as needed to provide the features you use (see section 5), to comply with the law, or as part of a merger or sale of the business with notice to you.

5. Where it is stored and who processes it

Where your data is stored

On the computer that runs the LyteKeepr application, when the application is run on a personal computer. There, your Google access token is saved as a file, synced Gmail messages and attachments are saved as files, and your leads and calendar data are saved in a database.
On our server. The website, early-access submissions and the LyteKeepr application at lytekeepr.xyz/app run on a cloud server hosted by Hetzner. When Google is connected there, your Google access token is saved on that server as a file that only the application's service account can read; synced Gmail messages and attachments are saved there as files; and synced calendar events, together with the notes and statuses you add to them, are saved in the application's database.
Backups. The calendar database on our server, which includes synced Google Calendar events and the notes and statuses you add to them, is backed up automatically every night, and the 14 most recent backups are kept, readable only by the server administrator. Google access tokens and synced Gmail files are not part of those backups.

Who else processes data

Google, to provide your Gmail and Calendar data and to let you sign in and approve access.
OpenAI (the OpenAI API), to power LyteKeepr's AI features. When you ask the assistant a question, or when LyteKeepr triages incoming email, drafts a follow-up or reads a document, the text it needs is sent to OpenAI. Depending on the feature this can include email sender, subject, date and body excerpts, attachment file names, images or text of attachments, calendar events, call transcripts and lead details. We send these requests with the API's response-storage option turned off. OpenAI processes the data under its own terms and privacy policy (openai.com/policies).
Fathom, only if you connect it: it records your calls under your own Fathom account and terms, and LyteKeepr reads the transcripts from it (fathom.video/privacy).
Anthropic (Claude), only if you connect LyteKeepr to Claude: when you ask Claude something, the LyteKeepr data its tools return (contacts, funnels, outreach statuses, tasks, reminders, LinkedIn and Instagram messages and recorded call transcripts) is sent to Anthropic so Claude can answer you. With your approval Claude can add or update contacts, stages, statuses, tasks and reminders, book or cancel meetings in your Google Calendar (Google sends the invitations), and write email or LinkedIn drafts that only you can send, from LyteKeepr. The text of your emails and your Google Calendar events are not sent to Claude (for "did they reply?" Claude only learns the date of an email). You can disconnect in LyteKeepr Settings → Claude. Anthropic processes the data under its own terms and privacy policy (anthropic.com/legal/privacy).
Hetzner, which hosts our server, and Brevo, which delivers the email notification for early-access requests.
Fontshare, which serves the website fonts.

We do not sell personal information. We may disclose information if the law requires it.

6. Security

These are the protections that are actually in place today:

lytekeepr.xyz is served over HTTPS.
The LyteKeepr application on our server requires signing in, with Google or a password. Repeated wrong passwords from the same address are temporarily blocked. New accounts stay locked until the operator approves them, and each account sees only its own workspace.
The server is administered by the operator over SSH. Server backups and the server's settings file are readable only by the administrator account.
Google access tokens never appear in the pages the application sends to your browser. On our server they are stored in a folder that only the application's service account can open.

What we do not currently do: the application does not add its own encryption to stored data. Google tokens, synced messages and databases are ordinary files protected by the access controls and disk protection of the computer or server they live on. No system is perfectly secure, and we cannot guarantee absolute security.

7. Retention, disconnecting and deletion

How long we keep data

We keep data until it is deleted; there is no automatic expiry for synced messages, calendar events, leads or early-access submissions. Messages that you delete in Gmail are removed from LyteKeepr's local copy the next time it syncs. Calendar events that disappear from Google's synced period are removed from LyteKeepr unless you added your own notes or a status to them. If an account is deleted, its workspace is moved to an archive folder on our server that only the administrator can read, and it is erased for good on request.

Disconnecting Google

You can withdraw LyteKeepr's access at any time at myaccount.google.com/permissions by selecting LyteKeepr and choosing "Remove access". After that, LyteKeepr can no longer read your Gmail or Calendar or send email for you.

Requesting deletion

To have your data deleted, email hotrunningwater@gmail.com with the subject "Deletion request", from the address you used or telling us which address you used. We will delete the Google access token we hold for you, the Gmail messages and attachments and any records derived from them, the calendar events synced from Google and the notes and statuses you added to them, the leads and calendar items you created, your saved assistant conversation, and any early-access submission from you. We will reply to confirm when it is done.

Server backups are not edited; copies of deleted data in them disappear when those backups expire, which is within 14 days. Anything already sent to OpenAI is governed by OpenAI's own retention terms, and emails we already sent from your account remain in your Gmail.

8. Your choices

You can ask us to tell you what data we hold about you, correct it, or delete it, and you can withdraw consent by disconnecting Google as described above. Email us at the address in section 11 and we will respond.

9. Children

LyteKeepr is business software and is not directed at children. We do not knowingly collect information from children.

10. Changes to this policy

If our practices change, we will update this page and the "Last updated" date above. If a change affects how we use Google user data, we will update this policy before the change takes effect.

11. Contact

For privacy questions or to make a request, email hotrunningwater@gmail.com.