← Back to cmrk.

Privacy policy

Version 2.4 · Effective from 10. 11. 2026 (“Stan” support chat in section 6.1, Google event fingerprint in section 5.5; previous versions 2.3 of 6. 11. 2026, 2.2 of 5. 11. 2026, 2.1 and 2.0 of 4. 11. 2026 and 1.0 of 21. 7. 2026)

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:

2. What data, for what purpose and on what legal basis (as controller)

DataPurposeLegal basisRetention period
Name, email, company name, password (only as a hash), role, language, and the Google account identifier if you sign in with GoogleCreating and managing the account, signing in, providing the servicePerformance 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 recordsPerformance 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 yourselfPerformance of a contract — Art. 6(1)(b)Until disconnected / turned off
IP address, time of access, technical logs, sign-in records (session), change auditSecurity, prevention of abuse, troubleshootingLegitimate interest — Art. 6(1)(f)Session 30 days; technical logs short-term (rotation); audit for the lifetime of the account
Content of communication with supportAnswering questions and requestsPerformance of a contract / legitimate interestFor 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)

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 permissionData we accessWhat we store
Sign in with Google
openid, 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 identification
openid, 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 — sync
https://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

We use data from Google exclusively for these features, which you can see in the app. Data from Google APIs is:

5.3 Where and how we store it

5.4 Who we share it with

5.5 How long we keep it, how to revoke access and how to delete it

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:

ProviderPurposeLocation / transfer outside the EU
Hetzner Online GmbH (Germany)Server and database hostingEU — 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 LLCSign in with Google and Google Calendar — only if you use themUSA — 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 messageAccording 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 botsGlobal 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 encryptedDepending 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.

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:

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.