Privacy policy
De Raiz – build control for people managing their own house.
Ler em portuguêsA build you keep to yourself never leaves your phone. A build you choose to share with whoever is building it with you also lives on a server in the European Union, where only that build's members can read it. You decide which of the two happens, build by build, and the whole app works with no account at all.
On a computer, at app.casaderaiz.pt, it is different, which is why it has a section of its own below: there the account is required, the build is always in the cloud, and the browser keeps a copy of it until you sign out.
What is collected
If you do not create an account: nothing
Without an account – which is only possible on the phone – the app does not collect, transmit or have access to any information about you. Everything you write stays in the app's private storage, on your device.
If you create an account
On the phone, the account is optional and exists in order to share a build; on a computer, it is the way in. Creating one stores:
- the email address you registered with, to identify the account, confirm the registration and reset the password;
- the password, if you chose that method – stored irreversibly, never in readable text;
- the identifier Apple or Google return, if you signed in with one of them, and the name those companies supplied. Apple often supplies no name at all, in which case no name is stored;
- the dates the account was created and last signed in on, recorded by the authentication service.
Signing in sends nothing from your build. Creating the account and signing in is all that happens; the quotes, the payments, the documents and the photos stay where they were.
If you share a build
From the moment you choose to put a build in the cloud – and only from that moment – that build has a copy on the server: the records you wrote and the files you attached. That is what lets the same build appear on the phone of whoever is building it with you. Any build you do not put there still does not leave your device.
What still does not exist
- usage analytics, telemetry or usage statistics in the app (what the browser may report to Cloudflare on its own is described under On a computer);
- automatic crash reporting;
- advertising, ad tracking or advertising identifiers;
- selling, sharing or handing your data to third parties for commercial purposes;
- tracking your activity across other apps or other websites;
- cookies – on a computer, the session is kept in the browser's storage.
The app's developer receives no copies, summaries or statistics of what is in your build, and does not open anybody's data to read it.
Where your data lives
On your phone, always: the build, its phases, the trades, the quotes, the payments, the suppliers, the documents and the photos are stored in the app's private storage. Files you attach are copied into that same private folder. The app was built to work this way – on a building site with no reception, everything keeps working.
And, for the account and any build you share, on a server in the European Union. The service is Supabase, acting as processor, in the Central EU – Frankfurt, Germany region. The data does not leave the European Union. Supabase is also what sends the registration and password-reset emails.
And, on a computer, in the browser you signed in on, for as long as you are signed in – the next section explains.
On a computer
De Raiz also works in a browser, at app.casaderaiz.pt. It is the same app, and the browser is one more device of the build. Three things differ from the phone:
- The account is required, and the build is always in the cloud. The computer only opens shared builds – ones already on the server, or one created there, which is saved to the server as it is created. A build you keep to yourself, on your phone, never reaches the computer.
-
The browser keeps a copy of the build – the records, the photos'
thumbnails, and the documents and photos you opened – in the private storage it gives this
site, so the app works without a connection, and keeps the session in its
localStorage. Signing out sends whatever is still to send and deletes both. Leaving an build and deleting the account also delete this browser's copy. If the browser needs the space, it may delete the copy on its own; the build is in the cloud and opens again. - Reminders stay on the phones. The computer sends no notifications, and the site forbids the browser itself the camera, the microphone and location: files are chosen in the browser's file picker or dragged onto the page. Some browsers ask whether the site may store data persistently – that is the copy of the build, and saying no only means the browser may delete it if it needs the space.
The page is served by Cloudflare. Cloudflare hosts the app's files and delivers them to your browser, acting as processor, under its data processing agreement. To do so it sees the requests your browser makes to it: the IP address, the browser and system (user agent) and the page requested. It is a United States company with servers around the world, and the request is answered by the nearest. The build's data does not pass through it: it goes from the browser straight to the server in the European Union.
The browser may tell Cloudflare when a page fails to load. Cloudflare adds
a Network Error Logging request to its responses, and browsers that support it send
a report to a.nel.cloudflare.com when a load fails – with the address
requested, the kind of error and when, and, like any request, the IP address. It is not
usage analytics nor anything the app does, and it cannot be switched off on the free service
that hosts this page; it is written here because it is a request your browser makes to a
third party.
Who can see a shared build
That build's members, and nobody else. This is not a matter of good intentions: every table on the server has row level security enabled – a rule the database itself applies on every read and every write, answering "nothing" to anyone who is not a member of that build. It is not the app's code deciding what to show; it is the server refusing to hand it over.
You join a build by being invited by whoever is its owner. Each member sees the other members' names (that is what the name is for), which of them is the owner, since when each has been there and whether any of them is still on an older version of the app, and nothing else about them. For that, the app keeps beside each member the number of the version they have installed – or, on a computer, of the version the browser is running: the same for everyone on that version, and nothing that tells one device from another. There are no public profiles, no user search, and no way to find out who has an account.
An invite is a six-character code that works once and expires after seven days. The server
keeps who created it, when it expires and who accepted it – not the code itself, only a
fingerprint of it, computed with a key that never leaves the server. An invite link carries
the code after the
#, which browsers never send to any server.
Beyond the members, access exists only for whoever hosts the service, under the processing agreement, and for the app's developer, strictly as far as needed to keep it running or to meet a legal obligation.
Backups you create
The app can export a single file containing all of your records and files. That file is created on your device and handed to the iOS share sheet: you choose where it goes – Files, iCloud Drive, email, or another service. On a computer, the browser downloads it to the downloads folder.
Once you send it to a service, that service's own terms and privacy policy apply, and they are outside this app's control.
Separately, if you have iPhone backup enabled, iOS may include this app's private storage in that backup. That is a feature of Apple's operating system, managed in your device settings.
Permissions the app asks for
On the phone, two, and only when they are needed:
- Camera – only when you choose to take a photo to attach to the build. The image is saved on the device, and leaves it only if the build is shared.
- Files – only when you choose a document to attach or a backup file to import. The app receives only the file you selected.
Choosing a photo from your library goes through the system's own picker, which hands over only the image you chose – the app never has access to your library.
Links out of the app
Some screens open things outside the app: a product address you saved, a supplier's phone number or email, and this page. In those cases your browser, phone or mail client takes over, and their rules apply.
Signing in with Apple or Google goes through those companies' own sign-in screens, and at that moment their policies apply too. If you would rather not involve them, you can create an account with an email address and a password alone.
How long it is kept
- On your phone, for as long as you want. Deleting the app deletes that data with it, and all that remains is whatever you exported or shared.
- In a browser, until you sign out, leave the build or delete the account – each of the three deletes that browser's copy of the build and its session.
- The account, for as long as it exists. Deleting it deletes the email, the name and the link to the builds it was a member of.
- A shared build, for as long as it has members. When the last member leaves it or deletes their account, the build, its records and its files are deleted from the server. Leaving a shared build deletes it from the phone or browser you leave from as well – the build carries on for the other members.
Legal basis
Processing the email address and the name rests on performing the service you asked for – the account and sharing do not work without them (GDPR, Article 6(1)(b)). There is no processing based on marketing interests, because there is no marketing. The controller is the person who develops the app, reachable at the address below.
Your rights
Over the data on your device, the control is entirely yours: you can see it, correct it, export it from the backup screen, and delete it by uninstalling the app – or, on a computer, by signing out. Nobody has to hand it to you, because it never left.
Over the data on the server, you have the right to:
- know what is stored and access it;
- correct anything that is wrong;
- receive a copy in a readable format – the app's export does exactly that, and you do not need anybody's permission to run it;
- delete the account and what belongs to it;
- object to the processing and restrict it.
To delete the account, there are two ways. In the app, under the button in the top-left corner, in Conta → Apagar a conta (Account → Delete account), the account is deleted there and then. Or write to suporte@casaderaiz.pt from the account's own address, and it is deleted within 30 days. Either way, the email, the name and any build you are the last member of are deleted, with its records and files; from a build other people are in, you leave, and it stays intact for them. If you run a build that has other members, you choose first whether to hand it to one of them or delete it for everyone – neither happens without your choosing it. The build saved on your phone is not touched; the copy in a browser is deleted, with the session. Export the backup before deleting: whatever is only on the server will have nowhere to be recovered from.
If you believe your data is being handled improperly, you can complain to the Portuguese data protection authority, Comissão Nacional de Proteção de Dados.
Children
The app is for managing a private building project and is not directed at children. No children's data is requested or collected, and the account is not meant to be created by them.
Changes to this policy
If the app ever does something that requires changing this text, the text changes here, with the updated date above. A version that collects or transmits anything new has to say so on this page before doing it – that rule is what forced this page to be rewritten when the app gained accounts.
Contact
Questions about this policy, or to exercise any of the rights above: suporte@casaderaiz.pt