Privacy · Updated 4 September 2026
This site sets no cookies, runs no tracking script and shows no advertising. What follows is the whole of it: what is collected, who holds it, how long it stays, and how to make it go away.
DesignDeck is operated as a sole business from Dubai, United Arab Emirates. That operator is the data controller for everything described here, and is the person who answers a request about it.
The exact registered entity and address are named in section 1 of the terms of service.
Browsing the site. Nothing personal. 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.
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.
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.
To perform the contract you asked for: your address and your content exist because we cannot host your site without them. For our legitimate interest in running the service: the event log, and the security logs our host keeps. To meet a legal obligation: the payment and tax records Stripe and we have to retain.
We do not sell data, we do not share it with advertisers, and we do not use it to train anything.
Five, and no more. Each one holds what it needs to do its job and nothing beyond it.
The database. Site rows, the content you typed into your deck, your address, billing state, and the event log.Serverless Postgres, in the region the database was created in.
Hosting and the request logs that come with it, which include IP addresses for a short period.Edge and serverless infrastructure, worldwide.
Our own artwork and video: the deck imagery and the films on this site. No customer uploads are stored here.Object storage.
Payment. Card details go straight to Stripe and never reach us: we hold only the customer and subscription identifiers Stripe hands back.Stripe's own infrastructure, under its own privacy policy.
Every claim and every enquiry, so a person can answer it. A claim message carries a transcript of what you typed, which is also the backup copy of your site.A private instance we run ourselves.
These providers operate internationally, so your data is processed outside the country you are in, including in the United States and Europe. Each of them publishes its own transfer safeguards, and we do not add a sixth.
An unconverted preview. Deleted when it expires, 7 days after it was claimed. That clock only runs while the site could actually have been paid for, so nothing is 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 and is deleted when that 7 day window runs out.
Enquiries 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.
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.
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: an expired or 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.
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.
Everything is served over HTTPS, payment never touches our servers, and the database is reachable only by the application. 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.
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.
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.