Last updated: September 22, 2026
Who we are
Vic’s Hangout (vics.plus) is a personal hobby website operated by Justin (referred to below as “I” or “me”). This page explains what data the site — and the personal tools connected to it — handle, and how.
Questions or requests: jbev2007@gmail.com.
What the site collects
- Server logs. Like any web server, this site records basic technical information about requests — IP address, browser type, pages requested, and timestamps — for security and troubleshooting. Logs are kept short-term and are not used for tracking.
- Comments. If commenting is enabled on a post, the information you enter in the comment form (name, email address, and comment text) is stored, along with your IP address and browser user-agent string for spam detection. Comments are moderated manually; no third-party spam-detection service is used.
- Cookies. WordPress sets a few standard cookies:
- Leaving a comment may save your name and email in a convenience cookie (lasts one year).
- Visiting the login page sets a temporary cookie that contains no personal data and is discarded when you close your browser.
- Logging in sets cookies for your login session and display preferences (login cookies last two days, or two weeks with “Remember me”; screen options last one year).
- Editing or publishing content sets a cookie containing just the post ID, which expires after one day.
- No analytics, no ad tracking. This site runs no analytics, advertising, or third-party tracking scripts.
Embedded content from other sites
Posts and pages may embed content from other websites (for example, a video). Embedded content behaves exactly as if you had visited the other site directly: those sites may set cookies, collect data, and track your interaction with the embedded content under their own privacy policies.
Who we share data with
No one. Data stays on the site owner’s own server, with two exceptions: (1) information sent to third-party sites you choose to interact with via embedded content, and (2) disclosures required by law.
How long data is retained
Comments and their metadata are kept until deleted. Server logs are kept short-term for troubleshooting. Data tied to any account you may create is stored in your user profile and can be edited or deleted by you at any time (usernames cannot be changed). Website administrators can see and edit that information.
Your rights over your data
If you have an account here or have left comments, you can ask for an export of the personal data held about you, and you can ask for it to be erased. This doesn’t include data that must be kept for administrative, legal, or security reasons. Requests: jbev2007@gmail.com.
Hermes Mail Assistant — Google account access
Hermes Mail Assistant is a private, personal automation tool used by the site owner to work with his own Google account. It is not a public service: it has a single user (the site owner), who authorizes it himself. The sections below describe its Google API data use.
What it accesses. After the site owner signs in with Google and grants consent, the tool can access — only within his own account:
- Gmail — to read mail, apply labels and filters, and send messages on the owner’s behalf;
- Google Calendar — to read and manage the owner’s calendars and events;
- Google Drive — to access files it is granted;
- Contacts (read-only) — to help identify people in mail and calendar;
- Google Sheets and Docs — to create and update documents the owner requests.
How it is used. Solely to provide the owner direct, user-facing features in his own account: auditing and organizing email and filters, producing summaries and reminders, and managing his calendar and documents. No one else’s data is accessed.
Storage. OAuth credentials (tokens) are stored locally on the owner’s private, self-hosted server with restricted filesystem permissions. Google user data is not sold, rented, or shared with third parties; it is not used for advertising, and it is not used to train generalized AI or machine-learning models.
Limited Use. Hermes Mail Assistant’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access and deletion. The owner (or anyone using a Google account with access) can revoke the tool’s access at any time at myaccount.google.com/permissions; local tokens are then deleted. Data questions: jbev2007@gmail.com.
Changes to this policy
If this policy changes, the updated version will be posted here with a new “last updated” date.