Beta privacy notice · Version beta-14
How ēvehit handles your data
This notice explains what personal data ēvehit, which is in beta, collects, why, who receives it, how long we keep it, and your rights.
- Operator
- Pinetrace Technologies ApSCVR 46754980
- Contact address
- Ndr Dragørvej 175, 2791 Dragør, Denmark
- Privacy email
- hello@evehit.com
- Last updated
- 13 November 2026
Who we are
ēvehit is operated by Pinetrace Technologies ApS, CVR 46754980, Ndr Dragørvej 175, 2791 Dragør, Denmark ("ēvehit", "we", "us"). For anything in this notice, email hello@evehit.com or use Message Kamran inside ēvehit.
Our role. A workspace holds what its members put into it or connect to it: opportunities, people, organizations, notes, tasks, documents, logged emails and synced meetings. For that workspace content, the workspace owner is the controller, and we process it on the owner's instructions. We are the controller for your account, for running and securing the service, for support, for sign-in records, connected-app records and product usage records, and for collecting Google data through the Gmail and Calendar connections.
What we collect
- Account details: your name, email address, workspace memberships and role. If you sign in with Google, Google shares basic profile details such as your name and email address. If you sign in with LinkedIn, LinkedIn shares basic profile information. We keep LinkedIn's identifier for that sign-in so it can be recognized later. When that sign-in creates the ēvehit account, we also keep the name and email address LinkedIn sends. We do not store the profile photo or the sign-in tokens. That sign-in is not your LinkedIn professional profile: we do not receive your headline, experience, education, connections, or messages. A LinkedIn profile you export and upload yourself, for Profile import, is a separate choice described with the AI features.
- Terms acceptance records: each time you accept the Terms of Service, we record the version and a fingerprint of its exact text, the time, whether it was your first acceptance or a new version, where in ēvehit you accepted (opening the app, creating a workspace, accepting an invitation or connecting an app). If you withdraw from the Terms online, the notice we receive, with your email address and account identifier, is our record of your withdrawal.
- Workspace content: what you and other members add, such as opportunities, people and their contact details, organizations, notes, tasks, documents, your Profile and Career Record, and assessment answers. It often includes information about other people, such as business contacts. Other workspaces cannot see it.
- Data from features you choose: Google data if you connect Gmail or Google Calendar, inputs and results when you use an AI feature, and records of apps you connect. Each has its own section below.
- Sign-in records: your IP address and your browser's user-agent string (the text a browser sends to identify itself and the kind of device it runs on), stored with each sign-in.
- Passkeys: when passkey sign-in is switched on, you can add a passkey to sign in with. If you add one, we store its public key, its credential identifier, the name you see for it, when it was added and last used, whether it can sync between your devices, how your browser can reach it, a signature counter, and the authenticator model identifier your device reports, if any. You can rename it.
- Product usage records: a short, fixed list of product actions, such as creating a pursuit, logging an interaction, completing a task or searching, recorded with the workspace and time. They contain no member identifier and no workspace content such as names, titles, notes or search terms. In a workspace with one member, the workspace and time may still show who acted. We look at them as workspace-level counts to see how the beta is used.
- Share links: if you share ēvehit with someone, we create a link for you. Its page shows your name to whoever opens it. If you type a first name for the person you have in mind, we store that name on the link and show it on the page as a greeting. We do not ask for, or store, that person's contact details.
- Joining through a share link: if you create your workspace after opening someone's share link, we record that your account joined through a share link, and through which one. The person who shared it sees that the number of signups on that link went up. They are not told who joined. If the link was made for one person, they may assume it was that person.
- Messages you send us through Message Kamran, including error reports, or by email.
You must give us your email address, to sign in, and your name, when you join or create a workspace; without them, you cannot use ēvehit.
ēvehit uses no analytics company, advertising technology or session-recording service. It uses cookies to keep you signed in and to remember display preferences, such as theme and sidebar layout.
Why we use it, and our legal basis
- Providing ēvehit (your account, your workspace, service emails, operating the service): necessary for our contract with you (GDPR Art. 6(1)(b)).
- Terms acceptance records: recording that you accepted the Terms is part of making our contract with you (Art. 6(1)(b)). Keeping the record afterwards rests on our legitimate interest in being able to show what was agreed (Art. 6(1)(f)).
- Gmail: your consent (Art. 6(1)(a)), given when you connect Gmail.
- Google Calendar: the connecting member's consent (not other attendees'). The workspace owner is responsible for the basis for using synced meetings as workspace content. Calendar stays switched off until we have settled the basis for attendee data and for records kept after disconnecting.
- AI features: the workspace owner, as controller of the content, relies on legitimate interests (Art. 6(1)(f)) in letting members use the AI features they deliberately choose.
- Connected apps: the connection and its credentials are needed to provide the connection you ask for (contract, Art. 6(1)(b)). The record of each tool an app runs rests on our legitimate interests in keeping app access secure and in being able to show what a connected app did in a workspace (Art. 6(1)(f)).
- Sign-in records: our legitimate interest in service security: limiting repeated sign-in attempts and looking into suspicious sign-ins.
- Passkeys: signing you in with a passkey you add is part of providing ēvehit to you (Art. 6(1)(b)). Recording when each one was last used, and emailing you when one is added or removed, rest on our legitimate interest in keeping your account secure (Art. 6(1)(f)).
- Share links: creating and showing the link you ask for is part of providing ēvehit to you (Art. 6(1)(b)). Storing a first name you type about someone else, counting signups per link, and measuring in totals whether people who join through links go on to use ēvehit rest on our legitimate interests in letting members recommend ēvehit and in learning whether recommendations work (Art. 6(1)(f)).
- Support, product usage records and service security: our legitimate interests in supporting users and running a small beta responsibly.
You can object to processing based on legitimate interests (see Your rights).
Google data
ēvehit uses Google for sign-in and for two optional connections, Gmail and Google Calendar. Each connection is a separate choice, and ēvehit asks Google only for read access.
The Google integrations data guide explains how to manage these connections and what is kept after you disconnect.
Gmail
If you connect Gmail, ēvehit reads message metadata—senders, recipients, dates, and subject lines—from mail you send and receive. It logs a conversation only when its sender or a To or Cc recipient is already a Contact in the workspace and is not archived. It does not log drafts, or mail that is in Spam or Trash when ēvehit reads it. For a logged conversation, ēvehit stores Gmail's thread and message IDs, the subject line, the date of the latest message, and links to the matching Contacts to keep relationship timelines current. It does not read or store message bodies or attachments.
Choosing Add for a domain adds its recipients in your most recent sent mail as minimal Contacts with a name and email address.
Logged conversations are part of the workspace: members of the workspace, and apps that members connect to it (see Connected apps), can see their subject lines and dates. Disconnecting Gmail stops future logging; conversations already logged stay in the workspace until the workspace is deleted.
Google Calendar
Calendar is currently switched off. When it is on and you connect it, Google grants ēvehit read-only access to events on calendars you own, and ēvehit requests events only from your primary calendar. It stores each event's Google event ID, title, time, recurrence and privacy setting, with links to matching Contacts. To match meetings and suggest new relationships, it checks attendees' email addresses and firm domains, leaving out you, meeting rooms and declined attendees. Until a workspace owner chooses Add for an unknown domain, ēvehit does not create a Contact or show a meeting based only on that domain; ēvehit remembers the Add or Ignore choice. Descriptions, locations, conference links and attachments are not imported, and private or confidential events are not shown or newly imported. Every active member of the workspace can see synced event titles, times and matched Contacts.
When you disconnect Calendar, or an event becomes private or otherwise ineligible, ēvehit removes the meeting's title and contact matches from the workspace but keeps its Google event ID, time, recurrence, privacy setting and a record of the removed matches, so reconnects cannot bring back or duplicate old meetings. A synced meeting you cancel in ēvehit stays hidden but keeps its stored details. There is no Calendar-only way to remove these records; deleting the whole workspace removes them.
Shared Google access
Gmail and Calendar use access to the same Google account. Disconnecting one in ēvehit may leave in place the access the other still needs; removing ēvehit in your Google Account permissions stops both.
Limited Use
ēvehit's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. ēvehit does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. A connected app can receive the subject lines and dates of logged emails through the access a workspace member approved for it.
AI features
ēvehit's AI features run only when a member chooses one. They currently include importing your Profile from a PDF you upload (such as a CV, or a LinkedIn profile you export yourself), drafting your assessment criteria from notes you type, preparing questions for an interview, and reviewing an opportunity's Positioning.
For each run, ēvehit sends its AI provider, Anthropic (Anthropic Ireland, Limited), the information that feature needs. Depending on the feature, this can include the selected opportunity, your Profile, Career Record and Positioning, private Career Story text, your assessment criteria, recent interactions and their notes, and what you type. Free text you include can contain names, other personal details or copied material. For interview preparation, an opportunity's basic details, such as its title, organization and stage, are sent even when it is marked Confidential; Confidential interactions and the subject lines of emails logged from Gmail are left out.
A Profile import sends the whole PDF to Anthropic. What you accept is saved as written, including positions such as board seats, trusteeships and volunteer roles; if one is with a religious, political, trade-union or health-related organization, that affiliation becomes part of your career history. Remove anything you do not want sent before uploading, or add positions by hand. ēvehit does not keep the PDF.
AI output is a proposal: nothing is added to your Profile or Career Record until you accept it. If you decline a row from a Profile import, ēvehit remembers what the document said for it, so the row is not proposed again. The AI features suggest and draft; they do not make decisions about you that have legal or similarly significant effects.
Interview preparation and Positioning review results are removed when you delete their opportunity. ēvehit keeps a record of each AI run (the feature, when it ran, its cost and, for some features, the input that was sent, which can include private Career Story excerpts) until the workspace is deleted, including run records from earlier AI features that ēvehit no longer offers (a pursuit assessment and a CV-versus-brief comparison).
ēvehit also records which member started each AI run. Every member of the workspace can see, in Settings → Mentat usage, how many credits each member used this month and who started recent runs. When a member is permanently deleted from the workspace, these records no longer show who started their runs, and the credits those runs used show as "Not attributed".
Anthropic does not use this content to train its models. It deletes inputs and outputs within 30 days of receiving or generating them, unless it needs to keep them longer to enforce its Usage Policy or the law requires it.
Connected apps
Where it is available to your account, you can connect an app that supports ēvehit, such as Claude, to work with your workspace for you. You choose one workspace and approve the access the app asks for: reading, making changes, or both. Each member manages their own connections.
A connection follows your current access. With read access, the app can read workspace information you can see, including records marked Confidential and the subject lines and dates of emails logged from Gmail. With change access, it can create and update records such as tasks, notes, people and opportunities, and save a file you give it as a document, which ēvehit stores like a document you upload yourself.
What the app reads is sent to the app's provider (for Claude, that is Anthropic) and is handled under your own agreement with that provider, not under ours. That provider is not our processor, and we do not control what it does with the data. Revoking a connection stops the app's further requests; a request already in progress may finish, and information the app has already received stays with it.
We keep a record of each connection (you, the workspace, the app, the access you approved, and when it started and ended) and the credentials the app uses to stay connected. We also record each time the app runs one of ēvehit's tools: who and which workspace it acted for, the tool, whether it reads or changes data, when it ran, and the outcome. These records do not contain what the app asked for, what ēvehit returned, or the name or text of any record.
You can see and revoke your connections in Settings → Connected apps. A connection is also revoked when your membership of the workspace is deactivated or removed, or when the workspace is deleted.
Who receives your data
We use these providers to run ēvehit:
- Railway: hosts the application, the database and its recovery copies.
- Cloudflare: stores the document files you upload and runs ēvehit's domain names, including redirecting links on alternative addresses such as evehit.ai to the main address.
- Resend: sends ēvehit's emails, such as sign-in links, emails telling you that a passkey was added or removed, workspace invitations, the copy of the Terms you accepted, billing and workspace-deletion notices, and emails telling us that a new Message Kamran message has arrived, without the message itself. If you withdraw from the Terms online, Resend also sends us the notice of your withdrawal, with your email address and account identifier, and sends you its acknowledgement.
- Anthropic: runs the AI features described above.
- ConfigCat: hosts the settings we use to switch features on for chosen accounts. These can hold ēvehit's internal account and workspace identifiers, but no names, email addresses or workspace content.
- Apple (iCloud Mail): hosts the mailbox that receives email sent to ēvehit's addresses, such as hello@evehit.com.
- LinkedIn: when you choose to sign in with LinkedIn, LinkedIn Ireland Unlimited Company checks that sign-in and tells us the basic profile information described above. It does not receive your workspace.
When a workspace member connects an app, that app's provider receives what the app reads, at the member's direction (see Connected apps).
Anyone who opens your share link sees your name, and the first name you typed if you typed one.
A passkey you save in Apple's, Google's or Microsoft's platform, or in a password manager, is kept by that provider under your own account with them. Your browser saves your email address with it, so you can tell which account it is for.
Where data is processed
ēvehit's application, database and scheduled jobs run in Railway's EU West region in Amsterdam, the Netherlands. The background process that carries out whole-workspace deletion runs in Railway's US West region.
Some of our providers process data outside the European Economic Area (EEA), mainly in the United States:
- Railway states that its primary processing takes place in the US. Railway participates in the EU-US Data Privacy Framework.
- Resend stores data in the US. We rely on the EU Standard Contractual Clauses in its terms, and Resend also participates in the EU-US Data Privacy Framework.
- Cloudflare stores data mainly in the US and the EEA, and the data can be accessed from other countries. Document files stored with Cloudflare are not restricted to the EU. Cloudflare participates in the EU-US Data Privacy Framework.
- Anthropic processes data in the US and may use other countries outside the EEA. We rely on the EU Standard Contractual Clauses in its terms.
- Apple states that Apple Distribution International in Ireland is responsible for personal data from the EEA and that data is generally stored by Apple Inc. in the United States.
- ConfigCat keeps data mainly on servers in the EEA and states that it may transfer data to the US.
- LinkedIn sign-in is provided by LinkedIn Ireland Unlimited Company. LinkedIn Corporation in the United States participates in the EU-US Data Privacy Framework.
You can ask us for a copy of the Standard Contractual Clauses we rely on.
How long we keep data
- Workspace content: until you delete it or the workspace is deleted.
- Logged Gmail conversations and Calendar records: until the workspace is deleted (see Google data).
- Gmail and Calendar connection records: for the life of the workspace, including after disconnecting.
- Documents: removing a document deletes the stored file. If that deletion fails, the file can remain in storage until we remove it or the workspace is deleted.
- AI features: run records until the workspace is deleted. A Profile import's proposal is held until you accept or discard it.
- Connected apps: each tool record for 90 days after the tool ran; a connection's record for 90 days after the connection is revoked; its credentials until they expire or the connection is revoked.
- Sign-in records: deleted when you sign out or sign that device out in Settings; otherwise 30 days after the sign-in expires.
- Passkeys: until you remove the passkey in Settings → Account or your account is deleted. Deleting your account deletes its passkeys.
- Product usage records: for the life of the workspace.
- Workspace access records, such as invitations and role changes: for the life of the workspace.
- Records of workspace creation and deletion, and of actions we take as operators: 2 years, except the permanent records of workspace deletions below.
- Workspace deletions: when a workspace deletion is confirmed, we keep a minimal record of it permanently, so that the workspace's identifier is never given to another workspace. It holds the workspace's identifier, an internal identifier of the account that asked for the deletion, the dates, and counts of what the workspace held. Records from an earlier tool we used in 2026 to remove unused workspaces are kept permanently too, and can also hold the workspace's name and the email address it was set up for.
- Messages sent through Message Kamran: until we have dealt with them, then for 90 more days.
- Emails to our addresses, and our replies: once a year we delete conversations whose last message is more than 2 years old, except emails that are accounting records, such as invoices and receipts, which Danish bookkeeping law requires us to keep until 5 years after the end of the financial year they belong to.
- Account details: while you have an account. You can delete your account in Settings → Account, where that control is available, or ask us to (see Your rights). When it is deleted we remove your name, email address, sign-in records and connected-app credentials, and keep an internal identifier that nothing can sign in to, so that the records below still make sense. Any guest access you have to other people's workspaces ends. Notes you wrote in other workspaces keep your name, or your email address if your account had no name, and each workspace keeps its record of who had access, including invitations.
- Terms acceptance records: while you have an account, and for 3 years after it closes, so that we can show what was agreed. When your account is closed, we keep your email address with them for those 3 years, as proof of who accepted. A request to delete your data does not remove them before then.
- Share links: until you deactivate the link or your account is deleted. Deactivating a link deletes it, with the first name typed on it and its count.
- The record that you joined through a share link: for 90 days after you join, then deleted within the following month. After that we keep only counts. It is deleted sooner if your account is deleted.
Backups. Railway keeps point-in-time recovery copies of the database for its configured retention period. We also make manual backups, which we keep outside Railway and delete 90 days after each one is made; they leave out sign-in records and the credentials for Google and connected apps. Data deleted from ēvehit can remain in these copies until the end of those periods.
Security
Each workspace is kept separate from every other workspace in the database, connections to ēvehit use HTTPS, and sign-in attempts are rate-limited.
If you add a passkey, your fingerprint, face, PIN or device password, and the passkey's private key, stay on your device or in your password manager. We never receive them.
The operator view we use to run ēvehit shows basic account information, such as the workspace, active seats, billing status and Google connection health. It does not open people, notes, documents, email subjects, Calendar titles or other workspace content. When you use Message Kamran, Kamran sees your message and the product area you sent it from.
Your rights
You can ask for access to, correction, deletion or restriction of your personal data, or for a copy of it (export). You can also delete your account yourself in Settings → Account, where that control is available. You can object to processing based on legitimate interests, and you can withdraw consent for Gmail or Calendar at any time by disconnecting, which does not affect processing before then.
You can ask us whether your account is recorded as having joined through a share link, and to delete that record.
Requests about workspace content go to the workspace owner, who is its controller. If you do not know who that is, or you send the request to us, we will help route it and assist the owner as processor. For data we control, including your account, sign-in records, Terms acceptance records, connected-app records, Gmail and Calendar connection records, support, security and product usage records, email hello@evehit.com or use Message Kamran. For information a connected app has already received, contact that app's provider. We may need to verify your identity, and we respond without undue delay, normally within one month.
You can also complain to Datatilsynet, the Danish Data Protection Agency.
Changes
Material changes to this notice are announced in the product or in the beta update email.