Website Privacy

Last updated: November 13, 2026

Asclepius Family OS Inc., a Delaware corporation, operates the FamilyOS website. This notice covers website visits, beta-interest registrations and messages you send us. It is not the FamilyOS app’s privacy notice.

Who registration is for

The interest form is for adult parents and caregivers using their own email address. Do not submit a child’s email address or information about a child. Registering interest means consideration for a closed-beta invitation. It does not create an app account, provide access or guarantee an invitation.

Earlier and new registrations

New registrations are kept in a separate system. Earlier registrations are not automatically moved into it, deleted or excluded from possible beta invitations. We retain the earlier list separately for possible beta invitations, subject to the retention rule below. Before using that list for invitations, we check removal requests. An earlier registration does not automatically enroll you in product updates.

The two systems do not automatically synchronize registrations or removal requests. If you registered earlier and now submit this form, you may have a registration in each system. A removal link applies only to the list identified on its confirmation page. You can ask privacy@familyosai.com to handle a request concerning both lists.

What the new form records

We record your email address after removing surrounding spaces and converting it to lowercase, the signup date and time, and the adult own-email declaration and its wording version. We also keep status and version information needed to manage the record and honor removal requests.

You may choose an optional category to tell us how you heard about FamilyOS. Other is a category, not a free-text field. New registration records do not include a country value or the referring page. This does not mean those details are absent from earlier records or hosting-provider information.

The product-updates checkbox starts unchecked. If you select it, we record the requested purpose, exact wording and version, signup time and website source. The choice does not verify age, identity or mailbox ownership and does not by itself establish legal consent. Submitting this form again does not change preferences already recorded in the new system, reactivate a held record or reverse a removal recorded there.

Earlier records and messages

Earlier forms collected an email address and signup time, with country code and referring-page information where available. Earlier spam-prevention processing also used IP information. Updating the website does not automatically erase earlier records, logs or other copies.

If you email us, we receive your email address, message and any information you choose to include, and use it to respond. Please send only what is needed for your inquiry and do not include information about children or other people.

How we use the information

We use beta-interest information to manage interest in FamilyOS and consider people for invitations. Optional product updates are limited to substantive beta or product milestones. They have no fixed mailing schedule, do not cover unrelated promotions and do not affect beta consideration.

For new registrations made after acknowledgement processing is enabled, we attempt to send one acknowledgement through Resend. It confirms receipt of beta interest, not an invitation, account or guaranteed access. Messages may wait in a pending list when sending is paused or limited. Delivery is not guaranteed. Earlier registrations and repeat submissions do not trigger this email. Selecting the updates option records a request, not a verified subscription. When verification processing is enabled, we attempt to send a separate verification email through Resend only for new registrations choosing updates. Earlier requests remain unverified and are not automatically sent verification emails. A link expires 24 hours after it is issued for a sending attempt; delivery may be delayed and is not guaranteed. Opening the link does not verify the address: you must explicitly confirm. Verification does not itself send a product update. Product-update campaigns remain disabled.

An authentic expired verification page can offer a button to request a replacement email when this feature is enabled. There is at most one replacement request per rolling 24 hours and three total attempts including the original. A replacement is not available while an earlier attempt is pending or a later link remains valid. A request queues an attempt; it does not confirm sending or delivery. For a missing message, an unavailable replacement or a failed link, contact privacy@familyosai.com. Do not send us verification or unsubscribe links.

Hosting and spam prevention

Cloudflare provides the website, registration infrastructure and storage. In the new service, we process the request IP address to create a keyed identifier for a separate spam-prevention counter. The raw IP address is not stored in that counter or the registration record by this service. The derived identifier is not anonymous.

The rate budget uses a 60-second window. Expired counter rows are cleaned during use and by scheduled cleanup. Cleanup can be delayed or fail, so this is not a promise that every copy is physically deleted after exactly 60 seconds. The service also keeps limited diagnostic counts without contact information or individual identifiers.

Hosting services process technical request information separately. A removal link includes information used to identify and authorize the request, which the hosting service processes. The new registration service’s limited records do not describe all hosting information.

Earlier welcome-email processing used Resend when a message was sent; Resend received the recipient’s email address and email content. Earlier code could also record the recipient’s address and provider error when sending failed. Historical provider and log copies may remain. Google Workspace provides inbound email routing, including the privacy contact.

The website files we publish load scripts, styles and images from this website and do not include externally hosted fonts, social-media widgets or a video walkthrough. Cloudflare hosting may also process technical usage and performance information, including through its website analytics features. Email links open your email service; they do not submit messages through this website.

For a new-registration acknowledgement, Resend receives the recipient's email address and message content, including its new-list removal link. We keep limited pending and sending-status records linked to the registration, including event identifiers, a message fingerprint and any provider acceptance identifier, to manage pending acknowledgements and prevent duplicate attempts. Those identifiers are not anonymous. Our application does not log message bodies or addresses for this sending path. Provider and infrastructure records may still exist. Separate hosting, access, security and operational records may still be processed by Cloudflare. Logging is enabled on the separate Workers retaining earlier registration and shared relay functions; that does not establish that a particular request was logged.

Deleting an active registration does not itself delete hosting logs, provider-held mail records or backups. Those records are subject to the relevant provider’s retention and deletion controls. We have not verified a single retention period or immediate-deletion mechanism covering all such records and do not promise one. For copies we control, we apply the purpose-based retention and review rules below.

For update verification, Resend receives your email address and message content, including verification and update-only unsubscribe links. We keep verification status tied to the current update choice and limited processing records, including keyed identifiers, link issuance information, attempt outcomes and provider receipts. These identifiers are not anonymous. Hosting services process the verification and unsubscribe link requests. The provider-copy and retention limits above also apply.

Retention

For both earlier and new beta-interest registrations, we keep contact details while a beta-invitation decision is pending. After that decision or the end of consideration, we keep details needed for product updates only if you separately requested them in the new system and verified your email for the current choice. An unverified request does not extend retention. We stop using the details for updates when you withdraw that choice or the update purpose ends. If no active purpose remains, we remove ordinary contact details; limited suppression and other records described below may remain.

We keep only what is necessary to honor removals, handle a specific incident or meet a legal obligation. Access to that information is restricted, and we review it when that purpose ends. Any unresolved retention exception is referred to Chris Rose for a decision. These are manual review triggers, not a promise of automatic deletion at a fixed time.

Removal and update choices

To ask about your information, request removal from either or both lists, or withdraw a product-update request, email privacy@familyosai.com.

A valid new-system removal link asks for confirmation before changing the new-system record. Full removal removes its active beta-interest information and saved update choice. An update-only unsubscribe asks for explicit confirmation, withdraws the update choice and verification, and leaves pending beta interest in place. If beta consideration has ended and no other active purpose remains, ordinary contact details are removed; limited suppression and processing records described in this notice may remain. Neither action automatically changes an earlier registration in the old list.

After full removal from the new system, a limited suppression record prevents an ordinary repeat submission from recreating that registration. It uses a keyed identifier derived from your email, together with status and version information. It does not keep the email address, referral answer, update choice or child-status flag in that record. The identifier can still be linked to you and is not anonymous.

An earlier removal link asks for confirmation before requesting deletion from the old list. It does not remove a separate registration in the new system. An acknowledgement from the old store does not establish immediate deletion at every location. If a link fails or the result is unclear, contact privacy@familyosai.com; a failed link is not confirmation of removal.

Removing an active registration does not automatically erase downloaded lists, logs, backups or provider copies. Those copies require separate handling under the retention rule above. Restoring a backup must not reactivate removed registrations.

Accidental child submissions

Do not submit information about a child. If we learn that a submission came from a child, we will not use the information or contact the child. We will restrict access and remove working records and controlled copies where possible. Provider logs and backups remain subject to the relevant provider’s deletion limits. Restoring a backup must not reactivate a removed registration. This website notice does not describe the app’s child-privacy practices.

Contact

Asclepius Family OS Inc., a Delaware corporation
Privacy and removal requests: privacy@familyosai.com