Privacy policy
Last updated
This text was drafted from how the product actually handles data, but it has not been reviewed by a lawyer or approved yet. Placeholders in [square brackets] still have to be filled in. It is not legal advice.
Effective date: 16 November 2026
This policy explains what personal data Nearlysent (the “Service”) processes, why, and what your rights are. We wrote it in plain language. If anything is unclear, contact us at info@lunevo.be.
1. Who we are
The Service is operated by Lunevo, Belgium, enterprise number BE 1036.645.433 (“we”, “us”).
We have two roles under the EU General Data Protection Regulation (GDPR):
- Controller for the data of people who use the Service: your account, sessions, the workspaces you create and how you use the Service, and the data of visitors to this website and of people who contact us.
- Processor for the content that customers put into the Service: the email in connected mailboxes, knowledge documents, drafts and replies. The customer (the company that owns the workspace) is the controller of that data and decides what goes in. We process it only to provide the Service, on the customer’s instructions, as set out in the terms and the data processing terms in them.
If you are a person who emailed one of our customers and want to exercise your rights, please contact that company first. We will help them answer you.
2. What we process and why
| Data | Why | Legal basis |
|---|---|---|
| Account: name, email address, password (stored only as a one-way hash), language, whether your email address is verified | To create and secure your account and send you service emails | Contract |
| Sessions: a session token (stored as a hash), IP address, browser user agent, start and expiry time | To keep you logged in, let you see and end sessions, and detect abuse | Contract; legitimate interest (security) |
| Workspaces and members: workspace name, members and their roles, invites (email address and role) | To let teams work together | Contract |
| Mailbox connection: email address, server names and ports, user name, password (encrypted); for a mailbox connected with Sign in with Microsoft instead the sign-in tokens Microsoft issues (encrypted) | To read and send mail on the customer’s behalf | Contract (as processor) |
| Email content: imported emails (senders, recipients, subject, text, cleaned HTML, dates, attachment names), threads, triage results, drafts, sent replies, edits and ratings | To show the inbox, write drafts and send approved replies | Contract (as processor) |
| Knowledge: uploaded files and their text, pasted text, FAQ entries, learned past replies (with email addresses, phone numbers, IBANs and postcodes replaced) | To answer customers’ questions from the customer’s own information | Contract (as processor) |
| Claude connector (only if a user connects it): the app that was approved (its name and address), the workspace, the user, when it was connected and last used, access tokens (stored only as a one-way hash), and a log line per call with ids and counts but no content | To let the user’s own Claude account read threads and knowledge and save drafts in the chosen workspace, and to let the user see and revoke the connection | Contract (as processor) |
| AI settings and usage: the AI provider and models chosen, the API key (encrypted), token counts and estimated costs per call | To call the customer’s AI provider and show usage and costs | Contract (as processor) |
| Audit log: which user did what in a workspace and when (for example “mailbox created”), without email content | Accountability and security | Legitimate interest |
| Rate-limit counters: short-lived counters keyed by IP address or email address | To prevent abuse of sign-up, log-in and forms | Legitimate interest (security) |
| Contact form: name, email address, company and message | To answer your request | Legitimate interest; pre-contract steps |
| Error reports: technical details about a crash (error type, code location, browser and server version), with request bodies, cookies, headers with credentials, keys and email content removed before sending | To find and fix bugs | Legitimate interest |
We do not sell personal data, do not use it for advertising, and do not use customers’ email or knowledge to train AI models.
3. AI providers chosen by the customer
The Service writes drafts with an AI model from the provider the customer chose (for example Anthropic, OpenAI or another OpenAI-compatible service), using the customer’s own API key and account with that provider. For each AI call the provider receives the email thread concerned, the matching passages from the customer’s knowledge and the customer’s AI settings, and returns the result.
The customer chooses and contracts with that provider directly, and that provider’s terms and privacy policy apply to this data. We do not send data to an AI provider the customer did not choose. The search index of the knowledge is computed on our own server and is not sent to an AI provider.
Claude connector. A user can also choose to connect the Service to their own Claude account (claude.ai, Claude Desktop or Claude Code) as a custom connector. After the user approves this for one workspace, Claude requests email threads, knowledge passages and drafts of that workspace through the connector and can save reply drafts; it cannot send email. What Claude requests is sent to Anthropic under the user’s own Claude account and Anthropic’s terms and privacy policy, not under a contract of ours; Anthropic is then a recipient the user chose, like the AI provider above. The user or a workspace admin can revoke the connection at any time in the Service. Workspace admins see every member’s Claude connection in the workspace settings and can revoke it; a workspace that does not want members to use Claude should tell them so and revoke connections it does not allow.
4. Other recipients (sub-processors)
| Recipient | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Servers and database that run the Service | Finland (EU) |
| Hetzner Online GmbH | Encrypted backups | Germany (EU) |
| Resend (Plus Five Five, Inc.) | Sending verification, password reset and invite emails, and contact form messages | Ireland (EU region); US company |
| Functional Software, Inc. (Sentry), when enabled | Scrubbed error reports (see above) | EU data region; US company |
| An uptime monitoring service, when enabled | Checks that the Service is reachable; receives no personal data | EU or US |
Your own mail provider receives the replies you send, as with any email. Where a recipient is outside the European Economic Area, we rely on the EU-US Data Privacy Framework where the provider is certified, and otherwise on the European Commission’s standard contractual clauses.
5. Cookies and tracking
The app uses two strictly necessary cookies: a session cookie that keeps you logged in, and a CSRF cookie that protects your actions against cross-site requests. The app also remembers a few display preferences (such as the theme) in your browser’s local storage; these never leave your device.
This website sets no cookies and uses no analytics, tracking pixels, advertising or third-party scripts. That is why there is no cookie banner.
6. How long we keep data
| Data | Kept |
|---|---|
| Account | Until you delete your account |
| Sessions | Until you log out or after 30 days of validity; all sessions end when you change your password or click Log out everywhere |
| Verification and password-reset links | 48 hours and 1 hour |
| Invites | 7 days |
| Workspace data (mail, knowledge, drafts, settings, usage, audit log) | Until the customer deletes it, the mailbox or the workspace. A workspace admin can set a retention period (in days) after which email text is removed automatically |
| Contact form messages | In our mailbox, for as long as needed to handle the request, at most 12 months |
| Error reports | At most 90 days |
| Backups | Up to 14 daily and 8 weekly copies, so deleted data disappears from backups within about 8 weeks |
When a workspace or account is deleted, the data is removed from the live database and file storage straight away; backups expire on the schedule above.
7. Security
We protect data with encryption in transit (HTTPS, TLS to mail servers), encryption of API keys, mailbox passwords and Microsoft sign-in tokens at rest (AES-256-GCM), strict separation between workspaces in the application and in the database (row-level security), hashed passwords and session tokens, rate limits, and a human approval for every outgoing email. Staff with administrative access to the Service cannot see email content or knowledge through the admin tools. More detail is on the Security & privacy page.
8. Your rights
Under the GDPR you have the right to access, correct, delete and export your personal data, to restrict or object to processing, and to withdraw consent where we rely on it.
You can do much of this yourself:
- Access and export: Account settings → Download my data; workspace admins: Settings → General → Data export.
- Correction: change your name and language under Account settings.
- Deletion: Account settings → Delete account; owners: Delete workspace on the Members page.
For anything else, email info@lunevo.be. We answer within one month. You also have the right to complain to a data protection authority, in Belgium the Data Protection Authority (Gegevensbeschermingsautoriteit, www.dataprotectionauthority.be), or the authority where you live or work.
9. Children
The Service is meant for businesses and is not intended for children under 16.
10. Changes
We will update this policy when the Service or the law changes. The effective date at the top shows the current version. We will tell account holders about important changes by email before they take effect.
11. Contact
Lunevo, Belgium, enterprise number BE 1036.645.433, info@lunevo.be.
See also:Terms of use