Next Up Sprout Privacy Policy
Updated October 17, 2026
Next Up helps you keep track of your baby’s first year. Creating a Next Up account stores your username, a salted password hash and a hashed recovery code. Passwords and recovery codes are not stored as readable text. A secure, HttpOnly cookie identifies your login session; the server stores only its hashed token. When you submit a baby profile, the app stores a private family page on its server, including your family stage, estimated due date or actual birthday, baby’s details, essentials-list choices, task check-offs, visit questions, selected office identifier, daily records, appointments, Parent Diary entries and milestones, caregiver notes and confirmed after-hours instructions. Your username identifies you in the caregiver list. All approved family caregivers can view and edit these records.
Account recovery and removal
You can save an optional recovery code from Account settings after signup or a password update/reset. Keep it private: it can reset your password. This app does not send password-reset emails. Password changes invalidate other login sessions and replace the recovery code. You can log out or permanently remove your account in Family → Account settings. Removing an account also removes any family page it owns. Existing family records from the previous sign-in system can move into your new account only through an explicit transfer while that previous access is available in the same browser.
Private family sharing
The public app link exposes the app and fictional sample, not private family records. The family owner can create a one-use invitation that expires after 24 hours, cancel it or remove a caregiver’s future access. Anyone with an active invitation who logs in can join, so share it directly with a trusted caregiver. Up to 8 accounts can join a family. Removing access does not recall information someone already downloaded or copied. The app checks family membership on private requests. It refreshes records while open, roughly every 20 seconds, and retains unsaved changes in session memory if a save fails.
Device-only profiles and deletion
Older remembered profiles remain in their original browser until you explicitly choose to move them into a private workspace. Guest age selections, example records and unsaved drafts stay in this tab’s memory. Browsing does not create an account or private family page. When you choose to save, an account is required; your draft is kept through signup or login and restored after you confirm your baby’s details. Example records are never copied into your private family page. Reloading or closing the tab can clear unsaved guest drafts. Ask drafts also stay in session memory. To export or delete a private family page, open Family. Deletion is available to the owner and removes the active records for every caregiver. Caregivers can leave a family; owners can remove caregiver access. To remove an older device-only profile, use Your baby’s details → Remove saved information. Clearing browser data can erase device-only profiles and unsaved drafts. Hosting-provider operational logs and backups are handled separately under the provider’s policies. Don’t enter insurance member numbers, Social Security numbers or document images into task notes.
Diary and Community
Parent Diary entries are saved with your private family records. They are visible and editable by you and invited caregivers, included in family exports, and removed when the workspace is deleted. They are never automatically shared in Community.
Community posts, photos and replies are visible to all signed-in Next Up accounts. Anyone can create an account. Your username identifies your posts and replies; baby profile details are not attached. Photos are resized and converted to JPEG before sharing, and location-bearing photo metadata is stripped on the server. Image files are kept in private object storage and served only after checking login and post visibility. Signed-in members may still copy or screenshot what you share. Share only pictures and details you have permission to share.
You can edit or delete your posts and remove your replies. Deleting a post removes its active photo and replies. Deleting your account removes your posts, replies, and reports. Reports include the reason, post and reporting account; a report hides that post for the reporter and is saved. There is no live moderation team or guaranteed review. Community is not an emergency service. Do not post private medical, insurance or identity documents. Posting and commenting use short-lived rate counters. Hosting-provider operational logs and backups are handled separately.
Google Calendar data
Next Up Sprout is operated by Spencer Ryan. Connecting Google Calendar is optional and is available after the family owner signs in and saves a family page. You can use Next Up Sprout without connecting Google. Google handles its own sign-in and permission screen; Next Up Sprout never receives your Google password.
What Google data we access
We request exactly these Google Calendar permissions:
https://www.googleapis.com/auth/calendar.events: view and edit events on your calendars. This lets the app show appointments for you to choose, import a selected event, create an event you choose to link, and update linked titles, times and locations in either direction.https://www.googleapis.com/auth/calendar.calendarlist.readonly: view the list of calendars you subscribe to. This lets you choose a calendar that you own or can edit. Next Up Sprout does not use this permission to change calendar membership or sharing.
Google's permission is broader than the visits you choose in Next Up Sprout. Our app uses the calendar list's identifiers, names and access roles to offer writable calendars. The event picker reads event identifiers, versions, titles, start and end times, locations, cancellation status and flags needed to exclude unsupported events. It looks from the past 30 days through the next year. It does not request event descriptions, guest lists, attachments or conference details. All-day, recurring, canceled and locked events are not offered for import. We do not request Gmail, Google Contacts, Google Drive, or Google profile permissions.
How we use and store Google data
We use Google Calendar data only to provide the calendar connection, calendar picker, selected-appointment import and synchronization features you choose. Selecting a calendar does not import all its events. Only visits you explicitly select are saved as family appointments. You can also choose to create a linked Google event from a Next Up appointment. Linked titles, start/end times and locations can synchronize while Next Up Sprout is open or when a family member chooses Sync selected visits. Appointment questions, care instructions, diary entries and baby-profile details are not sent to Google as part of this feature.
We store encrypted Google access and refresh tokens, the writable calendar list returned at connection time, your chosen calendar's identifier/name, the last successful sync time, and link records containing selected event identifiers, versions and a snapshot of their title, times and location. Imported appointments are stored in your private family records. Unselected event-picker results are processed for display and are not saved as family appointments or persistent event records.
Who receives Google data
Selected appointments become visible and editable to the people you invite to your private Next Up Sprout family. Invited caregivers can trigger synchronization of already-linked appointments; only the family owner can connect or disconnect Google, choose a calendar, import additional visits, or create or remove links. Calendar data is not automatically posted in the public Community.
Google receives the authorization requests and selected event changes needed to run the connection. OpenAI Sites and its hosting infrastructure, including Cloudflare Workers, D1 database storage and associated operational services, process requests and store the app's records on our behalf. The site operator can access stored records for operating and supporting the service; routine analytics reports do not contain calendar contents or credentials. We do not sell, rent or disclose Google user data to advertisers, data brokers or unrelated partners. We do not transfer it for advertising, credit decisions or other purposes unrelated to these user-facing calendar features. Any disclosure required by law is limited to what is legally required.
How we protect Google data
Connections between your browser, Next Up Sprout and Google's APIs use HTTPS. Google access/refresh tokens and temporary OAuth state payloads are encrypted on the server with AES-GCM, using a server-side runtime key that is not included in the public app or stored alongside those encrypted values. Tokens are not returned to the browser or included in analytics. Imported appointment fields are protected by server-side family-membership checks; they are not separately encrypted by the application in the same way as the tokens. The connection requires the owner's authenticated session. The OAuth flow also uses a short-lived, one-use state value and PKCE to bind the authorization response to the initiating session. Local login passwords are salted and hashed, and session cookies are Secure, HttpOnly and SameSite. These measures reduce risk; no system can promise perfect security.
Retention, disconnection and deletion
Connection tokens, the stored calendar list, selected calendar settings and link metadata remain while your Google connection is active. In Appointments, expand Calendar settings & other options, open Google Calendar and choose Disconnect to delete those active connection records and stop future syncing. Disconnecting keeps appointments already saved in Next Up Sprout and in Google. Use Stop syncing on an individual linked visit to delete its sync link while keeping the appointment in both places. Revoking access in your Google Account connections prevents further authorized access; also disconnect in Next Up Sprout to remove the stored connection records.
Imported appointment copies remain in your private family records until you remove them or the owner deletes the family page or owner account. Family or owner-account deletion removes the active Google connection, its links and that family's saved appointments; it does not delete events from Google. To remove the whole family page, use Family's delete-family control; to remove the owner account, use Family → Account settings. The app does not automatically delete imported appointments just because you disconnect or revoke Google. Copies other family members already exported or downloaded cannot be recalled.
OAuth state is accepted for 10 minutes and consumed when its authorization response is processed. Expired temporary state records are removed when a later connection starts. Active-store deletion does not promise immediate deletion from hosting-provider operational logs or backups, which are handled under the providers' retention policies. Contact spenceryan14@gmail.com about Google-data deletion or privacy questions; do not email passwords or sensitive family records.
Limited Use and AI
Next Up Sprout's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google Workspace API data is not used to develop, improve or train generalized or non-personalized AI or machine-learning models. It is not sent to an AI service or used to target advertisements.
Other calendar options
Calendar exports and Add to Calendar send only a selected appointment’s title, start/end time and location. Your questions, diary, care instructions and baby profile are not included. Opening Google or Outlook takes you to that provider. File imports are read in this browser; only the visits you select are saved with your family. File copies do not stay synchronized.
The family owner can optionally connect an iCloud calendar using an Apple Account email and app-specific password. The credential is encrypted on the server with a separate runtime key, is not sent to analytics or returned to the browser, and is used only with Apple’s HTTPS calendar servers. The app-specific password may permit access to other iCloud calendars, but Next Up syncs only the calendar the owner chooses. Only individually linked visits are copied or synchronized; imported descriptions, guest lists and private notes are not copied to family records. Everyone invited to the family can see and edit linked visits. Changes to linked title, start/end time and location sync while Next Up is open or when you choose Sync now. Removing a linked visit in Next Up deletes its Apple event on the next sync; deleting or canceling it in Apple marks it canceled in Next Up and preserves the notes. Concurrent changes prompt you to choose a version. All-day and recurring events are not supported.
Disconnecting deletes the active encrypted credential and sync links, while leaving appointments in both places. Family or owner-account deletion also removes the connection; it does not delete Apple events. You can revoke the app-specific password separately in your Apple Account settings. Sync errors keep saved family records; review the last completed sync time before relying on a calendar copy. No calendar contents or connection credentials are added to site-usage reports.
Pediatrician searches
The doctor or registered office name you search for, and any optional town/state in that search, are sent through this site to the U.S. Centers for Medicare & Medicaid Services (CMS) public NPI Registry to find matching providers. Choosing an office retrieves its public practice-location record. Your baby’s name, birthday, sex, preferences and question list are not included. The directory requires no Google API key, payment details or billing account. Only the selected NPI and address identifier are saved with your family page or existing device-only profile. A short-lived server cache holds public search results and provider records to reduce repeated requests; it does not hold your baby’s profile.
CMS operates the directory under its Privacy Policy. Opening directions or “Find practice website” takes you to Google’s ordinary Maps or Search website, under Google’s Privacy Policy. A web-search link is not a verified practice website. Patient portals and office websites have their own policies.
Ask Next Up
Questions entered into Ask Next Up stay in session memory and are not stored with a remembered plan or sent to an AI service. The feature matches common topics in your text to prewritten summaries of pediatric references. All matching happens in this browser; the question is not sent to a server. It does not provide a medical assessment. Choosing “Copy for ChatGPT” places your question, your baby’s chronological age (when using a personal plan), and educational instructions on your clipboard. It does not include the profile name, exact birthday, sex, office details or saved question list. Opening ChatGPT alone does not transmit this text. If you paste it there, ChatGPT handles the conversation under your account settings and its policies. Avoid identifying or sensitive details. Reloading this page clears the draft.
Feedback
Feedback is sent only when you select Send feedback. The site stores your message, category, the app section you sent it from, submission time, and an optional email you choose to provide. It does not attach your account, baby profile, family records or Ask question. The site owner can read messages and optional email addresses through a private owner inbox; other parents cannot read them. An email lets the owner contact you but does not guarantee a reply. Feedback is retained separately from family records and is not removed by deleting your account. Please leave out identifying baby details, medical information and passwords. Feedback is not an emergency or medical support service. To limit spam, a keyed hash of your network address is stored in a counter with a one-hour limit window; expired counters are removed on later submissions; the raw address is not saved in feedback records.
Site operation
The hosting provider handles normal requests, including network metadata. The office lookup uses short-lived request counts to limit repeated searches. Next Up records first-party site counts: page or section names, the day, broad device category and broad referral source (such as Google or Direct / unknown). Page loads include opens and refreshes. To estimate unique visitors, this browser saves a random identifier in local storage for up to 400 days. The server saves only a keyed hash of that identifier with visit days and times. Recorded page views are grouped into visits, ending after 30 minutes without a recorded page view. Visit records contain that hashed browser identifier, start/last-view times, broad referral/device categories, page-view counts and whether an earlier visit was observed. Per-visit counts of fixed section names let the owner see which sections browsers reopen on later visits; they never include record contents. Returning to an open tab after 30 minutes can record another view of its current section. Refreshes within an active visit count as page views but do not create another visit. Returning visitor figures recognize browsers, not verified individual people or cross-device accounts. Each browser counts separately; clearing browser data or using another device can create another visitor. No third-party analytics or analytics cookies are used. A successful account signup can send the same identifier so we can calculate how many tracked visitors create accounts. Successful login and account recovery, and signed-in page views, can associate this browser identifier with the account creation time to distinguish existing members from visitors eligible to sign up. Browser conversion analytics retains the hashed browser identifier and registration/observation times separately from account records. Signup journey counts also use fixed steps such as opening or submitting the signup form; failed attempts use coarse categories, never the username, password or error text. Multiple signups from the same browser count once in conversion reports. To measure first saved actions and repeat use across devices, the server separately records a keyed hash of the verified account identifier, registration time, broad signup source, first saved profile/record times, and per-day counts of fixed action categories such as saving a feed, diary entry or Community post. It derives these categories only after a successful write; no baby details, diary/post text, photos or other record contents enter analytics. Raw account identifiers and account names are not stored in analytics. These statistics remain after account or family deletion, independently of private records. Browsers unable to save a browser identifier do not enter unique-browser or signup-journey counts, but can contribute page-load/view counts and opted-in, hashed account-action counts. Random event identifiers are hashed for one day to avoid counting retried requests twice. Aggregate counts, hashed visitor/signup statistics, signup journey steps and hashed account-action records are retained for approximately 400 days; active account cohorts keep their first signup/profile/record times, while inactive cohort hashes expire approximately 400 days after their last recorded action. Expired records are removed on later tracking or recorded action requests. Broad source categories can be derived from allowlisted source tags in a link, but full URLs, query strings and campaign identifiers are not recorded. Baby details, usernames, passwords, diary text, office searches and Ask questions are never sent to the statistics endpoint. The owner can see aggregate statistics and counts of currently registered accounts; this report does not include account names or family records. Use the site-usage setting in Sources & privacy, or below, to opt out on this browser. Do Not Track and Global Privacy Control also disable these counts. Opting out removes this browser’s visitor identifier; it does not delete already recorded statistics. Your opt-out preference stays in this browser. These reports are private to anyone holding the owner’s private stats access link. Same-site analytics requests include the secure login-session cookie when present so the server can confirm that an account already exists. Only keyed account hashes are saved in account-action analytics; raw account identifiers, names and hashes are not returned in owner reports. Existing members on a new browser while logged out may remain unrecognized until login. The server uses short-lived request limits based on network addresses, without storing those addresses in analytics records. Do not enter patient details into the office search.
Sharing Next Up
The Share Next Up link opens the public site with a fixed referral tag. It includes no family identifier, invitation code, baby details or private records. You choose whether and where to send it. The device share menu receives only generic site text and this public link. Site counts may record opening sharing or copying the link as fixed categories; they do not record recipients or sent messages.