RenvoDesk1. Who is responsible for your data
The operator identified below is responsible for personal data used to manage its own website, business relationships, accounts, security and optional measurement. The operator and privacy contact are identified in the Operator and contact section below.
For customer, worker and other personal data entered into a company workspace, the company generally determines the purposes of processing and acts as controller. The operator processes that workspace data on its behalf to provide the service. That relationship requires a separate data processing agreement.
If your information was added by a renovation company, that company is normally responsible for requests about the project record. You may also contact the operator for help identifying the responsible company or forwarding your request. This does not restrict your rights or the operator’s own obligations.
2. Data collected and its sources
Account and company data includes email address, authentication/session information, company name, country, membership role, invitations and optional business contact details. It comes from you, the person inviting you or your company administrator.
Workspace data may include client contact and billing details, property addresses, project descriptions, estimates, tasks, assignments, expenses, notes, photos, voice recordings, files, sketches and activity records identifying who performed an action. It comes from authorised workspace users. Files may contain personal data or metadata supplied by their authors.
Technical services receive network information such as IP address, browser/request information and timestamps when handling a connection. Optional analytics and error-reporting data are described below. Payment-card collection and automated invoicing are not implemented.
3. Purposes and legal bases
Account administration and service delivery use data needed to perform a contract with you, or steps requested before entering it, where you are the contracting individual. For company representatives and team members, the relevant basis is the legitimate interest in administering the business relationship and providing authorised access, subject to their rights.
Security, abuse prevention, service integrity and handling enquiries rely on legitimate interests in operating a dependable service, or a legal obligation where one applies. Information required to establish, exercise or defend legal claims may be retained for that purpose.
Optional Google Analytics and Sentry collection relies on your separate consent. Workspace processing on a company’s instructions follows the company’s purposes, lawful basis and applicable processing agreement; the operator does not choose an independent marketing purpose for that content.
An account email and the information needed for a requested operation are necessary to provide that function. Optional contact fields and measurement consent are not required to use core features. Refusing optional tracking does not reduce your workspace permissions.
4. Browser storage and consent controls
Storage inventory (version 2026-10-03): RenvoDesk uses the following first-party browser storage for the purposes described here. Browser storage and provider-side retention are different; clearing one does not erase the other.
Necessary preference storage: renvodesk-privacy-v1 (local storage) records analytics/diagnostics choices and their date for RenvoDesk. Choices are valid for 180 days; the browser entry itself may remain until replaced or cleared. renvodesk-locale (local storage) remembers French or English until changed or cleared, with no automatic expiry. renvodesk-landing-entry (session storage) notes that this tab has already opened the public site, so it is sent to your browser’s language only once; it is erased when the tab is closed.
Authentication storage: sb-<project-ref>-auth-token (local storage) holds the Supabase session needed for signed-in features. RenvoDesk and Supabase use it to maintain authenticated access; it persists until sign-out, session cleanup or browser clearing. Token expiry and refresh are controlled by the authentication service. Related *-code-verifier entries, including per-flow entries and their index, support secure signup and recovery callbacks. Completed flows are cleaned up by the authentication library; abandoned entries may remain until library cleanup or browser clearing, without a browser expiry timer.
Optional analytics cookies: _ga and _ga_<measurement-id> identify a browser and maintain analytics session information for Google Analytics. They are placed only with analytics consent, with a configured maximum lifetime of 180 days and automatic cookie renewal disabled. RenvoDesk removes these cookies when analytics consent is withdrawn. Google receives the associated analytics data.
Optional diagnostics: the configured Sentry integration sends error reports after diagnostics consent and does not intentionally set a diagnostics cookie or persistent browser identifier. Session replay and performance tracing are disabled. Sentry receives error data as described below. This inventory covers the application integration; changes to providers or integrations require a renewed inventory review.
Browser storage keeps the login session, interface language and your privacy preferences. These support authentication, your chosen language and remembering your decisions. Signing out or clearing browser storage affects the corresponding stored information.
Analytics and diagnostics are off until you opt in. The Cookie Settings control on enabled production pages lets you accept, reject or choose them separately and change your decision later. Your preference expires after 180 days. If browser storage is unavailable, it applies only to the current page session.
Withdrawing consent stops future optional collection and removes the application’s Google Analytics cookies. It does not reverse processing already lawfully performed. Requests already sent cannot be recalled; deletion rights remain available where applicable.
5. Optional analytics and diagnostics
Google Analytics 4 measures generic page categories, language and selected actions, such as creating a project or saving an estimate. It uses a consented browser identifier in analytics cookies, configured for up to 180 days. Application events exclude customer names, project names, financial amounts, document contents and record identifiers. Full application URLs, query strings and authentication tokens are not intentionally sent.
Sentry receives technical error reports if you enable diagnostics. Reports are restricted to generic error types, static application file locations, line/column information, page category and an optional software release identifier. Raw error messages, user details, request bodies, form values and navigation breadcrumbs are removed. The configured Sentry project is in Germany.
Session replay, advertising tracking and performance tracing are not enabled by this integration. Both providers still receive network information when a request reaches them. These reports concern consenting browsers and are not an exhaustive record of users or company activity.
6. Who can receive data
Authorised people in your company can access records according to their roles. Owners have administrative and financial access; members have operational project access and may edit assigned tasks. Information you download and share outside RenvoDesk is then handled by the recipients you choose.
Technical providers include Supabase for authentication, database and private file storage, the VPS hosting provider for website delivery, and Google Analytics and Sentry when you consent. The website’s VPS is located in Paris, France. The configured Supabase project is in Frankfurt. Provider staff or subprocessors may have access where needed for their contracted operations and support.
Data may also be disclosed where required by law, to protect legal rights or to professional advisers subject to appropriate confidentiality. The actual VPS provider, processing agreements and remaining infrastructure retention settings must be verified by the operator before final publication of this notice.
7. Processing locations and international transfers
An EU database or error-reporting region does not mean every related service activity is confined to the EEA. Provider support, subprocessors and Google services may involve processing in other countries.
Transfers outside the EEA must use a lawful mechanism where required, such as an applicable adequacy decision or Standard Contractual Clauses with any necessary supplementary safeguards. The operator must confirm the mechanisms that apply to its actual provider agreements. You may request information about the safeguards and how to obtain a copy through the privacy contact below.
8. Retention and deletion
Account and workspace information is retained while needed to provide the requested service and maintain authorised business records. Retention decisions take account of the active relationship, the company’s instructions, the purpose of the record, applicable legal duties and any ongoing dispute or security investigation.
Removing membership, revoking an invitation or voiding an expense does not automatically erase related activity history. Some deleted or voided records leave a historical entry. There is currently no automatic account-deletion or whole-project-erasure workflow; requests need to be reviewed through the operator and, where appropriate, the workspace company. The absence of a self-service tool does not remove an applicable right to erasure or extend a legal response deadline.
Privacy choices and the application’s analytics cookies use the 180-day periods described above. Google Analytics user-level and event-level retention is configured to two months, with reset on new user activity disabled. Google deletes expired data through its monthly deletion process; this setting does not apply to standard aggregated reports. Sentry error events on the Developer plan have a standard retention period of 30 days. Cookie expiry does not erase data already received by either provider. Infrastructure log retention and backup deletion arrangements still need confirmation before this notice is finalised. Data subject to an applicable legal retention obligation may be kept for that obligation and restricted from unrelated use.
9. Security and your responsibilities
The application uses authenticated access, company-scoped database permissions and private file storage. Team roles limit available actions. These measures reduce risk but do not make any online service completely secure.
Protect account credentials, review company access and obtain the necessary permissions before uploading personal information, photos or recordings. Avoid unnecessary sensitive data. The service is intended for professional adults, not for children.
10. Your rights
Depending on the circumstances and applicable law, you may request access, correction, erasure, restriction and portability of your personal data. You may object to processing based on legitimate interests and withdraw optional consent without affecting earlier lawful processing.
Contact the operator using the details below, or the company responsible for your workspace record. Identity or authority may need to be verified proportionately. GDPR requests are normally answered within one month; an extension of up to two further months is permitted where necessary because of the complexity or number of requests, with notice and reasons within the first month. Requests are normally free of charge. Any lawful refusal or fee must be explained, with information about complaint and judicial remedies.
You may complain to a competent data protection supervisory authority, including in the EEA country where you live or work or where an alleged infringement occurred. You do not need to contact the operator before exercising that right.
11. Automated decisions
RenvoDesk does not use the described analytics or project functions to make solely automated decisions with legal or similarly significant effects on individuals. Calculated totals and project summaries assist users; they do not replace the business’s decisions.
12. Changes and further information
This policy is dated above and will be revised when relevant practices change. Material changes will be brought to your attention where required. A new optional purpose requiring consent must not be activated merely by changing this policy.
Use the contact details below for privacy questions. Provider privacy notices and the supervisory-authority directory are linked at the end of this page.
Operator and contact
- Service
- RenvoDesk · renvodesk.com
- Legal operator
- Chobanyan Solutions
- Business address
- Rue du Bauloy 81 · 1340 Ottignies-Louvain-la-Neuve
- Country
- Belgium
- Contact
- contact@renvodesk.com