Privacy Policy

Pataluha Ventures S.L. · Last updated: 6 October 2026 · Version 3.1

Looking for the privacy notice that covers our marketing website? See https://solidmaint.com/privacy.

We comply with the EU General Data Protection Regulation (GDPR) and the Spanish Organic Law on Personal Data Protection (LOPDGDD 3/2018).

1. Data Controller

Pataluha Ventures S.L. ("we", "us"), NIF B26627539, registered in Spain, operates the SolidMaint platform (Customer app, Crew app, web back-office) and is the data controller for your personal data. SolidMaint S.L. (NIF B27612159, registered office c/o The Pool, Avda. Bulevar Príncipe Alfonso de Hohenlohe 2, 29602 Marbella, Málaga, Spain) is a subsidiary of Pataluha Ventures S.L., registered on 7 May 2026. Until the platform is transferred to SolidMaint S.L., Pataluha Ventures S.L. remains the sole controller. Contact: privacy@solidmaint.com

2. Personal Data We Collect

We collect different categories of data depending on which app you use (Customer or Crew). Where a category applies to only one app, we say so.

• Account data (both apps) — Name, email address, phone number, profile photo, language preference, role.
• Authentication data (both apps) — Hashed password, session tokens, optional Apple Sign In or Google Sign In federated identifier, optional biometric unlock state (Face ID / fingerprint stays on the device and is never transmitted).
• Property data (Customer app) — Address, cadastral reference, construction details, devices and appliances, uploaded documents.
• Service data (both apps) — Service requests, task history, photos (before / during / after work), captions, ratings, logbook entries.
• Payment data (Customer app) — SEPA mandate references, Stripe customer IDs, last-four card digits stored by Stripe (we do not store full card numbers). Crew payouts go through Stripe Connect; the crew app does not collect cards.
• Bank-transfer data (both apps) — When you pay us by bank transfer, or we pay you by bank transfer: the payer's or payee's name, IBAN, the amount and the payment reference, as our business bank account records them. For crew and staff with a seat in our Revolut Business account: their name and e-mail address there, and the expenses and receipt images they submit in the Revolut Business app, which we import as their expense records.
• Voice recordings (Crew app) — Voice notes for work reports and AI co-driving voice mode. Server-side transcription on our own inference hardware, or via Google Gemini when that is unavailable (see §10); the audio file is deleted 30 days after upload, the transcript is retained with the task record.
• Receipt-OCR data (Crew app) — Receipt images uploaded for expense reporting; server-side line-item extraction (store name, date, items, totals) stored on the expense record.
• Location data (Crew app) — Precise GPS coordinates while a task timer is active, used for 100-metre geofence verification and for the foreground-service notification "tracking location during active task". Background location is requested only if you opt in to the timer-arrival reminder or while an active timer runs with the screen off. Coordinates are purged 8 weeks after task completion + invoice issuance.
• Bluetooth pairing data (both apps, when an edge device is enabled for you) — When you install or reconfigure a SolidMaint edge device (a small computer that connects your home's smart devices to SolidMaint), the app uses your phone's Bluetooth to set up the device's WiFi. The Bluetooth peripheral identifier and any pairing PIN you enter are used only during this setup, held in memory, never persisted, never transmitted to our servers, and never shared with any third party. We do not scan for nearby Bluetooth beacons and do not derive location from Bluetooth scans. Pairing requires a PIN printed on the device's setup card — without that PIN no one can configure your device, including us.
• Communication data (both apps) — Chat messages between you and HQ, crew, customers, or task-group participants. WhatsApp messages you exchange with us, sent and received through Meta's WhatsApp Business Platform. Calls to our phone line: your phone number and what you say, which Twilio's speech recognition turns into text during the call so that our assistant can answer.
• Push tokens (both apps) — FCM (Android) / APNs (iOS) device push tokens linked to your user account, used to deliver notifications about service requests, task assignments, approvals, messages.
• Crash diagnostics (both apps) — Sentry crash reports, breadcrumbs (user-interaction events, performance traces) and a userId tag, used to diagnose bugs.
• Usage data (both apps) — Login timestamps, device info (model, OS version), IP address (used briefly for rate-limiting and security checks; not retained as a profile field).
• Operator-handled data (HQ back-office) — Our staff may enter, import, or otherwise process your contact and property data on your behalf as part of internal operational workflows (for example during onboarding, scheduling, follow-up, or service coordination). Such processing may include AI assistance — see §10 for the AI processors we use.

3. Legal Basis for Processing

• Contract performance (Art. 6(1)(b) GDPR) — processing necessary to provide the maintenance services you request and to pay crew members.
• Legitimate interest (Art. 6(1)(f) GDPR) — platform security, fraud prevention, crash diagnostics, anonymous service-quality analytics, and operating, debugging and repairing the platform (including with AI engineering assistants — see §10).
• Consent (Art. 6(1)(a) GDPR) — marketing communications (opt-in only); AI training-data persistence (see §10).
• Legal obligation (Art. 6(1)(c) GDPR) — tax records and invoice retention (up to 10 years — minimum 6 years per Código de Comercio Art. 30, extended to 10 years where records support a base imponible negativa per Ley General Tributaria Art. 66 bis).

4. How We Use Your Data

• Providing and improving our property maintenance services.
• Processing payments (customer side) and crew payouts (crew side via Stripe Connect, or by bank transfer from our business bank account), and matching the bank transfers we receive to the invoices they pay.
• Communicating about service requests, tasks, approvals, and messages.
• Auto-translating chat messages between different language speakers.
• AI-assisted features: photo recognition (Smart Scan), voice transcription (Crew voice reports, AI co-driving), receipt OCR, agent assistance, vision analysis.
• Verifying crew presence at the property via geofence.
• Crash diagnostics and product analytics.
• Warranty expiry notifications for registered devices.

In-app conversations are NOT private from us

Messages in service-request chats (customer ↔ crew, customer ↔ HQ, crew ↔ HQ), in-app AI chat with our assistant, and WhatsApp conversations routed through our platform are visible to authorised HQ staff for:

• Service quality monitoring — spot-checking that the conversation between you and your assigned crew member is constructive, that quotes match what was agreed, and that issues are flagged early.
• Routine system maintenance and debugging — understanding what users have asked the AI assistant when a turn fails, why a translation produced an odd result, why a notification didn't land. We minimise this — but a closed-box "the system doesn't work" report can't be diagnosed without reading the failing turn. Our engineers carry out this work with the help of AI coding and support assistants, so the records being investigated may be read by those assistants as well as by the staff member — see §10, "Engineering support and debugging".
• Dispute resolution — when a customer or crew member reports that the other party promised X and delivered Y, HQ reviews the chat to mediate fairly with documented evidence.

Messages are encrypted in transit and at rest (HTTPS in transit; AWS-managed encryption on the S3 mirror and on the Neon Postgres database). The encryption protects against third-party interception and infrastructure-provider access — it does not make conversations private from SolidMaint operations staff. For confidential matters (legal complaints, HR-style concerns), email privacy@solidmaint.com.

This applies equally to direct customer ↔ crew chats; the platform is operated as a managed service, not a peer-to-peer messaging tool.

5. Data Sharing / Sub-processors

We share your data only with the processors and sub-processors listed below. We do not sell your personal data. The list reflects the actual data flows in the apps; we update it when we change processors.

6. Cross-Border Transfers

Primary data storage (database, file storage) is in the EU. AI inference that the model gateway routes to SolidMaint-operated infrastructure stays entirely within Spain on hardware we own; no third-party processor receives those prompts and no cross-border transfer occurs for them. Some processors operate in the United States for specific functions (some AI inference, AI-assisted engineering support and debugging, push notifications, crash diagnostics, email, OAuth identity); these international transfers rely on EU-Commission Standard Contractual Clauses per GDPR Art. 46(2)(c). Where a processor offers EU-residency options that we have selected, the §5 table says so.

7. Retention Periods

8. Security Measures

We protect your data with the following technical and organisational measures:

• TLS in transit — all client-server traffic uses HTTPS with modern cipher suites; HTTP is rejected at the load balancer.
• Encryption at rest — AWS-managed encryption on S3 file storage, provider-managed encryption on the Neon Postgres database, and Sentry-managed encryption on diagnostic data.
• Password hashing — passwords are stored as bcrypt hashes, never in plaintext.
• Role-based access control — HQ back-office and crew accounts have explicit roles (admin, supervisor, dispatcher, support, worker, customer) that gate which data each role can see.
• Audit logging — security-relevant events (login, role changes, data exports, account deletions, AI training-data toggles) are recorded and retained 2 years.
• Incident response — Sentry crash and error monitoring with operator-controlled access; PII handlers tagged for fast triage during security incidents.

9. Your Rights (GDPR Articles 15–22)

• Access (Art. 15) — Download all your data from Profile → Download My Data.
• Rectification (Art. 16) — Edit your profile at any time.
• Erasure (Art. 17) — Delete your account from Profile → Delete Account, or follow the data-deletion guide at /legal/data-deletion.
• Data portability (Art. 20) — Export your data as a machine-readable ZIP archive.
• Restriction (Art. 18) / Objection (Art. 21) — Email privacy@solidmaint.com.
• Withdraw consent (Art. 7(3)) — Toggle AI training-data persistence off in your profile, or unsubscribe from marketing emails via the link in any such email.
• Complaint — You may lodge a complaint with the Spanish data protection authority (AEPD) at www.aepd.es or with your local EU/EEA supervisory authority.

10. AI Processing and Training-Data Persistence

Some user and operational content is processed by AI models — to power features, and to build and maintain the platform itself. Three distinct flows, with different recipients and different legal bases:

• Inference (always on) — Content relevant to the feature you are using, or to an operator action taken on your behalf, is sent to a model, the model returns a result, and the result is stored on the related record (task, message, expense, property, etc.). This processing is necessary to deliver the feature you requested or to fulfil our service contract with you (Art. 6(1)(b) GDPR). Each call is routed by an internal model gateway to one of two paths: (a) SolidMaint-operated inference on our own hardware located in Spain, where no third party receives the prompt or response, or (b) Google's Gemini API for surfaces and capabilities not yet served by our own infrastructure and as a fallback when the in-house path is unavailable. We use Google's paid Gemini tier; under Google's API terms, paid inputs and outputs are not used to train Google's models, and Google's transient logs are retained no longer than necessary for abuse monitoring. The choice of path is operational and may change over time; both paths uphold the consent and retention rules below.
• Training-data persistence (consent only) — If you have toggled AI training data ON in your profile, we additionally retain the input + output of each AI call originating from your own activity in a pseudonymised archive on our own infrastructure for model improvement. This is consent-based (Art. 6(1)(a) GDPR) and you can withdraw consent at any time. AI calls made by our operators in the course of internal workflows do not flow through this opt-in archive; they are operational state, retained only as long as the relevant operational record exists.
• Engineering support and debugging (legitimate interest) — Our engineers use AI coding and support assistants (Anthropic Claude Code and OpenAI Codex) while building, operating and repairing the platform, and some routine maintenance is carried out by automated agents built on the same models — triaging failed builds and test runs, and reading the internal bug reports our staff file. When a fault is investigated, the records needed to diagnose it are read by that assistant as well as by the engineer: this is the AI-assisted form of the staff debugging described in §4, and the same minimisation applies — we open the records that explain the fault, not the database at large. This flow is separate from the feature inference above and does not run through the model gateway; the two paths described in the first bullet remain the only ones a product feature uses. The basis is our legitimate interest in operating, securing and repairing the service (Art. 6(1)(f) GDPR). Anthropic and OpenAI act as our sub-processors. We use company-managed business services with provider model training disabled. Providers may retain prompts, outputs and session data according to the applicable business terms and configured retention controls, including for service operation, security and abuse monitoring; we do not promise zero retention. This engineering processing is separate from the optional AI training-data consent above. Because this rests on legitimate interest you may object to it under Art. 21 GDPR — write to privacy@solidmaint.com and we will tell you what we can exclude without leaving faults on your account undiagnosable.

Withdrawing your AI training data consent removes your future calls from the training archive and triggers deletion of all previously-archived training records tied to your account. Use Profile → AI training data to toggle, or Profile → Erase AI training data to delete on demand. The deletion routine is DELETE /v1/profile/ai-training-data and is also invoked as part of full account deletion (gdpr-delete.ts).

Operational tables that hold AI session state (ai_sessions, ai_turns, ai_tool_calls) are runtime data, not training data. They exist to support resume-after-disconnect, debug-by-user, and audit-per-request, and they are deleted in the same cascade when you delete your account or revoke consent.

11. Cookies and Similar Technologies

We use only strictly-necessary cookies and storage. We do not set advertising, behavioural-tracking, or third-party analytics cookies.

Specifically: an authentication session token in localStorage (web) or expo-secure-store (mobile), anonymous service-worker / push-notification registrations, and platform crash-diagnostic identifiers (Sentry).

Our other processors do not set cookies in our apps; they receive request-bound telemetry only.

12. Children's Privacy

The platform is not intended for users under 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact privacy@solidmaint.com.

13. Changes to This Policy

We will notify you of material changes via email and/or in-app notice at least 30 days before they take effect. The version number and date at the top of this page indicate when it was last updated.

14. Contact

For any privacy-related questions: privacy@solidmaint.com.

For account deletion, see the dedicated guide at /legal/data-deletion.