Privacy policy

Operator / seller / data controller

Reference domain: marianataranu.com

Legal name

[DE COMPLETAT]

Legal form

[DE COMPLETAT]

Country of registration

[DE COMPLETAT]

Registration number

[DE COMPLETAT]

Tax / VAT identifiers

[DE COMPLETAT]

Professional address

[DE COMPLETAT]

Public email

[DE COMPLETAT]

Public telephone

[DE COMPLETAT]

Data protection contact

[DE COMPLETAT]

Scope and present stage

The data controller is the independently configured operator of this site, not automatically the author, the other site’s operator or TeÎncarc. Its identity, country and data protection contact are [DE COMPLETAT]. This policy distinguishes the current local preview from future purchases.

There are no public customer accounts, contact form, newsletter subscriptions or marketing campaigns in the current implementation. There is no visitor profiling or automated decision-making with legal or similarly significant effects by the site. Studio authentication is for authorised content editors, not customers.

Page requests and technical operation

Opening a page sends the IP address, requested URL and ordinary browser/connection data to the server serving it, to deliver the page and maintain security. Both public sites, marianataranu.com and metodorus.com, are hosted on Cloudflare Pages over HTTPS. The development preview remains local. Workers, remote D1 and private R2 delivery are not activated by publishing these static sites.

For a future operator, necessary delivery and proportionate security logging are assessed under Article 6(1)(f) GDPR: legitimate interests in providing a functioning, secure site, balanced against visitors’ rights. Hosting uses Cloudflare Pages; contracted entities, log contents, recipients and retention are [DE COMPLETAT]. Logs should be restricted to what is necessary, not used as undeclared analytics.

Published content and Sanity images

Sanity is configured for the published blog and product catalogue. Content requests are made from the build/server, without forwarding the visitor’s IP to Sanity for those queries. Images hosted at cdn.sanity.io, where displayed, are requested directly by the browser: Sanity/CDN can receive the visitor’s IP and technical request data. Locally hosted images do not require that external image request.

The purpose is publication and display of content, with Article 6(1)(f) as the proposed basis for necessary delivery after assessment. The author’s name, photograph and other editorial personal data also appear in published content; rights and publication basis must be confirmed for each contribution. The Sanity contracting entity, processor arrangements, processing locations and technical-log retention are [DE COMPLETAT]. Public content remains available while published and is reviewed when changed or lawfully removed.

Correspondence and complaints

A public email/form service is not configured. Once the confirmed contact is available, messages may contain your name, reply address and the information you choose to send. They will be used to answer requests, resolve complaints or take requested pre-contractual steps.

The relevant basis is Article 6(1)(b) for contractual/pre-contractual requests, 6(1)(c) where a specific legal duty applies, or 6(1)(f) for other correspondence and defence of rights, after balancing. Authorised staff and the selected email provider may receive the necessary data. Provider and retention are [DE COMPLETAT]; the criterion is resolution of the request plus applicable legal or limitation periods, not indefinite retention. Do not send unnecessary sensitive data.

Orders and Stripe: prepared test flow

The shared commerce implementation records product and order identifiers, title/language, amount/currency, site/interface language, origin, timestamps, payment session/status, checkout URL, a hash of the access token and identifiers/types of received payment events. The local D1 schema does not store customer names, email, postal addresses or card details. Signed webhook payloads are processed transiently and can contain additional Stripe data without those fields being persisted in these tables.

If test checkout is enabled, Stripe’s hosted page receives payment and any contact details entered there. The site does not receive full card numbers or security codes. Stripe test keys are currently empty; no real payments are supported. Mariana does not expose public purchasing; MetodoRUS exposes local test checkout only.

For future actual purchases, necessary order/payment processing is based on Article 6(1)(b), required fiscal records on 6(1)(c) once the applicable obligation is identified, and proportionate fraud prevention/claims on 6(1)(f). Authorised staff, the contracted payment provider, storage/hosting providers and legally entitled authorities may receive necessary data. Stripe’s legal role can vary between services; entity, roles, countries and retention are [DE COMPLETAT]. A test mode is not permission to use real card or unnecessary personal data.

Future supply, physical delivery and accounting

Future digital delivery may use email, order entitlements, access links and access/security events to provide the purchased files. Immediate-supply choices and the version/time of the contractual acknowledgement must be recorded as evidence. These contractual records rely on Article 6(1)(b)/(c) as applicable; agreement to immediate supply is distinct from consent to personal-data marketing.

If printed books are sold, name, delivery address and necessary contact details may be shared with the selected carrier under Article 6(1)(b). Necessary billing data may be processed for accounting under 6(1)(c). Carrier, invoicing/email providers, mandatory fields, applicable laws and periods are [DE COMPLETAT]. No carrier integration, automated invoicing, delivery email or private file delivery is active. Cloudflare R2 is planned only. Data needed to fulfil a future order must be identified before purchase; without necessary data that order may not be fulfilled. Browsing does not require an order.

Cookies, session storage and consent

The current site adds no analytics or advertising cookies, pixels or external tracking scripts. The analytics adapter is disabled. There is no cookie-consent banner or preference centre, and no consent is inferred from continued browsing. This describes the site code, not a promise about the separate Stripe service after leaving the site.

When a user initiates test checkout or opens a checkout return, the browser uses sessionStorage for the retry identifier, order identifier and secret order-status token. Keys start with checkout:intent: or checkout:order:. They support the requested payment/status flow, not cross-site advertising. Each origin has separate storage. It normally lasts for the tab/session, but browser session restoration can preserve it. There is no explicit expiry or automatic deletion in the code.

You can clear site data in browser settings; this can prevent recovery of an order status. Closing a tab usually ends its storage session. The proposed Article 4(6) Law 506/2004 exception is limited to storage strictly necessary for the expressly requested service; Article 6(1)(b) GDPR addresses necessary contractual data. Before launch, assess the necessity and lifetime of every key. Non-essential future technologies require prior valid consent under Article 4(5) and easy withdrawal; none are added here.

Recipients and international transfers

Access is limited to authorised persons and providers needed for the purposes described, or authorities with a lawful request. The two brands do not automatically share customer databases; any future sharing needs its own role, purpose, basis and notice. Sanity’s public content service is configured; Stripe is prepared for tests; the public sites use Cloudflare Pages; email and carriers are not configured. Contracted provider entities, logging and retention settings remain to be confirmed.

Providers may process data outside the EEA. Actual contracting entities, recipient countries, subprocessors and transfer safeguards are [DE COMPLETAT], to be verified against the selected contracts and settings. Applicable safeguards may include a valid adequacy decision or appropriate Article 46 safeguards, such as standard contractual clauses with any necessary supplementary measures. No unverified certification or EEA-only storage is claimed. Details and a copy of applicable safeguards can be requested through the completed privacy contact.

Retention and security

Local test orders and payment event records persist in local D1 until removed; there is no automated purge. Production retention must distinguish incomplete orders, concluded contracts, access entitlements, consent evidence, complaints and mandatory accounting documents. Concrete periods, legal references and deletion procedures are [DE COMPLETAT]. Necessary legal holds may restrict deletion; access and later deletion must still be controlled.

Technical logs follow a proportionate security period to be set with the host; correspondence follows resolution and applicable limitation periods; contractual/accounting evidence follows confirmed statutory duties; published content is reviewed while published. These criteria require operational schedules before launch.

The implementation hashes order-status tokens on the server and verifies Stripe webhook signatures. It does not establish a documented production backup or staff-training programme. Required access controls, secure production transport, incident handling and provider arrangements must be validated before production.

Your rights and how to exercise them

Where GDPR applies, you may request access, rectification, erasure, restriction and portability subject to their legal conditions; you may object to processing based on legitimate interests on grounds relating to your situation. If consent is used in future, it may be withdrawn at any time without affecting earlier lawful processing; direct-marketing objections must be respected.

Send a request to the privacy contact in the operator section: [DE COMPLETAT]. Describe the request and necessary identifying context; identity checks must be proportionate. The usual response period is one month, with an extension of up to two further months for complexity or number of requests, explaining it within the first month. Erasure is not absolute where a lawful retention duty or defence of claims applies.

You may complain to a competent supervisory authority, notably in your habitual residence, place of work or place of the alleged infringement, and seek a judicial remedy. For the Romanian operator scenario, ANSPDCP is available at www.dataprotection.ro. You need not first exhaust an internal complaint.

ANSPDCP

Links and policy updates

External sites, including a hosted payment page, have their own processing notices. This does not remove the site operator’s own obligations. This draft must be updated when providers, countries, retention, public contact or purchasing functions are confirmed; material changes must be communicated as required by law.

Data protection details to confirm

Contracted providers and their roles

[DE COMPLETAT]

Production hosting and log retention

Cloudflare Pages; [DE COMPLETAT]

Correspondence retention

[DE COMPLETAT]

Order and consent evidence retention

[DE COMPLETAT]

Applicable accounting duties and retention

[DE COMPLETAT]

Transfer countries, safeguards and how to obtain a copy

[DE COMPLETAT]

Deletion schedule and procedure

[DE COMPLETAT]