Who is responsible
Trayage is published by Kyle Reddoch under the RelayByte brand, operating in Texas, United States. Contact [email protected] about this policy or a privacy request. This policy covers Trayage’s direct Mac app, Mac App Store edition, website, and support. “Kyle,” “we,” and “us” mean Kyle Reddoch, trading under the RelayByte brand.
Your files stay on your Mac
Trayage reads top-level file names, sizes, types, and available creation, modification, and access dates in the folder being reviewed. It uses those details to suggest categories. For disk images, it also checks whether a similarly named app exists in Applications. The scanner does not upload file names, file contents, or scan results for analysis.
The app saves settings, the selected folder path, and a macOS folder-access bookmark locally. Review suggestions are held in memory. In the direct edition, Keylight stores license and trial state in device-bound encrypted storage. You can change or clear folder access in Settings. This does not delete billing or licensing records held by providers.
Direct licensing and trials
The direct edition connects to Keylight to activate and validate licenses, retrieve licensing settings, and report trial or unlicensed status. This also happens without a purchase.
Reported information includes a stable installation identifier, a one-way device hash, the Mac’s computer name during activation, license or trial state, app and SDK versions, operating-system information, CPU architecture, and broad CPU-core and memory ranges. The computer name may include a person’s name. Requests expose a network address to the service. Keylight records activation and request activity; trial or unlicensed status is reported at launch, when state changes, and periodically while the app runs.
These records support license delivery, activation limits, trial management, and installation and trial-to-purchase conversion reporting. The device hash is derived from the Mac’s hardware identifier; the raw hardware identifier stays local. The hash and installation identifier are pseudonymous, not anonymous, and may become associated with a license and purchase email. These reports do not include your scanned files.
Read Keylight’s privacy policy and the SDK release notes. The direct edition uses these reports for trial and license administration and conversion statistics. It has no in-app switch that disables all SDK reporting. Contact Kyle about access to or deletion of licensing records.
Direct app updates
The direct edition uses Sparkle to check for and install app updates. You can check manually or allow automatic checks, which run about once a day while Trayage is open. Change this choice in Settings → General. Updates require your choice before downloading and installing.
The update feed is hosted at trayage.app on GitHub Pages, and update downloads are hosted on GitHub Releases. Requests expose your IP address and technical request information such as the app version and user agent to the hosting provider. System-profile reporting is disabled. Update checks do not send your license key, email address, device identifier, scanned filenames, or file contents. Read GitHub’s privacy statement. App Store and TestFlight updates are handled by Apple instead.
Direct purchases
Stripe hosts direct checkout and the billing portal. It processes the email address, billing and payment information, transaction records, and technical information needed for payment and fraud prevention. This website has no embedded payment form and does not receive your full card details.
Kyle can access customer and transaction records in Stripe. Stripe sends purchase and refund events to Keylight, which connects the purchase email and order to a license and emails the key. A refund can change that license’s access. Kyle can access customer licensing records and device activity through Keylight.
These providers also have their own legal and service obligations. Their pages may use cookies. Read Stripe’s privacy policy and Keylight’s privacy policy.
Mac App Store edition
The Mac App Store edition uses Apple’s purchase system instead of Stripe checkout and Keylight licensing. Apple processes purchases using your Apple Account; its handling of account, payment, purchase, and device information is explained in App Store & Privacy.
Trayage reads and verifies Apple purchase and entitlement information to manage the optional seven-day cleanup trial, unlock paid features, and restore purchases. The App Store edition excludes Stripe checkout and Keylight licensing. Apple manages purchase records under its own policy. Kyle does not receive your full card details from Apple.
Version 1.1, including its TestFlight beta: Trayage also uses RevenueCat to process Apple purchases and restores, validate purchase access, and provide purchase analytics. RevenueCat receives purchase and transaction history, an automatically generated app user identifier, and technical information such as app and SDK versions, operating-system version, locale, and currency. Network requests expose an IP address to the service. Existing verified Apple purchases may be synced to RevenueCat when the app starts.
Trayage does not connect the RevenueCat identifier to your name or email, and does not send RevenueCat reviewed file names, file contents, or scan results. Automatic device identifier collection and optional SDK diagnostics are disabled. Kyle can view purchase and restoration records in the RevenueCat dashboard. There is no advertising or cross-app advertising tracking integration. Read RevenueCat’s privacy policy. Purchase records are retained as needed to administer access, restores, and purchase reporting; contact [email protected] for privacy requests. The older 1.0 App Store/TestFlight build does not include RevenueCat.
In version 1.1, duplicate-content comparison also reads candidate file contents locally, optional folder-size measurement can include subfolders, and ignored-file versions and reminder state are saved locally. These file-review details are not uploaded to RevenueCat.
Website analytics and appearance settings
This static website uses Tinylytics to count page visits and selected link clicks, including visits to the download and comparison pages, downloads, purchases, article sharing, support contacts, and links to outside services. Tinylytics receives the page URL and path, referrer when supplied by the browser, and user agent. Its infrastructure receives your IP address to create a short-lived daily hash and determine your country, then discards the address instead of storing it with the visit. Tinylytics does not set visitor cookies or create a persistent visitor identifier. Read how Tinylytics handles visitor data.
Link events include a category, action, and a general destination label, such as a provider name or download filename. They do not include the contents of your email, payment details, license key, or files. The app screenshots use sample files and do not access your files. The site has no advertising, tracking pixels, or third-party fonts.
The badges below the footer load from external providers. BuildHop, LaunchNest, TinyShelf, LetsLaunch, ScrollLaunch, Founder Battle, and PeerPush load from buildhop.io, launchnest.io, www.tinyshelf.co, letslaunch.today, www.scrolllaunch.com, founderbattle.com, and peerpush.com. When a badge loads, its provider receives connection information such as your IP address and browser details. These badges do not send the contents of files reviewed in Trayage. LaunchNest image requests do not include the page URL as a referrer. BuildHop, TinyShelf, LetsLaunch, ScrollLaunch, Founder Battle, and PeerPush image requests may include this website’s origin as a referrer.
Appearance follows your device’s light or dark setting by default. If you choose Light or Dark, this website saves only that choice in your browser under trayage-appearance. It is not an identifier and is not sent to Kyle. Selecting System removes the saved preference; clearing this site’s browser storage removes it too.
GitHub Pages hosts this website and receives connection and request information, including IP addresses, when serving pages. Read GitHub’s privacy statement.
Public feedback on GitHub
If you submit an idea or bug report through GitHub Issues, your GitHub profile, post, comments, and attachments are public. Kyle uses this information to investigate problems, discuss ideas, and plan improvements. Accepted issue titles, summaries, and statuses may also appear on this website’s roadmap.
GitHub hosts these conversations under its privacy statement. Keep private filenames, license keys, payment information, and account details out of public reports. Email [email protected] for private support or privacy requests.
Support through Proton Mail
Kyle uses Proton Mail for [email protected]. When you ask for help, Kyle receives your email address, message, and any attachments you send, and uses them to answer you, investigate the issue, or locate a purchase.
Proton processes and stores this correspondence. Its Mail privacy policy explains email metadata, spam screening, encryption, and storage. Ordinary email exchanged with other providers is not automatically end-to-end encrypted. Please redact private file names and other sensitive information from screenshots; do not send full card numbers or complete license keys.
Use, sharing, and processing locations
We use this information to provide the app and purchases, manage trials and licenses, answer support requests, prevent fraud, maintain security, and meet accounting or legal obligations. The app and site contain no advertising integration or data-broker integration. Kyle does not sell personal information or use it for targeted advertising.
Kyle operates in the United States. Providers may process information in other countries under the policies linked above. Information may also need to be disclosed to comply with law or resolve a legal claim. This is not permission for unrelated marketing.
We use information needed to deliver requested software and purchases, provide support, protect the service against abuse, and meet legal obligations. Where consent is required for a particular use, we obtain it and explain how to withdraw it. We require service providers processing information on our behalf to protect it and use it only for the service and applicable legal obligations.
Retention and privacy requests
Email [email protected] to request access, correction, or deletion of information held for Trayage. Depending on the law that applies, you may also request portability, object to or restrict a use, withdraw consent for a consent-based use, appeal a refused request, or complain to a regulator. A request may require a proportionate ownership check; never send your full payment card or license key.
Deactivating a Mac frees an activation; it does not erase the purchase record. Uninstalling the app does not remove provider records. Some information may need to remain for an active license, accounting, disputes, or legal obligations. A privacy request will be handled separately from a refund request.
We retain support messages while needed to resolve your request and related follow-up. Licensing records are retained while needed to administer trial limits, prevent abuse, and honor purchased access; payment records are retained for accounting, tax, fraud prevention, and legal obligations. Retention depends on the record’s purpose and applicable requirements. We review deletion requests with the relevant provider and explain any records that must be retained. Provider backup and legal-retention requirements may continue after deletion from active records.
Children and policy changes
Trayage is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided information, contact Kyle to request its removal.
This policy is effective October 9, 2026. We update this page when the app, providers, or data uses change and provide additional notice or obtain consent when required by applicable law.
