Privacy Policy

This section covers the X (formerly Twitter) data LinkIntel handles. There are two separate kinds: your own account, which you connect, and other people’s public posts, which you ask us to keep as references.

2.1 Connecting your own X account

When you connect X, you are sent to X’s own consent screen. We ask for three permissions: tweet.read, users.read and offline.access. The first two let us read posts and basic account details. The third lets us keep reading while you are not signed in, which is how the daily refresh works. We do not request any write permission, and we do not request the permissions X uses for direct messages or for your followers and following lists.

• We never post, reply, like, repost or follow on your behalf.
• We never read your direct messages or your lists of followers or accounts you follow.
• We never ask for your X password. You sign in on X, not on our site.

2.2 What we collect and store

• Your X user id and handle, so each connection is tied to the account that actually granted it.
• Your access and refresh tokens, and when the access token expires. See section 2.5 for how they are protected.
• Your recent original posts. We read your timeline without replies and reposts. For each post we store its id, link, publication date, the first 1,000 characters of its text, and its metrics.
• Post metrics, including metrics only you can see. Alongside the public counts, X returns private and organic metrics for your own posts to an account you have connected, such as impressions. We store whatever X returns, and record which kinds were available for each post.
• Usage records for X API calls. Each record holds only the endpoint called, a count of items returned and the time, never any content. We use them to enforce usage limits. They are kept with your account and are not deleted when you disconnect.

We also make one call that reads your display name and public counts when you connect. We use it to confirm whose account it is and we do not store the name or the counts.

2.3 How often, and how much

A scheduled job refreshes connected accounts once a day. Each refresh reads only posts published within a recent window of days, up to a fixed number of posts, and stops there. Older posts keep the last snapshot we stored and are not read again. Refreshes run only while you have an active subscription, and we apply daily limits per account and across all accounts to keep X API use bounded. If X rejects your grant, the connection is marked as expired and you are asked to reconnect.

2.4 How it is used

Your own X posts and metrics are used to show you, and the AI assistant you have connected, how your own posts have performed, and to ground the briefs your assistant prepares. They are visible only to you. We do not sell, rent or trade them, we do not share them with third parties for their own purposes, and we do not use them to train machine learning or AI models. As with LinkedIn data, the answers to a request you make through a connected assistant are sent to that assistant, which is operated by a separate company under its own terms (see section 3.4).

2.5 How your tokens are protected

Your X access and refresh tokens are encrypted (AES-256-GCM) before they are written to our database. The encryption key is held in our application environment, not in the database, so a copy of the database alone cannot be used to read them. They are decrypted on the server only when a refresh runs, and are never sent to your browser.

2.6 Public reference posts

You or your assistant can ask LinkIntel to look up public X posts by other people and keep them as references, so a brief can show what has worked for accounts you choose to learn from. This is the only way LinkIntel reads another account’s posts, and it reads public posts only. For each reference we keep the post id and link, a short excerpt of its text, its public impressions where X returns them, when we captured it, and the topic, group and observations about it that you or your assistant supplied. References are stored against your account and are not shown to other customers.

To avoid reading the same post twice, we also keep a short-lived copy of the posts fetched by a lookup (the post id, date, text and metrics X returned). A scheduled job deletes these copies once they are two days old. Lookups are subject to daily and monthly limits per account, and a daily limit across all accounts. You can remove references at any time through your assistant, and you can ask us to delete them.

2.7 X’s published ranking weights

LinkIntel also includes information about how X ranks posts, taken from material X has published openly. This is not personal data about you.

2.8 Disconnecting and deleting

• Disconnect at any time from your account page. This immediately deletes your stored snapshots (every X post and metric we stored for you) and your X connection, including the stored tokens.
• Disconnecting also asks X to revoke our access. We send X a revocation request for your tokens as part of disconnecting. If X cannot be reached, your data is still deleted on our side. To check, or to remove LinkIntel’s authorisation yourself, use X’s connected apps settings.
• Cancelling your subscription stops the daily refresh, but your stored X data stays until you disconnect or ask us to delete it. You can disconnect even after cancelling.
• To delete your account and everything linked to it, including your references, email support@getlinkintel.com. We will do so within 30 days. Section 9 explains how long backups take to age out.

3.1 What we are permitted to do

When you connect your LinkedIn account, you are asked to grant a single permission, r_member_postAnalytics. This permission is read-only and applies to your own account only. Concretely:

• We can read performance metrics for posts you have published on your own profile.
• We cannot publish posts, comments or reactions on your behalf. We do not request any write permission.
• We cannot read anyone else’s posts, your connections, your messages, your feed, or any company Page you administer.

3.2 What we read

We call LinkedIn’s Member Post Analytics API (memberCreatorPostAnalytics) to retrieve the following metrics, both in aggregate for your account and for individual posts you have published: impressions, members reached, reactions, comments, reshares, post saves, post sends, and link clicks. We refresh these daily and keep roughly 90 days of history, which is the window LinkedIn makes available.

LinkedIn’s API can measure a post only if we can name it, and it cannot list your posts for us. So we also store the LinkedIn share identifier, the post URL, the publication date and a short excerpt of the text for each post you register with LinkIntel, which is what lets metrics be attributed to the right post and grouped by theme. Section 4 explains where that list of posts comes from.

3.3 How it is used

These metrics are used for one purpose: to show you the performance of your own content. That includes summaries over a period, day-by-day trends, period-over-period comparisons, identification of unusually strong or weak days, and rankings of your own posts.

• Your LinkedIn data is visible only to you.
• We do not sell, rent or trade it.
• We do not share it with third parties for their own purposes.
• We do not use it to train machine learning or AI models.
• We do not aggregate it with other members’ data to produce benchmarks or industry reports.

3.4 Access through AI assistants

LinkIntel can be connected to an AI assistant using the Model Context Protocol, so that you can ask questions about your analytics in natural language. When you choose to do this, the answers to your questions are sent to whichever AI assistant you have connected, because that assistant is the interface you are reading them in. That assistant is operated by a separate company under its own terms and privacy policy, and your data is subject to those terms once it reaches it. We do not send your data to any AI provider except in response to a request you have made from a client you connected yourself.

3.5 Withdrawing access

You can revoke LinkIntel’s access at any time from LinkedIn’s permitted services settings, without going through us. Revoking access stops all further collection immediately. To also delete the metrics we have already stored, email us at support@getlinkintel.com and we will delete them within 30 days of your request.

Because LinkedIn will measure a post but will not list your posts, you have to give LinkIntel that list once. There are two ways to do it, and you choose which.

4.1 The analytics file LinkedIn gives you

You can download your own creator analytics export from LinkedIn, as a spreadsheet, and give it to us on the setup page. We read it in memory, take the post identifiers, URLs and dates out of it, and register those posts so they can be measured. We do not keep the file. It is never written to disk or to our database: all we record afterwards is its name, so the setup page can tell you which file you last used. The older Shares.csv from LinkedIn’s full data archive is also accepted and is handled the same way.

4.2 A scheduling tool you already use

If you publish through Typefully or Postiz, you can connect it instead, by giving us an API key from that tool. We use the key to read the LinkedIn posts you published through it, and take the same fields: identifier, URL, date and a short excerpt. We never read anything from those tools other than your own published posts, and we never write to them.

That API key is stored, rather than hashed, because it has to be replayed against the provider each time an import runs: a key we could not read back could never be sent. It is held in a column that our own web application does not query, and that our database refuses to return to any browser session. Only our server-side service role can read it, and only immediately before an outbound call to that provider. It is never displayed back to you and never appears in a page we render.

You can remove a connected source at any time from the setup page. Disconnecting deletes the stored key. Posts already imported are left in place, because they are measurements about your own content rather than something belonging to the tool you imported them from. If you want those deleted too, ask us and we will delete them.

4.3 A webhook from any other tool

If you publish through a tool we do not integrate with directly, you can create a webhook on the setup page and point that tool at it. Each call registers the posts it describes: the LinkedIn share identifier, the URL, the date and a short excerpt, the same fields as above. The webhook secret is ours rather than a third party’s, so it is stored only as a SHA-256 hash and used solely to check that a call is genuine; it is shown to you once, when you create it. Deleting the webhook on the setup page deletes the hash and stops further calls being accepted.

5.1 Information you provide

• Your email address. It is the core of your account. You sign in with Google, so we hold no password for you. Google shares your email address with us, along with the basic profile details its sign-in screen describes, such as your name and picture. We do not ask you for anything else.
• Payment information. Polar acts as merchant of record and takes the payment. Your card details go to Polar and never reach us. We receive confirmation that a subscription is active, and the identifiers needed to keep it in step with your account.
• Access credentials for connected services. Your X tokens, any LinkedIn authorisation token, and any API key you give us for Typefully or Postiz, as described in sections 2, 3 and 4.
• Correspondence. Messages you send us for support.

5.2 Information collected automatically

• Usage data: which features are used, to understand what to improve. For MCP requests, this means the name of the tool your assistant chose, whether it succeeded, how long it took, and a small set of non-content parameters such as metric and time period. Your assistant sends your natural-language question to its own provider, not to us, so LinkIntel never receives it. We do not put tool responses, post text, post URLs, X or LinkedIn identifiers, API keys or access tokens into product analytics.
• Technical data: IP address, browser and device information.
• Campaign and visit data: if you arrive from one of our adverts, the campaign details described in section 12.
• How you found us: when you create an account, the site that referred you (its domain only), the first page you visited and any campaign parameters in that page's address. This is sent along with your Google sign-in rather than stored on your device, so it is recorded whatever you choose on the cookie banner. We keep it with your account and copy it into the checkout we create with Polar, so we know which sites and pages bring our customers.
• Error logs: diagnostic information when something fails.

• Consent: for accessing your own X account and, for existing customers, your LinkedIn analytics. You give it through the authorisation screen of X or LinkedIn and can withdraw it at any time.
• Performance of a contract: to provide the service you signed up for, manage your account and take payment.
• Legitimate interests: to keep the service secure, prevent abuse, improve the product, measure whether our adverts lead to subscriptions, know which sites and pages bring our customers, and keep the public X posts you ask us to reference.
• Legal obligation: to meet accounting, tax and other legal requirements.

We do not sell, rent or trade personal information. We use a small number of service providers who process data on our behalf, under contract and only on our instructions:

• Hetzner, which hosts the servers that run LinkIntel and its database, in Finland, in the EU.
• Cloudflare, which sits in front of our website and stores our encrypted database backups.
• Google, which handles sign-in. Google is a controller in its own right for your Google account, under its own privacy policy.
• Resend, for sending the account emails we send you.
• Polar, for the subscription. Polar is the merchant of record and processes the card itself, so it is a controller in its own right for the payment, under its own privacy policy.
• PostHog, for product analytics, on its US cloud. See section 12 for what is sent.
• X, in two ways: its API, which we call to read your posts when you connect your account and to look up public posts you ask us to reference, and its advertising pixel, which tells X when a visit or purchase followed one of our ads so we can measure those ads.
• Meta, whose advertising pixel does the same for our ads on Facebook and Instagram, where we run them.

Beyond those, we disclose personal data only:

• when required by law, a court order, or to establish or defend legal claims;
• in connection with a merger, acquisition or sale of assets, with equivalent protections in place;
• where you have asked us to.

Our servers and database are hosted by Hetzner in Finland, in the EU.

International transfers. Some of our providers process data outside the UK and the EU: PostHog in the US, and Polar, Google, X, Meta, Resend and Cloudflare in the countries where they operate. Where they do, we rely on the safeguards each provider offers, such as the UK Extension to the EU-US Data Privacy Framework, or standard contractual clauses with the UK International Data Transfer Addendum.

Accounts from our earlier product. Accounts created for LinkIntel’s earlier LinkedIn company analytics product are being moved from our previous database provider (Supabase, London, UK) to our own infrastructure. We keep the account email, name, signup and plan history, and we do not keep the old LinkedIn page analytics. After the move, the previous provider’s copy is deleted.

• LinkedIn analytics: kept while your account is active, and deleted within 30 days of you closing your account or asking us to delete it.
• X posts and metrics, and X tokens: kept while your X account is connected. Disconnecting deletes them at once (section 2.8). If you cancel without disconnecting, they stay until you disconnect or ask us to delete them.
• Public reference posts: kept until you or your assistant remove them, or you ask us to delete them. The short-lived lookup copies are deleted after two days.
• LinkedIn access tokens: deleted when you revoke access or close your account.
• API keys for Typefully or Postiz: kept until you disconnect that source or close your account, then deleted.
• The analytics file you give us: not kept at all. It is read once, in memory, and discarded.
• Account and billing records: kept for as long as required by UK accounting and tax law, currently six years.
• Error logs: kept for a short operational period and then discarded.
• MCP tool usage: kept for 90 days, then deleted automatically.
• Database backups: a daily encrypted backup is kept for 35 days and one monthly backup is kept for 400 days. Data we delete from the live database therefore remains in those backups until they expire, and is not used for anything else.

We take a deliberately small-surface approach to security, and describe here only what we actually do:

• Data is encrypted in transit. Database backups are encrypted before they leave our server.
• Access tokens for X and LinkedIn are stored server-side, encrypted, and are never exposed to the browser. The key for X tokens is kept outside the database.
• The access key you use to connect LinkIntel to an AI assistant is stored only as a one-way SHA-256 hash, so it cannot be recovered from our database. You are shown it once, and you can revoke it at any time.
• API keys for Typefully or Postiz have to be replayed against those services, so they cannot be hashed. They are stored instead in a column that only our server-side service role can read, with database access rules that refuse the request for every other role, including your own signed-in session.
• Database access is restricted by row-level security, so one customer’s records cannot be read by another.
• Administrative access is limited to the company’s director.

No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to your rights, we will notify you and the ICO as required by law.

Under UK and EU data protection law you have the right to access, correct, delete, restrict or object to our processing of your personal data, to receive it in a portable format, and to withdraw consent where processing relies on it. Exercising these rights is free, and we will respond within one month.

To make a request, email support@getlinkintel.com.

If you are unhappy with how we have handled your data, you can complain to the Information Commissioner’s Office. We would appreciate the chance to put it right first.

Some cookies are strictly necessary and are set without asking. Everything else, meaning our advertising pixels, PostHog's cookies and storage and our campaign cookie, is switched on only if you choose Accept on the cookie banner. Choosing Reject, or not choosing at all, leaves them off. You can change your mind at any time with "Cookie settings" in the footer of any page, and you can also control cookies through your browser, though disabling them will stop parts of the product working.

Strictly necessary (no consent needed)

• Your cookie choice, li_consent. It records whether you accepted or rejected, for 180 days, so we do not ask on every visit.
• Sign-in and security cookies keep you signed in. While you connect X, a short-lived (10 minute) cookie holds the encrypted state of that step.

Only if you accept

• PostHog measures product usage in the browser through a same-origin relay on our own domain. If you accept, it uses a first-party cookie and browser storage. If you reject, it runs without cookies or storage and counts your visit anonymously, with no identifier kept on your device. Before you choose, it records nothing. It records page views (including the address and any campaign parameters), page departures and the actions you take on the site. It builds a profile only once you are identified, which happens when you sign in or pay. On the server we also send PostHog a small number of events tied to your account, whatever your cookie choice: each MCP tool call (the tool name, whether it succeeded, the platform and how long it took, never the content of your request or the result), your first prepared brief, and the start or cancellation of a subscription (the plan, amount, currency and subscription id, plus the campaign details below if you accepted).
• Advertising pixels from X and Meta are loaded on our pages only where we have turned them on for a campaign, and only after you accept. They tell the ad platform about visits and about key steps (sign-up, checkout, purchase and its value) so we can measure our ads. X and Meta may set their own cookies and receive your IP address and browser details, under their own privacy policies. If you reject, neither pixel loads and no event is sent. If you later reject after accepting, they stop loading from your next page load.
• A first-party campaign cookie, li_attr. If you accept and arrive from one of our adverts or a tagged link, we keep it for up to 90 days. It records the first campaign that brought you: the UTM parameters, the X or Meta click id, the page you landed on, the referring site and the date. When you start a checkout we copy these values, and your PostHog identifier, into the checkout we create with Polar, and into our PostHog subscription event, so we can tell which adverts lead to paying customers. A visit with no campaign parameters sets no such cookie, and neither does a visit where you have not accepted. Rejecting deletes it.

• Controller: DevRel Bridge Ltd, company number 15979110
• Registered office: 128 City Road, London, United Kingdom, EC1V 2NX
• Privacy, data requests and everything else: support@getlinkintel.com