跳到主要内容
Mercovio

Privacy Policy

版本
2026-11-20
生效日期
2026-11-20

本文件以英文撰写。界面翻译仅为方便阅读而提供。

1. Who is responsible

DrillityGroup OÜ, registry code 17467185, Vesivärava tn 50-301, Kesklinna linnaosa, 10152 Tallinn, Harju maakond, Estonia, provides Mercovio ("Mercovio", "we"). Mercovio is established in the European Union.

Mercovio has not appointed a data protection officer. Write to privacy@mercovio.ai with any question about personal data.

2. Two roles

  • Content in a workspace. Messages, files, quotes and other content that customers and their guests add to channels are processed on behalf of the company that owns the channel. For that content the customer is the controller and Mercovio is the processor under the Data Processing Agreement. When a guest from another company takes part in a channel, the company that owns the channel is the controller of the channel's content; the guest and the guest's own company decide what they share there.
  • Mercovio's own processing. For accounts, sign-in, billing, service emails, security and abuse prevention, Mercovio is the controller and this policy applies.

3. What we process

DataDetails
AccountName, work email, company name, chosen language and time zone, password stored only as a scrypt hash, whether the email address is verified, and two-step sign-in settings if you turn them on.
Sign-inAn HTTP-only session cookie. A session ends after 14 days without use and at the latest 30 days after sign-in. A second HTTP-only cookie remembers your browser for up to 400 days so that Mercovio can tell you about a sign-in from a new device; a device not seen for a year is forgotten at your next sign-in from a new device. Sign-in and registration attempts are rate limited by network address, with counters kept only in memory for up to 24 hours.
Sign-in history and audit logFor your company's audit log and your sign-in history, Mercovio records the browser family, the operating system and a coarse network (an IPv4 /24 or IPv6 /48 range, never the full address), together with what was done and when. These records are encrypted.
Channel contentMessages, translations, files and their revisions, document analyses, quotes, approvals and withdrawals. Message text and original files are encrypted at rest with keys derived for each company.
Readable metadataNames, email addresses, file names, file sizes and dates are stored in readable database fields.
InvitationsThe invitee's name and email address, the inviting person, an optional personal note (encrypted) and the email delivery status.
AI requestsWhen someone asks the assistant, or a translation, revision comparison, quote check or brief is produced, the relevant channel context is sent to Grunden AI AB in Sweden: messages, file excerpts, quote details, and search results or page text the assistant retrieved. Mercovio records token counts, cost and timing for billing.
Assistant searchesTo answer a question the assistant can look up public sources on its own: the GLEIF company register, Crossref literature metadata, or one public HTTPS page. Only the query the model writes leaves Mercovio, with email addresses, phone numbers and the channel's file names and participant names removed and at most 200 characters, or the page address. Each lookup (tool, query or address, time, outcome) is recorded, encrypted, and the company's administrators can see it in Settings.
BillingStripe customer and subscription identifiers, plan, seat counts, AI usage and charges, and invoices. The business name, billing address and VAT number a company gives at checkout, and its payment details, are entered on Stripe's own pages and held by Stripe; card numbers are never sent to Mercovio.
NotificationsEmail notification settings, quiet hours, time zone and the time of last activity, used to decide when to send a digest. If you turn on browser notifications or connect a chat app, the browser's push address or the chat app's webhook address, both encrypted.
Messages to MercovioWhat you write to Mercovio's email addresses or send with the feedback button, including any screenshot you attach.
Browser storageLanguage, theme, layout and notification choices, and unsent message drafts (kept for up to 30 days and cleared when you sign out), are kept in the browser's own storage. The browser also caches Mercovio's program files. Mercovio uses no advertising or analytics cookies and loads no third-party scripts.

4. Why and on what legal basis

The legal bases refer to Article 6(1) of the General Data Protection Regulation (GDPR).

  • To provide the Service and manage accounts. For people who accept our Terms of Service or Terms of use for invited users themselves, performance of that contract (point b). For other users of a customer's workspace, our and the customer's legitimate interest in providing the workspace the customer has ordered (point f).
  • To keep the Service secure, prevent abuse and keep evidence of quote decisions, legal acceptances and the company audit log: legitimate interests (point f).
  • To bill and keep accounting records: performance of the contract (point b) and our legal obligation under the Estonian Accounting Act (point c).
  • To send service emails: invitations, verification links, password resets, security notices and receipts are part of the Service (point b or f). Activity notifications and digests are sent in our legitimate interest in keeping people informed (point f) and can be switched off in Settings.
  • To understand how companies use Mercovio and offer a suitable package, for example when a company nears the limit of its package, we look at counts and usage, never at content: legitimate interests (point f).
  • To establish, exercise or defend legal claims: legitimate interests (point f).

Where we rely on legitimate interests, you can object as described in section 8.

5. Who receives data

  • Subprocessors. Mercovio uses the providers listed on the subprocessors page: hosting and backups at Hetzner, AI inference at Grunden, email delivery through Resend, mailboxes at Namecheap and payments through Stripe.
  • Public sources. The assistant's lookups go to the public sources described in section 3.
  • Other people in a channel. Content is shared with the other people in a channel, including people at other companies. That is the purpose of the Service.
  • Services you or your company choose. Single sign-on with Microsoft or Google, directory provisioning (SCIM), browser push services, a chat app you connect (WeCom, Feishu, Lark or DingTalk) and webhooks your company sets up receive what is needed for that service, as described on the subprocessors page.
  • Authorities. We disclose data to authorities only when the law requires it.
  • A successor. If the Service is transferred to another company, data goes with it under the same commitments.

6. Transfers outside the EU/EEA

Mercovio's servers are in Helsinki, Finland, its backups in Falkenstein, Germany, and AI requests are processed by Grunden in Sweden. Some providers are based outside the EU/EEA or may process data there: Resend, Namecheap and Crossref are based in the United States, GLEIF is based in Switzerland, and Stripe may process data in the United States. The push service of your browser's maker may be outside the EU/EEA; it carries browser notifications encrypted for your browser. A chat app you connect may be operated outside the EU/EEA, for example in China.

Where a provider outside the EU/EEA is not covered by an adequacy decision of the European Commission, Mercovio relies on the Commission's standard contractual clauses or another safeguard under Chapter V GDPR. A transfer to a service you choose for yourself, such as a chat app, takes place because you asked for it. You can ask privacy@mercovio.ai for information about the safeguards.

7. How long we keep data

  • Accounts: while the account exists. When you delete your account, your name, email address, password, sessions, two-step sign-in data, devices, push subscriptions and drafts are removed at once. The messages and files you added stay in the channel owner's records, shown as written by a former member. Quote approvals and similar records keep the name you signed with, because the other company relies on them.
  • Channel content: until the company that owns the channel deletes it or its workspace. When a customer's agreement ends in another way, its content is deleted from the live system within 30 days.
  • Backups: encrypted backups made automatically every day are kept for 14 days on the server, backups made before a release for 14 days (at most the five newest), and the off-site snapshots in the Storage Box for 35 days. Deleted data is therefore gone from all backups within 35 days.
  • Audit log and sign-in history: 24 months, then deleted. A company's audit log is deleted with the company.
  • Sessions and devices: a session ends after 14 days without use and at the latest after 30 days; a record that it ended is kept for 31 days. The device cookie lasts up to 400 days.
  • Links: invitation links expire unused after at most 14 days. Email verification and password reset links expire after at most 72 hours and are deleted seven days after they expire.
  • Assistant lookups: records of the assistant's lookups are deleted after 90 days, and with the company.
  • Error reports: reports of errors in the browser are kept for 30 days and contain no message text, address or identifier. Server error logs record the request method, a redacted path and the error, and are kept in rotating files of limited size that are overwritten as new entries arrive.
  • Email: the content of an outgoing email is encrypted while it waits and removed once it is sent; the delivery record is kept for 14 days. Delivery records of chat app notifications are kept for 14 days and of webhooks for 30 days.
  • Push subscriptions: until the browser stops accepting notifications, or 30 days after the session ended.
  • Billing and accounting records: seven years, as required by the Estonian Accounting Act (Raamatupidamise seadus).
  • Records of accepted terms: while the agreement lasts and afterwards for as long as claims under it can be made.
  • Messages to Mercovio: as long as needed to handle them. You can ask us to delete them.
  • AI provider: Grunden AI AB stores AI prompts and replies for history and debugging according to its privacy policy, which states that content is not used to train models, that the history is kept until it is deleted and that request logs are kept for 30 days. Deleting an account or a workspace in Mercovio does not delete these copies.

8. Your rights

You can ask for access to, correction or deletion of your personal data, restriction of processing and data portability, and you can object to processing based on legitimate interests. You can export your own data and delete your account under Account in Mercovio, or write to privacy@mercovio.ai. We answer within one month. For content in a company's workspace, we forward your request to that company, which decides as controller.

You can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee) or to the data protection authority where you live or work.

9. Security

See the security page for the measures in place.

10. AI and automated decisions

Mercovio does not make decisions with legal or similarly significant effects by automated means. The assistant helps people; people decide and approve.

11. Changes

Each version of this policy has a version number and an effective date, and the current version is published at mercovio.ai/privacy. We inform account holders of material changes by email or in the Service before they take effect.

This policy is written in English. If it is translated, the English version prevails.

条款使用条款数据处理协议次级处理方安全数据与联系方式