BlupintaSign in

Privacy notice

In effect from Version 1.16

Earlier versions: 1.15 (), 1.14 (), 1.13 (), 1.12 (), 1.11 (), 1.10 (), 1.9 (), 1.8 (), 1.7 (), 1.6 (), 1.5 (), 1.4 (), 1.3 (), 1.2 (), 1.1 (), 1.0 ()

This notice is given under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR) and Italian Legislative Decree 196/2003. We wrote it to be read, not just to be published.

1.Data controller

The data controller is the company that builds and runs Blupinta. We have not appointed a data protection officer (DPO), as our activities don’t require one: you can write to us directly with any question.

Ensiria S.r.l.
Via Federico da Montefeltro 3, 37135 Verona
VAT IT04975100233, share capital € 10.000,00
Email: info@ensiria.eu
Certified email (PEC): ensiriasrl@pec.it

2.What this covers

This notice covers the website blupinta.app, the guide at docs.blupinta.app, the application at editor.blupinta.app, the sign-in at auth.blupinta.app and the emails Blupinta sends. It explains which personal data we handle when you visit the website, create an account, draw and furnish your projects and work with other people. It does not cover other sites Blupinta links to: their own notices apply there.

The content of projects (the homes you draw, the files you upload, the comments) belongs to you and the people you share it with: we keep it and handle it only so you can use Blupinta. If you put other people’s data in it, or invite someone by giving their email address, make sure you may.

3.The data we handle

We handle only the data your account and your projects need to work.

Account data

Your email address, your name if you give it, your profile photo if you upload one, the language of the interface, the preferences you choose in the Settings (the theme and look, how you write numbers, dates and measures, how the editor opens, the shortcuts, the measures new homes start from, which emails to get and when, the suggestions you closed) and the account’s plan.

Sign-in data

  • Passkeys: the public key, the name you give the device, when it was created and when it was last used. The fingerprint, face or PIN that unlocks the passkey stays on your device and never reaches us.
  • Email sign-in links and the code written beside them: only a cryptographic fingerprint of each, the sign-in they belong to and how many wrong codes were typed.
  • Sessions: a fingerprint of the session code, how you signed in, the description of the browser and operating system your browser sends, when it was last used and when it expires.
  • Signing in at auth.blupinta.app, where every app of Blupinta sends you to sign in: that you are signed in there, since when and how (passkey or email), so other apps don’t ask you again; the codes and tokens given to the apps you use, kept as a fingerprint.

Connected apps

The apps you allow to use your account, such as a home dashboard connected with a code: which app, what you allowed it to do, the project it reads, when you allowed it and when it last used it.

Apps you register

If your account may make apps (the Developers section, on request for now), the apps you register, tied to your account: their name, how they sign in, the addresses they come back to, a server’s public keys, what they may ask for, whether Blupinta verified them and how many people connected them. People who connect them see their name, not yours.

Project content

The homes you draw and everything you write in them: walls, rooms, measurements, furniture, names, notes and, if you enter them, an address or coordinates. With them, the saved versions, the history of changes and the files you upload, such as scans and PDFs of floor plans or photos of floors and tiles. The floors and wall tiles you save among your kits, with their images, stay with your account and you find them in every project: the people of a project where you use one see its copy and its image.

Working together

Who is in a project and with which role; invitations, with the invited person’s email address, who invited them, the role offered and when it expires; comments and mentions; notifications: who did what, in which project, whether you read it and whether it already reached you by email.

Visits to the website and the guide

When you visit blupinta.app or docs.blupinta.app we count the visit: the page, the site you came from, the kind of browser, operating system and device, the screen’s size, the browser’s language, the country, region and city worked out from your IP address at the moment of the visit, and which links to the application, the guide or the other language you click. The IP address is not kept: it serves only at that moment, with the browser’s description, to work out an identifier that changes every month, so that someone coming back within the month is counted once. We don’t record what you type nor the part of the address after the question mark, and we don’t count the visit if your browser asks not to be tracked (Do Not Track).

Technical data

For each change made through the application we record who made it, the kind of request, the project and the time, without its content; for a change a connected app made on your behalf, also which app and which of its connections. For server errors we record the kind of request and the description of the error, never the page’s address or the data sent. For errors the application meets in your browser we record the description of the error and the place in the code where it happened, the kind of page (never its address, nor the project), the application’s version, the browser’s description and how many times it happened: not who met it.

We handle no biometric data, no payment data (Blupinta has no payments today) and no special categories of data. We don’t keep IP addresses: neither the website, nor the guide, nor the application records them; the count of visits uses them only at the moment of the visit, as explained above. To limit repeated attempts, the application holds in memory only, for a quarter of an hour at most, the address requests come from when whoever sends them hasn’t signed in yet.

4.Where the data comes from

From you

What you enter when you create your account, draw your projects and use the application.

From other people

Whoever invites you to a project gives us your email address; the people you work with can mention you in a comment; shared projects hold what their other members write in them.

From your browser

The description of the browser and operating system, sent automatically with each request, and the time of the requests; on the website and the guide also the screen’s size, the browser’s language, the page you came from and the IP address, used to count the visit.

5.How we use the data, and on what basis

Each use has a precise purpose and a legal basis under Article 6 of the GDPR.

5.1Signing you in and running your account

  • Creating the account, letting you in with a passkey or a link, keeping you signed in between visits.
Data
Account data, sign-in data.
Legal basis
Performance of a contract (GDPR Art. 6(1)(b)): it is the service you ask for by signing up.

5.2Keeping your projects and letting you use them

  • Saving the homes you draw, showing them in 2D and 3D, keeping them the same on all your devices.
  • Saving their versions, keeping their history, letting you undo and restore.
  • Exporting them as a file when you ask.
Data
Project content.
Legal basis
Performance of a contract (GDPR Art. 6(1)(b)): it is the service you ask for by signing up.

5.3Letting you work with other people

  • Sending invitations, giving each person their role, showing who is working and where.
  • Publishing comments and mentions, telling you with notifications of what others do in the projects you are in.
Data
Working together, account data.
Legal basis
Performance of a contract (GDPR Art. 6(1)(b)) for people with an account; for someone invited who has none, the inviter’s and our legitimate interest in delivering the invitation (GDPR Art. 6(1)(f)).

5.4Writing to you for the service

  • The sign-in link when you ask for it, invitations to a project and, as you choose in the Settings, at once or in the morning summary: mentions, replies and resolved conversations, new versions, answers to your invitations, role changes.
Data
Email address, name.
Legal basis
Performance of a contract (GDPR Art. 6(1)(b)): it is the service you ask for by signing up.

5.5Protecting the service and your data

  • Limiting repeated attempts, such as requests for sign-in links or invitations.
  • Tracing who did what in a project, when needed.
Data
Technical data, sessions and, in memory only and for a few minutes, the IP address of whoever hasn’t signed in.
Legal basis
Legitimate interest (GDPR Art. 6(1)(f)): the security of the service and of its users’ data.

5.6Understanding how the website and the guide are used

  • Counting the visits, knowing where they come from, which pages help and how many people go on to the application, to make the website and the guide better.
Data
Visits to the website and the guide.
Legal basis
Legitimate interest (GDPR Art. 6(1)(f)): knowing whether and how the website and the guide are used, with as little data as possible: no cookies, no IP address kept, no profile, no third party.

5.7Finding and fixing errors

Data
Technical data about errors.
Legal basis
Legitimate interest (GDPR Art. 6(1)(f)): the service working well.

5.8Meeting the law

  • Answering requests from authorities and meeting legal obligations.
Data
Whatever the law requires.
Legal basis
Legal obligation (GDPR Art. 6(1)(c)).

Where we rely on legitimate interest we have checked that it does not override your rights: the data is little, holds none of your projects’ content and protects you too. You can still object, as explained under your rights.

6.What happens if you don’t give us the data

An email address is needed to create an account and sign in: without it we can’t provide the service. Your name is optional. What to write in your projects is up to you: an address, coordinates and notes are never required.

7.The emails you receive

Blupinta writes to you only for the service: the sign-in link when you ask for it, invitations to a project and what happens in the projects you are in (mentions, replies, new versions, role changes), at once or in a summary every morning, as you choose in Settings → Notifications, where you can also stop them; every email carries the link to choose. We send no newsletters or promotional messages; if we ever do, it will only be with your explicit consent, which you can withdraw at any time.

8.Cookies and browser storage

The website blupinta.app uses neither cookies nor the browser’s storage; the guide at docs.blupinta.app uses no cookies and remembers in the browser only the theme you choose. Both take their pictures and videos from cdn.blupinta.app, our delivery network on Amazon Web Services, and nothing else from other sites: even the fonts come from our server. They count visits with a tool installed on our server (Umami), which uses no cookies, keeps no IP address and sends nothing to third parties. If you are already signed in to the application, the website asks it who you are, only to show your photo and take you to your projects: the answer stays in the page and is not kept.

The application and its sign-in use only technical cookies; the application and the guide keep a few preferences in the browser’s storage (localStorage), which stay on your device:

NameKindWhat it is forHow long
pb_sessionTechnical cookie, editor.blupinta.appKeeping you signed in. It holds the session code, can’t be read by scripts and is only sent over encrypted connections30 days from its last use; removed when you sign out
pb_sign_inTechnical cookie, editor.blupinta.appThe checks of a sign-in in progress, until you come back from auth.blupinta.appAn hour at most; removed when you are back
_sessionTechnical cookie, auth.blupinta.appKeeping you signed in where you sign in, so every app of Blupinta finds you there. It can’t be read by scripts30 days; removed when you sign out
_interaction, _interaction_resumeTechnical cookies, auth.blupinta.appThe sign-in in progress, so only the browser that started it can finish itAn hour at most
project-blu.languagelocalStorageThe interface’s language before you sign in (on editor.blupinta.app and on auth.blupinta.app, each its own)Until you clear it
project-blu.themelocalStorageThe theme you chose (system, dark, light), so the page opens in itUntil you clear it
project-blu:drawing-look:…localStorageHow the scan looks in each project (opacity, contrast), for you onlyUntil you clear it
project-blu:setup-step:…localStorageHow far you are in each project’s guided setup, and what you chose there and haven’t confirmed yet (the name you are typing, the points clicked on the drawing, the windows ticked)Until you clear it
starlight-themelocalStorage, docs.blupinta.appThe theme chosen in the guide (automatic, dark, light)Until you clear it
project-blu.last-projectlocalStorageThe last project you opened, to reopen it when you come in if you ask for that in the SettingsUntil you clear it

All of them are technical tools needed for the service you asked for: that is why they need no consent and we show no banner. We use no profiling, analytics or third-party cookies.

9.Who we share the data with

We don’t sell your data and don’t hand it to anyone for commercial purposes. Only these see it:

The people in your projects

Whoever is in a project sees its content, its comments, your name or, if you haven’t given one, your email address, your photo if you uploaded one, which changes you made to it and when (its history), and while you work together the spot of the plan you are looking at. Whoever you invite to a project sees your name and photo in the invitation.

The apps you connect

An app you allow to use your account receives only what its page asked you for, in your words: your name and language, your email address, the saved versions of the one project you chose. It is listed in the Settings, under Account, and in the project’s Share window, where you can disconnect it at any time: from then on it receives nothing more. An app made by someone else handles what it receives under its own notice.

Our providers

They handle data only on our behalf, as processors appointed with a contract under Article 28 of the GDPR:

  • OVH SAS (France): the server the website, the guide, the application and the count of visits run on, and the sending of emails.
  • Amazon Web Services EMEA SARL (Luxembourg): the storage of uploaded files and of the database’s encrypted backups, and the delivery of files (the website’s and the guide’s pictures and videos, the catalog’s and the projects’ files) from cdn.blupinta.app.

The people at Ensiria

Those who work on Blupinta, only when needed to run the service or answer a request of yours, and bound to confidentiality.

Authorities

Only when the law requires it.

10.Where it is kept

The data is kept in the European Union: on OVH’s server and, for files and backups, in Amazon Web Services’ Stockholm region (eu-north-1). Files reach your browser from cdn.blupinta.app, Amazon’s delivery network (CloudFront), which hands them over from its point nearest to you, in Europe or North America, and records no requests.

Amazon Web Services belongs to a group based in the United States. Its data processing addendum includes the Standard Contractual Clauses approved by the European Commission, and Amazon takes part in the EU-US Data Privacy Framework. On top of that, the database’s backups are encrypted on our server before they are sent: whoever stores the file can’t read it.

11.How long we keep it

DataFor how long
AccountAs long as the account exists; the photo until you remove or change it
Projects, files, versions, commentsUntil you delete them, or until you delete your account. A deleted project is removed with all its files. A new house left halfway through the wizard, and not touched for 30 days, is removed with its files
Floor and wall tiles kits, and their imagesUntil you delete them, or until you delete your account; the homes using one keep its copy, with the project
Database backups7 days: what you delete is gone from the backups within a week
Sessions30 days from their last use, or until you sign out
Signing in at auth.blupinta.app30 days, or until you sign out
Email sign-in links and codesValid for 15 minutes, then useless; erased after a day
Connected appsUntil you disconnect them, or delete the project they read or your account. Their tokens last an hour; those that keep an app connected, 90 days from their last use
Apps you registerUntil you delete them, or your account; deleting one disconnects whoever had connected it
Invitations7 days, if not accepted
NotificationsAs long as the project they are about exists, or until you delete your account
Technical data12 months at most
Visits to the website and the guide13 months, to compare a year with the one before, then deleted
IP address for the request limits15 minutes at most, in memory only

When you delete your account we remove your data and the projects you own. The comments and changes you left in other people’s projects stay in those projects, as part of their work, but no longer carry your name or email address.

12.Your choices

Much of it you decide yourself, without writing to us:

  • Your name is optional: you can give it, change it or remove it in Settings → Account, along with the language.
  • In Settings → Account you see which devices you are signed in on and can sign them out, and you can add, rename and remove passkeys.
  • You can delete a project you own, and export any project as a .home.json file.
  • In Settings → Account you download all your data as a zip file and delete the account. If you own projects shared with other people, you first hand them over to another member or delete them: nobody loses shared work unless you decided so.
  • You can decline an invitation, or let it expire, and leave a project you were invited to.
  • You can edit and delete your comments.
  • If you don’t want your visits to the website and the guide counted, have your browser send the request not to be tracked (Do Not Track) or block the counting script with an extension: the website works all the same.

13.Your rights

The GDPR gives you these rights, which you can use at any time and free of charge:

Access (Art. 15)

Knowing which data we have about you and getting a copy.

Rectification (Art. 16)

Correcting inaccurate data. You change your name, language and preferences yourself in the Settings, the theme from the account menu too.

Erasure (Art. 17)

Having your data deleted, except what the law requires us to keep. You do it yourself by deleting the account from its page.

Restriction (Art. 18)

Asking us only to store your data and do nothing else with it, for instance while we look into a complaint of yours.

Portability (Art. 20)

Receiving the data you gave us in a structured format other applications can read. You download everything as a zip file from Settings → Account; each project also exports from the editor as a .home.json file.

Objection (Art. 21)

Objecting, on grounds relating to your situation, to the uses based on our legitimate interest.

For those the application doesn’t already let you use yourself, write to the address in the contacts, preferably from your account’s address: we may ask you to confirm who you are. We answer within one month; if the request is complex we may extend that by two more months, telling you so.

If you believe your data is handled against the GDPR, you can lodge a complaint with the Italian data protection authority, the Garante per la Protezione dei Dati Personali, or with the authority of the country where you live or work.

14.Automated decisions

Blupinta makes no decisions based solely on automated processing that have legal effects on you, and builds no profiles. If we introduce artificial intelligence features in the future, this notice will say which data they use and how before they become available.

15.How we protect the data

  • You sign in with a passkey or a one-time link: there are no passwords to steal.
  • Of sign-in, session and app codes and tokens we keep only a cryptographic fingerprint, useless for getting into your account; the one exception is the code a device waits with to be connected, for its 10 minutes.
  • Every connection is encrypted (HTTPS), and the session cookie travels only over them.
  • Every request declares who may make it: a project is visible only to the people in it, each with their role.
  • The database’s backups are encrypted before they leave the server.

Should a data breach put your rights at risk, we will notify the Garante within 72 hours and, where the risk is high, tell you as well.

16.Children

Blupinta is not meant for anyone under 14. If you find out that a child under 14 has given us their data without the consent of whoever holds parental responsibility, write to us and we will delete it.

17.Changes to this notice

If this notice changes, we publish the new version here with its date and keep the list of earlier versions. If the change concerns what we do with your data, we also tell you by email before it takes effect.

18.Contact

For any question about this notice or to use your rights:

Ensiria S.r.l.
info@ensiria.eu
Certified email (PEC): ensiriasrl@pec.it

Supervisory authority

Garante per la Protezione dei Dati Personali
Piazza Venezia 11, 00187 Roma
www.garanteprivacy.it