OAuth authorisation only
LinkedIn access is based on user approval and approved scopes.
LinkedIn Integration
LinkedIn Data Usage Policy
This policy explains how Elaryx requests, uses, stores, protects, and deletes LinkedIn-connected data when users authorise LinkedIn features.
No password collection
Elaryx does not ask for or store LinkedIn passwords.
No scraping
Elaryx does not scrape LinkedIn or bypass LinkedIn restrictions.
User control
Users can disconnect LinkedIn and request deletion.
On this page
1. Relationship with LinkedIn 2. User Authorisation and OAuth 3. LinkedIn Data Categories 4. Permitted Uses 5. What Elaryx Does Not Do 6. LinkedIn-Connected Data Lifecycle 7. Storage, Retention, Token Handling, and Security 8. Publishing, Scheduling, and User Control 9. Compliance Responsibilities and Trademark Notice1. Relationship with LinkedIn
LinkedIn is a third-party platform. Elaryx is independent and is not affiliated with, endorsed by, sponsored by, or approved by LinkedIn unless an official approval is specifically shown. LinkedIn API availability, permissions, review requirements, rate limits, policy changes, and account restrictions are controlled by LinkedIn.
Your LinkedIn account remains subject to LinkedIn's own terms and policies.
2. User Authorisation and OAuth
Elaryx does not collect LinkedIn passwords and does not scrape LinkedIn.
Elaryx uses OAuth or approved authorisation methods. Users see a LinkedIn permission screen, and Elaryx receives only data or actions permitted by user consent and approved scopes. Users can revoke access from Elaryx settings or LinkedIn settings. Re-authorisation may be required when tokens expire or permissions change.
3. LinkedIn Data Categories
| LinkedIn data category | Examples | Why used | Stored or transient | User control |
|---|---|---|---|---|
| Basic profile identifiers | Name, member ID, profile URL/public identifier if provided, profile photo if scope permits | Profile setup, account matching, content personalisation | Stored where needed | Disconnect or request deletion |
| Organisation/page identifiers | Company page or organisation IDs if user manages pages and authorises access | Company publishing and integration health | Stored where needed | Revoke or disconnect |
| Post/content data | Posts, captions, media metadata, scheduled content created through Elaryx | Drafting, scheduling, publishing, audit | Stored in workspace | Delete drafts/schedules where available |
| Publishing status and API metadata | Request IDs, success/failure status, timestamps, error messages | Troubleshooting, audit, reliability | Stored in logs | Deletion subject to security/legal retention |
| Performance metrics | Engagement or analytics data if authorised and available | Insights and recommendations | Stored or refreshed | Disconnect or request deletion |
| OAuth/member tokens | Access/refresh tokens where applicable | Authorised API calls | Protected storage | Revoke/disconnect |
4. Permitted Uses
- Connect and verify a LinkedIn account.
- Personalise profile intelligence, content strategy, and draft content.
- Schedule or publish posts only when user authorisation and product configuration allow it.
- Display analytics or performance insights when authorised and technically available.
- Maintain integration status, troubleshoot support requests, and detect abuse or security issues.
5. What Elaryx Does Not Do
- Does not ask for LinkedIn passwords.
- Does not scrape, crawl, spider, or bypass LinkedIn restrictions.
- Does not sell LinkedIn data or disclose it to unrelated third parties for their independent marketing.
- Does not create fake engagement, fake followers, bot networks, or mass unsolicited messaging.
- Does not guarantee reach, impressions, engagement, leads, followers, or LinkedIn algorithmic treatment.
- Does not publish without user configuration, authorisation, and applicable product workflow controls.
6. LinkedIn-Connected Data Lifecycle
| Step | What happens |
|---|---|
| 1. User authorises | You approve the integration through LinkedIn OAuth or an approved flow. |
| 2. Approved scopes apply | Elaryx receives only the permissions and data available through approved scopes. |
| 3. Features run | Elaryx uses authorised data for profile intelligence, content, scheduling, publishing, analytics, and support. |
| 4. User disconnects or requests deletion | Tokens are revoked/deleted where applicable and data is deleted subject to legal, security, backup, and audit limits. |
7. Storage, Retention, Token Handling, and Security
Elaryx stores OAuth/member tokens only as required to operate connected features. Token access is limited to authorised backend services and operational staff with a need to know. Profile data, content, schedules, analytics, and logs are stored only where legally permitted and needed for service, support, audit, security, dispute, tax, or compliance purposes.
Tokens are protected with encryption or equivalent safeguards, least-privilege access, access logs, monitoring, and incident review. If an incident affects LinkedIn API content or data, Elaryx will follow applicable LinkedIn notification obligations and legal obligations.
8. Publishing, Scheduling, and User Control
Users remain responsible for content. Scheduled posts are published based on user settings, approval workflows, token validity, LinkedIn API availability, and platform rules. LinkedIn may reject posts or restrict actions. Elaryx may apply safety limits to reduce spam and compliance risk.
Users can disconnect LinkedIn, revoke app access in LinkedIn, delete scheduled posts or drafts where available, and request data deletion by emailing support@elaryx.ai. Deletion may disable connected features.
9. Compliance Responsibilities and Trademark Notice
Users must not use Elaryx to violate LinkedIn terms, upload scraped LinkedIn datasets, bypass platform restrictions, or operate client accounts without authorisation. Users are responsible for posts, claims, outreach, disclosures, and compliance with applicable law and platform rules.
'LinkedIn' and related marks belong to their respective owner. Elaryx uses the LinkedIn name only to identify integration functionality.
FAQs
Does Elaryx collect my LinkedIn password?
No. Elaryx uses OAuth or approved authorisation and never asks for LinkedIn passwords.
What LinkedIn data does Elaryx access?
Depending on your plan, authorisation, and approved scopes, Elaryx may access profile identifiers, organisation identifiers, content, publishing status, metrics, tokens, and error logs.
Can Elaryx post without my permission?
Elaryx posts only when user authorisation, connection, and product workflow settings allow it.
Does Elaryx scrape LinkedIn?
No. Elaryx does not scrape, crawl, spider, or bypass LinkedIn restrictions.
Can I disconnect LinkedIn?
Yes. You can disconnect from Elaryx settings or revoke app access from LinkedIn settings.
Can I request deletion of LinkedIn data?
Yes. Email support@elaryx.ai. Deletion is subject to legal, security, backup, and audit retention limits.
Why did a scheduled post fail?
A post can fail because of token expiry, missing permissions, LinkedIn API availability, content rejection, rate limits, or account restrictions.
Does LinkedIn endorse Elaryx?
No. Elaryx is independent and is not affiliated with, endorsed by, sponsored by, or approved by LinkedIn unless official approval is expressly shown.
Can agencies use Elaryx for clients?
Yes, if they have client authorisation and comply with LinkedIn policies, applicable law, and workspace permissions.
Does Elaryx guarantee LinkedIn growth?
No. Elaryx provides tools and recommendations, but does not guarantee growth, reach, engagement, leads, or followers.