Custody of IDs, payslips and KYC data
Path of the document from upload to storage. We look for public buckets, guessable URLs, lack of at-rest encryption and filenames that leak identity.
You shipped a valuation calculator on v0, a lead-capture bot on Lovable or an owners' portal on Cursor. We audit before a lead — or the entire owners' list — ends up in a competitor's hands.
ID copies for KYC, verifiable income for solvency checks, payslip scans, rental contracts, owner and tenant records, building association files. Real estate firms and property managers handle high-volume, high-value PII. When an AI tool built in six weeks mixes all of that with an unprotected endpoint, what leaks isn’t a bug — it’s a case for a data-protection authority.
We audit the lead funnels, calculators and portals your team built with AI. The lens is sector-specific: GDPR/LOPD-style data protection, lead containment (so a scraper can’t take your portfolio), and account isolation in multi-portfolio managers.
Path of the document from upload to storage. We look for public buckets, guessable URLs, lack of at-rest encryption and filenames that leak identity.
Ownership filters in the leads database. A Madrid agent shouldn't be able to list Valencia leads by changing an ID in the URL.
Listing, valuation and contact endpoints behind rate limits, authentication and, where applicable, anti-scraping countermeasures. Competitors don't lift your portfolio via API.
Who accessed which personal data, when, from where. Retention period, deletion policy, right-to-be-forgotten implemented in code — not just on the privacy page.
The owners' portal worked: each owner saw their own units. The unit listing, however, was served by a public API that accepted any owner ID. Anyone with curl could iterate and pull the full portfolio with contact details. The tenant-capture bot saved payslip scans in a Supabase bucket with USING (true) policies.
17 findings. 5 criticals: ownership filter added to the listing, RLS applied to the capture tables, payslip bucket switched to private with signed URLs, keys rotated, deletion policy implemented in code. The audit went to the investor as a data-room appendix.
Mid-market CRM with broad APIs — a natural fit for sales agents and lead enrichment.
CRM with strong adoption among Spanish SMBs — automations and agents at a contained cost.
Email, calendar and SharePoint as channel and context — triage, drafting and RAG over your inbox and files.
We only need read-only repository access. We don't copy real data: we work on code structure, database migrations and, when needed, synthetic data. Your PII doesn't leave your infrastructure.
We look at how the code handles data: where it's stored, retention, whether right-to-be-forgotten is implemented, what flows to logs and external providers. We don't issue a compliance certificate — that needs a DPO or legal auditor — but we produce the material they'll need.
We audit the endpoints and tell you whether they're open to scraping (no auth, no rate limit, predictable IDs). It isn't real-time monitoring — that's a separate service — but we tell you exactly what to change so scraping stops being trivial.
Yes. We audit the connector your team built: what permissions it asked for, what objects it can read and write, how it handles auth and errors. If the integration uses provider tokens, we trace where those tokens live.
We design for privacy from the start, human control, traceability, usage limits, permissioning and documentation. For sensitive processes, we help assess risk and applicable obligations under GDPR and the EU AI Act.
Every engagement is led personally by one of the partners. If there's a fit, you get a personal first read of your case within one business day — not a canned demo.