Who is responsible
The website operator is Morgan Yann Dominique, contactable at [email protected]. This notice covers processing for the LAYERNOTE publication. Hosting, security, email or access-control providers may also process information to deliver their services under their own privacy notices.
What the site processes
Serving a page involves network information such as IP address, request time, URL, browser information, referring page where supplied, response codes and diagnostic or security events. Hosting and security providers may record these in logs.
If you email us, we receive the email address, message, attachments and correspondence metadata you send. Only include what is necessary. Do not send wallet recovery phrases, private keys, financial details or unnecessary sensitive information.
The journal has no reader registration, mailing-list signup, payment form, wallet connection or public content-submission form.
Saved stories and browser storage
When you choose to save a story, the journal stores its article identifier in your browser under the key layernote.saved.v1. This is a functional preference kept on your device. The project does not transmit your saved list to its server or synchronise it between devices.
Use “Clear saved” in the Saved view or clear site storage through your browser to remove the list. It otherwise remains until you remove it or your browser clears it. If storage is unavailable, saving may work only for the current visit. Search, sorting and the article currently open are kept in memory for the visit.
Cookies and the editor
The public PHP journal code does not start a reader session or set a reader cookie. The password-protected editor uses an essential layernote_editor session cookie to authenticate the operator and protect editing requests. It is not a marketing cookie and is not required to read articles. Editor authentication expires after eight hours; the browser cookie is a session cookie.
For login-abuse prevention, the editor stores a keyed hash derived from the request IP address, failure counts and timestamps in private storage. Old login-attempt records are removed during subsequent sign-in handling after 24 hours. The raw IP is not stored in that table, although infrastructure logs may contain it.
Hosting or security systems may use additional essential technologies. The privately hosted preview may require authentication through its access provider, separately from the public PHP journal. Review that provider’s notices for its own processing.
Purposes and legal bases
Necessary request data is used to deliver, maintain, diagnose and secure the website. Functional storage provides the saved-story feature you request. Editor sessions and rate limits protect authorised publishing. Correspondence is used to answer questions, review corrections and handle rights requests.
Where the GDPR or UK GDPR applies, the operator relies on legitimate interests in operating a limited informational site and protecting it, after considering the impact on individuals, or on a legal obligation where required. Where a particular activity needs consent, it must not start before valid consent is obtained. Browsing is not treated as consent to optional tracking.
No advertising or analytics trackers in this edition
The project’s code includes no X Pixel, conversion tracking, third-party analytics, social embeds or advertising SDK. It does not create marketing profiles or make automated decisions producing legal or similarly significant effects. Browser requests still reach the hosting infrastructure.
If optional tracking is introduced, this notice and any legally required consent controls must be updated before that processing starts. A statement in this policy does not itself enable or authorise a tracker.
Recipients and international processing
Hosting, security and email providers may process information needed for their services. Information may also be disclosed where legally required or necessary to protect lawful rights or handle abuse. The project does not sell personal information or share it for cross-context behavioural advertising.
Providers may operate internationally. Where the operator makes a restricted transfer, the safeguards required by applicable law must be used, such as adequacy or appropriate contractual safeguards. Contact the operator for information relevant to a particular deployment.
Retention and security
Reader bookmarks stay on the reader’s device as described above. Editor authentication lasts up to eight hours. The login-abuse table follows the 24-hour cleanup rule described above. Articles and editorial settings are retained to operate the journal until changed or deleted by the operator.
Correspondence is kept only as long as needed to resolve an enquiry, meet an applicable obligation or handle a reasonably anticipated legal claim. Technical log retention depends on the actual hosting and security configuration; the operator can provide deployment-specific details. Data should be removed or anonymised when no longer needed.
We use proportionate access controls, but no internet system is guaranteed completely secure.
Your rights and choices
Depending on applicable law, you may request access, correction, erasure, restriction, portability or object to processing. If processing relies on consent, you may withdraw it without affecting earlier lawful processing. Contact [email protected]; verification is limited to what is necessary, and any lawful limitations will be explained.
You may complain to your local data protection or other competent supervisory authority. You can remove browser bookmarks without contacting us. You do not have to provide contact or financial details to read; basic network data is necessary to deliver the page.
Children, external sources and updates
The site is not designed to collect information from children and has no reader-registration feature. A parent or guardian may contact the operator about personal information a child has sent by email.
Opening an external source sends a request to that source’s website, whose own policy applies. The journal’s source links do not include affiliate identifiers. We will update this notice and provide any further notice required by law before materially changing processing.
Publication contact
Website operator: Morgan Yann Dominique
Email: [email protected]