Privacy Policy

Black Ocean Ventures (“Linqyou”, “we”), Vondelstraat 81, 1054 GL Amsterdam, the Netherlands, provides LinkedIn analytics, lead, content and career software. This policy explains what personal data we process, why, on what legal basis, for how long, and what rights you have under the EU General Data Protection Regulation (GDPR).

Who is responsible for what

Most of the data in Linqyou is processed for our customers: the person or company that uses Linqyou decides whose data to analyse and why, and we process it on their documented instructions under our Data Processing Agreement. For that data our customer is the controller and we are their processor. In a few areas we decide the purpose ourselves and are the controller. This table says which is which:

If you are a person whose data a customer analyses and you want to know why they hold it, ask that customer first: they are responsible for it. You can also always use our objection form; we act on it for every customer at once, as each of them instructed us to in our Data Processing Agreement.

Your own account

Account data. Name, email address, account type, plan, billing details (handled by Stripe; we never see card numbers), sign-in times, support messages and the security logs needed to keep the service safe.

Your LinkedIn export. When you upload a LinkedIn data export we read a fixed allowlist of files, at most:

• Profile, positions, skills, education, certifications, languages
• Connections (name, profile link, company, role and connection date; never their email address, whose column is not read)
• Posts you shared, and reactions, comments and poll votes you gave
• Invitations and endorsements, sent and received
• Volunteering, companies, people and hashtags you follow (counts and names of companies), saved items, events and learning (counts)
• Rich-media rows, to tell which of your posts had images, video or documents
• LinkedIn’s own files about you: inferred credibility scores, inferences about your career, and the ad-targeting profile LinkedIn built (job titles, seniority, functions, inferred skills, industries, company size, audience segments, locations). We show you only the career-related ones, and never use them for anything but your own Positioning view.
• The separate LinkedIn analytics export (impressions, engagement, followers and audience demographics), if you provide it

We never open, read or store your private messages, login and security history, phone numbers, email address book, or job-application answers. This is enforced in the software: those files are not read from the archive at all.

Giving us an email address is necessary to have an account; uploading an export is necessary to get an analysis. Nothing else is required.

Data about other people that customers analyse

This section is the information GDPR Art. 14 requires for people whose data we receive without them giving it to us. We publish it on behalf of our customers, who are the controllers. We do not contact these people individually: that would itself mean using their details for something new.

Tracked profiles. A customer can analyse the LinkedIn presence of a person they work with, for example an employee or an agency’s client, from that person’s own export. The customer must have a lawful basis for that, and for an employee we require that the person confirms it themselves before their posts or stories are used.

Connections of a tracked profile. Name, profile link, company, role and connection date, taken from the export the tracked person uploaded, plus a keyed one-way hash of the profile link used to recognise the same person within that customer. Used for network statistics, to show which target companies the customer already has a way into, and to suggest who to speak to. Never email addresses.

People who comment on a tracked profile’s or Company Page’s posts. Name, headline, profile link, the text and time of the comment, reactions it received and which comment it replies to. Collected from the public post by our sub-processor Apify, at most once in the post’s first week, once in its second week, and once for an older post. Where LinkedIn shows no job title, company and role may be filled in from the same customer’s own connection list. Comment text may be sent to our AI provider to choose a comment type and up to two of the customer’s own subjects from a fixed list; only the labels are kept with it. Used to show how conversations under the customer’s posts go and who takes part.

People who react to a tracked profile’s or Company Page’s posts. Name, headline, profile link, the kind of reaction (a like, a celebrate and so on) and the date we first saw it. Collected from the public list of reactions by our sub-processor Apify, at the same moments as the comments and for at most the first 250 people who reacted to a post. We do not collect who shared a post, and LinkedIn gives no time for a reaction. A reaction counts for less than a comment: it can add to what a customer already knows about you, and a person who only reacted is listed only if the customer is connected to them, they work at one of its target accounts, or they match the audience it describes. Reactions are never used for benchmarks or shown to other customers.

People who endorsed a tracked profile, or were endorsed by it. Name, public profile link, the skill, the date and the status LinkedIn gives. Read from the tracked person’s own archive, not collected from LinkedIn by us. Shown only to people at the customer who can see that profile. An endorsement is the weakest signal we use: it can add to what a customer already knows about you, and a person who only endorsed is listed only if the customer is connected to them, they work at one of its target accounts, or they match the audience it describes. An endorsement the profile gave is never used as a signal. Endorsements are never used for benchmarks or shown to other customers.

Ranking who to speak to (profiling). “People to engage” and Leads rank commenters, people who reacted and connections by how well their role, company and location fit the customer’s stated audience, how often they engage, and whether the customer already knows them. The ranking is a suggestion to a person at the customer; it decides nothing about you and has no legal or similarly significant effect.

Leads. When a customer uses Leads, it keeps its own record about you per organization: stage, notes, owner and follow-up dates. A customer can export its lead list (name, profile link, the customer’s own notes, and the date we first held your data, so they can inform you when they contact you) or send it to its own CRM through a webhook it sets up. That CRM is the customer’s own choice and responsibility. If you object, the CRM receives only a notice that the record was erased.

Profiles read on request. If you are already one of a customer’s leads, a user there can press a button to read your public LinkedIn profile through Apify. We keep your current role and company, location, previous employers, education, languages and the opening of your About section for that customer for 90 days, to suggest what to mention in a message the customer writes and sends themselves, and to judge whether you fit the audience they are trying to reach. A user can also ask us to look for a work email address for you through the same provider; if one is found we keep it for that customer for 12 months, and we never export it or pass it on. A user can run these for several leads they select at once, up to 50, but every person is read one at a time and only on a press, never on a schedule, and never combined across customers. Messages a user has us draft for you are kept for 90 days so they can be sent, and we send nothing to you ourselves.

People who post job listings. A personal-account user searching for jobs may see the name and profile link of the person who posted a listing, and can ask us to read that person’s public profile (same fields and 90-day limit as above). Nobody but that job seeker sees it.

Reviewers and people writing with Content. An agency can name one reviewer per profile to approve drafts. We keep the reviewer’s email address to send the approval request, and their decision and comment with a keyed hash of the address. A person who writes posts with Content (for example as part of their employer’s campaign) gives us stories, drafts and their edit history; those stay private to that person unless they share them, can be downloaded and deleted by them in the Privacy Centre, and the organization sees campaign totals only. The Voice tab keeps what a person chose about how they write (for example “no emoji”), which of their own posts they picked as examples, and a weekly list of suggested changes; it holds labels, choices and post references, not post text, and is deleted with the rest of their Content. Campaign results are shown for posts at least 14 days old, once at least five people’s posts count, and only refreshed when three more do. Owners and admins can still open each profile’s own analytics.

Where it comes from. From the export the tracked person uploaded, from public LinkedIn pages read by Apify, and from what the customer types in. Who sees it: only users of that customer who have access to the profile or organization involved, and the sub-processors listed on our sub-processors page. Never other customers, never benchmarks, never advertising, never sold.

Benchmarks and the Free plan

Sector benchmarks compare a profile with others in its sector. They are built only from a fixed list of numeric metrics (such as posting frequency and engagement rate), never from post text, names, connections, comments or research. A figure is shown only when it comes from at least 20 workspaces and 100 profiles, with each workspace’s weight capped and extremes removed.

• Free plan: consent. The Free plan is offered in exchange for contributing these metrics. We ask for your consent separately, before your first analysis. You can also get a complete analysis without contributing by buying a Snapshot or any paid plan. You can withdraw your consent at any time in the Privacy Centre: your metrics stop being used from the next nightly rebuild, and further Free analyses then need a paid option. Withdrawal never affects your other rights or data you already received.
• Paid plans: legitimate interest. We may include the same metrics on the basis of our legitimate interest in accurate benchmarks. You can object in the Privacy Centre at any time without losing anything you pay for.
• Customers’ profiles. For a profile analysed by an organization or agency, the customer decides whether its profiles contribute, per profile and for the whole workspace.

Replacing a name with a hash is pseudonymisation, not anonymisation, and we treat it that way: per-profile metrics stay personal data until they are pooled into figures that meet the thresholds above.

Uploads before signing up

You can upload an export and see your analysis before creating an account. If you never confirm your email, after seven days we permanently delete the uploaded file and erase your name, profile link, email, the text and links of your posts, and the names, links and identifiers of your connections and of people who commented. We keep the derived analysis (metrics, demographics, topic and format labels, company and role mix) for benchmarks and product improvement, on the basis of our legitimate interest. This is shown on screen before you upload. We call it de-identified, not anonymous, and treat it as such: it is not published, sold or linked back to anyone. If you want it deleted, tell us within those seven days. If you leave before uploading anything, we keep only the shape of the visit: account type, the goals you picked and how far you got.

Public profile pages

If you choose, Linqyou can publish a page about you at linqyou.com/people/…. It is your page, and it exists only if you confirm it yourself and press Publish: nobody else, including an agency or a colleague, can confirm or publish it for you. It shows only the blocks you switch on, such as your name, headline, a paragraph about what you are known for, facts counted from your own posts, your themes, posts you pick and a link to your LinkedIn profile. It never shows the people who comment on your posts, your connections, who reacted to or endorsed you, or anything about leads. The page is meant to be found by search engines and AI assistants. You can unpublish or withdraw at any time and the page then stops working, but copies that search engines and AI systems already made cannot be recalled by us. We count how often named crawlers fetch the page, without storing any visitor’s address, and may ask AI search engines about you once a week to see whether they cite it.

How AI is involved

We use an AI model to write explanations, suggestions, chat answers, post ideas and drafts, short messages, and to choose labels from fixed lists. Numbers are always calculated by ordinary software, never by the model. What is sent depends on the feature, and never includes raw export files, connection lists, private messages or contact details. Our AI provider may not keep what we send or use it for training. The AI Transparency Notice lists exactly what each feature sends.

Emails

We send sign-in links, upload reminders, and for Content: draft-ready messages, approval requests and, only if someone turns it on, a weekly prompt. An email to an address someone else typed is only sent once its owner has confirmed it. Every optional email has a one-click unsubscribe. A hard bounce or spam complaint stops all further email to that address; we keep a keyed hash of it for that. Our emails contain no tracking pixels. Pages linked from them record only what you do there (opened, copied, marked as posted).

Mail you send us. If you reply to a weekly prompt, your reply is saved as a private story on your profile, as if you had typed it on the page. We keep your own words, not our quoted email or your signature, and only when the reply comes from the address we sent the prompt to. Anything else you send to an address at our domain is received for us by Resend and passed on to the people who run Linqyou; we use it to answer you and for nothing else. [how long Resend keeps received mail]

How long we keep it

An erasure request for an account is honoured in full: we keep no de-identified per-person analysis of an account that asked to be deleted.

Who receives data

Our sub-processors, listed with their location and safeguards on the sub-processors page. Stripe also acts as an independent controller for fraud prevention and legal obligations; see Stripe’s own privacy policy. We do not sell personal data and do not share it for anyone’s marketing. If Linqyou is sold or merged, account data may pass to the successor only to continue the service under this policy, and we will tell you before it does.

International transfers

We store data in the EU. Some sub-processors belong to groups based outside the EU, mainly in the United States. Where data can be accessed from there, we rely on the EU-US Data Privacy Framework for certified companies and otherwise on the European Commission’s Standard Contractual Clauses (2021/914). The safeguard for each sub-processor is listed on the sub-processors page; you can ask us for a copy.

Your rights

You can ask for access to your data, correction, erasure, restriction, a portable copy, and you can object or withdraw consent. Most of this works directly in the Privacy Centre of your account; otherwise write to privacy@linqyou.com. We may ask you to confirm who you are. We answer within one month, or tell you within that month why we need up to two more. If your data is held for a customer, we pass your request to that customer, or handle it for them when they have instructed us to, as they have for objections.

You can complain to a data protection authority in the country where you live, work or where the problem happened. In the Netherlands that is the Autoriteit Persoonsgegevens.

Changes and contact

We will tell account holders by email before a material change to this policy takes effect. General questions: support@linqyou.com. Data protection: privacy@linqyou.com.