# ReceiverLogs Beta Privacy Notice **Version:** 1.0-beta.2 **Effective date:** 2026-07-20 This notice explains how **Frank Smith XYZ Inc.** (**“Frank Smith XYZ,” “we,” “us,”** or **“our”**) handles personal information in connection with the Phase 1 ReceiverLogs beta. It distinguishes the local desktop application from the website, download infrastructure, email, and support interactions. ## The desktop application ReceiverLogs is designed to process receiver-log files and related working data locally on the device where you run it. Using the desktop application does not, by itself, send Frank Smith XYZ the contents of imported files, extracted records, project metadata, file paths, or ordinary in-application activity. The current Phase 1 beta does not require a ReceiverLogs account and does not include product analytics, advertising trackers, automatic crash-report uploads, remote licence or acceptance checks, or automatic update checks. It does not automatically upload user data or application logs, and updates are obtained manually from the website. Apart from opening an external website or email address when you direct it to do so, the desktop application does not initiate network communications. Before each release, Frank Smith XYZ verifies these statements against the exact binaries. If a future build introduces collection or transmission, we will update this notice and provide any notice, choice, or consent required by law before that collection begins. The application stores information locally as needed to operate, which may include settings, evaluation status and acceptance records, digest-verified accepted End User Licence Agreement (**EULA**) text, indexes, caches, logs, and working data derived from files you choose to open. This information remains under the control of the device's owner or authorised user unless you deliberately send it to us. The installation guide identifies the application-data directory used by the installed build. To remove ReceiverLogs-managed local data, quit ReceiverLogs, uninstall it, and delete that directory. Doing so removes ReceiverLogs information stored there, including settings, acceptance evidence, project history, caches, and local application logs. It does not remove project directories, exports, backups, operating-system logs, or files stored elsewhere; remove those separately if desired. ReceiverLogs writes an active operation log under the application-data directory at `logs/operations/current.jsonl`. It records backend operations and diagnostic context and may include timestamps, command or operation names, performance information, project paths, and project-context information. Before a write would take the active file over 16 MiB, ReceiverLogs rotates and compresses it. At startup and after rotation, ReceiverLogs removes rotated archives older than 30 days and, if the remaining rotated archives exceed 256 MiB, removes the oldest archives until they are within that limit. Those age and aggregate-size limits apply to rotated archives, not to `current.jsonl`; cleanup does not run while the application is closed, and the active file may contain older entries until it rotates or is removed. Separate detailed instrumentation is normally disabled and writes local JSON Lines files under `logs/instrumentation/` only when it is explicitly enabled or a diagnostic build is configured to enable it. Instrumentation may include application interaction, performance, memory, query, and project-context observations. The current implementation does not automatically upload either kind of log and does not automatically delete instrumentation files; instrumentation files remain locally until removed by the device owner. Review logs before sending them because paths, identifiers, or study context may be sensitive. The local EULA acceptance record identifies the selected legal-document language, accepted EULA version and hash, acceptance time, application version, workflow-assigned Release Timestamp, and evaluation expiry. ReceiverLogs may also retain a digest-verified copy of the exact accepted EULA text. The record does not contain your name, email address, organisation, IP address, device fingerprint, hardware identifier, ReceiverLogs account identifier, or another generated cross-profile identifier, and it is not automatically transmitted to Frank Smith XYZ. Reuse of the record is limited to the same accepting individual in that local ReceiverLogs application-data and operating-system-profile context. ReceiverLogs does not identify the person using a shared, copied, restored, or migrated profile; another evaluator must use their own operating-system profile or remove the local ReceiverLogs `legal/` data as described in the installation guide and accept separately before evaluation use. ReceiverLogs may allow you to open an external website or email address. If you choose to do so, your browser, email provider, network operator, and the destination service handle the resulting communications under their own practices. ## Website and software downloads When you visit a Frank Smith XYZ website or download a ReceiverLogs build, the website, hosting provider, content-delivery network, and security services may automatically process standard request information such as your IP address, request date and time, requested URL, referring page, user-agent or browser information, response status, and download volume. This information is used to deliver the site and files, maintain security and reliability, diagnose faults, prevent abuse, and produce aggregate operational statistics. The Phase 1 evaluation is free of charge and requires no payment card. Frank Smith XYZ does not collect payment information for it. The help site uses browser local storage to remember the selected colour theme and session storage to restore scroll position and related navigation state. These functional values are not used for cross-site advertising and can be removed through browser controls. On Windows, the installer mode selected for the applicable release may use a Microsoft Edge WebView2 bootstrapper. If a suitable WebView2 Runtime is unavailable, installation may contact Microsoft to obtain or run components required by the application. The release-specific installation page identifies the selected mode and any expected network activity. Microsoft, network providers, and organisational network administrators may process information about that request under their own practices. The Phase 1 beta is not intended to use information from the desktop application or website for cross-site behavioural advertising or to sell personal information. Hosting, security, email, and other service providers may process or store information in Quebec, elsewhere in Canada, or outside Canada, where it may be subject to local law. We retain information under our control only for as long as reasonably necessary for the purposes described above, security, legal obligations, dispute resolution, and ordinary backup cycles, after which it is deleted or anonymised when no longer required. We require service providers to protect information as appropriate to their role. ## Email, feedback, and support If you email us, submit feedback, or request support, we receive the information you choose to provide, such as your name, email address, organisation, message, screenshots, diagnostics, and attached files. We use it to communicate with you; investigate your submission; improve or secure ReceiverLogs; administer the beta and provide requested support; satisfy legal obligations; and protect our systems, rights, and users. Do not send confidential information, passwords, security credentials, personal information you are not authorised to disclose, or receiver-log or project data unless we have specifically asked for it and you have confirmed that sending it is lawful and appropriate. Where practical, remove or redact information that is not necessary to the request. A narrow operational request about download, installation, access to legal notices, or another support issue is not treated as product feedback merely because it arrives by email. Feature requests, bug reports, usability observations, and other intentionally submitted product feedback are governed by the feedback clause in the ReceiverLogs EULA or by its approved summary when either is presented before submission. That clause applies to the substance of intentionally submitted comments, ideas, suggestions, and observations—not to personal information, files or data used with ReceiverLogs, logs, screenshots, attachments, or other supporting material. We handle that information and material under this notice and use or reproduce it only as reasonably necessary to investigate and respond, improve or secure ReceiverLogs, administer the beta, provide requested support, satisfy legal obligations, and protect our systems, rights, and users. Commercial-licensing or services inquiries may be retained as business correspondence and used to respond, prepare proposals, negotiate agreements, and administer a resulting relationship. ## Disclosure We may disclose personal information to service providers that perform hosting, content delivery, email, security, professional-advisory, or support functions for us; when you direct or authorise the disclosure; as required to comply with law, legal process, or a lawful government request; to protect rights, safety, systems, or users; or in connection with a proposed or completed financing, reorganization, merger, sale, or transfer of relevant business assets, subject to applicable safeguards. We do not authorise a service provider to use personal information for purposes unrelated to providing its services to us, except as law permits and its separately disclosed role requires. ## Your choices and rights You are not required to send files or optional feedback to evaluate the desktop application. You may contact us to ask whether we hold personal information about you and to request access, correction, or deletion, subject to applicable law and legitimate retention requirements. We cannot access, correct, or delete data that remains solely on your device and was never sent to us. You may also ask questions, withdraw a consent where processing depends on consent, or challenge our compliance. Withdrawal does not affect processing already lawfully completed and may limit our ability to provide an optional service you requested. ## Security We use administrative, technical, and physical safeguards appropriate to the sensitivity of personal information under our control. No storage or transmission method is completely secure, and we cannot guarantee absolute security. You remain responsible for securing your device, accounts, local files, and backups. ## Children ReceiverLogs is offered only for professional, scientific, academic, institutional, governmental, or business evaluation by people who have reached the age of majority where they live. It is not offered for personal, family, or household use and is not directed to children. Do not provide personal information about a child through feedback or support unless you are authorised to do so and it is necessary and lawful. ## Changes to this notice We will identify this notice by version and effective date and will not rewrite an archived version retroactively. We will make a new notice available before a material new collection, use, or disclosure begins and will seek consent where required by law. ## Contact Privacy questions, complaints, and requests may be sent to: **Frank Smith, President and Privacy Officer** **Frank Smith XYZ Inc.** Email: **frank@franksmithxyz.com** You may also have the right to complain to the Office of the Privacy Commissioner of Canada, the Commission d’accès à l’information du Québec, or another privacy regulator with jurisdiction.