Data processing agreement
The GDPR art. 28 agreement between each community (controller) and solcondo (processor), published so it can be reviewed before signing up.
Last updated: November 14, 2026
This agreement is part of the terms of service and is accepted with them. If your community or property manager needs a signed copy, write to jesus@solcondo.com and we will send it.
1. Parties and roles
- Controller: the owners' community that contracts solcondo, represented by its president or whoever it appoints.
- Processor: the owner of solcondo, identified in the legal notice.
The community decides what data is processed and why. solcondo processes it only to provide the service and following its instructions: those the community configures in its portal and those it gives in writing.
2. Subject, duration and purpose
solcondo processes the data to host and run the community's private portal: residents' access, communications, incidents, bookings, votes, minutes, documents, finances and the AI assistant. The agreement lasts as long as the service and ends as set out in section 9.
3. Data and data subjects
- Data subjects: owners, tenants and residents; board members; property managers and their staff; maintenance companies and suppliers the community registers.
- Data: identification and contact details (name, email, phone), home and ownership share, role in the community, content each user publishes (incidents, messages, bookings, votes), proxy documents, the community's financial data and, if the community publishes it, the list of debts owed to the community.
- We do not process special categories of data (GDPR art. 9). The community must not upload them to the portal.
4. solcondo's obligations
solcondo undertakes to:
- Process the data only on the community's documented instructions and warn it if any instruction seems unlawful.
- Ensure that anyone with access to the data is bound by confidentiality.
- Apply the security measures in section 6.
- Use subprocessors only on the terms of section 5.
- Help the community answer residents' requests to exercise their rights (access, rectification, erasure, objection, restriction and portability), and forward any that reach us directly.
- Notify the community of any security breach affecting its data without undue delay and within 48 hours at most of becoming aware of it, with the information it needs to meet its own notification duties.
- Help the community with any impact assessments and prior consultations it must carry out.
- Make available the information needed to show compliance with this agreement and allow reasonable audits, with prior notice and without access to other communities' data.
5. Subprocessors
The community gives solcondo general authorisation to use the published subprocessors. solcondo binds them by contract to the same data protection obligations it accepts here and is liable for their compliance. We will give 30 days' notice before adding or replacing one; if the community objects on reasonable grounds and we find no alternative, it may terminate without penalty.
6. Security measures
- Isolation per community: every database query is restricted by row-level security policies; one community cannot read another's data.
- Passwordless access: users sign in with Google or with a one-time code or link sent to their email, and only if the community has approved them. Sessions expire after 30 days.
- Role-based permissions: each role sees only what the community allows, and the AI assistant respects those same permissions.
- Encryption: in transit (HTTPS with HSTS) and at rest in the database.
- Traceability: sign-ups, changes and deletions are logged.
- Minimisation: proxy documents are deleted automatically 30 days after a vote closes, and the IP address of whoever fills in a form is not stored.
7. The community's obligations
The community warrants that it has a legal basis for the data it uploads, that it informs residents of this processing (each portal publishes its own privacy policy) and that its instructions to solcondo comply with the law.
8. International transfers
Data is hosted in the European Union. Where a subprocessor handles it outside the EEA, the transfer relies on the safeguards of GDPR chapter V, as stated in the subprocessor list.
9. End of the agreement: return and deletion
When the service ends, for any reason:
- The portal stays read-only for 90 days so the community can download what it needs.
- Within that period, at the community's request, we hand over a complete copy of its data and files in open formats (CSV, JSON, PDF and Markdown).
- After the 90 days we delete the data and certify it in writing, except anything a law requires us to keep, which will be blocked.