Household syncing
Kindlane uses Google Firebase Authentication and Cloud Firestore to sign in and synchronize household data across devices. The newer household experience supports individual Google sign-in and invitations, and email sign-in on supported devices. Older families may still use an imported Firebase project configuration. Where synchronized information is stored depends on the configured household and effective Firebase security rules.
Synced information can include household schedules, lists, and app data you choose to share across your devices. Authorized members and devices in the same household may receive relevant data. Pass the Baton requests are intended for the sender and recipient, rather than every member. Child-owned devices are designed to show child-appropriate data and permissions; the visible interface is not independent proof that server-side authorization has been audited.
Important: Firebase access controls depend on the project's authentication and Firestore security rules. This page does not claim that every custom Firebase project has been audited or configured identically.
Browser accounts and calendar imports
The web app uses individual Google sign-in. Authentication is kept for the current browser tab session; Firestore data uses an in-memory cache. Closing a tab can require signing in again. Appearance, Home layout, phone navigation, Daily-list visibility and weather-unit preferences are stored in your browser for the signed-in person and household. Calendar visibility preferences are also local to your browser account. These settings do not change household membership or permissions. Resetting browser preferences preserves shared household information. Editing your household display name is a separate shared change.
Calendar files selected in the web app are parsed on your device. Imported event titles, dates, times, locations and the calendar name are then stored in the household’s Firebase data and shared with authorized household members. Imports are snapshots, not live subscriptions. You can remove an imported snapshot in the Calendar setup controls. Do not import a private calendar you do not want your household to see.
Information kept on your device
The Android app also stores device preferences locally, including display/profile settings and Settings PIN preferences. Some shared displays can use a household PIN, which differs from local appearance preferences. Device-specific choices are distinct from household data that syncs.
If you import a Firebase project configuration, information needed to reconnect that project is saved by the app on the device. Treat configuration files and sign-in credentials as sensitive.
Android permissions
- Internet and network state: used for syncing and internet-based features.
- Approximate location: optional, for weather location functionality.
- Calendar read access: used when the app opens a specific calendar event for editing; the permission is requested for that feature.
- Install packages: supports Android app installation and update-related workflows. Android controls installation approval.
Android may present permission prompts as you use a feature. You can review and manage permissions in your device's system settings.
Feedback and support
Bug reports, feature requests, and support questions submitted on the Kindlane feedback page are collected using Notion Forms and managed in a private Notion database, rather than through the Kindlane Firebase sync system.
Reports may contain the description, device details, contact email, and screenshots you choose to provide. Avoid sending passwords, security codes, Firebase credentials, or private information about children or household members.
External services and links
Some app features connect to third-party services, including Firebase, online calendar sources, and weather sources. Links to release downloads, guides and Notion feedback may open in your browser, where the respective service's policies apply.
For details on Google's Firebase processing and Notion's handling of form responses, review their published privacy policies. This page is a technical transparency overview, not a representation that those providers cannot access data processed by their services.
Questions, corrections or deletion requests
Use Feedback & Support for privacy questions or to request help identifying which configured Firebase project holds your synced information. Please do not submit credentials or other sensitive details through the public form.
Scope: This page reflects a review of the application code and Android manifest. A full production privacy policy should additionally verify retention/deletion processes, third-party service behavior, and the effective Firestore rules for each deployment.