Privacy Policy
1 Introduction
Welcome to Keep.Up — a family calendar and reminder app that helps you stay organized together. Keep.Up is made and operated by Little Dove Dev LLC ("we", "us"). We built Keep.Up to make family coordination easier, and we take your privacy seriously.
This policy explains what information we collect when you visit trykeepup.com or use the Keep.Up app, how we use it, and the choices you have. We've written it in plain English so it's actually useful to read.
If anything here doesn't make sense or you have a question, just email us at jeremy@trykeepup.com.
The short version: We collect only what we need to run Keep.Up. We never sell your data. You can ask us to delete everything at any time.
2 Information We Collect
We collect two categories of information depending on how you interact with us.
On Our Website
- Email address (when you join the waitlist)
- Family organizing challenge (optional — what you typed in the text field)
- Referral / UTM source (how you found us)
- Price tier shown during your visit
- A randomly assigned A/B test identifier ("A" or "B"), stored in your browser, that keeps the page wording you see consistent between visits; it is also reported to Google Analytics (see Section 4)
- Standard browser information (device type, browser version). Your IP address is not stored in our waitlist database, but it does appear in our hosting provider's server logs (see Render in Section 4)
In the App (Coming Soon)
- Family calendar events and reminders you create
- Gmail messages and Google Calendar events, if you connect a Google account (see “Google user data” below)
- Attachments from those messages, when they belong to an item Keep.Up surfaced, or when reading the file is how Keep.Up decides whether there is one (see “Google user data” below)
- A push notification token, only if you switch on the optional instant-alerts relay — it is what lets that service wake this device. Keep.Up’s own reminder notifications and nudges do not use it: those are scheduled by the app on your own device and need nothing sent anywhere
- Account information (name, email address)
- Aggregate App Store statistics (downloads, crashes) that Apple provides to all developers through App Store Connect — the app itself contains no analytics or crash-reporting SDK
We access Gmail and Google Calendar data only if you explicitly choose to connect a Google account in the app. You can revoke that access at any time from within Keep.Up or at myaccount.google.com/permissions — the details are in the next section.
Google user data (Gmail and Google Calendar)
If you choose to connect a Google account, Keep.Up requests read-only access to Gmail
(https://www.googleapis.com/auth/gmail.readonly) and Google Calendar
(https://www.googleapis.com/auth/calendar.readonly). Here is exactly what
happens with that data:
- What we access. Message content and headers from your Gmail inbox, and events from your Google Calendar.
- Why. To detect time-sensitive family obligations — permission slips, RSVPs, registrations, payments — and turn them into reminders, and to flag conflicts with events already on your calendar.
- Where processing happens. On your device, using Apple’s on-device intelligence. Your email and attachment content is not transmitted to, stored on, or readable by any Keep.Up server. If you switch on the optional instant-alerts relay, that service learns that your inbox changed and when — never anything about what any message says; Section 4 lists everything it stores.
- What we never do. Our use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we do not (i) use Google user data for serving advertisements, including retargeting, personalized, or interest-based advertising; (ii) transfer Google user data to third parties except as necessary to provide or improve user-facing features that are prominent from the Keep.Up user interface, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with user notification; (iii) allow humans to read Google user data, unless we have your affirmative agreement for specific messages, doing so is necessary for security purposes such as investigating abuse, to comply with applicable law, or for internal operations where the data has been aggregated and anonymized; (iv) use Google user data to develop, improve, or train generalized or non-personalized AI and/or ML models — all email processing runs on-device using Apple’s on-device intelligence; or (v) modify, send, or delete your mail, or sell any of it.
- Attachments. When an email carries a document you have to deal with — a permission slip, a form, an invoice — Keep.Up downloads that file and stores it on your device, so you can open it without leaving the app. Keep.Up also reads the text of attached PDFs on your device, using the same Apple on-device intelligence it reads your mail with, because a form’s deadline is often stated only inside the file and nowhere in the email. The file itself is never sent to a Keep.Up server or to any other company — though it does sync to your family through your family’s iCloud, like the item it belongs to, so the other parent can open the same form. What Keep.Up reads from it becomes the item — the title, the dates, the key points — and those sync to your family like everything else on your radar. Files are encrypted at rest while your device is locked. You can remove the copies held on your device at any time from What Keep.Up sees in Settings. Keep.Up fetches an attachment either because it belongs to an item on your radar or because reading the file is how it finds out whether there is one — never your whole mailbox. A file fetched only to be read is read and discarded, not kept.
- Sharing within your family. Each item Keep.Up creates syncs to your family through your family’s iCloud account: its title, date and category, its notes, who it is for, and the key points Keep.Up pulled out of the message, together with the context that explains why it exists — the line of the message, or of its attachment, the item was drawn from, a short excerpt of the source message (for a calendar event, its description), its subject line, its sender, the address of the mailbox it came from, and Keep.Up’s one-line reason for surfacing it. An account of the message itself syncs too. An item drawn from one parent’s mailbox can reach a phone that cannot open that mailbox, so the device that did read the mail writes a short account of it — whether it is laid out as a form and what that form asks for (a signature, a parent or guardian’s name, the page sent back, a payment), the dates the message states and any times of day it gives for them, whether it reads as a change to something already scheduled, how many files it carries and what they are called, and roughly how many words long it is — and that account syncs to your family. It is written in Keep.Up’s own words: it describes the message and never quotes the message body. The one thing it repeats exactly as the sender wrote it is the name of an attached file, which already syncs and already appears on the item. Links sync too: a link back to the original message, and any RSVP, form or payment link Keep.Up extracted from it — such links can carry a token personal to you. Attachment files belonging to the item sync too, so the other parent can open the same form instead of hunting for the email. What is not shared: the full message body — that never leaves your device. Neither does the content of mail Keep.Up did not turn into an item, with three exceptions. First, when Keep.Up spots a yearly pattern in your older mail or calendar — an annual form, a yearly checkup, a membership renewal — the recurring reminder it creates carries the subject lines or event titles, senders and dates of the few messages or events that revealed the pattern, and that reminder syncs to your family. Second, so your family’s devices agree on which senders are worth reading, Keep.Up keeps a per-sender tally — the sender’s address if they write from a personal account such as Gmail or iCloud, otherwise only the domain they write from; how many of their messages it has read, how it sorted them, how many items came of them and how many were reminders about something already on your radar; when it last read their mail or your family last acted on something from them; and a count of each kind of thing your family did with those items (finished, swiped away unopened, hidden with Ignore, title or date corrected, sender trusted or blocked, or an automatic check-off undone) — and that tally syncs to your family. Because it syncs, another member’s device can see that you never act on a particular sender. The tally holds addresses or domains, dates and counts only, never the wording of any message or its subject line. When Keep.Up has decided that a sender’s routine-looking mail can be skipped, that sender is listed under Senders Keep.Up quietly skips in What Keep.Up sees in Settings, and Read again there clears the sender’s counts on that device and asks every other family device to clear theirs. What the tally keeps afterwards is a note of that sender’s address or domain and when you cleared it, which is how the other devices know to clear it too. If another device read new mail from that sender before it heard about the clear, the sender can reappear in the list, and Read again clears it again. Third, details about your family that Keep.Up finds in your mail — a child’s school, grade, teacher or activities, or a profile it drafts from your mail when you ask it to — are saved to your family profile or family list after you have reviewed them, and those sync to your family (Section 4 lists what they hold). Keep.Up shows you what it found before any of it is saved.
- Revoking access. Disconnect anytime in the app, or at myaccount.google.com/permissions. Items and reminders Keep.Up already created stay in the app, and in your family’s iCloud if you share with family. If you switched on Auto-add to Apple Reminders, or added an item to Reminders yourself, the reminders Keep.Up put in Apple’s Reminders app stay there too, in whichever account holds your reminders — usually iCloud. Access to your mail and calendar stops immediately.
Google API Services User Data Policy — Limited Use
Keep.Up’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. The specific commitments — no advertising use, restricted transfers, no human reading, and no use in training generalized or non-personalized AI/ML models — are enumerated in the “What we never do” bullet above. The advertising and analytics technologies described in Section 4 apply to this website only; they never receive Google user data from the app.
We use cookies and similar tracking technologies to understand how visitors use our site and to measure the effectiveness of our advertising (see Section 4 for the specific services we use). You can control cookies through your browser settings.
3 How We Use Your Information
We use the information we collect to:
- Send you waitlist updates and launch communications via email
- Understand what family coordination problems matter most, to build a better product
- Operate and improve the Keep.Up app and website
- Deliver push notification reminders you set in the app
- Measure which marketing channels bring people to Keep.Up (so we can advertise efficiently)
- Respond to your support requests or questions
- Comply with legal obligations
We do not use your personal information to make automated decisions that have significant legal or similarly serious effects on you.
We will only send you marketing emails if you opted in. You can unsubscribe at any time by clicking the unsubscribe link in any email or by emailing jeremy@trykeepup.com.
4 Third-Party Services
We work with trusted third-party services to operate our website and app. Each has its own privacy policy that governs how they handle data on their end.
These services may receive information like your IP address, browser type, and pages visited. Advertising pixels may also set cookies to help us understand which ad campaigns are working.
Apple is listed for a different reason: Keep.Up’s family sync runs on iCloud (CloudKit), so what it shares with your family is stored in iCloud — in the iCloud account of the family member who turned on family sharing — rather than on a Keep.Up server. Keep.Up’s family sync stores nothing in iCloud until family sharing is turned on. Once it is, iCloud holds:
- The items Keep.Up creates, including who finished each one, and the attachment files belonging to them (Section 2 describes what an item carries).
- Recurring reminders, including those Keep.Up finds in older mail or calendar events.
- Your family list: names, relationships, birthdays, notes, anything you typed to clarify an entry, and profile text.
- Your family profile: family and parent names; each child’s school, grade, teacher, activities, interests, notes and profile text; your family notes; the towns you entered and the area around them; and the senders you have marked as trusted or blocked.
- Each family member’s Keep.Up name, with the identifier iCloud gives their account and which entry in your family list is theirs, and iCloud’s own record of who has joined the family share.
- The per-sender tally described in Section 2.
- For a mailbox you mark as a shared family mailbox: its address and the IDs of the messages Keep.Up has already checked there, so another family member’s phone does not read them again.
Apple also answers a few requests that have nothing to do with sync. When you place a town on the map in your family profile, your phone asks Apple’s location service to find it, sending the town you typed, and it may also send points on the map near that town to learn the names of the towns around it. The app then shows that area on an Apple map — and again whenever you open that community in your profile — which loads the map of that area from Apple. These requests go from your phone straight to Apple, not through a Keep.Up server, whether or not you share with family.
Apple receives none of the website analytics or advertising data described above, and Google user data is never shared with any advertising or analytics service.
The instant-alerts relay is listed for a related reason: it is the one service in this table that Keep.Up itself runs, so it is worth saying exactly what it holds rather than only what it does. Instant alerts are off unless you turn them on, and until you do, the relay holds nothing about you at all. Once they are on, it stores, for each mailbox you enabled:
- Your Google account identifier and that mailbox’s email address. This is how a notification from Google gets routed back to your family’s devices, and it is the only thing the relay stores that names you rather than a device.
- For each of your devices: a random identifier for that installation, an Apple push token, and a one-way hash of a credential the relay issued to it. The installation identifier is generated by the app, means nothing outside this service, and is what the relay’s own logs name a device by. The credential itself lives in your device’s keychain; the relay keeps only the hash, and it is not a Google credential — it authorises nothing beyond this service.
- A few timestamps: when the mailbox’s mail subscription expires, when each device first linked, when it last signed in and when it last checked in, and when the relay last woke your devices.
- The identifiers of the notifications it has already acted on, so that a repeated notification from Google does not wake your devices twice. These are identifiers of Google’s own notification messages, not of anything in your mail, and they are cleared about a day later — on the relay’s next piece of work rather than by a clock, so on a mailbox that has gone quiet they persist until it next hears from Google.
What that adds up to is worth stating plainly rather than leaving you to work out: the relay learns that your inbox changed, and roughly when — that is its entire job. Usually that means a message arrived, but it equally covers you archiving or deleting one, because what your device subscribes to is your inbox rather than new mail specifically. That is information derived from your Gmail account, even though no part of any message ever reaches it. Google’s notification says only that something changed; Keep.Up deliberately discards the identifier that would let it ask Google what changed. The relay holds no password, no OAuth token, and no key of any kind that could open your mailbox: your device starts and stops the mail subscription itself, using credentials that never leave it.
Two further details, because a reader tracing the flow would otherwise have to ask. Setting alerts up does send one Google-issued token to the relay: a short-lived identity token proving which mailbox is yours. It is an assertion of who you are, not a key to anything — it cannot read mail — and the relay verifies it with Google’s public keys, takes only the account identifier and the address from it, and keeps nothing else it contained. And the relay keeps ordinary server logs, as any hosted service does. Two kinds: its own, which record which device was woken — by that random installation identifier — and whether Apple accepted the push; and a connection log, written automatically for every request, holding an IP address, the address requested and whether it succeeded. That second kind is the same thing our hosting provider records for this website, described in Section 2. Neither contains your email address, and neither contains any part of a message. The service runs in a data centre in the United States.
Turning instant alerts off deletes the relay’s record of that device, and its record of the mailbox once no device linked to that Google account is still using it — which may include a second parent’s phone sharing the same mailbox, so the mailbox record goes only when the last of them switches off.
We do not sell your personal information to any third party, including any of the services listed above. When data is shared with ad platforms, it is used solely for attribution and measurement — not sold.
5 Data Retention
We keep your information only as long as it's needed for the purposes described in this policy, or as required by law.
- Waitlist email addresses: kept until you request deletion. Unsubscribing stops our emails but doesn’t delete your address: we keep it, with a note not to email it again, until you ask us to delete it
- Waitlist form responses (your challenge description): kept for product research purposes until deletion is requested. If you click Reserve my spot, the price you were shown and your challenge description are saved a second time, without your email address, for the same purpose; we can match that copy to you only by what you typed and when you clicked, and when you ask us to delete your sign-up, we delete any copy we can match to it.
- Analytics and ad pixel data: governed by the retention policies of Google and Meta respectively
- App data (your items and their attachments, recurring reminders, and your family list and profile): kept on your device and, once you turn on family sharing or join a family’s share, in your family’s iCloud — not on a Keep.Up server. To delete it, choose Delete all my data in What Keep.Up sees in Settings. If you aren’t sharing with family, it removes every item, person, and file Keep.Up stored on this device and in your iCloud, and disconnects your Google accounts. If you are, it clears this device and disconnects your Google accounts, but the shared data itself isn’t touched: this device stays joined to it, so items can reappear here the next time it resyncs. What can be done about the shared data depends on who set up sharing. If you set up the family share, stop sharing first and then choose Delete all my data: that removes the family’s data from your iCloud, though each family member’s phone keeps the copy it already has until it is deleted there. If you joined someone else’s share, everything it holds — including items Keep.Up made from your mail — is kept in their iCloud, and stays there after you leave. Anyone still in the share can remove items one at a time with Delete permanently (you too, until you leave), but only the person who set up sharing can delete all of it at once. Reminders and calendar events Keep.Up added to Apple’s Reminders and Calendar apps stay there — delete them in those apps if you want them gone. If the iCloud copy can’t be deleted — no iCloud account is signed in, Keep.Up can’t confirm the delete with iCloud, or it finds this device is sharing after all — this device is still cleared, and the app tells you that what is in iCloud may still be there. Backups of a phone made before the delete, in iCloud or on a computer, still hold what they held.
- Attachments: kept on your device, and in your family’s iCloud storage, for as long as the item they belong to exists. To remove a document entirely, open the item and choose Delete permanently: this removes the item and its files from your family’s iCloud and every family member’s device. To stop the same email or event coming back, Keep.Up keeps a note of where it came from (the email’s or event’s identifiers, synced with the family — an email’s can include the name of the sender’s mail server) and, on the phone that deleted it, its title, its date and who it was for. For a calendar item, each phone that read that calendar also holds a note of the event’s title, time and place; on Keep.Up build 154 or later, each one deletes that note the next time it finishes checking its mail and calendars after the delete reaches it, not at the moment you delete. On those builds the delete also takes the item out of the spare copy of the item list that Keep.Up keeps inside the app on each phone (in case the main copy is damaged), and removes the Keep.Up notifications that listed the item: straight away on the phone that deleted it, and on each other phone as soon as the delete reaches it. Rarely, a summary notification that listed a second copy of the item, which Keep.Up later merged into this one, stays until it is cleared. A phone still on an older build keeps the event’s title, time and place until it updates, keeps the item in that spare copy until it next saves its item list, and leaves a summary notification that listed the item until it is cleared. If Keep.Up added the item to Apple’s Reminders or Calendar app and does not have full access to that app when the delete reaches the phone, that copy stays there until you remove it. Backups of a phone made before the delete, in iCloud or on a computer, still hold what they held. What Keep.Up sees in Settings separately clears the copies held on your device; because those files belong to shared items, they download again on the next sync. Signing into a different iCloud account removes them from that device. They are never stored on a Keep.Up server.
- Instant-alerts relay records: if you switch instant alerts on, the relay’s record of a device is deleted when you switch them off on that device — immediately, and the app reports alerts as off only once the relay confirms it. A device’s record is also deleted if Apple tells the relay that its push token is permanently gone (you deleted the app, or the device was reset), and automatically after 30 days without contact from it. “Contact” here means the app itself checking in — renewing the mail subscription or updating its notification token — which a device in normal use does every few days on its own; it does not require you to open the app. When the last device for a mailbox goes, by any of those three routes, the relay’s record of the mailbox — your Google account identifier and that email address — is deleted with it. Deletion is per device: if another of your family’s devices still has alerts on, that mailbox keeps working there, and alerts stop only on the device whose record was removed, until you sign in again on it. The 30-day sweep runs when the relay next handles traffic rather than on a timer, so a record belonging to a mailbox that has gone completely quiet is removed the next time the service runs.
- Email logs (Resend): typically retained for 30–90 days for deliverability diagnostics
You can request that we delete your data at any time by emailing jeremy@trykeepup.com. We'll process your request within 30 days.
6 Your Rights (GDPR & CCPA)
Depending on where you live, you may have specific rights over your personal information. We honor these rights for everyone, regardless of location.
- Access. You can ask us to confirm what personal information we hold about you and receive a copy of it.
- Correction. If any information we hold about you is inaccurate, you can ask us to correct it.
- Deletion. You can ask us to delete your personal information. We'll do so within 30 days unless we're legally required to keep it.
- Opt out of marketing. You can unsubscribe from our emails at any time via the unsubscribe link or by emailing us directly.
- Opt out of "sale" or "sharing" (CCPA). We don't sell personal information. Sharing data with advertising platforms for measurement purposes may qualify as "sharing" under California law — you may opt out by emailing us or by using browser-level privacy controls.
- Data portability (GDPR). You can request a copy of your data in a portable format.
- Lodge a complaint (GDPR). If you're in the EU/EEA/UK and believe we've handled your data incorrectly, you have the right to contact your local data protection authority.
To exercise any of these rights, email jeremy@trykeepup.com with the subject line "Privacy Request." We'll respond within 30 days. We may need to verify your identity before fulfilling certain requests.
7 Contact Us
If you have any questions about this privacy policy or how we handle your data, we'd genuinely like to hear from you.
We may update this privacy policy from time to time. When we do, we'll update the effective date at the top of this page. If we make significant changes, we'll notify you by email (if you're on our waitlist) or with a notice in the app.