This privacy notice describes the static Laura Dova Weddings website as supplied. It covers the journal pages and local assets. Hosting, email service, operator identity, applicable jurisdiction, and any future analytics or advertising configuration require owner review before public deployment. Those details are not presented as already verified.
What the supplied website does The website serves static HTML, CSS, a small navigation script, images, icons, and fonts. Its code does not include analytics, advertising pixels, embedded social feeds, a newsletter signup, user accounts, payment processing, or a contact form. It does not set cookies or use browser local storage or session storage. Checking an on-page checklist is temporary and does not submit a response or save your choices.
All page imagery and fonts are served from the site's own asset folders. Ordinary outbound links take you to external websites when clicked; those websites operate under their own privacy policies. Social sharing metadata describes a page but does not load a social network widget into it.
Hosting and request information Even a static website must receive a request to send a page. The hosting provider may process an IP address, request time, requested URL, browser information, referrer information, and security logs. The supplied files do not identify the future hosting provider, its retention period, processing locations, or contractual arrangements.
The owner must confirm these details, determine the applicable purposes and legal basis, and update this notice before deployment. Technical security and delivery logs should not be described as anonymous unless the actual setup supports that claim. Any hosting-level tracking or cookie behavior must also be reviewed, since it is outside the static source code.
Email correspondence The Contact page currently displays an unverified placeholder mailbox. Once an email channel is enabled, its provider may process the address, name, message content, attachments, and related technical information. The owner must explain the purpose of handling enquiries, who can access correspondence, and how long it is kept.
Do not send passport details, payment data, medical information, private guest lists, or other sensitive material for a routine editorial question. A correction normally needs a page URL and source link. The website itself does not upload or store attachments.
Cookies, analytics, and future changes No cookie banner is included because the supplied website code does not set cookies or use tracking services. That is not a statement that every future deployment will be exempt from consent requirements. If the owner adds analytics, ads, embeds, a response service, or other data collection, this notice and any required consent mechanism must be updated before the new processing begins.
Record the service name, data collected, purpose, retention, third-party sharing, and any available choices. Do not keep the statement “no analytics” after an analytics tool is enabled. A visual redesign alone may not affect privacy, but a new integration can change it substantially.
External links Following a reference leaves this website. The destination may collect information, set cookies, or provide commercial services. Review its notice before sharing information or purchasing anything. A link from the journal does not mean the journal operates the destination or controls its data handling.
Rights and requests Privacy rights depend on applicable law and the actual processing involved. They may include access, correction, deletion, restriction, objection, portability, or a complaint to a relevant authority. The operator identity and working request channel need confirmation so requests can be addressed to the correct responsible party.
The owner should identify the operator, jurisdiction, contact channel, hosting and email providers, and retention periods in this notice. Do not assume a placeholder email is a working rights-request address. Once verified, the Contact page should point to the confirmed channel.