Privacy and cookies

Updated 10 November 2026

Who we are

SIÈRYNE is operated by SIÈRYNE L.C.M SOLUTIONS LTD, registered in England and Wales, company number 15415730. You can contact us at Office 496, Unit 5, 399-405 Oxford Street, Mayfair, London W1C 2BU, United Kingdom.

The studio editor and saved submissions are private. The Shop is closed and does not accept purchases.

Your project enquiry

The project questionnaire holds your answers in the open page until you choose “Send my project brief”. Sending stores your name, business name, email address, phone number, any optional additional decision-maker names, your preferred contact methods and times, time zone, meeting request and text-reminder preference, seven project answers, budget and currency, contact permission, a submission reference and dates in the private studio inbox. Your enquiry status is also stored. The owner can add relevant follow-up notes, a pipeline stage, contact dates and a retention-review date. The original brief remains unchanged.

We use this information to consider your request and discuss possible work. Our basis is taking steps towards a contract at your request, or our legitimate interests in responding to a business enquiry when you contact us on behalf of an organisation. The contact checkbox requests a reply about your project. It does not subscribe you to marketing.

The questionnaire's suggested direction is generated from your choices in the page. It does not accept a project, set a binding price or make a significant automated decision about you. You can leave without submitting. A saved brief does not book a project. We send your submitted project brief to our studio email inbox, provided by Google Workspace, and our assistant’s work inbox, provided by Inkbox, to handle your enquiry. Cloudflare sends these notifications. The receiving mailbox providers store the messages, and our website database keeps delivery-status records. Automatic acknowledgement emails and appointment texts to you are not connected. A meeting request does not reserve a calendar time. We will email you to agree a discovery call. Please share other decision-maker names only with their permission and share this privacy notice with them; their contact details are not requested. If someone names you as another decision maker, we use your name only to understand the project team and arrange the project discussion. We do not treat it as permission for marketing.

Your privacy request

To send a privacy request, choose a request type and provide a reply email address. You can add a brief explanation. Cloudflare D1 stores these details in the studio’s private request queue, along with a reference, the submission date and handling and notification status. We use this information to handle your privacy request or complaint. Submitting this form does not start a project enquiry or subscribe you to marketing. Do not include passwords, payment details, identity documents, health information or other sensitive information. We may need to check your identity later.

Cloudflare sends an alert to the studio’s Google Workspace inbox with only the request reference and a link to the private request queue. The alert does not include your reply email or explanation. The receipt shown on the form confirms that your request was saved. A deletion or other requested change still needs to be reviewed and carried out separately. The internal alert is not an acknowledgement email to you.

Optional studio emails

A separate, optional and initially unticked choice asks whether you would like studio news, new work and offers by email. You can decline and still submit your project enquiry. Cookie or appearance preferences do not grant marketing permission.

If you make this choice, we retain the choice, the exact wording and notice versions shown, its source and date. Existing enquiries are not treated as subscribers. Recording a preference does not verify your email address or activate an email campaign. No marketing sender is connected. You can withdraw using the privacy request form; the owner can record a do-not-market restriction separately from your project brief.

Protecting the forms

Cloudflare Turnstile checks a security token before a new project brief or privacy request is saved. Our server-side verification request contains the security token and service credential, not your project answers, marketing choice, reply email or privacy-request explanation. The Turnstile browser check separately processes technical signals, such as IP address, browser information and the site being checked. Cloudflare uses these signals to detect bots and to improve Turnstile, as described in its Turnstile Privacy Addendum. Limited request counters use keyed identifiers rather than storing your raw IP address in the rate-limit tables. Privacy-request counters also use a keyed email identifier. These counters expire after short rate windows and expired entries are removed during later cleanup.

Where information goes

The website’s studio inbox is restricted to the two approved owner sign-in identities. Cloudflare provides website hosting, the D1 database used for website content, enquiry records and privacy requests, restricted sign-in through Cloudflare Access, Turnstile checks and enquiry-notification delivery. The studio email inbox uses Google Workspace and the assistant’s work inbox uses Inkbox. Private backups of website and enquiry data are also kept in the owner’s Google Drive and in our working environment. The private owner editor supports still JPEG, PNG and WebP image uploads to Cloudflare Workers KV, limited to 10 MB per file and 500 MB total. Original image bytes and embedded metadata, such as photo location, are not altered. Uploaded originals are not automatically included in existing recovery copies. New video and template ZIP uploads remain disabled; existing bundled website media remain served as deployed site assets. Hosting and security providers may process technical connection information to deliver and protect the service.

Client websites and our Instagram, TikTok and LinkedIn pages are external links. Their own privacy notices apply when you choose to open them. Their pages are not embedded as tracking widgets in the studio website.

Cookies and saved preferences

SIÈRYNE does not use advertising pixels. Cloudflare Web Analytics is enabled through our hosting provider to measure website usage and performance. According to Cloudflare’s documentation, its performance beacon does not use cookies or browser storage; it sends page and performance information to Cloudflare. Authentication and security services may separately use cookies and technical logs. The appearance-preference control below does not switch off Cloudflare Web Analytics.

Browser storage remembers the opening animation and page transitions for the current tab session. Edition can remember your Motion on/off choice across visits. These appearance preferences stay in your browser and are not used for advertising. You can object below. Only the choice needed to remember that objection will be kept.

The closed Shop's owner preview separately keeps sample shopping-bag and order information in that browser. These are demonstrations, not purchases. This preference control does not delete a submitted enquiry or sign you out.

Your rights and complaints

Depending on the circumstances, you can ask for access, correction, deletion, restriction or a portable copy of your personal information.

You can object to processing based on legitimate interests. You can also tell us to stop following up on your enquiry.

For a privacy request or complaint, use the privacy request form. Include a way for us to reply and enough information to identify the enquiry. Do not send identity documents unless we explain why they are necessary.

Data protection complaints must be acknowledged within 30 days, investigated and answered without undue delay. You can also complain to the Information Commissioner's Office.

Retention and arrangements still being confirmed

Retention periods or criteria, responsibility for handling privacy requests, provider processing locations and international-transfer safeguards still need to be confirmed. Retention-review dates are reminders for manual review, not deletion dates. Archiving changes an enquiry’s status and does not erase it. There is currently no automatic deletion schedule for enquiry or privacy-request records. The retention and deletion process must cover saved briefs, follow-up notes, privacy requests, marketing choices and do-not-market restrictions, notification records, both email inboxes, uploaded originals and backups.