Privacy information

What SteadySteps includes

SteadySteps includes a website and a mobile family app. The intended core is a small communication loop: an adult manages a family account and a child can use parent-chosen visual choices such as asking for help or space.

Information the current systems may hold

Adult accounts, security, and devices

• Adult name, email, profile image, sign-in provider, verified identity IDs and timestamps, account role, plan or entitlement, and website account links.
• Authentication sessions, OAuth tokens, password hashes, parent-PIN verifier and salt, device binding, pairing codes, notification permission, app/build information, and APNs or FCM notification tokens.
• Content-free rate-limit, idempotency, security, and abuse-prevention records.

Child profiles and legacy demographics

• A child name or nickname, visual theme, parent-selected My Voice choices, speech and review preferences, assignments, an optional token-mode setting that defaults off, historical token balances, and legacy reward settings.
• The website database schema can contain legacy exact birthDate, gender, and diagnosisNote fields. The current website no longer asks for or displays exact birth date or gender, and it does not collect a diagnosis note. Those columns have not been dropped and any legacy values have not yet been removed; a reviewed migration, retention decision, and deletion verification are still required.

My Voice, Help, and family connection

• Child-linked My Voice or connection choices, help requests, optional messages and activity context, caregiver responses, delivery/status state, and lifecycle times.
• Optional adult-to-child nudges and two-household or drawing concepts exist in source but are not approved core features. Shared drawing is blocked pending access rules, limits, and deletion controls.

Routines, family media, and progress

• Routines, schedules, stories, tests, steps, questions, assignments, rewards, stickers, tags, gallery images or audio, and parent-created family content.
• Completion receipts, dates, activity identifiers or titles, token awards, progress, answers, and scores. These optional or legacy records require a reviewed retention and export plan.
• Adult-selected educational-video favorites and viewing progress. YouTube playback may also send the viewer's network, device, and video-request information to YouTube when playback is enabled.

Optional behavior and ABC records

Gated website and mobile tools can hold parent-entered behavior labels, observation dates, notes, context, support tried, outcome, and legacy ABC or perceived-function fields. These records are not needed for the core communication pilot, are not a diagnosis, and must not be used to claim a revealed cause or treatment recommendation.

Adult messages, providers, bookings, and payments

• Gated adult-to-provider conversations can contain message text, participants, and read times.
• A provider application can include legal and display name, contact details, credentials, certification and jurisdiction information, license information where required, background-check status, eligibility-review evidence, payout status, and specialties.
• Gated booking and subscription records can include adult and provider IDs, an optional child link, availability, jurisdiction, free-text note, price and currency, Stripe customer/payment/session IDs, booking lifecycle, and a meeting link.

Video, AI, and generated media

• Family or provider video can involve participant identity, room and session state, join/leave evidence, short-lived meeting credentials, and device/network media transport. Video remains separately gated.
• Optional AI or media tools can process a parent prompt or speech text, generated images or audio, moderation and report data, provider request metadata, and cost/safety evidence. Child-facing AI is deferred pending review of content, retention, training terms, consent, and deletion.
• Optional sticker search can send a parent's search query and network request information to GIPHY.

Adult-selected email

The gated email lifecycle can hold an adult email address, educational topics, weekly or monthly frequency, consent version and times, confirmation-token hash, suppression evidence, and a separate provider/service-marketing choice. No production email provider is selected. Email choices must not be inferred from child messages, diagnosis, distress, refusal, activity, behavior records, media, or household conflict.

Support, administration, diagnostics, and community

• Adult-requested support, issue reports, deletion requests, and any details the adult includes. Do not include a child's diagnosis, photo, video, audio, My Voice or Help message, routine, schedule, behavior, custody, location, or event details in an initial support request. Also do not send passwords, sign-in codes, authentication tokens, payment details, or meeting links.
• Narrow audit, moderation, admin-report, reversible-delete/trash, reliability, crash, platform, and security records. Access, retention, and family-visible history still need stronger controls.
• The gated adult community can hold threads, posts, reports, moderation decisions, and actor/reviewer IDs. It remains off pending governance, staffing, child-PII response, retention, export, and deletion review.

Why information is used

• To authenticate an adult, authorize the intended family or device, and protect accounts from abuse.
• To provide the parent-selected child experience, deliver and close a child-initiated communication, and show assigned family content.
• If a separately reviewed feature is approved and enabled, to provide the optional action an adult intentionally chooses, such as notifications, media, record keeping, provider contact, booking, payment, email, or support.
• To operate, secure, troubleshoot, moderate, and improve reliability using the minimum practical operational evidence.

Uses SteadySteps prohibits

Current product policy prohibits selling family data or using child data for advertising. The current source has no third-party advertising integration. Child messages, Help or My Voice events, distress, refusal, silence, diagnosis, behavior or ABC records, progress, media, and household conflict must not be used for ads, provider lead scoring, sales email, service marketing, or individualized pricing. Repository evidence cannot by itself prove every production or organizational practice; external privacy and legal verification remains required.

We also prohibit using child completion records to rank siblings or caregivers, behavior entries for automated diagnosis or psychiatric inference, household access history to compare caregivers, or family content for AI training or product analytics without a separately reviewed policy and explicit choice.

Who can see or process information

• The signed-in adult and an authorized child/device can see the parts of the family experience intended for them.
• A provider can see a conversation, booking, or child-scoped record only when that separately gated feature and an appropriate access relationship are active. A provider role alone does not grant family access.
• Authorized support, security, or moderation personnel may need limited access for a specific request, safety issue, or incident. Purpose-bound, time-bounded access and complete audit procedures are still open work.
• Service providers process information needed to run the selected service. Gated community content may be visible to its participants and moderators if that feature is approved and enabled.

The current website child model links one adult account to a child and does not yet provide a reviewed two-household permission model. Do not treat the current model as proof of custody or permission to expose one household's private context to another.

Service providers and external systems

This is a source inventory, not a verified production subprocessor list. The final production host, enabled services, data flows, contracts, regions, retention, and security evidence must be confirmed before launch. A dormant integration receives no authority merely because its code or environment variable exists.

• Google Firebase and Google Cloud can provide mobile authentication, Firestore, Realtime Database, Storage, Cloud Functions, notifications, and Crashlytics diagnostics when configured.
• Apple and Google Sign-In can process adult identity assertions when configured and selected by an adult.
• Postgres stores website records. The production database host, region, backup, and security evidence are not selected or documented in this repository.
• Stripe is present for gated adult subscription, booking-payment, and provider-payout code. Public checkout is off by default; configuration alone does not enable it.
• Daily is the intended video transport for gated family or provider calls. Those public services are not currently offered, and recording, chat, screen-sharing, contracts, and configuration still require proof.
• Google Gemini and OpenAI are present for optional AI or generated-media source workflows; child-facing use is deferred and no production child-data flow is asserted here.
• GIPHY can provide optional sticker search, and YouTube can provide optional educational or reward video playback. These child-content surfaces are not approved in the current default public offer.
• A production email/SMTP provider has not been selected or connected. Public signup and delivery remain off pending processor, abuse, domain-authentication, and suppression review.

Your choices

• Use a child name or nickname. The current website does not require exact birth date, gender, or diagnosis.
• Choose My Voice options and accessibility preferences with the child. Optional notifications, photos, camera, microphone, video, AI, email, community, provider, behavior, and paid tools should remain off when they are not wanted or not approved.
• Change device permissions in system settings. Delete supported family content in the app where a delete control is available.
• Adult email requires confirmation of the exact topics and frequency. Service marketing is separate, and a suppression link stops all SteadySteps email until a fresh request is confirmed.
• Use the iOS deletion-request flow or the published support email to initiate an account, access, correction, deletion, or export request. Neither path confirms receipt, identity verification, fulfillment, export availability, or completion.

Deletion, export, and retention limitations

SteadySteps does not yet have a complete self-service export or a proven end-to-end deletion process across Firebase Authentication, Firestore, Realtime Database, Storage, Postgres, local device state, backups, logs, and external processors. Some in-app delete controls and an iOS deletion-request flow exist, but a request or database cascade alone is not proof that every copy, derived asset, backup, token, or vendor record was removed.

Exact retention periods and legal-hold rules are not yet approved. Security evidence and minimal newsletter suppression records may need limited retention to protect accounts and honor opt-outs. Legacy child demographic fields remain a known removal gap. The published support address starts a request only; this repository does not prove staffed mailbox coverage, a response time, identity-verification operations, fulfillment, receipts, or status tracking.

Children, sensitive details, and professional care

SteadySteps is designed for adult-managed family use, but the current code can hold child-linked and highly sensitive information. Avoid entering medical, diagnosis, trauma, custody, medication, crisis, meeting-link, or treatment details in free-text fields unless a separately reviewed service clearly requires them.

SteadySteps is not emergency care, medical advice, diagnosis, treatment, or a replacement for AAC or professional support. This review draft does not claim compliance with HIPAA, COPPA, FERPA, state privacy law, custody law, or professional-records requirements. Those questions depend on the final operating model, users, jurisdictions, contracts, safeguards, and external legal review.

Contact

To initiate a privacy, access, correction, deletion, export, or support request, you may draft an email to support@steadysteps.app. Email is not emergency or clinical crisis support, and there is no promised response or completion time. Do not send passwords, sign-in codes, authentication tokens, payment details, meeting links, or a child's diagnosis, photo, video, audio, My Voice or Help message, routine, schedule, behavior, custody, location, or event details.