Your household, your choices

Privacy

Updated September 10, 2026

This notice describes the Kindreday pilot operated by Signal Forward LLC. Contact daniel@signalforward.ai with questions, access requests, or deletion requests. Do not include passwords, PINs, or connection codes in email.

Information the dashboard uses

The dashboard stores adult sign-in information, household membership, names and settings entered by parents, device authorizations, chores, completion and approval records, allowance and goal records, and meal plans. Parents may enter children’s names and routines; children do not create sign-in accounts.

If you connect a calendar, the dashboard reads event information such as titles, times, and locations from the connected account. It stores an authorization credential for continued read-only access and caches calendar results to keep the schedule available during provider outages. Google access is limited to the calendar permission requested in the consent flow; the dashboard does not request Gmail access.

How information is used and shared

Information is used to display and manage the household’s schedule and routines. Household members, paired devices, and services authorized by a parent can access information permitted by their role or capability. Calendar titles are visible by default; turning titles off displays busy blocks instead. The underlying calendar information can remain in cached source data.

AWS hosts the dashboard, sign-in service, stored data, credentials, operational logs, and backups. Google and Microsoft process their respective calendar sign-in and API requests. Operational records are used to investigate errors and maintain the service.

If you use the optional assistant, your conversation and relevant tool results, which can include calendar information, are processed by the configured assistant service: AWS Bedrock (using GPT-OSS 20B) or Anthropic (using Claude). Each deployment uses one configured service; requests are not automatically retried with the other provider. Spoken responses use AWS Polly. Browser speech recognition may use the browser provider’s speech service. If a parent authorizes an external assistant or service, data returned to it is also handled by that service.

The dashboard does not sell household information or use it for advertising. Google user data is used for the user-facing calendar and assistant features described here, not to train general-purpose AI models. Kindreday’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Stripe (paid subscriptions). If you choose a paid subscription, Stripe receives your payment and billing information through its hosted Checkout and billing portal. We send a household identifier and selected plan to associate the subscription with your household. We store Stripe customer and subscription references, payment status, the billing contact you select, and your payment-terms acceptance. We do not send calendar contents, children’s chore records, or calendar credentials to Stripe. Full card details are handled by Stripe, not stored by Kindreday. Stripe also retains payment records under its privacy policy. Transactional subscription emails are described below.

Transactional email providers. AWS Simple Email Service or Microsoft Azure Communication Services processes the billing email address you select, service-notice text, and delivery-status information to send subscription notices. We use one configured provider for each send and do not automatically resend through another provider after an uncertain result. These emails do not include calendar content, children’s chore records, or calendar credentials. We retain delivery records and suppress addresses after permanent bounces or other adverse delivery feedback. Azure delivery reports that could not reach the app are retained in private Azure storage for up to 30 days before scheduled removal.

With whom we share Google user data

We share, transfer, or disclose Google user data to the following recipients for the purposes described below:

Your household and authorized services. We disclose Google calendar event information, including titles, times, and locations, to members of your household and people using its paired devices, subject to their access permissions and calendar title settings. If a parent authorizes an external assistant or service through a service grant, that service can receive Google calendar information returned by the calendar tools it is permitted to use. The recipient is the assistant or service the parent chooses; its own privacy policy also applies.

Amazon Web Services (AWS). We transfer and store Google calendar data, cached event results, and calendar authorization credentials in AWS infrastructure to host and operate Kindreday. AWS also processes operational records and backups. When the assistant uses AWS Bedrock, AWS receives your question, conversation context, and relevant calendar tool results to generate an answer using GPT-OSS 20B. These results can contain Google calendar event titles, times, and locations. This route uses the model hosted by AWS, not the OpenAI API. If you use spoken assistant responses, AWS Polly receives the response text to generate speech; that text can contain information from your Google calendar.

Anthropic. When the household assistant is configured to use Claude through Anthropic, we send your question, conversation context, and relevant calendar tool results to Anthropic to generate an answer. Requests using AWS Bedrock are not sent to Anthropic. These results can contain Google calendar event titles, times, and locations. The resulting answer is returned to your household. Calendar information is not sent to Anthropic merely because you connect a calendar or view Today or Week.

Google and browser speech providers. Google receives authorization and calendar API requests to provide the calendar connection. If you use browser speech recognition, your browser provider may process your spoken input; that input can include calendar information you say aloud. This is separate from the dashboard reading your calendar.

Signal Forward LLC. Signal Forward LLC operates the service and can access stored Google user data for authorized support and security troubleshooting. Human access to Google user data is limited to your affirmative permission for specific data, security investigations, or legal obligations, consistent with Google’s Limited Use requirements.

We do not sell Google user data or disclose it to advertisers, data brokers, or information resellers. We do not share or transfer it for purposes other than providing the features described in this notice, authorized support, security, or compliance with legal obligations. Google user data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models.

How we protect sensitive data

We use technical access controls and encryption to protect household information, including Google calendar data and authorization credentials.

Encryption in transit and at rest. The dashboard uses HTTPS with TLS to protect communication between your browser and the service, and uses HTTPS for Google authorization and calendar API requests. Household records and cached calendar results in Amazon DynamoDB, including its backups, are encrypted at rest. Calendar authorization credentials are stored separately as encrypted SecureString parameters in AWS Systems Manager Parameter Store, using AWS Key Management Service.

Authentication and household access controls. Adult accounts sign in through Amazon Cognito. The application checks household membership and permissions for protected requests. Paired devices and external services use revocable credentials with assigned capabilities; parent-only actions require parent authorization. Database access is scoped to the authorized household. Cloud service access uses AWS Identity and Access Management permissions, including permissions required to retrieve calendar credentials.

Connection controls. Hosted Google connections request read-only calendar access. Calendar credentials are used by the server and are not returned to the browser with calendar results. Parents can disconnect calendars and revoke paired devices or service access in Manage. Removing a hosted connection deletes its stored credential; Google account settings also allow you to revoke the app's access. Retained caches and backups are described below.

These measures reduce the risk of unauthorized access, loss, or disclosure; no online service can guarantee absolute security. Keep your parent PIN and device pairing codes private, revoke lost devices, and contact daniel@signalforward.ai if you suspect unauthorized access.

Your controls

Parents can remove calendar connections in Manage, revoke devices and services, manage household membership, export household data, and request or initiate household deletion. You can also revoke the application’s access in your Google or Microsoft account settings. Removing a connection stops future reads once active caches refresh; it does not delete events from the provider’s calendar.

Storage and deletion

Connected-calendar credentials are encrypted in AWS Parameter Store. Removing a hosted connection deletes its stored credential. Cached calendar snapshots are marked for expiry after 21 days; actual removal is asynchronous. Other household records remain until removed through the app or household deletion. Backups, operational logs, and older manually configured credentials can remain after removal from the active application. Contact Signal Forward LLC for a deletion request that includes these retained copies and any separate sign-in account.

Privacy requests and changes to this notice are handled by the pilot operator. Review this page before sharing information or enabling an optional integration.

Trial eligibility and retry protection

We keep a one-way digest of the verified parent email used to claim a free trial, the household identifier, and the claim date to prevent repeated free trials. This limited eligibility record remains after household deletion. We also keep minimal household-creation retry records to prevent duplicate setup after interrupted requests; these do not contain your PIN or raw household name. Contact daniel@signalforward.ai with questions about these records.