Scope and operator
Ron Heft operates these personal homelab services. Contact ron@ronaldheft.com with privacy questions or requests. This policy covers services that link to it or explicitly identify it as their policy. It does not replace the policies of independent software publishers or external providers.
Information and purposes
Depending on the service and features you use, information can include account identifiers and email addresses; content you upload or connect, such as documents, tasks, and calendar events; settings; and credentials or authorization tokens needed for an integration. Support messages contain the information you choose to send.
Services and infrastructure may process technical records such as IP addresses, request times, browser information, authentication activity, and errors. These records support operation, troubleshooting, and security. Applications may use cookies or similar storage for sign-in and preferences.
Information is used to provide the requested functions, maintain access, synchronize connected services, respond to requests, and protect the services. These are personal services, not an advertising business. Ron does not sell personal information or use it for targeted advertising.
Hosting and external services
This information site uses Cloudflare Pages. Cloudflare processes network requests to deliver and protect it; see Cloudflare’s privacy policy. The site adds no analytics scripts, advertising, or tracking cookies.
Application data is handled by the relevant homelab service and the providers used for its features. Connecting an external service can transmit information to that provider. For example, a synchronization feature sends content to a destination you select, and an explicitly used AI integration can send its inputs to the configured provider. Data is not necessarily confined to the homelab or end-to-end encrypted. Review the relevant feature before connecting sensitive information.
Information may be disclosed where required by law or necessary to address abuse or protect security. The stricter Google-data limitations below control how Keeper’s Google data is used and disclosed.
Keeper Homelab and Google data
Keeper Homelab is Ron’s personal self-hosted calendar synchronization application. It is independent of the hosted keeper.sh service. Its ordinary calendar synchronization connects directly to calendar providers rather than routing calendar data through keeper.sh.
Access and use
Keeper accesses Google account identifiers and email addresses, calendar lists and metadata, and event data for connected calendars. Depending on the event, that data can include titles, descriptions, locations, dates and times, recurrence, and other event metadata. Basic profile information is also used if you choose Google sign-in.
Calendar permissions support listing and selecting calendars, reading events, and creating, updating, or deleting synchronized destination events. Access is used for the calendar functionality you configure. The permission requested can be broader than the operations needed by a source-only calendar.
Storage and sharing
Keeper stores account and calendar records, synchronization settings, event data, and authorization tokens in its database. Tokens permit continued provider access until they expire or are revoked. Event details may be copied to selected destination calendars and become accessible to people who can access those calendars. If you enable a calendar feed, its URL can grant access to its contents; share it accordingly.
Google data is not sold, used for advertising, or used to train generalized AI models. Keeper’s Google data is not provided to other homelab AI features merely because they are covered by this shared policy. Transfers are limited to providing the user-facing calendar features you request, security purposes, or legal requirements as permitted by Google’s policy.
Keeper Homelab’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google data is limited to cases that policy permits, such as your affirmative consent to inspect specific data for support, necessary security investigations, or legal obligations.
Revocation and deletion
You can disconnect connected accounts in Keeper and remove Keeper’s access in your Google Account. Revoking access prevents future authorized Google API access; it does not automatically remove data already stored locally, copied to another calendar, or included in a backup.
Email ron@ronaldheft.com to request deletion of stored account data, tokens, or calendar data. Ron will confirm the scope, handle deletion from the systems he controls, and explain any remaining copies or retention constraints. Destination calendars and independent providers may require separate deletion. Do not assume that disconnecting alone deletes every stored credential or copy.
Retention, security, and your choices
Retention varies with the service, its settings, operational needs, and backups; there is no single automatic deletion period across the homelab. Data may remain until it is removed through the service or a deletion request is completed. Backup copies can outlast deletion from the live service. Ask about retention before providing information that requires a specific deletion deadline.
Access controls and other safeguards are used to protect the services, but no system guarantees security or availability. These services are not a substitute for your own backup. You can limit information you provide, stop using a feature, revoke external access, or contact Ron to request access, correction, or deletion of your information. Identity verification may be needed before acting on a request.
Changes and sources
Material changes will be described here with an updated date. If a change would introduce a new use of Google data, the disclosure and any required consent will be updated before that use begins.
Adapted and substantially shortened from Automattic’s Privacy Policy, with changes for Ron Heft’s personal services. This policy is licensed under CC BY-SA 4.0. See sources and licensing.