Privacy policy

Website support

Bug reports

When you use the bug report form, you choose what to share: your contact email, a summary, a description, and an optional screenshot. These details are used to investigate the issue and reply to you. Submitting a report does not subscribe you to marketing or create a Trayzen account.

Vercel processes the submission to run the website. The report is sent through Zoho Mail to the Trayzen support mailbox; an uploaded screenshot becomes a private email attachment. The form does not automatically capture your desktop or upload files you have not selected. Please remove personal or sensitive information from your screenshot before submitting it.

Report text and screenshots are not saved in the website’s storage or published in a public gallery. To limit automated submissions, private Vercel storage holds request counters keyed by protected identifiers instead of raw email or IP addresses. The delivered report remains in the support mailbox. Contact hello@trayzen.app to request access, correction, or deletion of information you submitted.

Existing website subscribers

Beta email waitlist

If you previously joined the Trayzen beta waitlist, Matúš Fojtík uses your email address to contact you about Trayzen beta access, within the scope of your consent. The website now directs visitors to Microsoft Store instead of promoting new signups. Existing removal links remain available. A waitlist signup does not create an account in the Windows app or grant access to a paid release.

We store your email, signup date, subscription status, and the wording and version of your consent in private Vercel storage. Vercel processes the information needed to host the list. The website attempts to send a signup confirmation through Zoho Mail, which processes the recipient address and message, including your removal link. We store the sending status and attempt time to limit duplicate messages. Confirmation emails contain no tracking pixels. We also use request counters keyed by a protected identifier to limit automated submissions; raw IP addresses are not stored in the waitlist records.

We process your signup on the basis of your consent. The form records the address you provide; it does not verify ownership of that mailbox. We retain it while organising beta access, until you withdraw your consent, or until the list is no longer needed. We do not use this signup as consent to unrelated marketing.

You can remove your signup using the removal link shown after your signup or included in the confirmation email, or contact hello@trayzen.app to withdraw consent, access, correct, or delete your information. Withdrawal does not affect processing that took place before it. You may also complain to your data protection authority.

Foundation

Local processing

Trayzen is developed and published by Matúš Fojtík. It processes only the information needed for the feature you choose to use. This can include local file names and paths, selected screen content, Windows media metadata, device state, app settings, and Windows system information. This data is not sent to Trayzen servers.

• Quick Preview reads only the selected item and applies bounded file-size limits.
• Settings, recent items, pinned items, and caches stay in the current user's app-data folder.

Data from Trayzen apps

Notes, Reminders, Preview, Journal, Automations, System Care, and OLED Care

Trayzen's companion apps keep their content and settings in the current Windows user's local app-data folder unless the user explicitly enables an available connection or sync feature.

• Notes stores note titles and bodies, rich text, folders, tags, pin and deletion state, and optional reminder dates locally.
• Reminders stores titles, notes, lists, sections, tags, priorities, due and repeat settings, completion state, and any location label you type. The location field is text only; Trayzen does not request or read the device's location.
• Preview reads a file only after you select, open, or drop it. Recent file paths, the last folder, and the sidebar preference stay local. Copying a path or file and saving a copy require an explicit action.
• Journal stores entries, rich text, tags, mood and favorite state, and references to attachment paths. Attachments remain in their original locations, and exports run only when requested.
• Automations stores names, triggers, and action values locally. Copy text writes the configured value to the Windows clipboard. Open may launch a file, app, or URL only when that user-created automation runs.
• OLED Care reads connected-display identity and supported monitor controls locally. Brightness and maintenance requests target the selected display only after an explicit action. Black and colour inspection surfaces do not capture the desktop or upload display information.

Content you choose

Capture, recordings, and OCR

Trayzen captures only the screen, window, or region you select. Screenshots and videos are saved locally, normally under Pictures\Trayzen, or copied to the Windows clipboard when requested. Text extraction uses local Windows OCR. Trayzen does not upload captured content.

Windows device state

Media, audio devices, and calls

Media controls read metadata exposed by the active Windows media session, such as title, artist, playback state, timing, artwork, and source app. The visualizer reads local loopback levels to animate the interface but does not save or transmit audio samples.

• Audio & devices reads local Windows endpoints and supported Bluetooth properties.
• Device names, connection state, and battery level are shown only when Windows exposes them.
• Call Dock reads configured local call apps and audio-session state.
• Call status, microphone levels, and audio samples are not uploaded.

Windows health

System Care

System Care reads health, storage, startup, installed-app, Windows Security, and maintenance information reported by Windows. It does not create a remote monitoring profile. Cleanup scans approved cache locations and removes nothing until the user reviews and confirms the action.

• Supported deletions use the Windows Recycle Bin where possible.
• Large-file and duplicate-file scans run locally.
• Duplicate candidates can be hashed with SHA-256 on the device.
• File contents, scan results, and hashes are not uploaded.

Connections

Limited network access

Most Trayzen features work without an internet connection. Network access is limited to:

• Microsoft Store or Windows package services when checking for app updates.
• Microsoft sign-in and Microsoft Graph / OneDrive when you connect Sync & backup. Sync requests access to Trayzen’s private OneDrive app folder.
• A displayed public source when the user explicitly installs FFmpeg.
• A destination opened by a user-created automation when its Open action contains a URL.
• Polar when the user chooses the paid download. Polar handles checkout, tax, receipts, and customer portal access under its own terms.
• Normal website hosting requests when visiting trayzen.app.

Optional connections

Sync & backup

After you connect a Microsoft account, you can enable Notes and app settings and content independently. App content includes reminders, journals and automations. Selected content is encrypted on your device using a separate sync password before upload to Trayzen's private OneDrive app folder.

• The sync password is protected locally for the current Windows user and is never uploaded. Neither Trayzen nor Microsoft can recover it.
• Microsoft can observe normal account and transfer metadata, including app-folder file names, sizes, and modification times. Your selected content remains inside encrypted sync documents and attachment chunks.
• Connected-account identifiers and the account choice are kept locally; Microsoft and Windows manage authentication tokens.
• Concurrent changes are kept as labelled conflict copies.
• Disconnecting stops sync on this device and clears its locally stored sync password and account choice. It does not delete existing files in OneDrive; remove those separately if you no longer want them.

Setup instructions are in Sync & backup documentation.

Local records

Diagnostics and retention

Local diagnostic logs are size-limited, rotated, and removed after 14 days. Trayzen redacts known user-profile paths and common credential patterns before writing new entries. A runtime report is copied to the clipboard only when the user presses Copy diagnostics. Nothing is submitted automatically.

Uninstalling Trayzen removes its local application data. Captures under Pictures\Trayzen are preserved by default and are removed only when the user explicitly selects that option.

Business model

Sharing, selling, and advertising

Trayzen does not sell personal information, build advertising profiles, show ads, or share app activity with data brokers. Polar processes paid website purchases as the merchant of record. Windows, Microsoft Store, and Polar services operate under their own terms and privacy policies.

Policy updates

Changes and questions

This page will be updated when Trayzen's data handling materially changes. More feature-level detail is available in the Trayzen documentation. For privacy or support questions, email hello@trayzen.app.