Privacy

Privacy

No integrated AI processing
The installed app contains no AI model and sends no process measurements or chat text to an AI service for its detection. AI assistance during development and design is separate from local runtime functionality. Process changes are recorded with application label, PID, creation identity and state transition in the run journal, subject to the same retention and deletion limits as other events.

Publisher and privacy contact
Felix Köhler
Needbuilt - Software & Apps
Sole proprietorship
Sydneystraße 18
22297 Hamburg
Deutschland
shutdown@needbuilt.de

Local processing
The app processes your selected schedules, language and appearance on your Windows PC. Active AI/resource monitoring may process executable names, process IDs and creation times, associated process trees, CPU/GPU load and, where available and permitted, aggregate TCP traffic rates. Optional rules use whole-PC resource counters. The no-input rule reads only the time since the last mouse/keyboard input, not the keys you press or their contents.

Generation controls
When enabled, the app uses Windows UI Automation to search selected processes for a limited list of visible enabled stop buttons. It does not record screenshots, chat histories, document text, passwords or network payloads. You can disable this check in AI settings. Detection may be unavailable depending on app versions and Windows permissions.

Local CPU reference
For diagnostics, the app detects CPU model, logical processor count, processor groups, architecture, Windows version and CPU counter source. cpu-reference.json stores this information and at most one confirmed idle observation of the selected apps with app names, time, CPU value and background/limit at that time. No serial number or device identifier. The file is limited to 16 KiB, remains local and is not automatically exported. The observation is removed after 30 days during use, on the next launch after expiry, or when the hardware, Windows or measurement context changes. CPU information remains until replaced or the profile is removed. AI settings can delete the saved observation; Clear history does not remove it. A saved reference cannot permit an action in a new run.

Direct events
Optional local project hooks process start/stop events from supported agents. Incoming event text is bounded and processed transiently in memory. Stored data consists of states, timestamps and bound process identity; session/turn identifiers are hashed. Prompt and response text is not stored. Hooks require your project selection and confirmation. Own hook entries can be removed again while preserving unrelated settings. Project configuration and one bounded predecessor backup are in your project, outside the app's data folder.

Parent mode
After deliberate setup, the local service processes the selected local child account name/SID, allowed times, action, password-attempt cooldown and bounded audit. It stores a salted PBKDF2-SHA256 verifier using 600,000 iterations, not the plaintext password. State uses Windows DPAPI plus SYSTEM/administrator file permissions. Enforcement is independent of the display. No active policy is preconfigured. A separate standard child account is required; administrator and boot access are outside protection.

Locations and limits
An MSIX installation stores own per-user state in the Windows-managed package profile / LocalState. The Info page shows its actual location. The portable predecessor uses LocalAppData/AIShutdownTimer/native-v5. Old profiles are not automatically migrated or deleted.
• History: up to 30 days / 200 events / 256 KiB.
• Diagnostics: up to 7 days / 2,000 entries / 384 KiB.
• Trends: up to 24 hours / 2,880 points / 832 KiB.
• Direct event states: up to 128 entries / 64 KiB; no chat text.
• Regular journals/signals: 1.5 MiB total, plus temporary replacement files.
• Preferences remain until changed or the profile is removed.
• Protected parent state: up to 256 KiB, including at most 200 events / 30 days. Service-health output rotates at roughly 64 KiB.
Age-based cleanup runs while the software is in use. A stopped application cannot prune files. Ordinary local journals contain readable metadata; parent state has additional encryption. Windows administrators can still access the device.

Controls and removal
Stop monitoring, disable individual checks and clear history in the app. Clearing history preserves settings and active completion states. Erasing the protected parent profile requires stopping its plan, elevated Windows parent rights and the parent password. It removes the verifier, account binding, schedules and parent audit; the remaining service is inactive. Shared service files may remain under ProgramData/AIShutdownTimer/Guard until administrative cleanup. Health output contains timestamps and error classes, not contents or account names.
Windows manages package files/profile on Store uninstall. Remove configured project hooks through AI settings first. Unrelated project files, exports and old portable profiles are not automatically erased. You control the retention and sharing of exported files.

No monitoring-data upload
The app does not send these measurements/logs to its publisher, run a cloud language model or include analytics, advertising or tracking SDKs. No AI API key or AI tokens are required. Monitored programs and Windows/Microsoft Store have their own data practices; this notice does not replace theirs. Browser links open only on your click in the default browser.

Support and Store purchase
No support message is sent automatically. If you contact the publisher, it processes the contact/problem data you choose to provide. Support processor: Zoho Mail in its European data center. Retention: Contact details and messages are deleted once the request is resolved and they are no longer needed for handling it. Longer storage is limited to statutory retention duties or establishing, exercising or defending legal claims, based on Article 6(1)(c) or (f) GDPR. The relevant legal period or conclusion of the legal matter determines retention.. Legal basis: Article 6(1)(b) GDPR for contractual or requested pre-contractual matters; Article 6(1)(f) GDPR for other enquiries and product feedback. Do not send passwords, chat contents or confidential unsaved projects. Review exports before sharing.
The intended one-time purchase, download and updates use Microsoft Store and its own terms/privacy notices. The app does not collect payment details or initiate its own charge. The intended model has no subscription or in-app purchases. The Store displays the price.

Run history · update 4 November 2026
When you deliberately start a run, the app stores a fixed copy of its effective timer, selection, threshold, waiting-period and safety rules, the app version, run ID, time zone and captured configuration/actual monitoring start times. This includes selected profile and executable names, the process ID and start identity for a process-exit trigger, and enabled and disabled conditions. Rule changes, measurement availability, quiet periods, triggers, warning withdrawals, extensions, cancellations, error categories and action requests are linked to that run. No passwords, hook tokens, chat/prompt text or project paths are recorded. The start copy is part of the events and uses the same 30-day/200-event/256-KiB limits; a retained ending event still includes it. Larger start copies reduce the number of retained events. Each entry is limited to 64 KiB; oversized start configurations are rejected before starting. Truncated or incomplete history is labelled. Start rules are retained with their associated retained events; for a long-running plan they may therefore refer to an earlier start.
HTML and optional JSON exports include either your selected run or all retained runs with their original rules, as you choose. Current settings are not substituted for historical rules. Exports remain in your chosen location and are not transmitted by the app. Clearing removes retained events; if a run is still active, a new gap notice preserves the same run ID and original start rules, followed by new observations. Stop monitoring first to end further recording. A returned action request does not confirm that Windows fully shut down.

Local error diagnostics
An unexpected app error creates or overwrites one last-error.json file in the local data folder. It contains the time, app version, error reference, exception type, technical error code, previous timer state and a bounded list of method names. Exception messages, complete stack file paths, chat text and full command lines are not stored. Nothing is transmitted automatically. The file remains until overwritten by the next error or deliberately deleted manually; Clear history does not remove it.

Rights and changes
Where the publisher processes your personal data, contact it about access, correction, deletion, restriction, portability or any applicable objection; statutory conditions apply. You may complain to the competent data-protection authority. For local processing, use the controls described above. This is not a general legal assessment of parents, employers or other users; they must ensure their own use is lawful.


Behavior and window positions
settings.json stores selected start values (including seconds), display and behavior options. Optional last saved main/timer window coordinates remain local. Turning off position memory and applying removes the respective coordinates. These data are not transmitted. Saved start values never start a timer.