Privacy Policy
Last updated: · Short version: we collect what we need to do the work, and nothing is sold
1. Who we are
Mohammed Ayan Hayat, trading as LUMORIA, is the controller of the personal data you share with us. Our business address is 80 Craddock Street, Cardiff, CF11 6EW, United Kingdom. Contact: [email protected].
2. What we collect
Contact details you give us (name, email, phone, company). Booking details, the property address and any access notes, which we need to turn up and get in. Anything you write in a brief or enquiry. A property price-match request includes your email, optional quote link, details or document and the page or package you were considering. An introductory-offer request includes your email, an optional telephone number, the offer shown and your separate marketing choices. We record the personal code, expiry and redemption against your email. The country for the telephone prefix can be suggested from your connection; you can change it. Requesting a code does not opt you into marketing. Uploaded quote documents are stored privately for our team to review. If you choose the optional email box, we also record your marketing choice, the wording shown and when you agreed. Correspondence. Payments run through Stripe, so we never see or store your full card details. We run first-party, privacy-friendly analytics: page views and referrers, no cross-site tracking and no advertising profile. If a link carries campaign labels, we can carry those labels to your enquiry, quote and booking to understand how you found us. This does not set an advertising cookie or collect advertising click identifiers.
3. Why, and our lawful basis
To deliver what you booked and support you afterwards (performance of a contract). To answer enquiries and improve the service (legitimate interests). To meet accounting and legal duties (legal obligation). Marketing email only where you asked for it (consent), with an unsubscribe in every message that works first time.
Website briefs, progress and optional contact sync
For website orders we keep the selected package, country/rate, page language, extras, payment reference and versioned terms/start choices. Your private client brief may contain business details, text, links, files, logos, images and audio you choose to provide. Saved progress lets you return to the same brief without retyping; treat its private access link as confidential. We use this material to plan, deliver and support your project. Do not upload passwords, payment-card details or personal data we do not need.
The storefront can remember your chosen website country in browser storage; configuration choices can also appear in its shareable URL. Contact details are not added to those URLs. The country suggestion uses coarse connection metadata and does not change your page language. Your checkout retry reference is stored for the current browser session to avoid duplicate purchase attempts.
If you change language during a website enquiry, the current tab can carry your unfinished answers to the next page. It can read them once, for up to one minute. Changing language does not send the enquiry.
Before calling, you may separately choose to save your name, phone and optional email in our customer system for your website enquiry. This is optional, is not marketing consent and is not required to call or use WhatsApp. If business address-book sync is connected, the enrolled contact can sync to Google Contacts and the studio phone. That sync may lag or require review; saving the enquiry does not guarantee that the caller’s name is already visible on a phone. The form reports the actual save/sync result, and direct contact remains available if it fails. For contacts enrolled in the optional business sync, a short website-brief summary can stay updated in the studio’s Google Contacts: business name, goal, audience, main action, pages/languages, requested launch and a link requiring project authentication. Files, voice-note contents, credentials and payment details are excluded from that summary. These updates do not sign you up for marketing.
4. Who processes it
A deliberately small set: Stripe (payments), Resend (email delivery), Cloudflare (hosting, delivery and analytics). Google provides the optional business contact sync described below. Choosing the call calendar loads Cal.com, which handles the details you provide to arrange a discussion. Choosing WhatsApp opens WhatsApp, provided by Meta; messages you send there are handled by that service. The calendar loads only when you choose it. These services operate under their own privacy policies. We do not sell your personal data to anyone, for any amount.
5. Google Contacts in HQ
Google Contacts is an optional, founder-only connection for our business address book. With the account owner's permission, HQ checks their Google account email and uses the Google People API to read matching contacts and create or update enrolled business contacts. Contact edits sync in both directions between HQ and Google, including connected Android devices. Synced fields are contact display names, phone numbers, email addresses, companies and known roles, websites, contact addresses and nicknames, with a LUMORIA contact group and record IDs for matching. Ordinary edits update automatically; competing changes, identity conflicts and missing contacts are held for review. A contact display name does not verify legal billing identity.
HQ stores Google contact identifiers and versions, the contact details needed for sync, and encrypted last-shared contact values to merge edits and detect duplicates or conflicts. It does not import the whole personal address book into the CRM. It does not copy private correspondence, uploaded files, voice-note contents, credentials or payment details to Google Contacts. For eligible enrolled website contacts, a studio-managed summary may include the business name, goal, audience, main action, agreed pages/languages, requested launch and an authenticated project link. Updates preserve manually added Google/phone notes and other project notes; the link does not grant public access.
OAuth credentials and tokens are stored encrypted in HQ's Cloudflare-hosted system. Google contact data is used only to provide contact sync, never sold, used for advertising or used to train AI models. Our use of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.
The account owner can disconnect in HQ or revoke access in their Google account. Disconnecting removes HQ's access tokens; contacts already synced remain in Google and on connected devices until separately changed or removed. Contact corrections and deletion requests can be sent to the address below.
6. Retention
As long as we need it to deliver the work and meet our accounting and legal obligations, then deleted. Access notes, keys, alarm codes, who holds a spare, whether anyone is living there, are erased automatically 30 days after the shoot is completed and the invoice is settled. The property address stays on the job and the invoice, because that is an accounting record we are required to keep. Delivered files stay available to you for 12 months and original unedited files are deleted after 90 days.
7. Your rights
You can access, correct, delete or port your data, and object to certain processing. Email [email protected] and we’ll action it. You can also complain to the UK Information Commissioner’s Office at ico.org.uk.
8. International transfers
Some processors operate outside the UK. Where data is transferred internationally it is covered by appropriate safeguards.
9. Cookies
Only what is needed to run the site. No advertising trackers, no consent-banner theatre, because there is nothing here to consent to.
10. Changes
Updates get posted on this page with a new date at the top.
Contact [email protected].