Privacy Policy
Last updated: Oct 16, 2026
Nectvia is built on the idea that your professional history belongs to you. That only means something if we are precise about what we hold, so this policy describes what the software does.
Who we are
Nectvia is operated by:
Lance Haig, Faehlmannweg 12A, 14089 Berlin, Germany
For anything in this policy, including a request about your own data or about data we hold on someone else, write to us at privacy@nectvia.work.
What we collect
When you create an account
- Your username, email address, full name and chosen interface language.
- Your password, stored only in a form that cannot be turned back into the password. We never hold the password itself and cannot recover it for you.
- If you register with an email address and do not confirm it within 48 hours, the account and everything entered when registering are deleted, and the username and any invite code become free again. Nothing is sent to the address when this happens.
On your profile
Your headline, summary, location, industry, profile picture and LinkedIn address, as far as you choose to fill them in. If you connect an AT Protocol identity, we also store its DID (a permanent identifier) and its handle.
What you write
Posts, articles, comments, likes and direct messages.
Verifying a work email address
To confirm where you work, we email a code to your work address. We store the address and its domain. The code is never stored in readable form.
Feedback you send us
A feedback report carries your user identifier, never your email address, along with the page you were on, the app version, your interface language and your browser window size.
If an administrator forwards a report to our public issue tracker, the text you wrote is copied across word for word. Please do not put anything in a report that you would not want to appear in a public bug report.
Technical data
Every request to Nectvia is written to a server log recording the time, the page, the response status and your IP address. Administrator actions are logged the same way.
We also use your IP address, and sometimes a one-way code of your email address, to protect accounts and the service from abuse such as password guessing. These records are kept for up to 24 hours.
We keep server logs for up to 30 days. Older entries are deleted automatically.
If you join the waitlist
We store your email address, the language you were reading the site in, whether you have been let in yet, and your invitation, stored in a form that cannot be read back.
If an existing member gave you an invite code, that code records nothing about you until you actually register. We never built a feature to email an invitation, because it would have meant holding your address and your relationship to someone else before you had agreed to anything.
Data about other people
If you import your LinkedIn data export, that file contains information about other people. For each of your connections we store:
- their name
- their LinkedIn profile address
- their email address, where LinkedIn included one
We do not store their headline, their employer or their job title, even though those columns are in the file.
From the same export we also store your LinkedIn invitations, your LinkedIn message history, which includes both parties' names and profile addresses and the full text of the messages, and endorsements.
What we do with it
We use those email addresses to match people to accounts, and only addresses that the member has confirmed with Nectvia. A name is never used for matching. A LinkedIn profile address in your imported LinkedIn messages is not used to match people to accounts or requests. It is used only to show which Nectvia member a message was with, and to offer to add those messages to a conversation you already have with that member on Nectvia. It never makes a connection or sends a request, and it never shows a member who has blocked you, whom you have blocked, or whose account is hidden or suspended. If someone imported a file containing your email address, and you register and confirm that address, Nectvia sends you a connection request from them. This works in both directions: if your import contains the confirmed address of a member, that member receives a request from you. No connection is made unless the person who receives the request accepts it. No request is sent between two people who are already connected or have had a request before, including one that was ignored or withdrawn.
If you are one of those people
If you have never signed up for Nectvia, someone else's import may still mean we hold your name, your profile address and your email address. You did not agree to that.
You can ask us what we hold about you, and ask us to delete it, by writing to privacy@nectvia.work. We will do it. You do not need an account, and you do not need to explain why.
When a member deletes their Nectvia account, every contact record from their import is deleted with it.
If you ask us to erase your name from a member's imported invitations or recommendations, Nectvia keeps a one-way code made from that name, tied to that member's imports, so importing the same file again does not bring it back. The code cannot be turned back into your name, and it is deleted when that member deletes their account.
What we never collect
- We do not track who looks at your profile. There is no such record anywhere in the system.
- We hold no salary information about you. Where a salary range appears on Nectvia, it is a range an employer advertised on a job listing.
- We run no advertising and no third-party trackers. There is no advertising pixel, no session recorder and no tracking cookie. We count visits from our own server log, without cookies, and keep those statistics for 90 days.
- We do not sell your data, and we do not share it for advertising.
Where your data goes
- Our database runs on a server in Germany, hosted by Hetzner.
- Images you upload are stored in Hetzner Object Storage in Nuremberg, Germany, and served through Nectvia.
- Email we send you goes out through our email provider.
- Payments, where you make one, are handled by Mollie. We send Mollie your name and email address so that it can process the payment. We never see or store your card details.
- Our issue tracker, if an administrator forwards your feedback there, as described above.
- Your own AT Protocol repository, described below.
- If you link an AT Protocol identity, resolving it involves a lookup against the public PLC directory and against your own provider.
- If something goes wrong, an error report about it goes to an error-tracking service we run on our own servers in Germany. Search terms and one-time links are removed from it first. Error reports are kept for 90 days.
- If you link an AT Protocol identity, we ask a public index of backlinks (Constellation, run by microcosm) which accounts have verified you, and Bluesky's public profile service which of Bluesky's trusted verifiers have. This sends your public DID to those services and nothing else about you.
Publishing to your own AT Protocol repository
Nectvia can copy some of your data into a personal data server that you control, so that it is yours independently of us.
- It is off by default. Nothing is ever written to your repository until you switch it on.
- It is per type. You choose separately whether to publish your profile, your posts, your positions, your education, and so on.
- Your repository is public. Anything published there can be read by anyone who has the address, including people who do not use Nectvia.
- Some things can never be published, by design. Your direct messages, pending connection requests and job applications have no route to your repository at all. This is not a setting you could switch on by accident: the capability does not exist.
Email we send you
We send three kinds of email, and they are treated differently. Each is described below.
Service emails
These are sent because of something you did or asked for. They are not marketing. They include:
- Verifying your email address, and resetting your password.
- Verification codes for a work email address you add to your profile.
- The link to download your data export once it is ready.
- A warning before one of your API tokens expires, 30 days and 7 days beforehand.
- The invitation to register, if you joined the waitlist.
- Notifications about new messages, new connection requests and accepted requests, if you have switched them on.
Message and connection notifications are off unless you switch them on in your settings, and every one of them contains a link to switch it off again.
Essential account notices
Every user with a verified email address may receive an essential notice. We send one only when something affects your account or the service, such as a change to these terms, a security matter or a change to the service. We never use these notices for marketing.
News emails
We send news about Nectvia by email only if you have given consent and then confirmed it. You can give consent in three ways: the box on the sign-up form, which is never ticked for you; the news switch in your settings; or the one-time question shown in the app.
Giving consent does not start the emails. We first send you a confirmation email, once your address is verified, and we send you no news until you have clicked the link in it.
For each request we record, as proof of your consent:
- when you asked for news;
- how you asked: at sign-up, in settings or through the in-app question;
- when we sent the confirmation email, and when you confirmed;
- if consent ends, when and how: in settings, through the link in an email, or because you changed your email address.
You can withdraw at any time, through the unsubscribe link in every news email, which needs no login, or with the switch in your settings. Changing your primary email address also withdraws it, because the new address has not confirmed anything: it receives no news until you ask again and confirm. Withdrawing stops future news emails; it does not undo ones already sent.
If you ask again after withdrawing, that is recorded as a new request, so your earlier requests and withdrawals stay in the record. If you ask again while a request is still waiting for confirmation, we update that request and send a new confirmation email. These records are included in your data export, and they are deleted when you delete your account.
Email delivery
Our email provider processes your email address in order to deliver these emails. See "Where your data goes" above for how the services we use handle your data.
Why we are allowed to hold this
We process your data to run the service you asked us to run: your account, your profile, your content and your connections.
We process technical data, meaning IP addresses in logs and in rate limiters, to keep the service available and to defend it against abuse.
We process data about people who are not members, arriving through members' imports, to provide the connection features described above. Where that concerns someone who never signed up, that section explains how to have it removed.
News emails are sent on the basis of your consent, which you can withdraw at any time without affecting the emails sent before. Service emails and essential account notices are sent to run the service you asked us to run.
Your rights
You can:
- See your data. Most of it is visible in the app.
- Take a copy of it, from your settings. We prepare an archive of everything we hold about you and email you a link.
- Correct it, by editing your profile and your content.
- Delete it, by deleting your account.
- Ask us anything about it, at privacy@nectvia.work.
The export arrives as CSV and JSON, with a plain-text file explaining what each part contains and which parts include information about other people. The download link works only while you are signed in to your account, and both the link and our copy of the archive expire after 72 hours. Ask for another whenever you like.
Deleting your account
Deleting your account is permanent and immediate. There is no grace period and no recovery. Your profile, posts, articles, comments, messages, connections, imported history and uploaded images are erased from our database in a single operation, not merely hidden.
These things are kept, without your name, because they are not only about you:
- Applications other members sent to your job ads stay with those members after you delete your account, with only the job title and company name, because they are the applicants' own records.
- If you joined using someone's invite code, that code stays marked as used, with the link to you removed. Otherwise deleting your account would bring a spent code back to life.
- Job ads you posted for a company stay with that company after you delete your account, without your name. Job ads you posted for yourself are deleted.
What deletion does not touch
Anything already published to your own AT Protocol repository stays there. That repository belongs to you, not to us, and emptying it is not ours to do. If you want those records gone, remove them through your provider or through another AT Protocol application.
Leaving Nectvia does not un-publish what you chose to publish.
How long we keep things
- Account data: until you delete your account.
- Server logs: up to 30 days.
- Rate-limit records: between one minute and 24 hours, depending on the limit.
- Verification codes: they expire, and only ever existed as hashes.
- Waitlist entries: until you register or ask us to remove you. If you register, the entry is deleted along with your account when you delete it.
- Consent records for news emails, including withdrawn ones: until you delete your account.
- Records of emails we could not deliver (the address, the subject and the reason it failed): 30 days.
- If an account is suspended for abuse, a one-way hash of its email address is kept to stop it registering again, for as long as the suspension stands.
- Reports you make, and the copy of reported content we keep with them (for a message, also the 10 messages before it): until 6 months after the report is closed, even if the content or either account is deleted.
- Messages you exchanged with a member who deleted their account: they stay in your copy of the conversation, shown as from a deleted member, until you delete the conversation or your account.
- If a member has blocked you and you delete your account: a one-way code made from your confirmed email address and from any AT Protocol identity you have linked, used only to restore that block if you join again. While your account exists, we also keep such a code for an identity you unlink. These codes are deleted when that member deletes their account, or after three years.
- Feedback reports an administrator has declined: one year after the decision.
- A username you stop using, by changing it or by deleting your account: 90 days, so nobody else can take it and pose as you. If you changed it, you can take it back in that time. After an account deletion only the name itself is kept, not whose it was.
- If you pay for a company's subscription: your email address, kept with that subscription for as long as it runs, even if you delete your Nectvia account or stop managing the company, so that we can tell you how to cancel it. It is deleted when the subscription is cancelled. Mollie keeps its own record of the payment.
- Visit statistics counted from the server log: 90 days.
- Error reports: 90 days.
Content we show but do not host
A company can connect its own AT Protocol account to its Nectvia page. When it does, we read what that account publishes and show it on the company's page and in the feeds of people who follow it. We do not copy it: we store only the address of each record and fetch the content from the company's own server each time it is shown. The one exception is a record that a member reports to us: we keep a copy of its text with the report, as set out in the retention section.
That content belongs to the company and lives on infrastructure we do not run. We cannot edit or delete it. If the company deletes a record, it stops appearing here; if the company disconnects its account, everything from it stops appearing here.
We can stop showing an individual record on Nectvia, and we will do so where it breaks our terms or the law. That only hides it from Nectvia. The record itself stays where its author published it, and anyone reading that account directly can still see it. To have something removed at the source, you need to contact whoever published it or the provider hosting their account.
When a company connects its AT Protocol account so that its admins can publish verifications, we store a reference to that account's session. We use it only to publish the verifications those admins issue. The session is stored encrypted and can only publish verifications. The session is deleted when the company disconnects, unlinks or changes the account, or is deleted.
Changes to this policy
If we change what we collect or what we do with it, we will change this policy and update the date at the top. That date reflects when the document changed, not when you loaded the page.
Contact
Write to us at privacy@nectvia.work.
This document is published in several languages. Where a translation and the English version differ, the English version is the one that applies.