Official privacy policy

Privacy Policy

Application: Auto Shutdown & Scheduler
Developer: Idylle Soft
Last updated: October 10, 2026

In short: The App does not require an account, display advertising, or automatically upload your personal files to the cloud. Automation runs locally on your device. However, the App may send limited technical data through a Cloudflare Worker to the developer's private Telegram chat and Cloudflare D1 database for launch statistics, certain product interactions, feedback you submit, and error reports when reporting remains enabled. Feedback may include an optional screenshot that you choose to attach. Disabling error reporting does not disable launch or product-interaction events. Cloudflare derives an approximate country name from the connection's IP address. The IP address itself is not included in Telegram messages or the App's Cloudflare D1 record.

1. Scope and data controller

This policy explains the processing of data in the Free and Pro editions of the Auto Shutdown & Scheduler Windows desktop application distributed by Idylle Soft through Microsoft Store. It covers local operation, notifications sent through the Cloudflare Worker, records in Cloudflare D1 and the developer's management panel, Telegram messages and attachments, and Microsoft Store interactions where applicable.

The responsible contact for privacy questions and data requests is idyllesoft@outlook.com.

2. Core principles

  • No account, registration, or cloud sign-in is required to use the App.
  • Timers, schedules, routines, monitors, and custom rules run locally on your device.
  • The App displays no advertising and does not sell or rent personal data for advertising.
  • The App does not automatically upload personal file contents. Stop-protection passwords and Microsoft account credentials are not sent to the developer. Information you voluntarily include in feedback or an attached screenshot is transmitted with that submission.
  • Transmitted data is limited to the purposes described below.

3. Data stored on your device

Settings Language, thresholds, selected action, notifications, widget, warning, and similar preferences are stored in a local settings file.
Action history The latest 100 runs are stored locally with their source, action, status, time, and a limited configuration summary.
Logs Runtime and diagnostic records are stored in size-limited local log files.
Error queue Error reports that could not be delivered may remain in a local file for later retry, and duplicate errors may be consolidated.
Technical-event queue Undelivered launch and product-interaction events may be saved locally for retry. Event identifiers and delivery status help prevent duplicate notifications.
Password A password set for Stop-action protection is held only in application memory and is forgotten when the App closes.

Most of these records are located under %LOCALAPPDATA%\OtomatikKapatici\. Depending on the distribution method, the Start with Windows preference may be stored by Windows StartupTask infrastructure or in a Registry location belonging to the current Windows user.

This policy page stores only your selected policy language in the browser's local storage (sas-privacy-language). This preference is not sent to the developer.

4. Persistent pseudonymous identifier

The App creates a random identifier in the form SAS-XXXX-XXXX-XXXX-XXXX to distinguish limited events originating from the same Windows user profile. It is not a hardware fingerprint and contains no name, email address, Microsoft account, user name, computer name, file path, IP address, or device serial number.

The identifier is protected with Windows DPAPI and may be stored in the current user's Registry, %PROGRAMDATA%\IdylleSoft\Smart Auto Shutdown & Scheduler\telemetry_device_id.dat, and the Store package's LocalState or LocalCache\Local\IdylleSoft folders under %LOCALAPPDATA%\Packages\, where writable. Copies can restore one another. Uninstalling the App or deleting only one copy may therefore not reset the identifier. A new identifier is created when no usable copy can be recovered.

Events can be linked to the same identifier over time. These records are pseudonymous, not guaranteed to be irreversibly anonymous. Deleting local copies does not delete records already held in D1 or Telegram.

5. Automatic technical events and product interactions

To understand whether the App operates correctly and how its features are used, some of the following events may be sent automatically to the developer:

  • App launch and edition type (Free or Pro); a launch event alone does not confirm that the interface opened correctly
  • Display of the Pro offer when you choose to explore Pro, or dismissal through its Close button; the offer is not automatically displayed on first launch or when restoring the App from the system tray
  • Selection of Update now or Later in an update prompt
  • Opening the product website from the About screen
  • Opening the rating prompt from the moon image
  • Display of the rating prompt and the user's rate/remind-later choice

Technical fields that may accompany these events

  • App version and pseudonymous identifier
  • Windows version
  • App language and Windows system language
  • Country name and country code approximately determined by Cloudflare

The App does not collect a city, district, postal code, street address, GPS location, or coordinates. Cloudflare technically sees the source IP address when the internet connection is established and uses it to determine the country. The developer does not add that IP address to the Telegram message or the Cloudflare D1 record.

D1 may store the identifier, first/last-seen times, launch count, version, country, and last event; country-level device statistics; a device-linked timeline of launches, critical errors, and feedback. Event and delivery identifiers, timestamps, and delivery status are used for retries and deduplication. The developer can review these records in an access-controlled management panel to diagnose startup problems, follow repeated errors, and understand aggregate use.

Scope of the error-reporting switch: It controls error/crash reports only. It does not turn off automatic launch or product-interaction events. Interface-readiness timing, JavaScript error/recovery counts as health measurements, session tracking, and heartbeat telemetry are no longer transmitted. The current App has no separate in-App switch for the remaining automatic events. The local technical-event queue may continue retrying them after error reporting is disabled.

6. Local action history

The latest 100 automation-history records are stored locally. The current notification service does not forward action-history events to Telegram or save them as remote action history; queued action-history events from older editions are accepted and ignored. Separately, an enabled error report can include the active task type and diagnostic context described in section 8. This is not a remote copy of the local action history.

7. Feedback and new-language requests

Feedback and new-language requests are transmitted only after you press the relevant Send button. Disabling error reporting does not prevent a submission that you initiate.

A submission may include:

  • Your message, selected category, or requested language
  • App version, pseudonymous identifier, App language, and system language
  • Windows version/build, architecture, screen resolution, DPI/scaling, and WebView2 version
  • Country name determined by Cloudflare

If you voluntarily type a name, email address, or other personal information into your message, it will be transmitted as part of that message. The App does not require you to provide such information.

Optional screenshot

A screenshot is captured only when you select the screenshot option. The capture targets the App window's on-screen rectangle, not the entire desktop. Content overlapping that rectangle may also be visible. You can preview or remove the attachment before sending. Capturing or previewing does not itself upload the screenshot; it is transmitted when you send the feedback with the attachment included.

Screenshots are not automatically masked. Visible text, file/program names, or personal information can be included. Review the image and do not submit passwords or other sensitive information. Feedback and attachments pass through the Cloudflare Worker to the developer's private Telegram chat. D1 stores feedback text, category, technical context, identifier, version, languages, country, submission time, and attachment metadata. The image itself is stored in Telegram, not as an image in D1; its Telegram file identifier lets the access-controlled management panel retrieve and display it through the Worker.

8. Error and crash reports

Current application versions report only directly evidenced critical failures. Interface-health and session telemetry are discontinued. Successful recovery and missing heartbeat data do not produce error reports. Previously collected health/session records and their dedicated tables have been removed from the active D1 database. Legacy health and session events arriving from older versions are accepted and ignored, without new storage or Telegram notifications. Previously delivered Telegram messages or copies in backups are not automatically erased by deleting the active D1 records.

Default: enabled. You can disable the option labelled anonymous error reports in Settings. Reports can still be linked by the pseudonymous identifier; they are not guaranteed to be irreversibly anonymous.

Only critical failures with direct technical evidence are reported: startup, automation engine, Windows action, unrecoverable WebView2, or fatal native failures. JSON reports are sent to Telegram and grouped in D1. Offline reports remain in the bounded retry queue.

The Worker also stores error groups, diagnostic samples, occurrence counts, first/last-seen times, and device associations in D1 for review in the access-controlled management panel. Disabling error reporting clears its pending local queue but does not delete previously delivered reports or the separate technical-event queue described in section 5.

An error report may include:

  • Error title, sanitized details, and traceback
  • App, Python, Windows, and WebView2 versions
  • Diagnostic information such as architecture, core count, memory, and current CPU usage
  • Observed critical failure, technical evidence, build identity and limited diagnostic logs
  • Pseudonymous identifier, App/system language, and country name

User names, computer names, and file paths are processed for masking before transmission. The monitored program name, selected file path, and personal file contents are not intended to be included in an error report. However, no automated masking method can guarantee a perfect result for every possible free-form error message.

9. Pro purchase and Microsoft Store

When you initiate the Pro purchase flow, the developer may be notified that the purchase window opened and whether the process succeeded, was cancelled, remained incomplete, or could not start. The event may include the App version, pseudonymous identifier, technical environment information, country name, and a Microsoft Store result code.

Payment is handled by Microsoft. The App does not see or store your card number, payment details, or Microsoft account password. Processing performed by Microsoft Store is governed by Microsoft's own privacy terms.

10. Version and update checks

  • The Microsoft Store edition may check update availability through Windows/Microsoft Store infrastructure.
  • If you choose to open an update link, Microsoft Store may process its standard connection data.
  • Your Update now or Later response in the update prompt may be reported as a product event.

11. Service providers and data transfers

Cloudflare Receives submitted data through the HTTPS Worker, determines approximate country, and stores device/country statistics, error records, feedback, and delivery metadata in D1. The Worker serves the access-controlled management panel and retrieves attached images from Telegram.
Telegram Technical events, feedback, optional screenshots, and error-report documents are delivered to the developer's private bot/chat.
Microsoft Used for Store distribution, licensing/purchase, updates, and Windows notification/startup functionality.

These providers may operate infrastructure in different countries. When a connection is made, the provider may process the IP address and standard HTTP connection information under its own service policies. The App developer does not sell personal data to advertising networks or data brokers.

Provider information: Cloudflare Privacy Policy, Telegram Privacy Policy, and Microsoft Privacy Statement. These links describe provider practices; they are not a statement that a particular international-transfer safeguard or data location has been verified for this App.

12. Retention and deletion

  • Local settings and history: retained until you clear them, delete the related files, or remove the App data.
  • Logs and temporary crash traces: retained according to size limits, rotation, and next-session cleanup rules.
  • Local retry queues: ordinary error and technical-event entries have a seven-day retry eligibility limit. Expiry is evaluated when the queue is processed, not by a continuously running deletion service. Diagnostic backups of unreadable queue files have no automatic deletion period.
  • Pseudonymous identifier: may survive uninstall or deletion of a single copy. See section 4 for all storage locations.
  • D1 device timeline: entries older than 180 days are removed when new timeline activity is recorded.
  • D1 error-notification throttling log: entries older than seven days are removed during subsequent notification processing. This does not delete the underlying error groups or samples.
  • Other D1 records: device/country statistics, error groups and samples, feedback, and notification-delivery records currently have no fixed automatic deletion period and remain until the developer deletes them.
  • Database exports/backups: a database export made before deletion may retain earlier records. Such copies currently have no fixed automatic deletion period; deleting a record from the active database does not erase it from an existing export or backup. A deletion request should also identify backup copies for assessment.
  • Telegram: transmitted messages, screenshots, and error documents have no App-managed automatic deletion period and may remain until deleted by the developer.

Cleanup triggered by a new operation does not guarantee deletion exactly when a period expires. Deleting feedback from the management panel removes its D1 record and associated feedback timeline entries, not the corresponding Telegram message or image. A deletion request should cover both D1 and Telegram if both copies are to be removed. Deleting local App data likewise does not erase previously transmitted records.

13. Data security

  • Data is transmitted from the App to the Worker over HTTPS.
  • The Telegram bot token and chat identifier are not embedded in the App package; they are held as Worker secrets.
  • The pseudonymous identifier is protected with Windows DPAPI.
  • Local paths in error details are masked before transmission.
  • Management-panel records and screenshot retrieval require administrative access. Optional screenshots are not covered by error-text masking.
  • Core automation continues to operate locally when the Worker or Telegram is unavailable.

No internet transmission or electronic storage method can guarantee absolute security. Reasonable technical measures are used, but zero risk cannot be promised.

14. Your choices and rights

  • You can disable error/crash reporting in Settings; the automatic events in section 5 remain active.
  • You can choose not to submit feedback or a language request, and remove an optional screenshot before sending.
  • You can clear local action history from within the App.
  • You can remove local settings/history by deleting the relevant App-data folder while the App is closed. This does not remove every identifier copy described in section 4 or any remote records.
  • You may request deletion of D1 or Telegram records associated with your pseudonymous identifier by email.
  • Depending on your jurisdiction, you may have rights of access, correction, deletion, restriction, or objection.

Because the pseudonymous identifier is not stored against your real name, you may need to provide the SAS-... identifier shown by your App so that a particular remote record can be located. Additional verification may be requested when assessing a request.

Contact us at idyllesoft@outlook.com, stating the request and relevant identifier, version, or approximate event time. Share only what is necessary to locate the records and verify the request. Requests will be assessed under applicable law and its response deadlines. Where applicable, rights may also include data portability, withdrawal of consent for consent-based processing, and a complaint to your competent data-protection authority. In Türkiye this is the Personal Data Protection Authority (KVKK); in the EEA, your competent national supervisory authority. These rights depend on the law and processing basis that apply.

15. Children's privacy

The App is not designed as a service directed to children and does not knowingly request personal data from children. If you believe that a child's information was sent by mistake, you may contact us to request deletion.

16. Changes to this policy

This policy may be updated when App features or data-processing practices change. The last updated date will be revised in the new text. Material changes may be announced through an appropriate in-App notice, website notice, or release note.

17. Contact

For privacy questions and access or deletion requests:
Idylle Soft
idyllesoft@outlook.com

© 2026 Idylle Soft · Auto Shutdown & Scheduler