How we process your data.
Information about the data you provide when contacting us, purchasing a package or using the private area.
1. Data controller and contact
Roto y Descosío is managed by the company that owns the brand. For privacy matters you may contact us at hola@rotoydescosio.com.
2. Data we may process
Contact details, information about the property and project, selections made within the package, information required for orders and deliveries, communications, and basic technical data arising from website use.
3. Why we use the data
To respond to enquiries, prepare and manage proposals, formalise and deliver the contracted service, manage orders and logistics, provide access to the private area, handle issues and comply with administrative or legal obligations.
4. WhatsApp and external links
When an action opens WhatsApp, Google Maps or another external service, subsequent processing is also subject to the relevant provider’s terms and policies. The website must not send message content, names, phone numbers, exact property location or private selections to Analytics.
5. Analytics
Only if you accept analytics may Google Analytics measure visits and general interactions to help us improve the website. We do not use this integration for personalised advertising. You may withdraw consent from “Cookie preferences”.
6. Retention
We retain data for as long as necessary to handle the request or provide the service and, afterwards, for the periods required to meet liabilities and legal obligations.
7. Recipients
Suppliers and collaborators required to perform the service —for example manufacturers, logistics or installation providers— may access information only to the extent necessary to manage the project and orders.
8. Your rights
You may request access, rectification, deletion, objection, restriction or portability where applicable, and withdraw consent for processing based on consent. Write to us at hola@rotoydescosio.com.
9. Security
We apply reasonable security and data-minimisation measures. The final private area must use secure server-side authentication; the local preview does not represent the final authentication system.
