How the ScreenMinutes pilot handles account, device and service information, and how to contact us about privacy.
1. Who is responsible for your information?
ScreenMinutes is operated by Kai Eysselein at No 9 Love Street, Windhoek, Namibia. For privacy questions or requests, contact [email protected]. [CONFIRM whether [email protected] is the correct monitored contact, and add any required representative or data protection officer details.]
This statement covers the ScreenMinutes website, application and associated service operations. It describes the pilot currently implemented, not every future household or parental-control feature. Other websites and services have their own privacy notices.
2. Information we handle
- Account and profile information: an account identifier, email address, display name, optional first name and surname, optional profile picture, account status and sign-in-duration preference.
- Authentication and security information: password hashes, session records, expiry times, verification and recovery records, and information used to limit abusive sign-in attempts. The application uses protected identifiers derived from email addresses and IP addresses for its rate-limit counters. Network and service providers may also process connection information.
- Google sign-in: if you choose this option, the application requests identity and email information and stores Google's account identifier, email address and connection time. It does not request access to your Gmail messages, contacts or files through the current sign-in configuration.
- Router and device information: where a router is connected to the pilot, device names and identifiers such as MAC addresses, router/network identifiers, authentication events, reported session times and durations, traffic totals and operational status. Router configuration may include network addresses and credentials needed to operate the integration.
- Administration and content: approval/invitation records, administrative audit events, support correspondence you send, and CMS page revisions with editor identifiers. Published pages are publicly readable; draft pages and their history are restricted to authorised Platform Owners.
- Service operations: technical logs, host resource measurements, backup copies and delivery records used to operate, troubleshoot and recover the service.
Information may come directly from you, an authorised administrator, an integrated router, Google when you select Google sign-in, or service operations.
3. Why we use information
We use information to create and administer accounts; authenticate users; deliver verification, invitation, recovery and account-notification emails; apply access permissions; receive router reports; provide dashboards and help content; investigate faults or suspected misuse; respond to support requests; and maintain backups and service security.
Email and authentication information are needed to provide an account. First name, surname and profile picture are optional. Choosing not to use Google sign-in does not require you to connect a Google account.
4. Cookies and local browser storage
The application uses a first-party session cookie to support sign-in and protected requests. Server-side session expiry and your role determine how long a sign-in remains valid. Ordinary users can select a future sign-in duration from 1 to 30 days; Platform Owner sign-ins have a 12-hour limit. Signing out ends the current sign-in.
Blocking or deleting required cookies may prevent sign-in or require you to sign in again. Choosing Google sign-in takes you through Google's own service, which may use its own cookies.
5. Who can receive or access information?
Authorised Platform Owners can administer accounts and view the operational account/device summaries available to their role. Ordinary users do not receive platform-wide access. Household-specific access arrangements must be explained before those future features are enabled.
Service providers support hosting, delivery, security and operations. The current deployment uses Linode/Akamai hosting, Cloudflare connectivity/security services, Resend for transactional email, Google for optional sign-in, Netdata for operational monitoring, and separate backup storage. These services have different roles; their inclusion does not mean every provider receives every category of information.
Information may also need to be disclosed in response to a lawful requirement or to investigate a security incident. Such disclosure must have an appropriate legal basis and be limited to what is necessary.
6. Where information is processed
The application, its providers and backup systems may process information in different countries.
7. How long information is kept
Different records serve different purposes. Authentication codes and sessions have expiry times; expiry ends their validity and is not necessarily the same as removal from every log or backup. Router event/session cleanup uses a configurable retention setting. Backups and provider-held records have separate lifecycles.
8. Security
The application uses measures including encrypted web connections, password hashing, server-side permissions, protected sessions and backups. Access to administration and unpublished content is restricted. No security measure provides an absolute guarantee, and we cannot promise that an incident will never occur.
If you suspect an account or privacy incident, contact [email protected]. Do not send your password, verification codes or recovery links in a support message.
9. Your choices and privacy requests
You can edit supported profile details, remove your profile picture, manage supported sign-in options and sign out through Account settings. Some requests, including account deletion or a copy of information, may require assistance from the operator.
Depending on the law that applies, you may have rights to access, correct, delete, restrict or object to processing, or receive a portable copy of information. Where processing depends on consent, you may be able to withdraw it without affecting earlier lawful processing. Rights can have exceptions.
Send requests to [email protected]. We may need proportionate verification before acting.
10. Children and household use
ScreenMinutes is intended to support household screen-time management, but the current pilot does not yet provide the complete child-profile and household-permission workflows. This statement does not authorise unrestricted collection or monitoring of children's information.
Do not add a child's information to the pilot until the operator has confirmed appropriate arrangements. Before enabling child-facing features, the operator must establish who can act for a child, the relevant legal basis and any age/parental-authorisation requirements, access controls, and privacy information that children can understand.
11. Changes and questions
This statement should be updated when the service or its information practices change. The published page will show its latest update date. We will notify existing users of material changes to this disclaimer through an in-app notice, identifying the changes and when they take effect.
See also the Disclaimer.
Effective date:19 October 2026