Privacy policy
Last updated: 27 October 2026
1. Who is the controller
- Data controller: Enrique Rodríguez Marty
- Registered address: Calle Corazón de María 5, esc. 1, planta 2, puerta B, 28002 Madrid, Spain
- Contact email: contact@darcemi.com
Darcemi is an appointment-management platform for businesses with premises (clinics, veterinary practices, hair salons, workshops, studios and similar), available at darcemi.com and on each client company's subdomain.
2. Two distinct roles, depending on whose data it is
This distinction is the key to understanding the rest of the document.
Darcemi is the controller of the data of the businesses that contract the service and of the people who use the administration panel: sign-up, billing, support, account security.
Darcemi is the processor of the data of the end customers (patients, users, the business's customers) that each business enters or generates on the platform. In that case the controller is the client business, which decides what data it collects and why. Darcemi only processes it following their instructions and under the data-processing agreement signed with them.
If you are an end customer of a business that uses Darcemi and want to exercise your rights, contact that business. If you contact us, we will forward your request to the controller.
3. What data we process
Of client businesses and their panel users: first and last name, email address, password (stored hashed, never in plain text), role and permissions, business details (name, address, phone, hours, services, professionals), billing data and activity and access logs.
Of end customers, on behalf of the business: name, phone, email if provided, appointment history, notes the professional records and the content of the conversations held over WhatsApp with the business.
Technical data: IP address, browser type, date and time of access and session identifiers, for security and abuse-prevention purposes.
4. Your Google account data
When you sign in with Google or connect your calendar, Darcemi requests the following permissions and only for what is stated:
- Permission requested
- openid, userinfo.email, userinfo.profile
- What it is used for
- Identify you when signing in, create or link your account and show your name and photo in the panel.
- Permission requested
- https://www.googleapis.com/auth/calendar.events
- What it is used for
- Create, update and cancel in your Google Calendar the events corresponding to the appointments managed in Darcemi, and read existing events so as not to offer slots that are already taken.
| Permission requested | What it is used for |
|---|---|
| openid, userinfo.email, userinfo.profile | Identify you when signing in, create or link your account and show your name and photo in the panel. |
| https://www.googleapis.com/auth/calendar.events | Create, update and cancel in your Google Calendar the events corresponding to the appointments managed in Darcemi, and read existing events so as not to offer slots that are already taken. |
Limited Use. Darcemi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- We do not sell Google user data to third parties.
- We do not use it for advertising or to build advertising profiles.
- We do not use it to train generalized or third-party artificial-intelligence models.
- We do not transfer it except to the providers strictly necessary to deliver the service (section 7), to comply with the law or with your express consent.
- No human reads it, unless you give us explicit permission for support cases, it is necessary for security or to comply with the law, or the data is aggregated and anonymized.
You can revoke access at any time from myaccount.google.com/permissions. When you revoke it, we stop syncing the calendar and delete the stored tokens; appointments already created in your Google Calendar remain under your control.
5. Why we process the data and on what legal basis
- Purpose
- Provide the contracted service (agenda, appointments, panel, reminders)
- Legal basis
- Performance of the contract
- Purpose
- Process end-customer data on behalf of the business
- Legal basis
- Data-processing agreement (art. 28 GDPR)
- Purpose
- Security, fraud prevention and access logging
- Legal basis
- Legitimate interest
- Purpose
- Billing and tax and accounting obligations
- Legal basis
- Legal obligation
- Purpose
- Commercial communications about Darcemi
- Legal basis
- Consent, revocable at any time
| Purpose | Legal basis |
|---|---|
| Provide the contracted service (agenda, appointments, panel, reminders) | Performance of the contract |
| Process end-customer data on behalf of the business | Data-processing agreement (art. 28 GDPR) |
| Security, fraud prevention and access logging | Legitimate interest |
| Billing and tax and accounting obligations | Legal obligation |
| Commercial communications about Darcemi | Consent, revocable at any time |
6. How long we keep it
For as long as the contract is in force. When it ends, the client business's data is kept for 30 days for its full export and then deleted, except for what the law requires to be kept (billing: six years under the Commercial Code). If the export has not been delivered within that period, the data is not deleted until it is: a history nobody has taken is not destroyed. Security logs are kept for 12 months.
Requests received through the website form are kept for 12 months from receipt and then deleted.
7. Who we share data with
We do not sell data. We rely on the following providers, all with a data-processing agreement:
- Provider
- Hostinger (VPS)
- What for
- Hosting of the application and the database (VPS managed with Dokploy)
- Location
- Spain (EU)
- Provider
- Meta Platforms Ireland Ltd.
- What for
- Sending and receiving messages over WhatsApp Business
- Location
- EU / USA
- Provider
- Google Ireland Ltd.
- What for
- Sign-in and Google Calendar sync
- Location
- EU / USA
- Provider
- Stripe Payments Europe, Ltd.
- What for
- Charging booking deposits and managing each client business's connected account
- Location
- Ireland (EU) / USA
- Provider
- Resend, Inc.
- What for
- Sending the service's emails (invitations, password recovery, consents, notices)
- Location
- USA
- Provider
- Groq, Inc.
- What for
- Interpreting the messages the end customer writes to the WhatsApp assistant: it receives their text and, if it was the last thing they received, the last automated message sent to them (without their name)
- Location
- USA
- Provider
- Verifacti (Bilbabit S.L.)
- What for
- Registration of invoices with the Spanish Tax Agency (VeriFactu), only if the client company enables it: receives each invoice's data, including the recipient
- Location
- Spain (EU)
| Provider | What for | Location |
|---|---|---|
| Hostinger (VPS) | Hosting of the application and the database (VPS managed with Dokploy) | Spain (EU) |
| Meta Platforms Ireland Ltd. | Sending and receiving messages over WhatsApp Business | EU / USA |
| Google Ireland Ltd. | Sign-in and Google Calendar sync | EU / USA |
| Stripe Payments Europe, Ltd. | Charging booking deposits and managing each client business's connected account | Ireland (EU) / USA |
| Resend, Inc. | Sending the service's emails (invitations, password recovery, consents, notices) | USA |
| Groq, Inc. | Interpreting the messages the end customer writes to the WhatsApp assistant: it receives their text and, if it was the last thing they received, the last automated message sent to them (without their name) | USA |
| Verifacti (Bilbabit S.L.) | Registration of invoices with the Spanish Tax Agency (VeriFactu), only if the client company enables it: receives each invoice's data, including the recipient | Spain (EU) |
We also disclose it to public authorities when there is a legal obligation.
About Groq: the WhatsApp assistant needs a language model to understand messages written in the customer's own words, and today Groq provides it. It cannot be switched off separately: if the client business does not use the assistant, nothing is sent. For each message the assistant has to interpret, we send the end customer's text (up to 500 characters); if the last thing they received was an automated message, that message, cut to 500 characters and without their name —it may include the date, time, service and professional of their appointment—, and never one written by the client business's staff nor a reminder or notice sent as a WhatsApp template; the step the conversation is at, and whether or not they have an upcoming appointment. When a person is already handling the conversation, a message that may describe a symptom is still sent, solely to assess whether it is urgent, with the step the conversation is at and whether they have an upcoming appointment, without any earlier message. When the message is a question and the client business has active FAQs, a second call sends that same text and the questions of those FAQs (up to 25, without their answers) to choose which one answers it; the questions are written by the client business about its business and are not personal data. If the client business uses “Import” in its FAQs, the content it provides —its website, a text or a PDF, up to 12,000 characters— is sent to suggest drafts. Their phone number, record, histories and files are not sent, but since end customers write whatever they want, the text may contain health data, such as an ailment. Groq processes it in the USA as a sub-processor, under the European Commission's standard contractual clauses incorporated in its data processing addendum, and under its terms does not retain request content except for temporary logs of up to 30 days to troubleshoot incidents or investigate abuse.
8. International transfers
Some providers process data outside the European Economic Area. In those cases the transfer relies on the standard contractual clauses approved by the European Commission and, where applicable, on the EU–US Data Privacy Framework.
9. Your rights
You can exercise the rights of access, rectification, erasure, objection, restriction, portability and not to be subject to automated decisions by writing to contact@darcemi.com, proving your identity. We will respond within a maximum of one month.
If you believe we have not handled your request properly, you can lodge a complaint with the Spanish Data Protection Agency (aepd.es).
10. Security
We encrypt traffic with TLS, store passwords hashed with bcrypt, isolate each client business's data by client identifier in every query, apply role-based access control, limit sign-in attempts and log administrative actions.
No system is invulnerable. If a breach occurs that poses a high risk to your rights, we will notify you and report it to the AEPD within 72 hours of detecting it.
11. Minors
Darcemi is aimed at businesses. We do not create panel accounts for people under 18. If a client business records data of minors as end customers, it is that business that must obtain the consent of the holders of parental authority.
12. Cookies
We only use first-party cookies, technical or preference ones, that the website and the panel need in order to work. They are the following:
- Cookie
- NEXT_LOCALE
- What it is for
- Remembering the language you choose (Spanish or English).
- Type
- Technical
- Duration
- Until you close the browser
- Cookie
- darcemi_session
- What it is for
- Keeping you signed in to the panel, including the demo.
- Type
- Technical
- Duration
- 14 days, or until you sign out
- Cookie
- darcemi.demoFrom
- What it is for
- Remembering which solution you entered the demo from, for the banner that goes with it.
- Type
- Technical
- Duration
- 2 hours
- Cookie
- theme
- What it is for
- Remembering the light or dark theme you choose in the panel.
- Type
- Preference
- Duration
- 1 year
- Cookie
- sidebar_state
- What it is for
- Remembering whether the panel side menu is collapsed or expanded. It replaces the old sidebar cookie, which is deleted when you open the panel.
- Type
- Preference
- Duration
- 7 days
- Cookie
- sidebar_start
- What it is for
- Remembering how you want the side menu to open when you sign in: as you left it, expanded or collapsed.
- Type
- Preference
- Duration
- 1 year
- Cookie
- agenda_view
- What it is for
- Remembering which view the panel agenda opens in: day or week.
- Type
- Preference
- Duration
- 1 year
- Cookie
- text_size
- What it is for
- Remembering the text size you choose in the panel.
- Type
- Preference
- Duration
- 1 year
- Cookie
- corners
- What it is for
- Remembering the corner style you choose in the panel.
- Type
- Preference
- Duration
- 1 year
- Cookie
- density
- What it is for
- Remembering the density of tables and lists you choose in the panel.
- Type
- Preference
- Duration
- 1 year
- Cookie
- motion
- What it is for
- Remembering whether you asked to reduce the panel's animations.
- Type
- Preference
- Duration
- 1 year
- Cookie
- links
- What it is for
- Remembering whether you asked to underline the panel's links.
- Type
- Preference
- Duration
- 1 year
- Cookie
- darcemi_flash
- What it is for
- Showing the confirmation notice after you save a change in the panel.
- Type
- Technical
- Duration
- 1 minute
- Cookie
- login_email
- What it is for
- Remember the email of a failed sign-in attempt so you don't have to type it again.
- Type
- Technical
- Duration
- 1 minute
- Cookie
- darcemi_2fa
- What it is for
- Remembering, while you enter your two-step verification code, that your password was already correct.
- Type
- Technical
- Duration
- 5 minutes
- Cookie
- darcemi_totp_enroll
- What it is for
- Keeping the two-step verification key, encrypted, while you turn it on in your account, until you confirm it.
- Type
- Technical
- Duration
- 10 minutes
- Cookie
- booking_draft
- What it is for
- Keeping the details of an online booking that could not be sent, so you do not have to type them again.
- Type
- Technical
- Duration
- 10 minutes
- Cookie
- site_preview
- What it is for
- While you review the draft of a centre's website with its preview link, so that its online booking looks like that website and you can return to the draft.
- Type
- Technical
- Duration
- 12 hours
- Cookie
- g_nonce, g_pkce, gc_nonce, gc_pkce
- What it is for
- Protecting sign-in with Google and the connection to Google Calendar.
- Type
- Technical
- Duration
- 5 minutes
| Cookie | What it is for | Type | Duration |
|---|---|---|---|
| NEXT_LOCALE | Remembering the language you choose (Spanish or English). | Technical | Until you close the browser |
| darcemi_session | Keeping you signed in to the panel, including the demo. | Technical | 14 days, or until you sign out |
| darcemi.demoFrom | Remembering which solution you entered the demo from, for the banner that goes with it. | Technical | 2 hours |
| theme | Remembering the light or dark theme you choose in the panel. | Preference | 1 year |
| sidebar_state | Remembering whether the panel side menu is collapsed or expanded. It replaces the old sidebar cookie, which is deleted when you open the panel. | Preference | 7 days |
| sidebar_start | Remembering how you want the side menu to open when you sign in: as you left it, expanded or collapsed. | Preference | 1 year |
| agenda_view | Remembering which view the panel agenda opens in: day or week. | Preference | 1 year |
| text_size | Remembering the text size you choose in the panel. | Preference | 1 year |
| corners | Remembering the corner style you choose in the panel. | Preference | 1 year |
| density | Remembering the density of tables and lists you choose in the panel. | Preference | 1 year |
| motion | Remembering whether you asked to reduce the panel's animations. | Preference | 1 year |
| links | Remembering whether you asked to underline the panel's links. | Preference | 1 year |
| darcemi_flash | Showing the confirmation notice after you save a change in the panel. | Technical | 1 minute |
| login_email | Remember the email of a failed sign-in attempt so you don't have to type it again. | Technical | 1 minute |
| darcemi_2fa | Remembering, while you enter your two-step verification code, that your password was already correct. | Technical | 5 minutes |
| darcemi_totp_enroll | Keeping the two-step verification key, encrypted, while you turn it on in your account, until you confirm it. | Technical | 10 minutes |
| booking_draft | Keeping the details of an online booking that could not be sent, so you do not have to type them again. | Technical | 10 minutes |
| site_preview | While you review the draft of a centre's website with its preview link, so that its online booking looks like that website and you can return to the draft. | Technical | 12 hours |
| g_nonce, g_pkce, gc_nonce, gc_pkce | Protecting sign-in with Google and the connection to Google Calendar. | Technical | 5 minutes |
None of them is used to track you across other sites. We do not use analytics or advertising cookies today, neither our own nor third-party ones. If we ever did, we would ask for your consent before setting them and say so in this policy.
13. Changes to this policy
If we change this policy, we will publish the new version at this same address and update the date in the header. If the change is substantial, we will notify client businesses by email at least 30 days in advance.