Back to Home

Privacy Policy for Sincra.cloud

Last Updated: November 12, 2026

At Sincra.cloud, we are committed to protecting the privacy and personal data of our customers (Tenants) and their end-users. This Privacy Policy describes how we collect, use, store, and share personal data in accordance with the General Data Protection Regulation (GDPR), the Spanish Organic Law on Data Protection and Guarantee of Digital Rights (LOPDGDD), and California Consumer Privacy Act (CCPA/CPRA).


1. Data Controller Identification

  • Entity: Ernesto Alonso Céspedes Cáceres (The Operator)
  • NIF: Z1362749G
  • Address: Calle Horno 4 2B, CP 30003, Murcia, Spain
  • Email: support@sincra.cloud

2. Categories of Personal Data Collected

Sincra.cloud collects and processes different types of personal data depending on how you interact with our Platform:

A. For Tenants (Customers of Sincra.cloud):

  • Account Information: Email address, company name and website. Your password is handled by Firebase Authentication, which stores it in hashed form; Sincra never stores it. If you sign up with Google, we also receive your name and profile picture from your Google account.
  • Billing Data: Your plan, the state of your subscription and the identifiers Dodo Payments gives us for it. Your payment and invoicing details are collected by Dodo Payments, not by Sincra. Note: Sincra does not collect or store debit/credit card details.
  • Configuration Metadata: The settings you choose in the dashboard, such as the email address for notifications, your booking link (for example, Cal.com) and the appearance of the widget.
  • Signup source: when you create your account, the site you came from and the campaign tags (utm_) in the link you followed, so that we can tell which channels bring new customers. We do not store ad click identifiers.

B. For End-Users (Visitors interacting with the Sincra Web Widget on Tenant sites):

  • Conversation Logs: Chat history and text inputs. Qualification details the visitor chooses to share in the conversation, such as what they need, their timeline or their budget.
  • Contact Information: Name, email address, and phone numbers captured dynamically during the conversation to log leads.
  • System Telemetry: IP address, Browser User-Agent, Session ID, Timezone, and Locale (used for secure dual rate limiting and regional server-side rendering).

3. Purposes of Data Processing and Legal Basis

We process your personal data under the following legal bases:

| Category of Processing | Purpose of Processing | Legal Basis (GDPR) | | ------ | ------ | ------ | | Account Management | Provisioning the SaaS, enabling access to the Dashboard, and managing user profiles. | Contractual Necessity (Art. 6.1.b GDPR) | | Account setup emails | A few emails to help you finish setting up your assistant, which you can stop at any time. | Legitimate Interest (Art. 6.1.f GDPR) | | Signup source | Knowing which channels bring new customers. | Legitimate Interest (Art. 6.1.f GDPR) | | Transaction Processing | Executing subscription checkouts and billing via our reseller, Dodo Payments. | Contractual Necessity (Art. 6.1.b GDPR) | | Cognitive Inference (AI Chat) | Answering end-user queries, performing semantic searches (RAG), and qualifying leads. | Consent / Legitimate Interest of Tenant (Art. 6.1.a & f GDPR) | | System Security | Executing Dual Rate Limiting (IP + Fingerprint) and Cloudflare Turnstile token validation to block malicious bots and DDoS attacks. | Legitimate Interest (Art. 6.1.f GDPR) | | Compliance & Logs | Retaining conversations and operation logs to verify transactions and system health. | Performance of a contract (Art. 6.1.b GDPR) |


4. Sub-processors and Data Sharing

To run the service, Sincra.cloud shares personal data with the providers below. Where they process data on our behalf they act as our sub-processors under Article 28 of the GDPR:

  1. Google Cloud (Cloud Run, Firebase Hosting): runs the application in the europe-southwest1 (Madrid) region. Its task queues (Cloud Tasks) run in us-central1 (United States).
  2. Google Cloud (Firestore, Firebase Authentication, Cloud Functions): stores accounts, knowledge sources, conversations and leads in the us-central1 (United States) region.
  3. Google Cloud (Vertex AI): generates the assistant's replies through Google's global endpoint, and the embeddings of your content in europe-southwest1.
  4. Upstash: holds the search index of your content (Upstash Vector, in the EU and in the United States) and the rate limiting and caching layer (Upstash Redis). Each account's content is tagged with its account identifier and every search is filtered by it.
  5. Cloudflare (Turnstile): protects the chat from automated abuse.
  6. Resend: sends account emails and the lead notification emails.
  7. Jina AI (Reader): reads the public pages of the website you add as knowledge. It receives the address of the page, not visitor data.

Dodo Payments (dodopayments.com) is not our sub-processor. It is our online reseller and Merchant of Record: it processes payment card data, calculates taxes and handles transaction-related fraud detection as the seller of your subscription. When you start a checkout, we send Dodo Payments your email address, your country and your account identifier, so that it can calculate the applicable taxes and activate your subscription.

Cal.com is involved only if you connect a Cal.com account of your own, under your own agreement with that provider.

Your webhook address receives data only if you connect one in your dashboard (paid plans). Each time a visitor leaves their contact details, Sincra sends that lead, on your instructions, to the address you choose. You choose that destination and are responsible for it.

Where personal data is processed outside the European Economic Area, the transfer relies on an adequacy decision (including the EU-US Data Privacy Framework where the provider is certified) or on the European Commission's Standard Contractual Clauses included in the provider's data processing terms.


5. Security Measures and Tenant Isolation

Sincra.cloud is designed under a Zero-Trust security architecture:

  • Allowed Domains: On third-party websites, the widget only appears and answers on the domains the Tenant authorizes in the dashboard.
  • Tenant Isolation: Every entry in the search index is tagged with the Tenant ID and every search is filtered by it. Access to account data is validated against that tenant identifier on every read and write operation.
  • Input Validation: All incoming payloads are validated against Zod schemas at the edge, and Cloudflare Turnstile tokens are collected and verified on widget traffic.
  • Encryption: Data is encrypted in transit using TLS and at rest with the default encryption of Google Cloud and Firestore.

6. Data retention and deletion

Data retention. We keep your account data, knowledge sources, conversations and leads for as long as your account is active. You can delete individual leads and conversations from your dashboard at any time. When you delete your account, we remove your data from our systems within 30 days. Data you delete may remain in our database backups, which are used only for disaster recovery and expire automatically within 30 days.

Visitor data. For the conversations and contact details that visitors share through your widget, you are the controller and Sincra processes them on your behalf. If a visitor asks you to delete their data, you can delete their lead and conversation from your dashboard. When a visitor shares their contact details, the lead also records the address of the page where the conversation started, without query parameters.

Browser storage in the widget. The chat widget stores no identifier in the visitor's browser until the visitor sends a message. From then on, it keeps a single conversation identifier in the browser's local storage (or, if local storage is blocked, in session storage, which is cleared when the tab is closed), so the conversation continues across pages and tabs. It expires 24 hours after the last message. Separately, when the widget shows its welcome message next to the chat button, it stores a single flag with no identifier in session storage so that the message appears only once per browsing session; the flag is cleared when the tab is closed. When the visitor opens or closes the chat window, it also stores in session storage a flag with no identifier that records whether the window is open, so that a conversation under way opens again on the next page; it is cleared when the tab is closed. Sincra's widget code sets no cookies. To protect the chat from automated abuse, the widget loads Cloudflare Turnstile the first time the visitor interacts with the page (scrolls, moves the pointer, taps or uses the keyboard) or when the chat opens (also when it opens again on its own on another page in the same tab), whichever comes first; Cloudflare may process technical data about the browser for that check.

Website analytics. On our own website, sincra.cloud, we use Cloudflare Web Analytics to count visits and measure page speed. According to Cloudflare, it uses no cookies or browser storage and does not fingerprint visitors. It receives the page address, the referring page and technical data about the browser and connection. It does not run inside the chat widget on our customers' websites.

Cookies on our website. On sincra.cloud we set two cookies, both strictly necessary. One remembers the language of the pages you visit (NEXT_LOCALE) and is deleted when you close your browser. The other (__session) is set when you log in, keeps you signed in to your dashboard for up to 14 days and is removed when you log out. We set no advertising or tracking cookies. Your browser also keeps a few settings on your device, outside cookies: your conversation with the chat on our website, so that it continues if you reload the page, and, in your dashboard, the light or dark theme and whether the Get started list is collapsed. You can delete them by clearing this site's data in your browser.


7. User Rights (GDPR / CCPA)

Under global privacy regulations, you have the right to access, rectify, restrict, object to, export (portability), or erase your personal data.

To exercise any of these rights, please contact our data protection team at: support@sincra.cloud. We confirm the date we received your request and answer within one month. If the request is complex, we may extend that by two more months and tell you why within the first month. Under the CCPA, we confirm receipt within 10 business days and never take more than 90 days in total. If we have reasonable doubts about your identity, we may ask you for the information needed to confirm it. If you believe your data has been handled unlawfully, you have the right to lodge a complaint with the Spanish Data Protection Agency (AEPD) or your local supervisory authority.


8. Changes to this Privacy Policy

We may update this Privacy Policy to reflect legal or technical changes. We will publish the new version at this address and update the date at the top of the page.