Privacy

1. What we collect

From a member. Your email address, because that is how you sign in — Lynkur has no passwords. If you confirm a second address, we keep that too: either address signs you in, guests’ replies go to the one you choose, and we email your primary address whenever one is added or removed. Then whatever you choose to put on your page: name, photo, role, company, location, bio, links, uploaded documents, events, and your brand colors and mark. For each signed-in session we keep the browser and device it uses, which you can see and end in Settings.

From a visitor. If you register for an event or exchange contact details on somebody’s page, the details you type — typically your name, email and sometimes your company, title or phone. That is a deliberate act; see section 3 for what happens when you only read a page. When you send either of those two forms we also keep a salted hash of your network address for one day, to limit how often they can be sent, and never the address itself.

Automatically. Counts of page views and link opens, and the address of the page a visit came from, so a member can see whether their page is working. We do not record where a visitor is.

2. What is published

A Lynkur page is public. Anyone holding the address can open it, it can be listed by search engines unless the member asks otherwise, and the link shows a preview when it is shared.

A member’s email address and phone number are not published until they turn each one on. While a detail is off it is not hidden by the page — it is never sent to the browser at all, so it is not in the page for anyone to find.

A member may instead set a detail to reach only the people who exchange contact details with them. Such a detail is sent to you with their contact card after an exchange and is never published on the page.

A member can also hand their contact card over directly: as a code another phone’s camera reads, a file sent through their phone’s share sheet, a picture saved to their phone, or a text message from their own phone. The card carries the details they set to reach people after an exchange, and any they made public. It goes from their phone, not from us.

Another member who scans the code of your Lynkur page can keep you in their People, filled from what your page shows: the details you made public, and nothing you did not.

When a member links their record of you to your Lynkur page, by scanning its code or entering its address, their record of you follows your page. If you later change something your page shows, such as your role or your company, Lynkur offers that member the change to apply to their record of you; nothing changes until they do. Only what your page shows is offered, and hiding something on your page does not remove it from a record they already have, and they can stop following your page at any time. A member is never told that someone is on Lynkur from an email address.

3. Visitors are anonymous until they choose not to be

Reading a page does not identify you. Lynkur sets one cookie that names your browser to nobody; it cannot be read by scripts on the page, and it exists so that a return visit is not counted twice.

That identifier becomes connected to you only when you volunteer your own details — registering for an event, or exchanging contact details — and only for the member whose page you did it on. Nothing in the browser ever carries a person’s identity, which is why those two actions go through our server rather than being done in the page.

From then on, when that browser opens a link on that member’s page, the open is recorded against your details for that member. Clearing the cookie ends it. The two forms are also checked by our hosting provider for automation, which reads how the request was made and nothing you typed.

4. People a member collects

When you register for an event or exchange details, the member whose page you did it on receives those details and a record of how you met — which event, which document you opened, when. That is the point of the exchange, and it is visible only to that member.

A member can also add a person themselves: by typing their details, by capturing a conference badge, a business card or a slide in Connect, by scanning a code the person shows them, or by importing contact cards somebody sent them. A scanned code is read on the member’s phone, and nothing from it reaches us unless the member keeps the card. That person may never have used Lynkur. What the member records is visible only to that member, and is theirs to keep and correct like anything else in this section.

On Pro, a member can import an attendee list an event’s organiser gave them, such as the list a sponsor receives. Lynkur reads the file once and does not keep it. It is matched against the people the member already recorded at that event, and only what the member chooses is kept: details missing from someone they already have, and, if they ask, the other people on the list. Nothing they already have is replaced, and Lynkur never emails anyone on a list.

Lynkur notes where each detail about a person came from, and on what day: that they gave it when they exchanged details or registered, or that the member typed, captured, scanned or imported it, or took it from an attendee list, or read it from an email signature or a screenshot they added, or applied it from the person’s own Lynkur page, or that Lynkur found it from their work address, or that the member confirmed it from a company name Lynkur suggested a website for. If a person the member recorded without an email address later gives one, by exchanging details or registering, it is added to that same record rather than a second one. That happens only when exactly one record from the last two weeks has the same name, and the same company where both name one.

A member can look a person up on LinkedIn from their record. That opens LinkedIn’s own search in the member’s browser, with the person’s name and company in it. Lynkur sends LinkedIn nothing and reads nothing from it; a profile address the member pastes back is kept on the record.

When you exchange details, we send the member’s contact card to the address you gave, once, with a link that works for seven days. Our email provider tells us whether that message was delivered or refused, and that outcome is shown to the member beside your address, so they know whether they can reach you. Nothing else is sent to that address.

For those records the member decides what they are used for and we host them. If you want a member to correct or delete what they hold about you, ask them. If you cannot reach them, write to us and we will help.

5. How we use it

• To run the service: publish pages, send sign-in links, deliver event email and the contact card you asked for.
• To show a member how their page is performing.
• To keep the service secure and to investigate abuse and reports.
• To support you when you ask for help.
• To comply with the law.

We do not sell personal information, and we do not use it to train AI models.

6. Automated processing

Seven features are automated. The first five run only when a member asks; the other two run on their own for members on Pro. When a member asks Lynkur to match their brand, our server fetches their company’s own public website and reads the mark and colors it publishes, to propose a look. It reads a public page; it sends nothing of theirs to anyone.

When a member uses Connect, what they captured — a line they typed or said, or a photograph of a conference badge, a business card or a presenter’s slide — is sent once to a language model run by Anthropic, which returns the name, company, role and contact details it can read, for the member to check before saving. Nothing from the member’s existing contacts is sent with it. The photograph is held only for the length of that request and is never stored by Lynkur. If the member has no signal, the photograph or line waits on their own phone, in its storage for this app, until there is; it is then sent once as above and deleted from the phone. A card the member keeps with no signal waits the same way until it can be saved. Signing out deletes anything still waiting. What is kept is the card the member confirms, which is a record of the kind section 4 describes. We do not use these captures to train anything, and our agreement with Anthropic does not permit them to.

On Pro, a member can also bring a person’s record up to date by pasting their email signature, or an email from them, or by adding a screenshot of a profile. It is sent once to the same Anthropic model, which returns the name, role, company and contact details it can read; nothing else from the member’s People is sent with it. Nothing on the record changes until the member ticks what to apply, and only that is kept. The screenshot and the pasted text are not stored by Lynkur. We count each of these reads, and each Connect capture, against the member’s monthly allowance, keeping that a read happened and its size, never what it read.

On Pro, a member can ask for a draft of a follow-up message to someone they met. To write it, the same Anthropic model receives that person’s name, role and company, how and when the member met them, the member’s notes about them and what the member has noted they owe them, with the member’s own name and role. When they met at one of the member’s own events, it also receives that event’s name and date; and when the member’s record of the person follows their Lynkur page, it also receives the role, company and first sentence of the bio that page publishes, as anyone visiting the page could read. It does not receive the person’s email address or phone number, or anything about anyone else. The draft appears for the member to edit; Lynkur does not keep it and never sends it. The member sends the message themselves, from their own email, LinkedIn or phone, and Lynkur records only that a follow-up went and how, never its words.

On Pro, a member can ask a question about the people they know, such as “the CFO who asked about SOC 2”. To answer it, the same Anthropic model receives the question and, for up to 30 of the member’s people, their name, role, company, tags, how and when the member met them, the member’s notes about them and the lines of their history in Lynkur. When the member has more than 30 people, the question alone goes first, to choose the words Lynkur searches their records for. It does not receive anyone’s email address or phone number. The answer appears for the member to read; Lynkur keeps neither the question nor the answer, only that a read happened and its size.

For a member on Pro, Lynkur also looks up the company behind the work email addresses in their People. Our server reads that company’s own public website and asks Logo.dev for its logo, using the web domain alone, never the person’s name or address, and never for a personal address such as Gmail. The company’s name, logo and website are kept with the member’s People, once for each company, and shown beside the people who work there.

When a member on Pro has recorded a company for someone whose address does not name it, Lynkur may suggest that company’s website. The company name, as the member recorded it, is sent once to Anthropic’s language model, which answers with a website or with nothing; never the person’s name, contact details, or anything else from the member’s People. Our server then reads that website’s own public page, and the suggestion is shown only if the site names the company. Nothing is added to anyone’s record until the member confirms it; the member’s answer is kept so the same name is not asked about again.

7. Cookies and your device

We use cookies to keep you signed in, to remember preferences, and the anonymous visitor cookie described in section 3. We do not use advertising cookies. Blocking cookies will stop you being able to sign in.

On each device where you use Lynkur while signed in, it keeps a copy of your own contact card, so the card can be shown with no connection. It holds what section 2 says your card holds and is refreshed when your card changes. It is removed from a device when you sign out there; if you delete your account, from the device you deleted it on at once, and from any other the next time it opens Lynkur.

8. Who else handles it

We share information with the providers that run the service, each processing it on our instructions and for nothing else:

• Supabase — database, authentication and file storage.
• Vercel — hosting and delivery, including telling a script from a person on the two public forms.
• Resend — sign-in and notification email, and the contact card sent after an exchange; it tells us whether a message was delivered.
• Logo.dev — looking up a company’s logo and colors from its web domain: when you ask us to, when your sign-in address carries one, and on Pro for the work addresses of the people you have recorded. We send the domain and nothing about you or them.
• Anthropic — reading what a member captured through Connect or added to a person’s record, writing a follow-up draft, answering a question about a member’s people, and on Pro suggesting a company’s website from its name, as section 6 describes. It receives the capture, the signature or screenshot, the record and notes a draft is written from (with the event they met at and what the person’s own page publishes, where section 6 says so), the question and the records it is answered from, or the company name, and nothing else.
• A payment processor, if and when you subscribe to a paid plan.

We also disclose information where the law requires it, or to investigate a report or protect someone’s safety.

9. How long we keep it

For as long as your account exists, and afterwards only as long as needed to meet a legal obligation, resolve a dispute or enforce our terms. Deleted content can remain in backups for a short period before it is permanently removed.

One exception: a handle you have used is held for six months after you leave, forwarding nowhere, before it is released, and the record that it was taken is kept. The handle policy explains why.

For a visitor: the hash of your network address is kept for one day, a contact card link for seven, and the record of whether an email to you arrived for as long as the member keeps your details. Where each detail about you came from is kept for as long as the member keeps your record.

10. Security

Lynkur LLC uses commercially reasonable administrative, technical and organizational safeguards. A visitor has no direct access to our data at all — every public page is served by a function that applies the member’s own visibility choices before anything is sent. No system is perfectly secure, and we do not claim otherwise.

11. Where it is processed

Lynkur is currently intended for people in the United States, and information is processed and stored there. If you use it from elsewhere, you are sending your information to the United States.

12. Your rights

You can delete your account yourself, from Settings. That removes your profile, your links and files, your events and their registrations, and the people you have recorded; your page stops resolving at once.

Depending on where you live, you may also have the right to see what we hold, correct it, object to how it is used, or withdraw consent. Write to privacy@lynkur.com and we will act on it. For details a member collected about you, see section 4.

13. Children

Lynkur is not for anyone under 18, and we do not knowingly collect information from them. If you believe a child has given us information, write to us and we will remove it.

14. Changes

We may update this policy. Where a change is material we will give reasonable notice through the service or by email, and the date at the top will change.

15. Contact

Privacy questions and requests go to privacy@lynkur.com.