Privacy policy
Application: home-server
Operator and sole intended user: Jesper Beerepoot
Last updated:
Configuration and testing are ongoing. This policy describes intended handling as integrations are implemented. Google authorization is outstanding, and recurring production briefing delivery is not yet enabled.
Information and purpose
With the owner's authorization, home-server is intended to read relevant Gmail messages and Google Calendar events for concise daily briefings, scheduling context and personal project continuity. Gmail and Calendar access will be read-only.
Selected Google Drive instructions, personal profiles, plans and training records will provide context for briefings and training-plan reviews. Training information may include the owner's recorded activities, progress, preferences and training constraints. Access should be limited to information needed for these personal features.
Processing, delivery and storage
Selected information is intended to be transferred to OpenAI for analysis, to the owner's Telegram destination for briefing or notification delivery, and to Google Drive for storage of briefing outputs and analysis history. These transfers are for the owner's authorized personal features.
Applicable OpenAI data controls must be verified before any Google user data is sent for AI processing. This verification has not yet been completed. Google API information, including derived information, must not be used to train generalized AI models.
home-server's use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Use is limited to the disclosed personal features, with transfers only as permitted by that policy and the owner's authorization.
Local protection and recovery
Private credentials and local job and delivery state stay protected locally on the Chromebook. Administrative access uses Tailscale. Recovery backups containing credentials must be encrypted. These public pages contain no application credentials or private records.
Retention and deletion
Long-term content is retained under the owner's control. Temporary files and logs will use bounded retention when implemented; no fixed retention period is asserted here.
The owner manages deletion across local files, Google Drive, Telegram and recovery backups, subject to the relevant providers' retention practices. Removing a local record does not automatically remove copies stored elsewhere.
Google authorization and revocation
The owner can revoke Google access through Google Account connections. Revocation prevents continued access through the revoked authorization; it does not delete previously saved files, analysis outputs, Telegram messages or backups. Those copies require separate deletion by the owner.
No sale or advertising
Personal data is not sold or used for advertising.
These public pages
These static information pages use no application cookies, analytics, JavaScript, trackers or external assets. The hosting provider may retain ordinary web-access logs.