1. Scope
This Privacy Policy applies to laziness.rocks and to small self-hosted applications or sign-in pages operated under this domain that link to this policy. Individual applications may process additional data if their function requires it; where that happens, the application should provide additional notice.
2. Information collected automatically
Like most web servers and reverse proxies, the infrastructure may create technical logs when you connect. These logs can include an IP address, date and time, requested URL, response status, browser or user-agent information, and basic network or security events. Logs are used to operate, troubleshoot, secure, and maintain the homelab.
3. Information received from Google
If you choose “Sign in with Google,” the service may request standard OpenID Connect scopes such as openid, email, and profile. Depending on what Google returns and what is needed for authentication, laziness.rocks may receive:
- your Google account email address;
- your display name;
- your profile image URL;
- a Google-issued unique account identifier; and
- authentication tokens or session information needed to complete sign-in.
The service is not intended to request access to Gmail, Google Drive files, Google Calendar, contacts, or other sensitive Google account content unless a future application clearly explains that need and asks for the corresponding permission.
4. How information is used
Information is used only as reasonably necessary to:
- authenticate you and maintain your signed-in session;
- decide whether your account is authorized to access a private service;
- display basic account information inside a connected application;
- protect the service from abuse, security incidents, and unauthorized access;
- diagnose technical problems and maintain the homelab; and
- comply with applicable legal obligations.
5. Google user data
Google user data obtained through OAuth or OpenID Connect is used for the functionality you requested, primarily authentication and access control. It is not sold, rented, or used to build advertising profiles.
Google user data is not disclosed to unrelated third parties except when necessary to operate the service, when you explicitly direct or authorize a disclosure, or when required by law. Any service provider used to operate the system is expected to receive only the information reasonably needed for that function.
The use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements where applicable.
6. Cookies and sessions
The site or its authentication layer may use cookies, browser storage, or similar session mechanisms to keep you signed in, remember security state, prevent request forgery, and route you to the correct application. These mechanisms are used for service functionality rather than advertising.
7. Data retention
Authentication records, session data, and technical logs are kept only for as long as reasonably useful for access control, security, troubleshooting, or system operation, after which they may be deleted, rotated, or overwritten. Because this is personal infrastructure, exact retention periods can vary by service.
Where an application creates a local user record from Google sign-in, that record may remain until access is removed, the application is rebuilt, or the record is deleted as part of normal administration.
8. Data deletion and revoking access
You can stop future Google sign-in access by revoking the application's authorization from your Google Account settings. You may also request deletion of locally stored account information by contacting the administrator of laziness.rocks using the contact information published on the main site or provided with your invitation.
Revoking Google access does not automatically erase server logs or records that must temporarily remain for security, backup rotation, or legal reasons, but such data will not be kept longer than reasonably necessary.
9. Security
Reasonable technical measures are used to protect the service, such as encrypted HTTPS connections, access controls, restricted administration, and standard authentication practices. No internet-connected service can guarantee absolute security, and users should avoid treating this homelab as a storage location for highly sensitive or irreplaceable information.
10. Sharing and sale of information
laziness.rocks does not sell personal information. Personal data is not shared for cross-context behavioral advertising or unrelated marketing. Information may be processed by infrastructure or identity providers only as needed to deliver the service, or disclosed when legally required.
11. Children
The service is not directed to children under the age required to consent to online services in their jurisdiction, and it is not intended to knowingly collect personal information from children.
12. International access
The service may be reachable from multiple countries. If you access it from outside the location where the homelab is operated, information may be processed in a different jurisdiction from your own. By using the service, you understand that data may be transferred to and processed where the infrastructure is located.
13. Changes to this policy
This policy may be updated when authentication, hosting, or connected applications change. The current version will be posted here and identified by its effective date.
14. Contact
Questions, privacy requests, or requests to delete a locally stored account record can be directed to the administrator of laziness.rocks using the contact information published on the main site or provided with your invitation to use the service.