Your information
Privacy policy
Effective November 6, 2026
Finn is a privately operated tool for personal family use. This policy explains what it accesses, why it uses that information, and how you can stop access or request deletion.
Who operates Finn
Finn is operated by Adam Lesinski. For support, privacy questions, or deletion requests, contact the operator through your existing private family contact channel. This public informational website is separate from the privately hosted Finn application.
Information Finn accesses
- Google authorization: the OAuth client ID and client secret, a refresh token supplied by Google, and short-lived access tokens. Finn does not receive or store your Google password.
- Daycare photos: still-image files and associated identifiers, original media URLs, filenames, media types, and available dates from the authorized 1Core account. The initial photo sync may import the account’s available still-photo history.
- Photo sync records: the Google Photos album ID and link, imported source identifiers, corresponding Google media identifiers, source dates where available, and records of pending operations.
- Other enabled Finn features: daycare and Huckleberry account credentials, child/account identifiers, nap, feeding and diaper activity, care settings, and device identifiers or notification tokens needed for private family notifications.
- Operational information: service status, error categories, and access or diagnostic logs generated by Finn or its hosting providers.
How Google access works
The photo integration requests https://www.googleapis.com/auth/photoslibrary.appendonly. Finn uses this permission to upload daycare photos, create a destination album, and add uploaded photos to that album in the Google account you choose. It does not request permission to read your existing Google Photos library.
Authorization occurs on Google’s website. The one-time setup uses a temporary localhost callback, state validation, and PKCE. The stored refresh token permits unattended access until it expires or is revoked.
Why information is used
Finn uses information only to provide the family features you enable: saving daycare photos, keeping care activity in sync, delivering family notifications, maintaining settings, preventing duplicate imports, and diagnosing service failures. Photo metadata is not used to build advertising profiles.
Where information goes
| Provider | Purpose |
|---|---|
| 1Core | Authenticating the authorized daycare account and retrieving its activity and photos. |
| Google Photos | Storing uploaded photos in the authorized Google account and Finn-created album. |
| Google OAuth | Account consent and token issuance or renewal. |
| Huckleberry | Reading or recording care activity when that integration is enabled. |
| Firebase Cloud Messaging | Delivering device notifications when enabled. |
| Anthropic | Interpreting free-text care notes when the optional note-parsing feature is enabled. The photo sync does not send photo files to this service. |
| Hosting and network providers | Running the private application or serving this informational website; providers may process connection and access logs. |
These providers handle information under their own terms and privacy policies. Finn does not sell personal information or use Google user data for advertising. Finn does not use Google user data to train AI or machine-learning models.
Album sharing is controlled in Google Photos. People you invite or give a sharing link to may be able to view, save, or further share photos according to your Google Photos settings.
Storage and protection
The operator-controlled Finn server stores configuration, credentials, and sync records. OAuth credentials and photo sync state are written to files with owner-only permissions. Access tokens are held in process memory. Finn uses HTTPS for supported provider connections; application access is restricted through the operator’s private network.
Original photo bytes are handled in memory during transfer. The photo sync does not maintain a permanent local photo library. Any investigation captures or manually saved samples are separate operator-managed files and must be protected or deleted separately. No security measure can guarantee absolute protection.
Retention and deletion
OAuth credentials are kept until the operator removes or replaces them. Sync records are retained while needed to reuse the destination album and avoid duplicate uploads. Other account data and logs are retained according to the operator’s configuration and operational needs. Backups, if configured, can retain copies until their retention period ends.
To stop access, disable Finn’s sync and remove its authorization from your Google Account connections. Revocation does not delete photos already uploaded. You can delete those photos and the album directly in Google Photos. Removing a photo from an album may leave it in your Google Photos library.
To request deletion of Finn-held credentials, sync records, or other personal information, contact the operator through your existing private family contact channel. The operator may verify that you are entitled to make the request. Deleting local sync records without disabling sync can cause photos to be imported again. Provider-held copies and recipient copies must be managed separately.
Family and child information
Finn is operated by adults for their family. It may process child-related daycare photos and care activity at the direction of an authorized adult. It is not a service for children to create accounts or independently authorize access. Only connect accounts and share photos you are entitled to access and use.
This website
This site contains static informational pages. It has no registration form, advertising, analytics scripts, tracking pixels, or application cookies. The hosting provider may still record standard technical information such as IP address, requested path, and request time when serving a page.
Google API data commitments
Finn’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Changes and contact
This policy may change when Finn’s features or data handling change. Updated versions will show a new effective date on this page. For questions or requests, use your existing private contact channel with the operator. No public email address is published on this site.