Privacy policy

What the application does

The journal captures and edits boat time-lapses. Only when the owner explicitly initiates an upload does it send a selected, completed video render and its title and description to Google/YouTube using YouTube API Services. Uploads go to Adventures by Moonlight and are always Private. The owner reviews them and changes their visibility manually in YouTube Studio.

Google permissions and their purpose

• Upload videos (youtube.upload): send the selected video and metadata to the owner’s YouTube channel.
• Read YouTube account information (youtube.readonly): read channel information to verify that the authorized destination is Adventures by Moonlight.

The application uses the read permission to check the destination channel. It does not provide a public Google sign-in service on this website.

Data handled and where it is stored

• Selected video files and metadata: completed renders, titles, and descriptions are handled on the Home Assistant server. The selected video and metadata are transmitted to Google/YouTube for an explicitly initiated upload.
• Channel identity: the channel identifier and information returned by Google are used to verify the destination.
• Authorization credentials: OAuth client credentials and refresh tokens are stored in Home Assistant’s private application storage. Short-lived access tokens are held in server memory. Any separately downloaded client or authorization files remain under the owner’s control.
• Upload records: upload state, progress and resumable-upload checkpoints, and the resulting YouTube video identifiers are stored on the Home Assistant server so uploads can be tracked and recovered.

The public website does not receive or store the uploader’s Google credentials, video files, or upload records. Those belong to the separate Home Assistant application. Home Assistant backups may contain stored credentials and upload records.

How information is used and shared

The application uses this information to authorize access, verify the destination channel, perform owner-initiated uploads, and show or recover upload status. It does not sell this information or use it for advertising. Video content and metadata are shared with Google/YouTube to carry out the upload; token exchanges and channel verification also send the information needed for those requests to Google.

Google/YouTube processes information under Google’s Privacy Policy. Use of the application is subject to YouTube’s Terms of Service.

Retention and removal

There is no automatic deletion period for the application’s stored authorization credentials or upload records. They remain on the Home Assistant server until the owner removes them through server administration. Video files remain subject to the owner’s management of the journal’s local media. Completing an upload does not automatically delete the local video.

To request access to or removal of information held by the owner, email mr.erik.sharp@gmail.com, describing the information concerned. Removal is handled manually by the owner, including the relevant local files or application records and any retained backup copies. The application does not offer an in-app disconnect or credential/upload-record deletion control.

Separate client or authorization files retained on the owner’s desktop must be removed there as well. Removing local records does not delete copies already uploaded to YouTube. The owner can delete uploaded videos separately in YouTube Studio.

Revoke Google access

The owner can revoke the application’s access through Google Account permissions: select Moonlight Camera Journal and remove its access. Revocation stops future authorized access once Google applies it; it does not itself remove the locally stored credentials or upload records, and does not delete videos already uploaded to YouTube.

Local removal requires the manual procedure above. YouTube video deletion is managed separately in YouTube Studio. A new Google authorization is required to reconnect after access is revoked.

Website cookies, analytics, and hosting

These informational pages do not set application cookies, use browser storage, include analytics or advertising scripts, or embed YouTube players. Following an external link opens a service with its own privacy practices; following the contact link opens your email application.

The pages are hosted by Cloudflare. To deliver and protect the website, Cloudflare processes request information such as IP addresses, requested URLs, timestamps, and browser/request details, and may retain operational or security logs under its own practices. Cloudflare security features may set necessary security cookies when used. No fixed hosting-log retention period is promised by this policy. See Cloudflare’s Privacy Policy.

Policy updates and contact

Changes to the application’s data handling will be reflected here with an updated effective date. Contact Erik Sharp at mr.erik.sharp@gmail.com with questions about this policy.