Sold and operated by StarkOne LLC
Privacy policy
Last updated: October 6, 2026
This policy explains how StarkOne LLC handles information when you use RTLright, rtlright.com, our contact form and our shop. For privacy requests, contact [email protected].
1. Who is responsible
StarkOne LLC operates RTLright and determines how the information described here is used. Contact [email protected] for access, correction, deletion or other privacy requests. We may need proportionate information to verify that a request concerns your records.
2. Keyboard and Mac permissions
Input Monitoring recognises shortcuts; Accessibility identifies editable fields and invokes direction or alignment actions. This processing is local. Keyboard features do not upload your keystrokes, document contents or clipboard. Settings are stored on your Mac. Secure input and password fields are excluded.
2a. Optional file sharing
When you choose a file and invoke RTLright Share, the app uploads that file and its filename over HTTPS to the external service wget.co.il. The service also receives your IP address and connection metadata. Anyone with the resulting link can download the file. Storage and availability are controlled by wget.co.il. Closing the share window does not delete an uploaded file. No other files are uploaded automatically.
2b. Optional clipboard history
Clipboard history is off by default and must be enabled separately on each Mac. When enabled, it records supported copied text, images, file references, source application and copy times. Persistent history is encrypted on this Mac with a key stored in Keychain; clipboard history is not uploaded or synced by RTLright. File references do not duplicate the original files. You can choose content types and limits, exclude apps, pause collection, clear history including pins, or turn off persistence to delete the saved disk copy. Turning off collection alone keeps existing history. Content marked confidential or transient, known password managers and secure input are excluded, but apps do not always identify sensitive content.
3. First-launch registration
On first launch, RTLright sends a randomly generated installation ID and app version to rtlright.com. The server records the connection IP, approximate country, initial interface language and registration time. This selects Hebrew in Israel and English elsewhere. No hardware serial number is collected. Country lookup is local on our server; a VPN can change its result. Registration retries when offline. You can override the language in settings. The record recognises retries; it is not a history of your movements. For trials and licensing, we store the random installation ID, a hash of its random device secret, app version, trial dates, license assignment, activation dates, last verification time and an audit of license changes. License codes are encrypted at rest. The app keeps its identity and signed authorization in macOS Keychain, which may remain after uninstalling. No hardware serial number or typed content is used. Periodic requests expose the connection IP to the server and its security logs; the license database itself does not keep an IP history. We retain these records to provide the trial and license, enforce device limits and handle support or abuse. Deletion requests are considered under the retention rules below.
4. Contact requests
If you contact us, we store your name, email, chosen topic, message, language, request time and handling status. These details are optional to provide, but the form cannot be processed without its required fields. We use them to respond, investigate issues and maintain support records. Notifications are sent through PingMail.Cloud, which receives the message details. A saved request may remain available to us even if email delivery is delayed.
5. Purchases
Stripe collects payment and billing details on its hosted payment page. We retain the purchase reference, email returned by Stripe, amount, currency, payment status and coverage dates to fulfil the order, support you, address refunds and meet legal obligations. We do not store full card numbers or security codes. Stripe handles payment data according to its own privacy information.
6. Connections, logs and essential storage
Update checks fetch a signed release feed from rtlright.com. Our hosting and Cloudflare may process IP addresses, URLs, times and technical security data. We use Google Analytics to measure aggregate website traffic; it sets first-party analytics cookies and Google receives technical data such as IP address as our processor. We do not use advertising cookies. Administration uses an HttpOnly session cookie expiring after 12 hours. The purchase confirmation page uses session storage to keep its private order access token during that browser session. These are used for the requested functions.
7. Purposes, recipients and international processing
We process information to supply requested services, fulfil purchases, answer requests, secure the service and meet applicable legal obligations. Where consent is required, you may withdraw it without affecting earlier lawful processing. Access is limited to authorised operators and relevant providers: hosting, Cloudflare, Google Analytics, PingMail.Cloud and Stripe, and wget.co.il when you choose to share a file. Providers may process data outside your country. We do not sell personal information or use support messages for advertising.
8. Retention and security
We retain installation records to recognise an installation and registration retries; contact records for handling requests and follow-up; purchase records for fulfilment, disputes and applicable accounting obligations. Retention depends on these purposes and legal requirements. You may request deletion when retention is no longer required. Access controls, encrypted transport and protected server storage reduce risk, but no system is immune to incidents.
9. Your choices and rights
You can change interface language, disable shortcuts or update checks, and uninstall the app. Depending on applicable law, you may request access, correction, deletion, restriction, objection or portability, and complain to a competent privacy authority. Contact [email protected]; we will explain any lawful reason that prevents fulfilling a request.
10. Changes
We will update the date above when this policy changes and provide appropriate notice of material changes. Contact us if any part of the policy is unclear.