Privacy, consent and LinkedIn API data.

This Privacy Policy applies to the Laurence Deer website, enquiries sent to Laurence Deer, and any software, workflow, or application operated by Laurence Deer that connects to LinkedIn APIs, including LinkedIn content publishing, Page management, analytics, or related review workflows.

Contact and enquiry details, such as your name, email address, company, website, message content, and any information you choose to send by email, form, meeting request, or direct communication.

Website and technical information, such as IP address, browser type, device information, referring pages, pages viewed, timestamps, security logs, and similar diagnostic information. If analytics or advertising tools are used, they may collect cookie or usage data according to their own settings and policies.

Client and project information, such as URLs, SEO notes, content briefs, analytics exports, documents, campaign context, meeting notes, invoices, and operational records needed to provide consulting services.

If you connect a LinkedIn account, Page, or organisation profile to an application or workflow operated by Laurence Deer, we may collect the LinkedIn data needed to provide that function. This may include your LinkedIn member identifier, profile basics made available by LinkedIn, authorised Page or organisation details, account permissions, OAuth access tokens, post IDs, drafts, approved content, media, publishing status, comments or messages where an approved API grants access, and analytics or performance data where LinkedIn permits it.

We use LinkedIn API data only to authenticate the connected account, display authorised accounts or Pages, prepare, review, schedule, publish, manage, or report on LinkedIn content, maintain security, troubleshoot errors, and comply with LinkedIn developer requirements and applicable law.

We do not sell LinkedIn data, use it for advertising targeting, recruitment, sales prospecting, list building, scraping, surveillance, or creating or supplementing third-party profiles. We do not collect more LinkedIn data than is reasonably required for the approved application function.

Before a LinkedIn account is connected, the user must authorise the requested permissions through LinkedIn or another approved consent flow. The user can choose not to connect LinkedIn, can revoke access in LinkedIn settings, and can request deletion of LinkedIn data held by us.

Where content is drafted, pre-filled, generated, scheduled, or published, users remain responsible for reviewing and approving that content before publication. Any pre-filled content can be edited before it is published.

If AI tools are used to help draft, rewrite, classify, or summarise LinkedIn content, we only use content that the user supplies, creates, or is authorised to manage for that purpose. We do not use LinkedIn data from people who are not application users to train AI models.

Where third-party AI providers process content, they are used as service providers for the requested function. We aim to configure those services so customer content is not used to train their general models where that control is available.

We use information to respond to enquiries, provide SEO consulting services, operate websites and applications, manage content workflows, authenticate authorised users, process payments and administration, protect against misuse, comply with legal obligations, and improve service quality.

We may also use business contact details to follow up on an enquiry or existing client relationship. You can ask us to stop non-essential communications at any time.

We share information only where needed to provide the service, operate the website or application, publish content at the user’s direction, comply with law, protect rights or security, or work with trusted providers such as hosting, email, analytics, payment, document, automation, and professional advisory services.

When a user directs us to publish or manage content through LinkedIn, relevant content and account data is sent to LinkedIn through the approved LinkedIn API. LinkedIn processes that data under its own terms and privacy policy.

We keep personal information only for as long as needed for the purpose it was collected, to provide services, maintain business records, resolve disputes, comply with legal obligations, and protect security.

LinkedIn API data is stored only for the time reasonably needed to provide the approved function and in line with LinkedIn requirements. Where LinkedIn imposes shorter storage limits, we follow those limits, including limits that may apply to member profile data, social activity data, tokens, and content. OAuth tokens are deleted or invalidated when no longer needed, when access is revoked, or when deletion is requested, subject to legal obligations.

To request deletion of your personal information or LinkedIn API data, email hello@laurencedeer.com.au with the subject line "LinkedIn data deletion". We will verify the request and delete or de-identify the relevant data unless we must retain it for legal, security, or legitimate business record reasons.

We use reasonable technical and organisational safeguards to protect information against unauthorised access, misuse, loss, alteration, or disclosure. No internet service can be guaranteed to be completely secure, but access is limited to people and providers who need it for the relevant purpose.

Depending on where you are located, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. Australian users may also contact the Office of the Australian Information Commissioner if they are not satisfied with how a privacy concern is handled.

To make a privacy request, contact hello@laurencedeer.com.au. We may need to verify your identity before acting on a request.

Some service providers may store or process information outside Australia. Where this occurs, we take reasonable steps to use reputable providers and appropriate safeguards for the information being processed.

This policy may be updated from time to time. The latest version will be published on this page with the effective date above.