Privacy Policy
  Last updated: 9/2/2025

  1. Who we are

  - Secure Consulting Solutions, LLC (“we,” “our,” “us”) provides a community & engagement console that helps authorized users manage LinkedIn posts and conversations under their own accounts and (where permitted)
  organization pages.

  2. Scope

  - This Policy explains how we process Personal Data when you use our application and related services (the “Service”). It covers data we collect directly, data obtained via LinkedIn APIs (and
  optional, customer‑enabled integrations), and your choices.

  3. Data we process
     A) You provide

  - Account identifiers (e.g., username), name (optional), organization (optional).
  - Authentication artifacts: LinkedIn OAuth access tokens (we never see your LinkedIn password).
    B) From LinkedIn (via your consent and scopes)
  - Post and engagement metadata: post/comment/reaction URNs, text you or others publish, timestamps, counts.
  - Basic profile fields exposed by LinkedIn for moderation display (e.g., name, headline, public profile URL, profile image when available).
  - Page/post analytics available under approved products/scopes (e.g., comment/reaction counts; impressions/clicks where permitted).
    C) Optional, customer‑enabled integrations
  - Publer (publishing/scheduling) and Apify (discovery) may process URLs, text, timestamps, and public profile/page information necessary to perform their functions.
    D) System metadata
  - Audit logs, request UUIDs, IP address, user agent, and operational telemetry.

  4. How we use data

  - Provide and secure the Service (auth, role‑based access, abuse prevention).
  - Community management: queue/triage comments, post or reply (member or page, subject to roles), measure responsiveness (e.g., time‑to‑first‑response), and display lightweight analytics.
  - Troubleshoot and improve features (aggregate and de‑identified usage patterns).
    We do not sell Personal Data, do not use it to build advertising profiles, and do not conduct contact harvesting.

  5. Legal bases (EEA/UK)

  - Performance of a contract (to deliver the Service you request).
  - Legitimate interests (security, audit logging, service improvement proportionate to risk).
  - Consent (LinkedIn OAuth scopes you approve; where required by law).

  6. Sharing & processors

  - We use vetted subprocessors to operate the Service, such as:
      - Hosting & infrastructure (e.g., container runtime, database/redis).
      - Optional, customer‑enabled: Publer (publishing) and Apify (discovery).
      - Monitoring/logging (operational telemetry).
        We require appropriate confidentiality, security, and data protection commitments via contract.

  7. Data retention

  - OAuth tokens: retained while linked; deleted promptly on disconnect or token revocation.
  - Content/engagement metadata (URNs, timestamps, counts, comment text for moderation): retained for the shorter of your configured retention or 24 months; you may request earlier deletion.
  - Audit logs: ~30–180 days (operational needs).
  - Backups: follow rolling schedules and are purged per policy.

  8. Security

  - Encryption in transit (HTTPS/TLS); encryption at rest where supported.
  - Role‑based access control, least‑privilege service accounts.
  - Audit logging with request IDs; rate‑limit/backoff with LinkedIn APIs.
  - Segregated environments and periodic hardening reviews.

  9. Your choices & rights

  - Disconnect at any time: unlink LinkedIn from within the app or via LinkedIn Settings → Apps & services. Disconnect removes tokens and halts processing.
  - Access, correction, deletion, portability, and objection (where applicable by law). Contact us at [Contact Email].
  - We will verify requests and respond in accordance with applicable law.

  10. International transfers

  - If data is processed or accessed outside your country, we rely on appropriate safeguards (e.g., SCCs or equivalent) as required by law.

  11. Children

  - The Service is not directed to children under 16 (or as defined by local law). We do not knowingly collect children’s data.

  12. Changes

  - We may update this Policy to reflect changes to the Service or law. We will post a “Last updated” date and, where required, provide notice.

  13. Contact

  - Controller: Peter Paccione
  - Email: ppaccione@securesolutionsdc.com
  - If you are in the EEA/UK, you may lodge a complaint with your supervisory authority, but we encourage you to contact us first.

  Product‑specific notes

  - LinkedIn permissions: We request only the scopes you approve (e.g., w_member_social_feed, and if enabled for your org, r_/w_organization_social(_feed)). All actions run under the
  authenticated member token; page actions require a valid page role.
  - Minimal display: In moderation views, we show only the fields the APIs provide and needed for context (e.g., name, headline, public profile URL, avatar, comment text, timestamps, counts). No
  emails or private messaging are surfaced to moderators.
  - Optional integrations: Publer/Apify are disabled by default; enabling them is a customer choice and subject to their terms & privacy policies. You can disable them at any time.

  If you have any questions about this Policy or our data practices, please contact contact@securesolutionsdc.com