1Who is responsible
DesignDeck is operated as a sole business from Dubai, United Arab Emirates. That operator decides what is collected as described here, and is the person who answers a request about it.
The registered entity and address are not named yet. Section 1 of the terms of service carries that gap in writing, and it is filled before we take a payment.
2What is collected, and when
Browsing the site. No account, no cookie, no pixel, no fingerprint. Our host keeps ordinary web server logs, which include IP addresses, for its own security and diagnostics. Page counts and a speed measurement are described below.
Claiming a preview. An email address, the name you choose for the site, which design you picked, and everything you type into it: your business name, your copy, your prices, your telephone number and address if you put them on the page, and the web addresses of any images you point at. All of that is content you are publishing, so treat it as public the moment the site is live.
Sending an enquiry. Your name, your email address and whatever you write in the message.
Reserving a plan. While card payments are not open, the page for keeping a site asks for one thing: an email address. It goes to our CRM with the address of the site and the plan, so a person can write to you the day cards open. Nothing is charged and no card is asked for.
Writing to a customer’s site.A paid site can carry a contact or booking form. What a visitor sends through it (their name, the email address or phone number they type, their message, and for a booking the service, date and time of day) is kept in our store for that site, shown to the site owner behind their edit link, and included in the owner’s content download. The sender’s IP address is used to limit repeat sends and is not written into the enquiry. If our email is switched on, the owner is told by email that something arrived. Any reply comes from the owner’s own mail or phone, not from us.
Paying.Card details are entered on Stripe’s own checkout and never touch our servers. What comes back to us is the Stripe customer and subscription identifier, the plan, and whether it is paid. We never see or store a card number.
Product events. We record when a site is claimed, edited, published or cancelled, as a row in our own database, from the server. It is counted so we know which designs people finish; it is not linked to an advertising profile and it is never shared.
Page views. We count visits to the home page, the gallery and the design previews, so we know how many people get from one to the next. Your IP address itself is not stored. What is stored is a visitor code: a hash of your IP address, the calendar day and a salt, cut to 16 characters. It changes every day, so a visit today does not carry over to tomorrow. No cookie is set and the count stays in our own database or storage. If your browser sends Do Not Track or Global Privacy Control, no page view is counted.
Visitors to a customer’s site. This is the part people do not expect. Every site we host for a customer runs a small script of our own, served from the same address as the site, that measures how fast the page loaded and moved. When a visitor leaves the page it sends the site name, the design, three speed numbers, the page path, the screen width in pixels and the visitor code above to us, and the customer’s site is not told. It sets no cookie and loads nothing from a third party. A visitor whose browser sends Do Not Track or Global Privacy Control is not counted. Customers who hold their own visitors’ trust should know this runs.
Is that visitor code anonymous? We do not claim it is. It is a hash of an IP address, and IP addresses can be guessed one by one, so the code is a pseudonym and not a guarantee that nobody could work out the address. How strong it is depends on a secret salt that the operator is meant to set. If that secret is not set, the code falls back to a fixed salt that is written in our source code, which makes it weaker still. We do not state here which of the two the live service uses. We set no deletion schedule for these rows; they are kept until a person removes them.
The edit key. When you claim a site you are given a link with a long random key in its address. It is the only credential this product issues: there is no login. Anyone holding the link can read and change the site. It travels in the link itself, in the claim message in our CRM, and in any mail we send you. There is no feature to cancel a link once issued.
3Why we hold it
To run what you asked for: your address and your content exist because we cannot host your site without them. To run the service: the event log, the speed measurement, and the security logs our host keeps. Because the rules require it: the payment and tax records Stripe and we have to retain. We have not set out a legal basis for each of these on this page, and we do not claim one.
We do not sell data, we do not share it with advertisers, and we do not use it to train anything.
4Who else holds it
These are all of them, and the list follows the code, not a template. The first group is your data as a customer. Visitors to your site are covered in section 2.
Neon (Postgres) or Cloudflare R2, as the site store
Your site: the name you chose, the design, everything you typed into it, your email address, your plan and its dates, the Stripe identifiers, the custom domain if you connected one, and your edit key, stored as the key itself and not as a hash. On a paid site, the enquiries and booking requests its visitors send through it are kept in the same store.Which of the two holds it depends on how the live service is configured, and we have not fixed that on this page. If a database is configured it is Neon, otherwise a private Cloudflare R2 bucket, and either way it is a store we pay for and control. Neither is chosen by you, and the region is whichever the account was created in.
The event log (same store, or off)
One row per event: its name, the site name, the design, a source label, a few numbers, and for visitor events a daily visitor code described in section 2.Written to the same Neon database or to R2, or nowhere if the log is switched off.
Our CRM
Every claim, every enquiry sent to us and every reservation, so a person can answer it: your name, your email, your message, and for a claim a transcript of what you typed (long values are cut) together with your edit link. That transcript is also the backup copy of your site.A private instance we run ourselves. The host is not named on this page.
A push alert, only as a fallback
If the CRM cannot be reached, the name, email and first line of the message are pushed to a notification endpoint we configure so a person sees the lead. The edit key is masked out of that copy.We do not name the provider of that endpoint on this page.
Resend, for email
The recipient address, subject and body of any message we send you about your own site: an edit link, a short note or two while a preview is new and unpaid, a warning before a preview pauses, and, on a paid site, a note that a visitor has sent an enquiry. A message that carries your edit link carries the key itself.Resend sends nothing until a sender is configured. Until then no mail leaves this system through it; this entry is here so the notice is true on the day it starts.
Stripe
Payment. Card details go straight to Stripe and never reach us: we hold only the customer and subscription identifiers Stripe hands back. Stripe also sends receipts and invoices from its own systems.Stripe's own infrastructure, under its own privacy policy.
Vercel
Hosting and the request logs that come with it, which include IP addresses for a short period. If you connect your own domain, Vercel is also told that domain name so it can serve the site.Edge and serverless infrastructure, worldwide.
Cloudflare R2, as the media bucket
Our own artwork and video: the deck imagery and the films. The product has no upload feature, so no photograph of yours is stored here by it.Object storage, separate from the site store above.
These providers operate internationally, so your data is processed outside the country you are in. We have not fixed the country or region for any of them, and we cannot tell you one on this page. Each of them publishes its own terms and transfer safeguards.
5How long it is kept
An unconverted preview. Public for 30 days, then paused: the public address stops showing it, it stays visible to you through your edit link, and you can resume it for 12 months. After that window it may be deleted. That clock only runs while the site could actually have been paid for, so nothing is paused or deleted for non-payment on a day when payment was not possible.
A paid site. Kept for as long as the subscription runs. After a cancellation the site reverts to a preview, is paused when that 30 day window runs out, and may be deleted only after a further 12 months paused. Its enquiries stay with it until then.
Enquiries, reservations and claim messages. Kept in the CRM while there is a reason to keep them, and deleted on request. A claim message is also the backup copy of a site, which is why a lost site can sometimes be rebuilt by hand. Ask for it to be deleted and that safety net goes with it.
Payment records. Kept as long as tax and accounting rules require, which is longer than everything else here and is not something either we or Stripe can shorten on request.
6Cookies
This site sets none. Not for analytics, not for advertising, not for preferences. There is no consent banner because there is nothing to consent to.
Stripe’s checkout and billing portal are Stripe’s own pages and do set cookies, which are necessary for the payment to work and are covered by Stripe’s privacy policy. If you never go to checkout, you never meet one.
The one thing your browser stores on our behalf is the secret key in your edit link, and only if you bookmark it. It is in the address, not in a cookie.
7Your rights, and how to use them
You can ask for a copy of what we hold about you, ask for it to be corrected, ask for it to be deleted, ask us to stop using it, or object to us holding it at all. Depending on where you live these rights come from the UAE Personal Data Protection Law, the GDPR, or your own local equivalent. We apply the same standard to everyone rather than sorting people by passport.
Deleting your own site does most of it in one move: a deleted site takes its content with it. For anything beyond that, use the form at the foot of the homepage and say plainly what you want, along with the address of any site involved. A person reads it and answers it, normally within a few days. We may ask you something only the right person would know before deleting an account’s worth of data, because there is no login here to prove it with.
If you are unhappy with the answer, you can complain to your local data protection authority. Telling us first is faster.
8Children
This is a product for businesses. It is not for anyone under 18 and we do not knowingly collect anything from a child. If a child’s data has reached us, ask and it will be removed.
9Security, and what we cannot promise
Everything is served over HTTPS and payment never touches our servers. There is no password to steal because there is no login: an edit link carries a long random key instead, which means anyone you forward that link to can edit the site. Do not post it anywhere public. The key is stored as it is, readable by us and by the store that holds it, and it is also in the CRM message that carries your edit link.
No service can promise a breach will never happen. If one does, and it puts you at risk, you will be told what happened and what to do about it.
10What we do not do
We do not have a data processing agreement, we do not sign one today, and we cannot give you one. If your regulator or insurer requires one, say so in the form on the homepage and a person will take it to the owner of the business and answer you in writing. Until then, do not rely on us to act as your processor.
We make no claim of compliance, certification, registration or audit under any law or standard. Section 7 names laws as the source of your rights; that describes your rights and is not a statement that we have been assessed against them.
A site here is a public brochure. It is not built to collect patient, client or child records, and nothing of that kind should be typed into it. Contact details on a site are usually links that open the visitor’s own mail program, so that a message goes to you directly; we have not checked that this holds for every design we sell. On a paid site, the contact or booking form described in section 2 keeps what visitors send in our store, with the site. We have set no backup, retention or deletion schedule beyond what sections 5 and 7 say, and deleting a copy held by Resend, Vercel or Stripe is for those providers.
11Changes
The date at the top is the date of the current version. If this notice changes in a way that matters, the change is made before the practice it describes, not afterwards.