HOME RECORDS LABEL ACCOUNT, PURCHASE AND LICENSE PRIVACY NOTICE

Scope of this notice

This notice covers the shared website, HRL Center and PSynth3 account, product assignment, licenses and delivery of Paddle purchases. Other offers and the voluntary newsletter have their respective stated notices. Paddle separately determines the purposes of its own sales processing.

Account and login

To perform the account agreement, we process email addresses, random IDs, creation and address-confirmation dates, and the history of accepted terms and presented notices. Email and mailbox confirmation are required for an account, but not for reading product information. Short-lived challenges, protected representations of codes/tokens, session deadlines and attempt limits protect access on the basis of the legitimate interest in security. Hosting and connections process IP addresses and request information. The account database encrypts email addresses and stores hashes of codes/tokens. A code expires after 10 minutes; an HRL session lasts no more than 8 hours without remembering it, or 30 days after a deliberate choice. The login-message language is sent to the server separately from the language recorded for document acceptance. The planned login-email channel runs through DiH to your mailbox provider. The actual sender, SMTP parameters and delivery through that channel remain to be verified before publication. Purchase email addresses in other systems are not automatically covered by the same encryption as the account database.

Purchase, license and delivery

Paddle supplies data needed to deliver and handle a purchase: the purchase email address; customer, transaction and event identifiers; product/price, quantity, amount, currency, dates and payment or refund status. The backend design provides for storing this information in Cloudflare D1 and a delivery queue, including attempt results and message IDs. The delivery queue and archive are not yet operating in a hosted environment. Full card details are not sent to Center or the license register described here. An authorized operator has access to the necessary part of the Paddle dashboard. The code register stores a protected hash of PS3R; its plaintext form is needed for sending and customer use. Resend and the mailbox provider handle the message containing the code. Assignment links a product to an account ID; activations record a random installation ID, supplied platform/device name, version, dates, device count and license status. The installation ID is not a scan of the entire computer or proof of a person's identity. Code status and necessary events support delivery, entitlement handling, failures and refunds. The basis for data needed for the agreement is its performance, for required records the applicable legal obligation, and for proportionate security and claims the legitimate interest. Marketing is separate.

Providers and transfers

The service design separates provider channels: DiH for the account and login email, Cloudflare for the license API, purchase register and D1/Worker queue, Resend for purchase messages, and Paddle for sales. The client panel shows an active NetHome service. DiH states that the physical server is in Poland and backups are stored in AWS, Frankfurt region (Germany). These are provider statements, not a complete processing map. The applicable contracting entity, service and data-processing terms, full list of subprocessors, and remaining processing locations and provider-log retention still need to be established. Authorized people and providers have access to the extent necessary. In the reviewed Workers Free plan, both D1 databases have the Eastern Europe region, jurisdiction None and read replication disabled. This does not guarantee that all data is processed exclusively within the EU. The standard Self-Serve terms incorporate a DPA for data processed on behalf of a customer; DPA 6.4, effective from 3 April 2026, was reviewed. The description of the reviewed Free account relies on these standard terms, without inventing a historical date of individual acceptance. Sources: https://www.cloudflare.com/terms/ and https://www.cloudflare.com/cloudflare-customer-dpa/. Resend (Plus Five Five, Inc.) has a confirmed Free account and an existing provider-signed DPA which, under its standard terms, applies from account creation. Ireland/eu-west-1 identifies the sending region, not the storage location. The provider describes storage of customer data in the USA and transfer safeguards through SCC and additionally DPF. Source: https://resend.com/security/gdpr. The reviewed HRL purchase transport sends Resend the recipient address, sender, subject and plaintext product or activation code; it does not itself add tracking pixels or links. A read of the configuration for psynth3.homerecordslabel.com at 2026-10-15 22:53:32 CEST (20:53:32 UTC) confirmed that open tracking (open_tracking=false) and click tracking (click_tracking=false) were disabled. This concerns this domain's configuration at the time of the read; it is not evidence of the resulting MIME, delivery, the absence of possible application overrides or the absence of other personal-data processing. The read does not cover other domains, DiH login mail or the newsletter. Paddle and HRL act as separate controllers within the scope of the standard data-sharing agreement. For a Polish supplier, the standard MSA identifies Paddle.com Inc. for transactions in the USA and Paddle.com Market Limited for others; buyer terms additionally identify Paddle.com (Canada) Ltd. for Canada. Checkout and the confirmation identify the entity applicable to a particular purchase. We do not add a historical HRL acceptance or a potentially different agreement without evidence. Sources: https://www.paddle.com/legal/data-sharing-addendum and https://www.paddle.com/legal/privacy. The applicable DiH entity and contract/data-processing terms, complete subprocessor list, remaining locations and log-retention periods, and binding backup policy remain to be completed. The panel shows an active NetHome service; the server and backup locations and standard one-month retention of backups and mail logs have already been stated by the provider. DiH states an SMTP limit of 200 messages per mailbox per day and a shared pool of 1000 for the entire account, all domains, scripts, shop and mailboxes, counting each message recipient. The actual reset and its timezone, sender/SMTP/TLS parameters and actual delivery have not been established. Statements about patch maintenance and permitted cron use do not replace acceptance of the runtime and actual execution. The selector shows native PHP 8.3; this does not confirm extensions or the application environment. Observed mailbox counts concern different scopes: 13 for the entire hosting account and 6 for the homerecordslabel.com domain; they do not identify the HRL message sender. Retention and task execution, D1 backups, completeness and restoration of the received manual account-database export, backup rotation, actual delivery and resulting messages, including possible application overrides of the Resend domain settings, and the full scope of operator access require separate verification. The response confirming no additionally configured backups or tasks has been received; it does not replace verification of future mechanisms. Existing Workers' links to separate D1 databases are confirmed; running API versions and applied migrations are not confirmed by a dashboard review. A read client's block on /healthz is not evidence of a service failure. The full source-and-gap matrix is private operator material.

Website session and local files

The account panel uses a necessary session and a __Host-HRLAccount cookie containing a random website-session ID, restricted to the host, with Secure, HttpOnly and SameSite=Strict. After choosing “Remember me on this device”, remembering lasts no more than 30 days; without that choice, the cookie is a session cookie and the absolute HRL session limit is no more than 8 hours. An earlier HRL session expiry may end access. The HRL token and challenge data remain on the server, rather than in browser localStorage or URLs. The cookie serves login and security, not advertising. This does not cover every technology used by the entire website or checkout; those have their own descriptions and required choices. Center protects the session using the Windows user mechanism; clients also store a local signed license cache, random ID and language/theme settings. The license remains after logout. Operating-system protection does not protect against a person or program controlling the logged-in system account. Deleting files yourself may require reconfiguration or activation. Center and PSynth3 diagnostics remain local; a support report is deliberately exported and is not sent automatically. Center rotates logs to a limit of five files of 1 MiB each. Crashpad memory dumps may contain fragments of private data; they are not added to the ordinary JSON report. At the next startup, Center deletes dumps older than 7 days or exceeding the limits of five files and 50 MiB. Local diagnostic periods are not the retention periods for hosting logs or purchase data.

Retention and deletion

Account data is retained until deletion; deletion removes the email address, sessions and challenges from the active account database. The approved HRL policy provides for deleting expired sessions by the next day and code challenges no later than approximately 48 hours after expiry, account database backups for up to 30 days, and a limited deletion journal for approximately 32 days to reapply deletions after restoration. Our ordinary logs have a target of 30 days, and necessary security and delivery audit records 90 days. We reduce duplicated purchase email addresses after 90 days when delivery and safe recovery are assured. Minimal evidence of entitlement remains while servicing a valid license, with annual review. Obligations and claims may justify other periods for billing and complaint records. Account deletion does not automatically erase every purchase, used-code, license, old-ID blocking or purchase-email record in commerce. Pseudonymous IDs are not anonymous. Confirmed D1 databases have 7 days of Time Travel, and standard Workers Free dashboard logs have 3 days; these are separate from HRL's own targets. Resend describes 30 days for messages/logs, 7 days for backups, and deletion of remaining data within 90 days after its service ends. Paddle determines retention by the duration of the relationship, applicable obligations and claim periods; it does not state one fixed period for all data. Locally tested BFF cleanup also covers obsolete pseudonymous support counters. One newsletter task is configured to run every minute in the DiH dashboard; execution or delivery has not been confirmed, and it has not been shown to implement HRL account retention. The Cloudflare staging schedule is separate and likewise does not prove execution. The DiH restore-backup selection view did not show an available file; this does not prove that provider backups do not exist. A known local website-backup folder exists. The operator confirmed that, apart from the known website backup and configured newsletter task, they had not configured additional backups or tasks. A new private manual account-database export was prepared; the received file was structurally checked. This does not yet confirm completeness against the active database, restorability, automated backups or rotation. D1 backups, full database restoration and reapplication of the deletion journal still require acceptance. According to DiH, standard backups cover all account files and directories, application logs and database dumps transferred to S3; they are retained for one month in AWS, Frankfurt region (Germany). According to the provider, mail logs are retained for one month on the server only, outside the backups. One month does not mean a guaranteed 30 days or confirmation that the HRL target of retaining backups for no more than 30 days is met. The provider refers formal retention guarantees to the service terms and policy, whose applicable version still requires acceptance. Restoring a full dump also rolls the deletion journal back to the backup state; preserving its current version through selective restoration or a separate database is the application's responsibility and requires acceptance. Actual implementation of HRL retention, restoration and compliance with deletion requirements still require verification before publication. Approved HRL periods and schedule configuration do not replace acceptance of actual operation.

Rights and human review

You may request access, rectification, erasure and restriction, and, where you are entitled to do so, data portability or the right to object to processing based on legitimate interests. Some records may remain because of applicable obligations and claims. The website-panel and Center export includes the basic account, available entitlements and accessible document history; it is not a complete copy of all Paddle, D1, email and hosting records. Send broader requests to contact@homerecordslabel.com; we use proportionate identity verification. You may complain to the President of UODO or the competent authority. We automatically check codes, payments/entitlements and limits, without advertising profiling. You may submit a disputed refusal for human review; the legal classification of these mechanisms still requires assessment.

Support and purchase recovery

After you deliberately submit the form, we handle the problem description, supplied transaction reference, language, request identifier, and verified account ID and email address. A short-lived login proof for purchase recovery remains server-side and is sent to authorized support; it is not a login code. The proof is valid for up to 15 minutes and does not automatically transfer ownership. The message is sent to contact@homerecordslabel.com. Attempt limits and pseudonymous counters protect email against abuse. Handling is based on performing the service or processing the request; proportionate security relies on the legitimate interest. Do not send login codes, full card details, passwords or other unnecessary data. Retention of support messages and actual DiH email requires confirmation in the final notice.

Marketing and changes

An account, purchase or trial does not subscribe you to Studio Notes. Login and purchase messages support the requested service; marketing requires a separate choice and notice. We present material changes to purposes, recipients and terms in good time. Acceptance of the account terms does not replace a processing basis or consent required for another purpose. We preserve document history and earlier acceptances instead of silently rewriting their versions.

Website, media and Studio Notes

The description above concerns accounts, purchases and licenses. Information for website visitors, embedded YouTube/SoundCloud media, contact and the voluntary Studio Notes newsletter is available at /privacy/. Before publication, we jointly update the scope descriptions and links between the two notices. Historical offers from other stores retain separately identified terms; we do not present them as Paddle purchases.

Controller and contact

The controller of the HRL data described here is Piotr Jaczewski, operating Nuera – Piotr Jaczewski, ul. Januszowicka 13/12, 53-135 Wrocław, Poland, NIP 8942771960, EU VAT PL8942771960. Contact: contact@homerecordslabel.com. Website, media and newsletter privacy: https://homerecordslabel.com/privacy/