DaPrimp Home

Privacy Policy

Version of 1 Sep 2026

This page explains what data DaPrimp processes, why, and what rights you have. We collect a minimum: the service takes no payments, so we hold no payment data at all.

1. Data we process

Account: email, internal user ID, role, language, name (if provided), and profile photo (if uploaded). The current app signs in by email. Earlier accounts may retain a phone number; it is used only as contact between parties to a confirmed or completed booking and is erased when the account is deleted.

For pros: studio address/area and geolocation, bio, services and prices — that is your public storefront.

For clients: approximate or precise location only during a nearby search, with browser or Android permission; manual city selection is always available. Search coordinates are not saved to the profile or used in the background.

Service activity: booking history and prices, favorites, reviews, reports and appeals. Profile, service and review text becomes public only when you publish it.

Technical: locale cookie and app preferences, session tokens, and server logs containing IP address, user-agent, normalized path, status and response timing. Request bodies and query strings are excluded from the new access-log format.

2. Why

To show nearby openings, run bookings, verify sign-in by one-time email code, handle safety reports, prevent abuse and operate the service.

3. Who receives data

Required data is processed by our infrastructure and email providers to operate the service. Parties to a confirmed or completed booking receive only the contact details defined by the product flow.

The web app and PWA use the official VK Maps Web SDK mmr-gl 0.2.43. To load the style and tiles and operate the map, the browser may send VK LLC the application API key, the center and bounds of the visible viewport, map interactions, and ordinary network, browser and device technical data. The SDK stores an anonymous SDK UUID and technical event state in browser localStorage and sends required operational telemetry to events.maps.vk.com. DaPrimp does not add email, account ID, booking data or slot IDs to these requests. VK Maps policy: https://help.mail.ru/legal/terms/maps/privacy/. Terms: https://help.mail.ru/legal/terms/maps/terms/.

The Android app uses VK/RuStore Maps SDK 1.1.33. To render the map, the SDK may send VK LLC the application key, the center and bounds of the visible viewport, map interactions, and ordinary network, device and app technical data. DaPrimp does not enable the SDK LocationSource or add email, account ID, booking data or slot IDs.

The standard VK/RuStore Maps logo and attribution, including OpenStreetMap source information, remain visible in Web/PWA and Android. OpenStreetMap data terms: https://www.openstreetmap.org/copyright.

4. What we do NOT do

We take no payment data. We do not sell personal data. We do not use your data for third-party advertising.

5. Storage and security

Data is stored on protected servers with restricted access. Sessions are token-based and no passwords are used. One-time codes expire quickly; the accepted Terms and Privacy versions are recorded in an audit log without copying the email into its metadata.

6. Your rights

You can edit your name and photo, disable notifications, request an export, or delete your account yourself in Profile or at /account-deletion. Transactional data that must be retained remains anonymized.

7. Regional compliance

We follow applicable data-protection law in the countries we operate, including LGPD in Brazil and local law in Uzbekistan and Kazakhstan. Questions: support@daprimp.com.

DaPrimp · daprimp.com · support@daprimp.com