ReplayPath Privacy Policy

ReplayPath processes automation, recognition, screenshots, project data, settings, and diagnostics locally on your device.

ReplayPath does not intentionally transmit your recordings, screenshots, OCR text, project files, or other ReplayPath User Content to Lyon Developers.

As of this policy version, ReplayPath’s own application code does not include telemetry, behavioural analytics, crash-reporting uploads, cloud sync, remote accounts, or automatic update checking.

While you use ReplayPath, it may process:

• keyboard and mouse input you generate while actively recording;
• screen regions or images you explicitly capture for recognition, Watch Areas, Start Position, Click Sequence, or related tools;
• text extracted locally by on-device OCR from regions you configure;
• automation projects, project metadata, labels, settings, and recent-project information; and
• bounded local diagnostic log entries.

This information is processed so ReplayPath’s features can work. ReplayPath does not sell this information or use it for advertising.

ReplayPath captures keyboard and mouse input only while you have actively started recording using the Record control or configured recording shortcut.

Recording stops when you stop the recording.

ReplayPath filters its own synthetic playback input so that input generated by ReplayPath is not intentionally recorded back into the same recording.

Recorded input becomes part of the action timeline for the project you are editing and remains on your device unless you choose to save, copy, move, or share the project.

When you use features such as Watch Areas, recognition, or Start Position, ReplayPath may capture the screen region you select and store a local reference image associated with your project.

When you configure a Watch Area to use text recognition, ReplayPath performs OCR locally on your device and uses the extracted text for matching.

ReplayPath does not intentionally transmit OCR text or reference images to Lyon Developers.

Screenshots used only as temporary editing backgrounds, such as region-selection or Click Sequence overlays, are temporary unless you explicitly commit a selection as project/reference data.

A ReplayPath project (.replaypath) contains information you choose to save, which can include recorded actions, timing, labels, settings relevant to the project, and embedded or referenced recognition/Start Position images.

ReplayPath stores a project wherever you choose to save it.

ReplayPath may also maintain local recovery/autosave data and a rebuildable cache of reference images so unsaved work or recognition features can continue to function.

ReplayPath does not automatically upload project files to Lyon Developers.

If you copy, email, upload, sync, or otherwise share a project yourself, that sharing is initiated by you.

ReplayPath maintains a local, size-bounded rotating diagnostic log, currently designed to remain roughly around 1 MB by dropping older entries.

The log may record technical events such as recording start/stop, playback outcomes, hotkey registration results, errors, simple counts, version information, and similar operational information.

ReplayPath does not intentionally log:

• the full content of what you type or click during a recording;
• passwords or credentials;
• full project payloads;
• screenshot/reference-image bytes;
• OCR-extracted text; or
• payment-card or PayPal account credentials.

Diagnostic logs remain on your device unless you choose to share them.

The “Copy Diagnostic Summary” feature copies a limited technical summary to your clipboard so you can decide whether to share it when requesting support.

ReplayPath stores its own application data locally on your device, including settings, recent-project information, recovery/autosave data, local caches, and diagnostic logs.

Saved project files are stored wherever you choose to save them.

ReplayPath does not provide cloud storage or a ReplayPath remote account.

As of this policy version, ReplayPath’s own application code does not make network requests for telemetry, analytics, crash reporting, project upload, cloud sync, or automatic update checking.

ReplayPath does not intentionally upload recordings, screenshots, OCR text, project files, or diagnostic logs.

The current exception is an action initiated by you: selecting “Donate with PayPal” opens the Lyon Developers PayPal page in your default external web browser. ReplayPath does not embed PayPal and does not receive your payment credentials.

This section describes ReplayPath’s own application code. Windows, the .NET runtime, the Windows App SDK, your browser, PayPal, and other third-party software are governed by their own behaviour and privacy terms.

If you choose “Donate with PayPal”, ReplayPath opens PayPal in your default external browser.

From that point you are interacting directly with PayPal. Any payment or account information you provide is handled by PayPal under PayPal’s own terms and privacy practices.

ReplayPath does not see, receive, process, store, or track your payment-card or PayPal account credentials and does not track whether you complete a donation.

ReplayPath uses third-party software components listed in the in-app Third-Party Licences view, summarised on the website’s Third-Party Notices page.

ReplayPath does not intentionally direct those components to upload your ReplayPath User Content. Lyon Developers cannot make representations on behalf of third-party component authors about their independent code or services.

ReplayPath’s local data remains on your device until it is removed through normal application use, deleted by you, removed when applicable app data is cleared, or removed as part of uninstalling ReplayPath.

Because ReplayPath does not maintain a ReplayPath cloud account or remote database for your project data, Lyon Developers generally does not hold a server-side copy of your ReplayPath projects, recordings, screenshots, OCR text, or local diagnostic logs to delete on your behalf.

ReplayPath does not add its own encryption layer to local project files or other local app data beyond the protections provided by Windows, the file system, your Windows account, and your device security configuration.

You are responsible for protecting access to your device, Windows account, project files, backups, and any locations where you choose to copy or sync ReplayPath files.

ReplayPath is a general-purpose desktop automation tool and is not directed specifically at children.

ReplayPath does not intentionally operate a service that collects children’s personal information for Lyon Developers. Its current local-only processing model applies regardless of the user’s age.

Depending on where you live and which laws apply to Lyon Developers, you may have privacy rights that cannot be excluded.

Because ReplayPath currently does not maintain a ReplayPath cloud account or server-side database containing your project content, most ReplayPath project data is controlled directly by you on your own device.

For questions about this policy or privacy matters, use the official contact method published on the Lyon Developers website.

Lyon Developers may update this Privacy Policy if ReplayPath’s features, data handling, distribution, or applicable legal requirements change.

A material change will use a new Privacy Policy version. Where appropriate, ReplayPath may require acknowledgement of materially updated legal documents.

Lyon Developers

For privacy or product enquiries, use the official contact method published on the Lyon Developers website.

Lyon Developers intends to handle personal information transparently and responsibly.

Where the Australian Privacy Act 1988 and the Australian Privacy Principles apply to Lyon Developers, this policy is intended to be read consistently with those requirements and does not limit any privacy rights that cannot lawfully be limited.