PSLNest — beta privacy notice
Version beta-20261010-r1.

Controller: JARKKO TAPIO NYKÄNEN, Finnish Business ID 3655618-2, Peltotie 1 as. 8, 15560 NASTOLA, Finland. Support and privacy requests: Info → Feedback and support → My conversations and replies, https://api.pslnest.com/support with your private support code, or the postal address above. This beta support channel uses Cloudflare and does not forward messages to Zoho Mail. No phone number or email address is required. Do not include passwords or recovery codes.

Activation
The service processes machine codes, entitlement and activation identifiers, accepted terms version, timestamps, request identifiers and application build details. Secret codes are processed for authentication; the database holds hashes and temporarily encrypted retry responses. The purpose is to provide and secure the two-computer trial. Necessary activation processing is based on the contract; abuse prevention on legitimate interests. Automatic activation cannot work without necessary data. Drawings are not required for activation.

Optional reports
A technical report contains application version and build identifiers, report ID and creation time, processing stage, available job counts and settings, and bounded event/fault traces with numeric method identifiers. Bounded local collection supports fault investigation based on legitimate interests. The automatic collector does not attach DXF files, geometry, part names, file paths or free-form exception messages. Your optional description of up to 2000 characters may still contain personal data: check it separately. You see the content before approving an individual report. Automatic consent for future technical reports is off by default and excludes your description.

Sending and investigating reports rely on separate consent. Withdrawal under Info → Feedback and support stops future and not-yet-started automatic transfers, but cannot recall bytes already sent. Request deletion of a received report separately using its report ID. Withdrawal does not affect earlier lawful processing. Reporting credentials and a random installation ID are separate from the licence, but the invitation link and network IP address can link information: reports are not guaranteed anonymous. Releasing a licence seat does not withdraw reporting consent. No advertising profiling.

Optional work attachments
You may separately select (1) a job copy containing part geometry, names, quantities, stock, materials, settings and current layout, (2) the part list, (3) a screenshot of the application, and (4) the nesting report as PDF and layout data. Original DXF files are not read from disk; the copy includes geometry already imported into the application. Attachments capture the currently open job, not an automatic copy of the job at the time of a crash. Original file paths, library and order references, stock location text and experiment profile identifiers are removed from the job copy. Part names, material text and pictures may still reveal personal or customer data and business secrets. Only the PSLNest view is captured, not the desktop or other applications.

All attachment choices start off. Prepare the files, inspect them, and separately approve sending that exact snapshot to Jarkko Nykänen to investigate faults and develop PSLNest. Reporting and your trial remain available without attachments. Sending and investigating attachments rely on voluntary consent; ownership stays with the data owner. Send only material you have authority to share. Never send secret credentials. Automatic reports never include attachments, and preparation sends nothing. Changing a selection clears its previous preparation and approval. Later changes to the job are not added to the approved snapshot.

Attachments use private Cloudflare R2 storage, restricted to the EU before the channel is enabled. Only the controller's protected administration view can retrieve them; there is no public download address. The application does not send attachments to GitHub or AI services; a separate transfer to an AI service requires separate permission. Limits are 1 MiB per report, including all files and packaging. Up to ten approved local bundles are retained (10 MiB, plus a temporary file of up to 1 MiB while saving). The service's total attachment limit is 2 GiB. The separate layout-data companion is included only up to 64 KiB; the review shows when it is omitted. The PDF is still included if it fits. Full layout data is available through the separately selected job copy if that copy fits the total limit. Larger files need a future transfer method and stay on your computer.

Cancel queued manual delivery in the same window. Bytes already sent cannot be recalled; request withdrawal of consent and erasure of received material in your private support conversation using the report ID. Withdrawal does not affect earlier lawful processing. Local bundles are removed on cancellation or receipt; service bundles are removed with the report and during cleanup at the 30-day attachment retention limit. Retention starts at technical report creation; retries do not extend it. If only technical details have arrived, the entire report stays queued until approved attachments are also acknowledged. Outages may delay service cleanup. R2 attachment files are not part of D1 database restore points; file names, sizes, hashes and the consent notice version are D1 metadata and may be held in those restore points.

Private support conversations
You can read replies and send follow-up messages in the application or at https://api.pslnest.com/support. Authentication uses the separate reporting credential, never the licence recovery code. Each installation sees only its own reports; anyone with its support code can access those conversations, so keep it private. Credentials normally last 90 days and can be renewed in the application. The controller can read and answer messages through the protected administration page. No email notification is sent.

Replying to your requested support conversation is based on the controller’s legitimate interest in helping testers and resolving software faults; only necessary message and routing information is used. Optional technical-report and attachment consent remains separate. You may object or request deletion in the conversation. Messages are retained only until the original report expires (90 days from its creation), and deleting that report removes its conversation. Follow-ups do not extend retention. Up to 100 follow-up messages per conversation and 4000 characters per message are accepted. The application checks for replies at most every 15 minutes, and every 5 minutes in the open conversation window.

Recipients and locations
The technical platform is Cloudflare, Inc. (United States) and its group companies, acting as processor. The licence database (Cloudflare D1) and update package storage (Cloudflare R2) are restricted to the EU region. Application code runs on Cloudflare's edge network at the nearest server, which may be outside the EU and EEA, and Cloudflare routes traffic across its global network. Transfers outside the EU and EEA rely on Cloudflare's data processing addendum and the European Commission's standard contractual clauses included in it. EU-only processing is therefore not promised; EU-only storage is.

The application's private fault-notification channel to GitHub is not currently in use; if it is enabled, this notice will be updated in a new version before that happens. The service's administration view is protected with Cloudflare Access and limited to the controller's own account with multi-factor authentication. There are no other recipients; data is not sold or disclosed for marketing.

Retention and deletion
The local technical queue holds up to 10 reports / 2 MiB. Files older than 90 days are removed during application maintenance, not while the application is closed. Consent and licence records remain separately on the computer. On the service, report content is cleared 90 days after report creation and receipt records 90 days after receipt. Licence and invitation data become eligible for cleanup 30 days after expiry; administration records are kept for 30 days. Cleanup is scheduled and batched, so deletion can be delayed by an outage.

The database platform automatically keeps restore points for the last 7 days on the current Workers Free plan (Cloudflare D1 Time Travel). This cannot be switched off. Deleted data may therefore remain recoverable for up to 7 days after deletion, after which the restore point expires. The application's own logging is switched off and the service writes no request log. Cloudflare still processes connection data such as IP addresses on its own network to route traffic and prevent abuse, under its own practices and retention periods. Do not assume that uninstalling the application deletes records held by the service.

Your rights
You may request access, correction, erasure, restriction and, where applicable, portability, and object to processing based on legitimate interests. You may complain to Finland's Data Protection Ombudsman or your competent local authority. Ownership of records may need secure verification; never include recovery codes or private keys in reports. Requests are answered within one month; if erasure concerns data still held in restore points, we will tell you when those expire.

Optional usage sharing (consent text usage-20261013-r1)
A separate, initially unchecked consent in User settings permits sending basic usage statistics to Jarkko Nykänen to improve PSLNest and evaluate the beta. The data includes a random tracking ID, consent time and text version, app version, UTC activity day and counts of launches and nestings started, completed, cancelled or failed. Completed means calculation finished, not that every part fitted. Returning means activity on at least two different UTC days. Counts describe installations, not people. A new consent creates a new tracking ID. No job contents, geometry, quantities, part names, file names or paths, screenshots, mouse movements or keystrokes. The application does not store IP addresses in these statistics. Cloudflare processes network connection data according to its own policies.

Transfers use the existing private reporting connection and Cloudflare D1 database. The tracking ID is not a login secret. The reporting grant and beta invitation can technically link the statistics to the trial entitlement: the data is pseudonymous, not guaranteed anonymous. You may share the tracking ID shown in settings with the developer if you wish to identify your installation. The dashboard uses the existing Cloudflare Access protection. The processor and international-transfer provisions elsewhere in this notice also apply.

Consent does not affect your license or separate report and attachment permissions. Usage consent is never saved in a job or nesting defaults. You may uncheck it at any time in User settings. Collection and new usage transfers stop immediately; local counters are cleared and deletion of uploaded usage statistics is queued for the next successful connection. Bytes already dispatched cannot be recalled, but the server rejects late retries under a withdrawn consent. A new consent can be enabled after the earlier deletion succeeds. Withdrawal does not affect earlier lawful processing. If the app cannot start, request deletion through the private support channel using the tracking ID; do not disclose secret codes.

The service retains at most 90 activity days, each for at most 90 days from the activity date. A maintenance outage may delay physical erasure; the dashboard hides expired data. A consent receipt is kept up to 90 days from the last receipt. A withdrawal receipt retains only the tracking ID, consent version and consent/withdrawal times for 90 days to prevent a late upload restoring deleted usage. Deleted data can remain in D1 recovery points for up to 7 days. The local queue holds only the last 7 UTC days, at most 8 KiB, and is pruned while the app is used. Transfers run in the background at most every six hours. Short-session statistics may arrive on the next launch; outages do not interrupt the application. No advertising profiles or marketing disclosures. Rights and contact details are described above.