Privacy policy

Who is responsible

This site is published by Desinable. To be completed: legal name, legal form, registered address and registration number of the business responsible for this site, and the address to write to about personal data

When you browse the site

• No advertising, no tracking cookies. The site loads no advertising or tracking scripts and sets no cookie to follow you from page to page or site to site. Its fonts and images are served by this site itself.
• Visit statistics. To count visits (such as pages viewed, the page that sent you here, the type of device and the country), we use Cloudflare Web Analytics, which does not set cookies. Its script is loaded from Cloudflare (static.cloudflareinsights.com) and sends its measurements to Cloudflare. To be verified: what Cloudflare Web Analytics collects and keeps, for how long, where it is processed, and whether consent is required in each country where we sell
• A cookie for your choice of region. If you pick a regional site at the bottom of a page, a cookie named "region" remembers that choice for one year, so you are not sent to another regional site. It contains only the region's code.
• Your country, to pick a regional site. When you open desinable.com, the country of your connection, as reported by the network provider in front of the site (worked out from your IP address), is read to send you to the regional site for your country, if there is one. It is not stored. To be completed: the name of that network provider
• Protection against abuse. To limit automated messages, the server counts, per IP address and per email address, the messages sent through the contact form, the support request form, the project form and the chat, and the requests for sign-in links and codes, over short periods (up to one day). These counts are kept in memory only and are not written to any file or database.
• Your browser's storage. If you choose "Later" when the site offers to install the app, your browser remembers the date for 30 days, so the offer does not come back sooner. When you pick a package or plan on one page, your browser keeps that choice until you reach the contact form in the same tab. If you switch the site between its light and dark theme, your browser remembers which you chose, so it opens that way next time; without a choice it follows your device's own setting. Both stay in your browser and are never sent to us.
• Technical logs. To be verified: whether our hosting provider and any network provider in front of the site (such as a CDN) keep access logs (such as IP address and pages requested), for how long, and in which countries

If you are a client

• Your client record. When our team adds you as a client, it records your name, email address, company (optional), language, regional site and maintenance plan, with internal notes the team may add. They are stored in our database.
• Colleagues on your record. If you ask us to give a colleague access to your account, we record their name and email address so they can sign in and see the same requests, orders and project as you. At your request we also email them what we send you about the account; we do that only for the people you ask us to. We add or remove them only at your request, and removing them ends their access, their sessions and their notifications at once.
• Signing in. To sign in to the client area, you ask for a link or a 6-digit code, sent to your email address. Once you are signed in, a session cookie keeps you signed in for up to 12 hours; the IP address and browser of each session are recorded to protect your account.
• Notifications. If you turn on notifications in the client area, we store the address your browser's push service gives this device (Google, Mozilla, Apple or Microsoft, depending on your browser), with its keys and your language, to tell you when we reply. Turn them off at any time; the address is then deleted.
• Time spent for you. The time our team spends on your requests is recorded, with a short note you can see in the client area.
• Confirming an order. When our team sends you a summary of an order, confirming it records the name you type, your email address, the date and time, your IP address and your browser, and a fingerprint of the exact text and figures that were on your screen. That is kept so both sides can see what was agreed, and it is not changed afterwards. To be verified: what a confirmation made this way is worth in each country where we sell, and what we may say about it
• Payments. When we receive money from you, our team records the amount, its currency, the day it arrived, how it arrived (a bank transfer, cash, a card or something else), any reference that identifies it, the agreement or the month of a maintenance plan it pays for, and a short note. It is kept so both sides can see what has been paid and what is still outstanding, it is shown to you in your client area, it is in the copy of your data you can download, and it goes when your record does. We do not take payments on this site and we store no card or bank account details. To be verified: how long records of payments must be kept for accounting in each country where we sell, which may be longer than the rest of your record
• What you say about the work. If you tell us what you thought of the work and agree to it being shown, our team types your words, your name and, if you give one, your job title or company, and records that you agreed. It is shown on the site only while that agreement is recorded, only in the language you said it in, and never translated. Ask us and it comes down; it is also in the copy of your data you can download, and it goes when your record does.
• Your project. If we build something for you, our database holds the project: its title, the stage it is at, the steps and the things we have asked you for, what you tell us you have sent and any note you add, the changes you ask for in your own words, the preview and live addresses, and the launch date.

When you open a support request

• What is kept. A request records your name, email address, company (optional), the subject, your messages and attachments, and the regional site and language you used. Your messages and our replies are stored in our database; attachments in private file storage, opened only through short-lived links. To be completed: the file storage provider
• Your client record. If your email is not yet a client's, a client record is created with it, so you can follow the request in the client area.
• Emails. You receive a confirmation, then our replies, by email; our team is told of new requests and replies by email.

When you send a project brief

• What is kept. The "Start a project" form records your answers: your name, email address, and whatever else you choose to share about your business and your project (phone, business name, current website, goals, pages, features, what each page should say, brand, colours, logo, links to your files, domain, preferred launch date, budget, notes), the details you want the site itself to show (the address its contact form should send to, a phone number, a postal address, opening hours, links to your social profiles), and, for a shop, how you sell (products, categories, payment, delivery, currency), with the regional site and language you used. They are stored in our database as a request you can follow in the client area, like a support request.
• Before you send it. Your answers are saved as you type, so you can come back to them: a copy stays in your browser tab (session storage), and a copy is kept on our server. Your browser holds a code in a cookie named "desinable_brief" (only a fingerprint of that code is stored, so the saved answers cannot be opened without it), and the saved answers include your email address once you have typed one. You can ask us to email you a link back to them; that email repeats nothing else from your answers, because the address has not been checked. A saved draft nobody comes back to is deleted after 30 days, and the one you send is deleted as soon as it is sent.
• Your client record and emails. As for a support request: a client record is created with your email if needed, you receive a confirmation, and our team is told of the new request.

When you chat with us

A chat button appears when someone from our team is available. If you start a chat, it records your name, email address, your messages and ours, the page you started from, and your regional site and language, in our database. A cookie named "desinable_chat" holds a random code that links your browser to the chat for 24 hours; only a fingerprint of that code is stored. When the chat ends, we email you a copy if our team answered you in it (your address is not checked, so a chat nobody answered sends nothing). Our team may turn a chat into a support request.

When you contact us

The contact form asks for your name, your email address, your company (optional), the subject and your message. The regional site and language of the page you used are added. The form sends all of this to our team as an email; this site does not store it in a database.

We use it to reply to you and to discuss your project. If you email us directly, we receive your address and your message in the same way.

Email is delivered through To be completed: the email provider used to send the form's messages, and the provider hosting our mailbox.

How long we keep it

Support requests, chats and client records are kept until they are deleted: To be completed: how long resolved requests, chats and client records are kept, and when they are deleted (the back office can apply these periods automatically). To be completed: how long project emails are kept

Who receives it

Your message goes to our team's mailbox. To be completed: the service providers that host the site and handle email, and in which countries they process data

Your rights

We can give you a copy of the data we hold about you (your details, requests and replies, time logged, payments recorded, chats and devices), or delete all of it. Signed in to the client area, you can download that copy yourself. To be completed: how to ask, and how we confirm the request comes from you

To be verified: the rights you have over your personal data under the data protection laws that apply to you, depending on your country, and how to exercise them, including any authority you can complain to

Changes to this page

When what the site collects changes, this page is updated. To be completed: date of the last update