Privacy policy
The Slovak version is legally binding; this English version is a translation. Slovak original: Ochrana osobných údajov
This policy describes how the cmrk. service processes personal data under Regulation (EU) 2016/679 (GDPR) and Slovak Act No. 18/2018 Coll. on the Protection of Personal Data.
1. Who processes your data
MACET, s.r.o., Nitrianska 32/189, 949 11 Nitra, company ID (IČO) 35 953 781, registered in the Commercial Register of the Nitra District Court, Section Sro, Insert No. 17071/N, email info@cmrk.eu (“we”). We have not appointed a data protection officer; please contact us at the email address above with any questions.
In the cmrk. service we act in two roles:
- Controller — for data about you as a user of the service (account, sign-in, subscription billing, support, security).
- Processor — for data that you enter into cmrk or that cmrk. loads from your email mailbox (contacts, companies, deals, tasks, emails, invoices to your clients). The controller of this data is your company; we process it only on your instructions under the data processing agreement, which forms part of the terms and conditions.
2. What data, for what purpose and on what legal basis (as controller)
| Data | Purpose | Legal basis | Retention period |
|---|---|---|---|
| Name, email, company name, password (only as a hash), role, language, and the Google account identifier if you sign in with Google | Creating and managing the account, signing in, providing the service | Performance of a contract — Art. 6(1)(b) | For the lifetime of the account. When the subscription ends, the account is not deleted automatically (you can return and export your data); on your request we will delete it within 30 days. Copies in backups — see section 7. |
| Company billing details, plan, subscription status, payments (card details are processed only by Stripe; we do not see them) | Billing and subscription records | Performance of a contract; legal obligation (accounting) — Art. 6(1)(b) and (c) | Accounting documents for 10 years under the Accounting Act |
| Telegram chat ID and notification settings; push notification subscription (address of the browser's push delivery service) | Delivering notifications that you turn on yourself | Performance of a contract — Art. 6(1)(b) | Until disconnected / turned off |
| IP address, time of access, technical logs, sign-in records (session), change audit | Security, prevention of abuse, troubleshooting | Legitimate interest — Art. 6(1)(f) | Session 30 days; technical logs short-term (rotation); audit for the lifetime of the account |
| Content of communication with support | Answering questions and requests | Performance of a contract / legitimate interest | For the lifetime of the account |
Providing data for registration is a contractual requirement — without it we cannot provide the service. We do not use automated decision-making or profiling with legal effects.
3. Data we process on your behalf (as processor)
- CRM content: contacts (name, email, phone, position), companies (including company ID (IČO), tax ID (DIČ), address), deals, tasks, notes, comments, invoices, custom fields, web form submissions.
- Connected email mailboxes: sender, subject, content and identifier of incoming emails. We read them via IMAP in read-only mode — we do not change or delete anything in your mailbox. We send only when you reply or write an email yourself, or when you yourself turn on an automatic reply or an out-of-office reply. Mailbox passwords are encrypted (AES-256-GCM). cmrk keeps the latest 100 emails per mailbox (configurable); emails you have replied to or that are linked to a contact are kept.
- Company data enrichment: if you enter a company ID (IČO), cmrk. requests public data from the RPO register (SK) or ARES (CZ).
4. Artificial intelligence
Email summaries, priority sorting, reply suggestions, contact and deal summaries, next-step suggestions and the business card scanner are powered by the Claude model from Anthropic. To process a specific request, only the necessary text (e.g. sender, subject and the first 6 000 characters of an email) or the image of the business card is sent to the provider. Under Anthropic's commercial terms, this content is not used to train models, and inputs and outputs are generally deleted within 30 days. AI outputs may be inaccurate — always check them before sending or using them.
5. Data from your Google Account (Google API)
This section applies only if you sign in with Google or connect Google Calendar in cmrk. Otherwise cmrk. does not access your Google Account. We request no Google permissions (scopes) other than those in the table — in particular no Gmail, Google Drive or Google Contacts scopes. Email mailboxes (including Gmail) are connected via IMAP with your own password; that is not a Google API.
5.1 What permissions we request and what data we access
| Feature and permission | Data we access | What we store |
|---|---|---|
Sign in with Googleopenid, email, profile | Google account ID, email address and whether it is verified, name (Google also returns a profile photo, which we do not use). | The Google account ID and email with your user; the name only when a new account is created. We do not store the profile photo or the sign-in access token. |
Google Calendar — account identificationopenid, email | The email address of the Google account you connect. | This address, so that you can see in Settings which account is connected. |
Google Calendar — synchttps://www.googleapis.com/auth/calendar.events | Events in your primary calendar. The Google API returns the full event (e.g. title, time, description, location, attendees). We do not read other calendars. | Only the event title and start time, the event ID, its revision tag (etag) and whether it was cancelled. We do not store or further process descriptions, locations, attendee lists or attachments. |
5.2 How we use data from Google
- Sign-in: the email and identifier are used only to sign you in to your account (or, after you accept the terms, to create a new one) and to link the Google account to your user.
- Reading the calendar: on first connection we read events from 7 days back to 90 days ahead, then only changes every few minutes. A new event from Google appears in cmrk as a task with the same title and time. A change of title or time in Google is carried over to that task; cancelling the event in Google deletes the task in cmrk.
- Writing to the calendar: when you create or edit a task with a due date in cmrk, we create or update an event in your primary calendar with its title, time (30 minutes, or 60 minutes for a meeting) and description (the task note and a link to cmrk). When you delete such a task, we also delete its event.
- cmrk. never modifies or deletes events you created directly in Google. It edits and deletes only events it created itself from your tasks.
- You can pause the sync at any time (Settings → Integrations → Google Calendar → “Sync enabled” (in the Slovak interface “Sync zapnutý”)) or disconnect completely (section 5.5).
We use data from Google exclusively for these features, which you can see in the app. Data from Google APIs is:
- not sold and not transferred to data brokers, advertising platforms or information resellers,
- not used for advertising (including personalised, retargeting or interest-based advertising) or for profiling,
- not used to develop, improve or train artificial intelligence or machine learning models — neither ours nor anyone else's,
- not used to determine creditworthiness or for lending purposes.
5.3 Where and how we store it
- All data is in our database on a server in Germany (Hetzner Online GmbH, EU). Communication with Google and with you is encrypted (HTTPS/TLS).
- We store the Google Calendar refresh token encrypted (AES-256-GCM); the key is kept separately from the database. A short-lived access token is obtained for each sync and is not stored.
- Events imported from Google are ordinary tasks of your company in cmrk: they are visible to you and to members of your company account who have access to the relevant project — just like other tasks.
- Staff of MACET, s.r.o. do not read your Google data, except where you explicitly ask us to (e.g. for support), where it is necessary for security reasons (investigating a bug or abuse), or where required by law.
5.4 Who we share it with
- Hetzner Online GmbH (Germany) — operates the server and database as our processor; the data does not leave the EU.
- Google LLC — data that cmrk. writes to your calendar is sent back to your Google account.
- Anthropic (Anthropic Ireland, Limited; processing by Anthropic, PBC in the USA under the EU Standard Contractual Clauses — sections 4 and 6) — only when you trigger it yourself: if you attach a task imported from Google to a contact or deal and then run an AI feature on that contact or deal (e.g. a summary or a next-step suggestion), the title and date of the task may be part of the input. It is used only to produce the output for you; Anthropic does not use this content to train models. We do not send any Google data to Anthropic automatically.
- Otherwise we do not share Google data with anyone — except where required by law, and in the event of a sale or merger of the company only with your prior explicit consent.
5.5 How long we keep it, how to revoke access and how to delete it
- Disconnecting: in cmrk open Settings → Integrations → Google Calendar and click “Disconnect” (in the Slovak interface “Odpojiť”). We immediately ask Google to revoke the permission and delete from our database the refresh token, the address of the connected account, the sync token and all links between events and tasks. This stops the sync. For tasks created from Google events, only a one-way fingerprint of the event identifier remains — the event or its content cannot be derived from it; it is used solely to prevent duplicate tasks after you reconnect and is deleted together with the task.
- You can also revoke access directly in Google at myaccount.google.com/permissions; cmrk. then loses access and shows you in the app that the connection is no longer valid.
- Tasks already created in cmrk from events remain as your ordinary records after disconnecting until you delete them (individually in the app) or until we delete your account. If you want all data obtained from Google deleted, email info@cmrk.eu — we will delete it within 30 days.
- Sign in with Google: we keep the Google account ID for the lifetime of your account; it is deleted together with the account.
- Deleting your account (on your request, within 30 days) deletes all tokens, links and tasks. Copies may remain for a limited time in encrypted security backups used only for disaster recovery (section 7).
5.6 Compliance with Google's policies (Limited Use)
cmrk.'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. For Google Calendar data we also comply with the Google Workspace API User Data and Developer Policy.
6. Recipients and processors
We do not sell personal data. We use only the following providers:
| Provider | Purpose | Location / transfer outside the EU |
|---|---|---|
| Hetzner Online GmbH (Germany) | Server and database hosting | EU — Nuremberg, Germany |
| Backblaze, Inc. (USA) | Encrypted backups (we encrypt the content before sending it) | Data centre in the EU (eu-central); EU-US Data Privacy Framework |
| Anthropic Ireland, Limited (Ireland) — contractual partner for the EEA; processing by Anthropic, PBC (USA) | AI processing as a processor (see section 4) | USA — EU Standard Contractual Clauses (Modules 2 and 3) under Anthropic's data processing agreement. Anthropic is not a participant in the EU-US Data Privacy Framework (checked in the dataprivacyframework.gov list on 4. 11. 2026). |
| Stripe Payments Europe, Limited (Ireland, Dublin) — contractual partner of MACET, s.r.o.; payment services may also be provided by Stripe Technology Europe, Limited (Ireland, an electronic money institution supervised by the Central Bank of Ireland) | Card payments for the subscription. For verification, fraud prevention and compliance with financial regulations, Stripe is an independent controller under its own policies. | EU; transfers to the USA (Stripe, LLC) on the basis of the EU-US Data Privacy Framework (Stripe, LLC is an active participant) and standard contractual clauses |
| Google LLC | Sign in with Google and Google Calendar — only if you use them | USA — EU-US Data Privacy Framework |
| Callania (callania.com) | “Stan” support chat on cmrk.eu and in the app (the “Help” button) — only if you open the chat and write a message | According to the chat operator's terms (callania.com) |
| Telegram Messenger Inc. | Notifications via Telegram — only if you connect it (summaries of new emails, deal won) | Outside the EU (Telegram group, including countries without an adequacy decision); standard contractual clauses under Telegram's policies |
| Cloudflare, Inc. | Turnstile — protecting registration and forms against bots | Global network; EU-US Data Privacy Framework |
| System email provider (SMTP) | Sending system emails (invitations, password reset, invoices) | EU |
| Browser push delivery services (Google, Apple, Mozilla) | Delivering push notifications — only if you turn them on; the content is encrypted | Depending on the browser, possibly the USA |
We read emails from your mailbox and send them via your email provider's SMTP — that provider is your supplier, not our processor.
6.1 “Stan” support chat
The cmrk.eu website (bubble in the bottom right) and the app (the “Help” button) offer a support chat. It is operated by Callania (callania.com); the chat is loaded from admin.callania.com.
- What is transferred: the text of the messages you type into the chat, and your email address if you enter it in the chat yourself. When the chat loads, your browser sends technical data as with any website (IP address, browser type).
- What for: answering your question about cmrk. and, if needed, creating a request (ticket) for our support team.
- What is NOT transferred: no data from your CRM — contacts, companies, deals, emails or account details are never sent to the chat. The chat does not know who you are unless you tell it.
- Chat replies are prepared by an automated assistant solely from the published description of cmrk. features (chatbot-znalosti.md).
If you prefer not to use the chat, email us at info@cmrk.eu.
7. Storage and security
The database runs on a server in Germany (Hetzner). Communication is encrypted (HTTPS). Mailbox passwords and Google tokens are encrypted with AES-256-GCM, and user passwords are stored as a hash. Companies' data is kept separate in the application. Security backups of the database are encrypted and are used only for disaster recovery, never for any other purpose:
- daily backups on the server (Germany) — we keep the latest 14;
- copies in Backblaze B2 (data centre in the EU) — automatically deleted approximately 91 days after creation; for the first 30 days they are protected against deletion, even by us (ransomware protection);
- one-off snapshots before an application update or an intervention in the data — we keep them on the server without a fixed period as a safeguard in case a change needs to be reversed; their copies in B2 expire as above.
Deleted data may therefore remain in backups for some time. We do not remove it from backups individually, nobody works with it, and if a backup were ever restored, we would delete the deleted data again before resuming operation.
Support access. To resolve a support request, an authorised member of the operator’s staff may temporarily access your account; every such access is logged. Access lasts at most 60 minutes, a notice is shown in the application throughout, and it is not possible to change the password or e-mail, payments or the subscription, export data (GDPR), delete the account or organisation, or connect Google, Telegram or mailboxes. Changes made during access are marked “(cmrk. support)” in the history.
8. Your rights
You have the right of access to your data, to its rectification, erasure, restriction of processing, portability, and the right to object to processing based on legitimate interest. Send your request to info@cmrk.eu; we will handle it without undue delay and at the latest within one month. You can export your company's data in the app at any time.
If you are a contact of one of our customers (e.g. you sent them an email), the controller of your data is that customer — please contact them first; we will forward any request we receive to them.
You have the right to lodge a complaint (a petition to initiate proceedings) with the Office for Personal Data Protection of the Slovak Republic (Úrad na ochranu osobných údajov Slovenskej republiky), Galvaniho 7/B, 821 04 Bratislava, dataprotection.gov.sk.
9. Cookies
We use only strictly necessary cookies and browser storage — details on the Cookies page.
10. Changes
We may update this policy. In the event of a material change we will notify you by email or in the app and change the version and effective date in the header.