Privacy Policy

1. What Projado is, and who is responsible for your data

Projado is a tool for interior designers and design studios for running projects: briefs, surveys, concepts, inspiration, product lists and client consultations. The data controller is VISUAL SPACE Hanna Półtorak (“we”, “the operator”). Contact for data-protection matters: contact@projado.com.

Registered business details: adres: ul. Świemirowska 15 lok. 1, 81-877 Sopot, NIP: 5851502129, REGON: 526447544.

Within Projado we process two kinds of data, and our role differs for each:

• designer account data: here we are the data controller;
• client data entered by designers: here the designer or studio is the controller, and we process it on their behalf as a processor (Article 28 GDPR).

2. Designer account data

When you create an account and use Projado, we process:

• your e-mail address, and whether it has been confirmed;
• your first and last name, which you need to give to use the account; if you sign up through Google, we fill them in from the name Google provides;
• your password, only as a cryptographic hash (we never store it in readable form);
• if you sign in through Google: the Google account identifier, and the e-mail address and name Google provides at sign-in;
• your phone number and the country it was entered under, if you give them, and the language you use the app in;
• membership of workspaces (studios), the roles and permissions assigned within them and the history of joining, leaving and role changes, plus team invitations;
• the date the account was created and of your last sign-in, the label of the link you registered through (if it carried one) and the record of important events in the app (section 9);
• records that protect the account: the two-step sign-in settings, if you turn it on, the counters of sign-in attempts and of account e-mails, the record of studio export downloads (date, a shortened network address, the browser) and the record of what our operator did with your account and why;
• the record of your acceptance of the terms (date, version, language and how you accepted);
• the history of e-mails we sent you (kind, subject, delivery status and dates, without the content);
• your support conversations (section 4), with the technical details recorded when a conversation opens (the browser and system, the page of the app, the app's version, the window size and the identifier of the last failed request), and the notes our support team keeps on the conversation;
• a note of how far you have read “What's new” in the application, so that entries you have not seen yet can be marked;
• technical session data needed to keep you signed in (refresh tokens).

The processing is based on performing the contract for the electronic service (Article 6(1)(b) GDPR), and, for the security of the service and fraud prevention, our legitimate interest (Article 6(1)(f) GDPR).

Giving an e-mail address, setting a password (or signing in with Google) and giving your first and last name are required to use an account. Without them we cannot create one or let you work in it. The phone number is optional.

When a studio invites a person who has no account yet, we process that person's e-mail address, together with the studio's name and the role offered, to send the invitation and let them accept it. The basis is the inviting studio's legitimate interest in building its team, and ours in carrying out its request (Article 6(1)(f) GDPR); the person learns about it from the invitation e-mail. An invitation that is not accepted is deleted 30 days after it expires.

The Projado Chrome extension. If you use it, it reads a shop page only when you click its icon (inside the Projado app itself, also the button that adds a product), and only that one tab: it does not run in the background and does not look at other tabs or at your browsing history. It sends the product data (the name, price, photo and address of the page) only to Projado, and only when you save the product in a project. The extension has no sign-in form of its own: it uses the session you have in the app, so it never sees your password. It keeps a short-lived access token in the browser's session storage for extensions, which is cleared when the browser is closed, and small settings (the project and room you picked last, the panel language, the Projado site you are signed in on) in the extension's local storage. The extension contains no analytics and no advertising.

Projado is a tool for professionals, and accounts are for adults: you must be 18 or over to open one. We do not direct the service to children and do not knowingly collect personal information from anyone under 18; if we learn that we have, we delete it. A studio's questionnaire may contain information about its client's children (section 3), given by an adult; that information is the studio's, and the studio decides about it as its controller.

3. A designer's client data

While running a project, a designer may record their clients' data in Projado, in particular:

• the client's name and contact details;
• the client's company details for invoicing (name and tax number);
• the designer's own notes about the client, meaning any text they choose to write;
• the address of the property being worked on;
• answers to the brief questionnaire, including a description of needs, style and budget and the household's composition; optional answers about accessibility features of the space; and, unless the studio switches them off, the questions about children's rooms: the children's age and number, their activities and interests, their favourite and disliked colours and style, and what their room needs (bed, desk, storage, space to play);
• uploaded photos, inspiration, files and survey documentation;
• comments on, and acceptances of, concepts;
• the name the client gives when accepting materials through a shared link. We record it on the acceptance certificate together with whether the client typed it themselves or confirmed a name suggested from the designer's own records; we do not verify whether it is genuine, and we do not record an IP address or browser data alongside it;
• product and shopping lists, and consultation appointments.

The client enters some of this data themselves, through a link the designer shares with them (for example a brief or a concept), without creating an account.

The designer or studio is responsible for this data as its controller. They decide what data to collect and why, and any request about it should go to them first. Projado processes this data solely to provide the service to the designer, never uses it for our own purposes, and never shares it with anyone outside the designer's own workspace.

We do this on the terms set out in this policy: for the purpose stated above, with the safeguards in section 7, involving the sub-processors named in sections 5 and 6, and for the periods named in section 8. Before we start processing a designer's client data, we conclude a data processing agreement with the designer or studio that meets Article 28 GDPR. The agreement sets out in particular the subject matter and duration of the processing, its nature and purpose, the types of data, the categories of people, and the rights and obligations of the parties. The agreement is an annex to the Terms of Service: you accept it together with them when you open an account, and its text is on the “Data Processing Agreement” page.

4. Support conversations and screenshots

Inside the app, in the “Help” panel, you can write to us. We then store the content of your messages and our replies, the conversation's subject, date and time, the name of the studio you are writing from, and a project identifier if you give one as context. The conversation belongs to you, not to the studio, so the studio's owner cannot see it. You can also write to us from the demo project, without an account: there the conversation is text only, is not linked to any account or e-mail address, and is deleted together with the demo visit.

You can attach an image to a message, usually a screenshot. A screenshot shows everything that was on your screen at that moment, including your clients' data, file names, open tabs or notifications. Before you send an image we show it to you in a preview, and you can black out anything you do not want to send us. The blacked-out parts are removed from the file in your own browser. The original never reaches us, only the image you approve.

We re-encode every uploaded image as WebP. This means we do not keep any extra information the original file might have carried, for example a location stamped by the camera, or a thumbnail from before you blacked anything out. Only our support team can access conversations and their attachments.

We process support conversations about using an account in order to perform the contract (Article 6(1)(b) GDPR). When someone contacts us without an account, in particular about a demonstration of the service or before concluding a contract, we process the data to the extent needed to take steps at that person's request before a contract is concluded (Article 6(1)(b) GDPR), as long as the contact really is such a request; in other matters the basis is our legitimate interest in handling correspondence (Article 6(1)(f) GDPR).

You can also write to us without an account: through the form on the “Contact” page, or in the “Book a call” window on the home page and in the demo project. From the form we receive your e-mail address, your name (if you give it), the topic and your message; they reach us by e-mail, in the mailbox of our contact address, which is hosted by OVH (section 6). From a call request we receive your e-mail address, your name (if you give it), what you would like to see, the day and time of day that suit you, your note, and where the request was sent from (the home page, the demo project or the contact form). A call request reaches us by e-mail and is also stored in the app so that none gets lost; that record is deleted automatically after 30 days. We delete the e-mail correspondence 6 months after the last message in the matter. If you become a customer, we keep correspondence about the contract for as long as your account exists (section 8). We need your e-mail address to reply; without it we cannot. If you ask about the service or request a call, we process this data to take steps at your request before entering into a contract (Article 6(1)(b) GDPR). We process other messages in our legitimate interest in answering correspondence (Article 6(1)(f) GDPR); you can object to that processing (section 10).

5. E-mail

We send only messages tied to running the service. Below is every kind of message, grouped by what it is about. We do not send a newsletter or marketing e-mail.

We send messages through Lettermint (Lettermint B.V., the Netherlands), a transactional e-mail provider that receives the recipient's address and the message content, and reports delivery back to us. Under its data processing agreement, Lettermint stores and processes message data only in the European Union. We do not track whether messages are opened or which links are clicked.

We send messages to account holders to perform the contract (Article 6(1)(b) GDPR); the notice that an account was locked is also sent in our legitimate interest in protecting accounts from unauthorised access (Article 6(1)(f) GDPR). Service notices to studio owners are sent to perform the contract and, where the law requires the notice, also to comply with that obligation (Article 6(1)(c) GDPR).

6. Where we store your data

The service and its database run on Hetzner Online servers in Germany (Nuremberg), in the European Union. Uploaded files and photos are stored in S3-compatible object storage, also in Germany (Nuremberg).

We entrust data only to the providers the service cannot run without: our server and file storage provider (Hetzner Online), our transactional e-mail provider (Lettermint, section 5), the provider of the mailbox of our contact address (OVH, a French hosting company; the mailbox is hosted in the European Union), the provider of network protection (Cloudflare), the provider of our code repository and build pipelines (GitLab) and the tool our team receives operational alerts in (Slack). The last three are described below. They act on our instructions. We may also disclose data to public authorities where the law requires us to.

Connections to the service pass through the network of Cloudflare (Cloudflare, Inc., USA), which protects the service and delivers its pages. Within the scope of its data processing agreement Cloudflare acts as our processor and may process data outside the European Economic Area, including in the USA. The safeguards for such transfers under Chapter V GDPR are the European Commission's standard contractual clauses, which are part of that agreement, and Cloudflare's participation in the EU–US Data Privacy Framework. We provide information about the safeguards and a copy of the relevant documents on request: write to contact@projado.com.

Our code, and the pipelines that build, deploy and check the service, run on GitLab.com (GitLab Inc., USA). To check that our database backups can be restored, and when we rebuild the server after a failure, an encrypted copy of the database (without files and photos) passes through GitLab for at most one day. GitLab also holds the key that opens it, so we treat GitLab as a recipient of the data in the database. The copy is decrypted and restored only on a build server we control in Poland, in a database that exists only for as long as the check runs. GitLab may process data outside the European Economic Area, including in the USA; the safeguards are the European Commission's standard contractual clauses and GitLab's participation in the EU–US Data Privacy Framework.

Our team receives operational alerts in Slack (Slack Technologies, LLC, part of Salesforce, USA): for example that a studio asked for the Studio plan, that a support conversation is waiting for our reply, or that an account could not be erased on time. An alert carries only an account or studio identifier and a link to our operator panel, never a name, an e-mail address or the content of anyone's work. Slack may process data in the USA; the safeguard is Slack's participation in the EU–US Data Privacy Framework.

Signing in with Google uses Google Identity Services. When you use it, Google processes your data under its own privacy policy.

We do not sell data, and we do not pass it to advertising networks or data brokers.

7. Security

• connections to the service are encrypted (HTTPS);
• we store passwords only as cryptographic hashes;
• project data can be accessed by members of the studio, according to their assigned roles, and by clients and other people the studio shared a link with, as far as that link goes; our team reaches into this data only when running the service, keeping it secure or giving the help you ask for requires it;
• client links (brief, concept) carry a random identifier that is not derived from the project's data.

8. Retention period

We keep account data until the account is deleted. We keep project data, including client data, for as long as the project or the studio it belongs to exists. The designer can delete it at any time.

When an owner deletes a studio, we lock it at once: nobody can open its projects, and the links sent to clients stop working. We keep its data for a further 30 days. During that time the owner can download a copy, restore the studio or erase the data at once. After that we erase it from the service and it cannot be restored; copies may remain in backups until they expire, as described below.

When you delete your account, we lock it at once: we sign you out of every device, and any studio where you were the only person is locked with it, just like a studio its owner deletes. We keep the data of the account and of those studios for a further 30 days, and send you the date it will be erased by e-mail. During that time, signing in is all it takes to restore the account together with those studios. A studio where someone else still works is left untouched; your membership and your assignments to its projects disappear from it at once and do not come back when the account is restored. After 30 days we erase the account entirely: the account itself, the profile and every sign-in method, along with the studios locked with it, together with their projects, briefs, concepts, surveys, files and client data. A background job does this, usually within a few minutes; we send an e-mail once it finishes. After that nothing can be restored.

An account whose e-mail address has not been confirmed can be used for 30 days from registration. After that, signing in is paused until the address is confirmed: one click on a fresh confirmation link brings everything back. If the address is still not confirmed 60 days after registration, we erase the account, together with the studios where it was the only person and their data, as described above. We send a warning to the unconfirmed address 7 days before each of those dates.

Three things outlive this, and we say so plainly. The e-mail send history is kept for 7 days after sending, but without an address or any link to an account, because we remove that link the moment the account is erased. An address whose e-mail bounced permanently stays on a suppression list at most 30 days, and is removed together with the account if it was the account's own address, so we do not e-mail it again after a fresh registration. An address that reported our message as spam stays on it with no time limit, so we do not write to someone who does not want it; we remove it from the list at that person's request, and after the account is erased we keep it only as a hash. Such a hash can recognise the same address again, so we still treat it as personal data. Data may remain in backups for at most 37 days: we keep a backup for 30 days, and a deleted backup can be recovered for 7 more days. If we ever restore a backup, we keep a log of deleted accounts, studios and projects so that they are deleted again, and of deleted clients so that we can ask the studio to delete them again. Smaller deletions, such as a single file or photo, a person removed from a project or a link a studio revoked, are not in that log, so such data could come back with a restored backup.

A file or photo deleted in the app stays recoverable by us for up to 31 days after the deletion, as a safety copy in the file storage; after that it is gone.

The record that you accepted the terms (date, version and how you accepted; no IP address) is kept for 30 days after the account is erased, but without the account identifier: we replace it with a hash. The hash is not anonymous: someone who knows the account identifier can check whether the record is about it, so until it is deleted we treat the record as personal data. This lets us answer a dispute about what you agreed to. After 30 days we delete the record. We treat the record that we showed you a notice about a change to this policy in the same way.

Image addresses generated before a project or a studio is deleted stop working the moment it is deleted, including while we still keep a deleted studio's data. An image opened earlier may remain in the cache of the browser it was opened in.

Support conversations follow their own rhythm. If nothing happens in a conversation for 14 days and we sent the last message, we close it automatically. A conversation in which you sent the last message stays open, waiting for our reply, and does not close by itself. You can reopen it for a further 14 days simply by writing in it again. We delete a closed conversation, together with any attached images, after 180 days. An image you uploaded but never sent with a message is deleted after 24 hours. If you delete a studio, the conversation stays (it belongs to you, not the studio), but images sent from that studio are deleted along with it.

We keep the service's technical logs for up to 14 days, after which they are deleted automatically. In the application's logs we record the IP address only in a shortened form (without the ending that points to a specific device) and, for requests from a signed-in account, the account identifier; this serves to detect errors and abuse. A sign-in session lasts at most 14 days; we delete its record from the database 15 days after it expires or you sign out.

We keep statistics about visits to the public pages (section 9) for 12 months, and recordings of visits and click maps for 30 days. Older data is deleted automatically once a day.

We keep the record of events in the app (section 9) for at most 24 months from the event; entries about a studio are also deleted together with it. Older entries are deleted automatically once a day.

9. Cookies and browser storage

We use only cookies that are strictly necessary for signing in, session security, opening a studio client's links, running the demo and remembering the language you chose:

• projektado-refresh: the session refresh token, not accessible to page scripts (HttpOnly);
• projektado-refresh-remember: whether you chose the “remember me” option; with that option the cookie is valid for 14 days, without it it is gone when you close the browser;
• projektado-session: a sign-in marker that tells the page a session exists in this browser and can be resumed; it holds no data about you or your account;
• projektado-registration: a short-lived registration session, valid until you confirm your e-mail address (at most 1 hour);
• projektado-demo: a random identifier for a visit to the demo project, not accessible to page scripts (HttpOnly), set only after you click “See the demo project”. A visit expires 24 hours after its last activity and at most 72 hours after it started. Every visit gets its own copy of the sample project; what you enter or add in it (files included) is visible only to you and is deleted with it when the visit expires or when you start the demo over. The identifier is not linked to any account or IP address.
• projektado-client-portal: the remembered browser of a studio's client who confirmed the link to the project's materials with a code from an e-mail or a PIN; not readable by the page's scripts (HttpOnly), sent only with that one link, and valid for at most 30 days from the confirmation. A new link generated by the studio ends it.
• projektado-client-brief: the same for the link to the questionnaire (brief).
• projektado-client-studio: the remembered confirmation by a code from an e-mail, which lets the other links of the same studio (the questionnaire, the materials, another project of the same client) open in this browser without a new code; it holds only random identifiers, no e-mail address and no studio name, is not readable by the page's scripts (HttpOnly), is sent only with client links, and is valid for as long as the remembered browser, which is at most 30 days. It opens only links of the studio where the address was confirmed, and only those the address has access to. A PIN does not set it.
• projektado-lang: the language you chose (Polish or English) and nothing else. It is set only by a choice, never by merely visiting a page: when you pick a language in the language switcher, when you open a link that names a language (the “lang” parameter), or after you sign in, from the language saved in your account. It lasts 12 months and is readable by the page's scripts, because it holds no secret.

The cookies used for signing in, session security, a studio client's links and the demo project are strictly necessary for the service you explicitly ask for, so they do not require your consent. The cookie holding the language is set only as a result of your own choice and serves only to remember it. We ask for consent separately for two purposes: counting visits to the public pages, and recording a visit and click maps on the public pages and in the demo project (described below).

Your browser also stores interface settings locally (for example, which export columns you chose) and a working copy of a brief the client is filling in. On the public pages it also holds your privacy choice (key projektado-privacy: the version of the prompt's wording, the date, the choice and a random browser identifier).

The public pages look the same wherever you are: we do not choose their content or prices by country. We use the country code of your connection, as reported by our network provider (Cloudflare), for one purpose only: we do not record a visit or click maps (described below) when the code is the United Kingdom, even if you agree to that recording. Cloudflare works that code out from the IP address of the connection. Our app uses only the two-letter country code, not the IP address. We do not store the country code in a user profile or pass it separately to other recipients.

On the public pages (home, features, pricing, contact and the other information pages) we count visits and measure how fast pages load with our own statistics tool (Umami), running on our own server, but only after a separate consent to statistics, which we ask for in the prompt on those pages. Until you agree, nothing is counted. No analytics company receives the data; it is handled only by the providers named in section 6. The tool uses no cookies. The IP address of your connection reaches it with every recorded visit and is used only at that moment, for two things: working out the approximate location and calculating the hash described below. The tool does not store the IP address itself. It stores nothing in your browser by itself; we store only your privacy choice there (described below). We record the address of the page you visited without any parameters after the question mark (parameters from links, such as a channel label, do not reach the statistics), the page that brought you to us, your browser, operating system and device type, language, screen size, an approximate location (country, region, city) worked out from your IP address, and page load times. Repeat visits from the same browser are recognised by a one-way hash calculated from the identifier of our site, the IP address, the browser's User-Agent and a value that changes every month, so the recognition does not reach beyond a calendar month. We do not link the hash to any account. The purpose is to assess how popular the pages are and how well they perform. The legal basis is your consent (Article 6(1)(a) GDPR). We collect no statistics once you are signed in, on the sign-in and registration pages, or on pages shared with a designer's clients (the brief and the client portal) with this tool. You can withdraw your consent at any time in “Privacy settings” in the footer; withdrawal does not affect the lawfulness of counting done before it. We also do not count people whose browser sends a Global Privacy Control or Do Not Track signal.

Once you are signed in, we keep our own short record of important events in the app, such as an account being created, a studio or a project being created, a project being closed, a client link being generated, such a link being opened for the first time, a client sending a questionnaire, or a product being added. We record the name of the event, the date and time, and the identifiers of the account, studio or project, and for some events one word from a fixed list (for example the sign-in method) or the label of the channel a registration came from. The record has no field for text at all: it never holds the content of your work or your clients' details, and an event caused by a client names only the studio, not the client and not the project. In the demo project we record the course of a visit in the same way, not linked to any account. We keep the record on our own server, with no scripts and no cookies, in our legitimate interest (Article 6(1)(f) GDPR): to know how the app is used and how many projects a studio runs at a given time. Entries about a studio are kept for as long as the studio exists and are deleted with it. We delete every entry after 24 months from the event at the latest. When we erase your account, we remove its identifier from the entries. Entries that carry your identifier are in the copy of your data you download under “Account → Data and privacy”.

We record how a visit goes, and click maps, only after a separate, voluntary consent to that purpose. Consent to statistics is not consent to recording, and the other way round; you can change each of the two choices separately in “Privacy settings”. A recording runs only while counting visits is on as well, because the tool does not record without it: consent to recording alone starts nothing. Refusing does not limit access to the public pages or to the demo project. After you agree, the same tool records the page layout, mouse movement and clicks, and scrolling, so we can see what is unclear on these pages and improve them. Everything you type into form fields is masked and never recorded. Consent to recording covers the public pages and the demo project, which you can open without registering: we do not ask again in the demo, and the strip at the top of the screen says that data is being collected and has a “Turn off” button that withdraws your consent. For the recording we also count the pages you visit in the demo. Text on the pages of the demo project, including text you save there (for example names, notes, tasks or file names), is masked in the recording: the page layout and the navigation bar are visible, but letters and digits appear as asterisks. Recording stops when you go from the demo to sign-in, registration or any other page, and never covers the app after you sign in, your own projects or pages shared with a designer's clients, including the client view in the demo project. The legal basis is your consent (Article 6(1)(a) GDPR). You can withdraw it at any time in “Privacy settings” in the footer, with the button below or with the “Turn off” button in the demo. After withdrawal the page loads again and recording stops at once; withdrawal does not affect the lawfulness of recordings made before it. Your choice is remembered in your browser's storage (localStorage), together with a random identifier. We also keep a copy of the choice on our server (the version of the prompt's wording, the date, the choice for each of the two purposes and that identifier, with no IP address and no browser details) as proof of consent, and delete it after 12 months (Article 7(1) GDPR).

We do not use analytics or marketing cookies. Counting visits and recording a visit, described above, work without cookies and only after separate consents. If we change these tools or purposes, we will update this policy and, where required, ask for consent before the processing starts.

10. Your rights

You have the right to access your data, to have it corrected or deleted, to restrict its processing and, in the cases provided for in Article 20 GDPR, to data portability, and the right to object, described separately below. Send requests about your account data to contact@projado.com.

We answer a request without undue delay, and within one month of receiving it at the latest. If a request is complex, or there are many requests, we may extend that period by two further months; we will tell you so within one month of receiving the request and give the reason (Article 12(3) GDPR).

The right to object. Where we process your data in our legitimate interest (the record of events in the app in section 9, messages not connected with entering into a contract in section 4, notices that signing in was locked in section 5), you can object at any time on grounds relating to your particular situation (Article 21 GDPR). Write to contact@projado.com. After an objection we stop processing that data, unless we show compelling legitimate grounds for the processing that override your interests, rights and freedoms, or grounds for establishing, exercising or defending legal claims.

You can download a copy of your account data yourself, straight away once signed in, under “Account → Data and privacy”. The file lists what it covers and what it deliberately does not, with the reason why.

You can delete your account from the same place. Before anything happens, we show you a list of your studios and what will happen to each one. If you are the sole Owner of a studio where someone else still works, we will ask you to hand over that role first. We delete nothing until then. If you cannot hand the role over, write to us (section 12): we will handle the deletion request within the time stated above. You can restore a deleted account for 30 days by signing in (section 8); after that, deletion cannot be undone. We never ask you to delete your account by e-mail.

We do not make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you, and we do not profile you (Article 22 GDPR).

If you are a designer's client and have no account of your own in Projado, the designer or studio you work with is the controller of your data. They decide what happens to it, and any such request should go to them first. If you do not know their address, write to us at contact@projado.com and tell us the studio's name or the designer's e-mail address, and we will pass your request on for you. We do not search studios' data looking for your address. Data we hold ourselves (the e-mail suppression list, call requests and support conversations) we do search, and we answer for it ourselves.

You also have the right to lodge a complaint with the President of the Polish Data Protection Authority (PUODO), ul. Stanisława Moniuszki 1A, 00-014 Warsaw, Poland.

11. Changes to this policy

This privacy policy may be updated as the service develops. The current version is always available at this address, together with the date it was last updated. When a change is material, people who have an account see a notice about it in the app after signing in: what changed, and a link to the current text. We show that notice ahead of time, before the change takes effect; anyone who does not sign in during that time sees it the next time they sign in. It is not a request for consent. We record only what is needed to show that the notice was displayed: the account identifier, the version of the policy and the date. Section 8 says how long we keep that record.

12. Contact

For anything about privacy and data protection, write to contact@projado.com.

13. Information for people in the United States

This section adds to the rest of the policy for people who live in the United States. Everything above applies to you as well. Some US state privacy laws cover only businesses above a certain size; we give the rights below to everyone, whichever state you live in.

We do not sell your data. We do not sell personal information, we do not share it for advertising based on your activity on other sites, and we do not pass it to other companies for their own marketing. There is no advertising in Projado.

Sensitive information. We use your sign-in details only to sign you in and to keep your account secure. We do not use any information to work out characteristics about you.

Your rights. You can ask us for a copy of your personal information, ask us to correct it and ask us to delete it. Section 10 says how: most of it you can do yourself under “Account → Data and privacy”, or you can write to contact@projado.com. We answer within the time stated in section 10. If we decline a request, we tell you why, and you can ask us to look at it again by replying to our answer. Using these rights does not change how we treat you.

Privacy signals from your browser. If your browser sends a Global Privacy Control or Do Not Track signal, we do not count your visit and do not record it, whatever you chose in the prompt (section 9).

If you are a designer's client. The studio you work with decides what happens to your information; we act only on its behalf, as its service provider (processor). Send requests to the studio first (section 10).

Health information. We do not ask about anyone's health or diagnosis. Some optional answers about features of the space (for example no thresholds, or wider doors) can indirectly reveal health needs; we never use them to infer anyone's health. The questionnaire asks them only if the studio chooses to include them. We do not use these answers, or anything you write or upload, to work out or label anyone's health. If you mention a health condition in a text field, it is stored with the project like any other answer: the studio sees it, and we process it only to provide the service. You can ask the studio to remove it.

Where your data is kept. Our servers are in the European Union (section 6), so information about people in the United States is sent to and stored there.