INITIALIZING MAJESTIC MADE SYSTEMS...

CONCEPT ONLY · TARGET CLOUDLESS DESIGN

Your baby's data. On your phone. Period.

Tender Days proposes fast feeding, diaper, sleep, growth, and milestone logs, with a target design for partner sharing over local Wi-Fi. The architecture and sharing behavior have not been implemented or validated.

Website privacy policy

Concept research list. Any testing program, platform support, or launch timing will be announced only after implementation and review.

9:41● ● ●

TODAY · ELLA · 4 MO

Daily Log

7 feeds · 6 diapers · 14h 22m sleep

🍼

FEED

💧

DIAPER

🌙

SLEEP

✎

NOTE

LAST FEED · 47 MIN AGO

Left breast12 min

Right breast9 min

Next reminder10:55 AM

01 · THE PROBLEM

The 3am notebook, the 3pm pediatrician, and the parent who has no idea what happened on the last shift.

Tracking a newborn is four jobs that don't fit into one tool: logging in seconds at 3am, handing off to your partner, plotting growth over months, and answering a pediatrician's questions from twelve weeks ago. Tender Days is the four-button log that does all four — and never tells a server about any of it.

The nightstand notebook

Last entry was 4 hours ago. You're guessing whether the next feed is in 30 minutes or 90. The handwriting from 3am is unreadable.

The cloud baby app

Their privacy policy reserves the right to share with "analytics partners" and "service providers." Your baby's feed schedule is being modeled.

The pediatrician question

"When was her last cluster feed?" You scroll back through three days of mixed notes, bottle photos, and a half-written sleep log.

The other parent

They took the 3am shift. You wake up and have no idea what happened — when she ate, for how long, which side, whether the diaper was a blowout.

02 · PROPOSED CAPABILITIES

One app. Three jobs. Zero data leaving your phone.

Tender Days is structured around the three things new parents actually need: a log fast enough to use at 3am, a growth view the pediatrician will read in 30 seconds, and a way to keep both parents in sync without trusting a baby-app company with the schedule.

01 · DAILY LOG

Four buttons. The whole day.

Feed, Diaper, Sleep, Note — each one tap, optional detail. The home card always shows the last feed timer, today's diaper count, and sleep totals from midnight.

Feed: left / right / bottle, oz, duration
Diaper: wet, dirty, both
Sleep: tap to start, tap to stop
Note: rash, fever, fuss, milestone

02 · GROWTH & MILESTONES

The data the pediatrician asks for.

Weight, length, and head circumference plotted against WHO percentile curves on-device. Milestones logged with date and optional photo. One-tap Pediatrician PDF rolls everything into a front-desk-readable summary.

Percentile curves rendered on the phone
Milestone log: smile, roll, sit, walk, words
Pediatrician PDF — feeds + diapers + sleep + growth + milestones since last visit
No data leaves until you tap Share

SHIPS v1.1

03 · PARTNER PAIR

Both parents updated. No server in the middle.

Scan a QR code from your phone, point your partner's phone at it, pair confirmed. Phones sync directly over local Wi-Fi via Apple's MultipeerConnectivity layer. The other parent took the 3am shift — you see it before coffee.

QR-paired token in the Secure Enclave
Local Wi-Fi sync only — no relay, no account
Best-effort: syncs next time both phones share a network
Either parent can revoke the pair instantly

03 · PROPOSED SCREENS

Three views of the same log.

Tap a pillar to see the fields. Everything you see — every feed, every weight, every milestone — was typed in by you and lives only on your device until you choose to export or pair-sync it.

The four-button log designed for one thumb at 3am.

The home screen is four buttons and a summary card. Open the app, tap Feed, tap Left, swipe up to confirm — you're back to holding the baby in under three seconds. Optional detail (oz, duration, notes) only when you want it.

The summary card rolls up every entry since midnight. It's what your partner sees when they wake up, what you show the pediatrician's MA at the door, and what feeds the Growth tab over months.

Feed (L / R / bottle)
Bottle volume (oz / ml)
Feed duration
Last-feed timer
Diaper (wet / dirty / both)
Daily diaper total
Sleep start / stop
24-hour sleep ribbon
Free-text note
Milestone tag

Percentile curves rendered on your phone. Not on someone else's server.

Enter weight, length, and head circumference at each visit. Tender Days plots them against the WHO 2006 reference curves locally — no upload, no analytics ping, no growth data crossing the network. The PDF you hand the pediatrician is the only time anything leaves.

Milestones get their own row: date, name, optional photo, optional note. The Pediatrician PDF pulls feeds, diapers, sleep stats, growth points, and milestones since the last visit into one front-desk-readable summary.

Weight + percentile
Length + percentile
Head circumference
WHO 2006 curves on-device
Milestone log (dated)
Milestone photo (encrypted)
One-tap Pediatrician PDF
PDF range: since last visit
Export to Files, Mail, AirDrop
No cloud copy retained

The other parent took the 3am shift. You wake up already updated.

Partner Pair is the feature most cloud baby apps build by funneling everything through their servers. Tender Days does it without a server. One phone shows a QR code, the other scans it, both Secure Enclaves now hold a pair token. When the phones share a Wi-Fi network — your home, the in-laws', the pediatrician's waiting room — they exchange new log entries directly over Apple's MultipeerConnectivity layer.

No relay, no account, no cloud step. If you're on different networks, the new entries queue up locally and sync the next time you're both home. That's a deliberate trade — the cost of never trusting a server with your baby's data.

QR-paired bootstrap
Token in Secure Enclave
Local Wi-Fi sync
MultipeerConnectivity / Bonjour
No relay server
No account required
Best-effort: syncs when paired
Either-side revoke
Pair history hidden by default
Unscheduled research idea

04 · TARGET PRIVACY ARCHITECTURE

The concept avoids a MAJESTIC-hosted record server.

This is a design target, not a current technical claim. Storage, sharing, network use, backups, and deletion must be implemented and security-tested.

TARGET: NO BACKEND

The proposed design uses encrypted local storage without a Tender Days account or record server. This has not been implemented or security-tested.

TARGET: NO ANALYTICS

The concept excludes analytics, crash reporting, and usage telemetry. Any future binary must be verified before release.

TARGET: NO DATA BROKER

The plan is to avoid collecting baby records on MAJESTIC systems. Final data flows and platform backups remain subject to implementation review.

05 · PROPOSED PRICING

A $4.99 monthly or $34.99 annual model is being considered.

These are planning targets, not offers. Features, store pricing, trial eligibility, cancellation, refunds, and availability are not final.

MONTHLY

$4.99/mo

Full app, all four log types
Growth curves + milestones
One-tap Pediatrician PDF
Partner Pair (ships v1.1)
Unlimited children
Optional iCloud KVS backup

PROPOSED OPTION

ANNUAL

$34.99/yr

~$2.92 / MONTH

Everything in monthly
Proposed introductory trial, if the store offers it
Store checkout terms would control eligibility
No locked-in price is promised
Refunds would follow store policy

Competitor prices, privacy practices, and feature comparisons change. Any launch-page comparison will be revalidated against current public terms before release.

Joining the list requires no payment. Platforms, trial terms, and release timing have not been announced.

06 · CONCEPT QUESTIONS

The questions privacy-minded parents actually ask first.

Answers below describe intended behavior. They remain subject to implementation, privacy review, platform testing, and any future app-store review.

Would my baby's data leave my phone?

The target design keeps the log in encrypted local storage with no Tender Days account, analytics, or record server. Explicit PDF sharing and proposed local peer-to-peer sharing would be the intended exceptions. Those data flows still require implementation and security review.

What would happen if I lose my phone?

Backup and recovery behavior is unresolved. Platform backup and peer-to-peer recovery may be explored, but Tender Days will not promise recovery until a complete flow is implemented and tested.

How might Partner Pair work without a server?

The proposal exchanges a pairing token and syncs directly over local Wi-Fi. Exact key storage, discovery, revocation, conflict handling, and platform support remain research and have no committed version or release timing.

What if my partner and I are on different Wi-Fi networks?

The current concept would queue entries locally and attempt best-effort sync when both devices share a network. Whether that behavior is reliable and useful remains to be tested.

Why does this matter so much for baby data specifically?

Feed times, weight curves, sleep windows, and growth percentiles are biometric-adjacent data tied to an infant. Most cloud baby-tracking apps upload all of it to their servers and reserve broad sharing rights in the privacy policy with “service providers” and “analytics partners.” There is a reason the data-broker exposés around baby and women's-health apps keep happening. Tender Days's design assumes the only safe place for that data is your phone.

How might Tender Days be priced?

$4.99 monthly and $34.99 annual are planning targets, not offers. Features, trial eligibility, cancellation, refunds, and availability would be finalized and shown by the app store if Tender Days ships.

Would Tender Days require an account or social features?

The target design has no account, upload prompt, friend graph, or social feed. This remains a product requirement rather than a claim about an implemented app.

Who builds Tender Days?

Tender Days is built by MAJESTIC MADE LLC, an Alabama-based military-family software company that develops cloudless mobile apps including Lockbox, Tally, What We Own, Paws, Brassmark, and Pantry Clock. The founder is an active-duty military software developer separating in February 2027 to build MAJESTIC MADE full-time.

07 · TARGET PRINCIPLES

Built from a parent's needs, with a privacy-first target.

Privacy claims require evidence. Tender Days has no implemented app today; any future binary must prove the data flow and architecture described here.

TARGET CLOUDLESS ARCHITECTURE

Minimize the breach surface.

The proposal avoids a MAJESTIC-hosted baby-record backend. That architecture must be implemented and verified before it becomes a product claim.

OPEN POSTURE

Plain-English data flow.

Any future store privacy disclosure must match the tested binary. Tender Days has not been submitted to or approved by an app store.

Each proposed feature has a 3am reason.

The four-button log, last-feed timer, Pediatrician PDF, and Partner Pair are product ideas shaped by the founder’s family experience.

The waitlist gets Partner Pair first.

Join the concept research list. A testing program, supported platforms, and launch timing have not been announced and depend on implementation, privacy review, and store review.