Privacy Policy

Last updated: April 3, 2026

1. Introduction

Scouthook (“we,” “us,” or “our”) helps you create LinkedIn content that matches your voice. The Scouthook application may connect to LinkedIn on your behalf so you can publish content when you choose. This Privacy Policy describes how we collect, use, store, and protect your information.

If you have questions about this policy or your data, contact us at privacy@scouthook.com. Until that inbox is live, use the same personal email you use to reach the Scouthook team (for example the address from your account or onboarding).

2. Data we collect

We may collect the following categories of data:

• Profile fields (stored in our database): Information you provide in the product, such as audience role, audience pain, content niche, and contrarian view.
• Writing samples: Text you submit for one-time voice extraction. Samples are processed using Claude (Anthropic) to generate a voice fingerprint. Raw writing samples are not retained after the fingerprint is generated.
• LinkedIn OAuth tokens: When you authorize Scouthook, we receive and store an access token and refresh token so the app can perform actions you request. Tokens are stored encrypted at rest using AES-256-GCM.

3. How we use LinkedIn data

This section is important if you connect a LinkedIn account:

• LinkedIn tokens are used solely to publish posts on your behalf when you explicitly click Publish or confirm a scheduled post. We do not use your tokens for any other automated action.
• We do not read your LinkedIn feed, connections, messages, or profile data beyond what is needed to identify your member ID for authorized publishing.
• We do not sell, share, or use LinkedIn data for training general-purpose AI models or for advertising unrelated to operating Scouthook for you.
• The LinkedIn scope we request is w_member_social (posting on your behalf as permitted by LinkedIn’s platform).

4. Data storage and security

• Application data, including profile fields and encrypted tokens, is stored in a SQLite database on servers hosted with Vercel (or equivalent cloud infrastructure we use to run the service).
• LinkedIn tokens are encrypted with AES-256-GCM. Encryption keys are managed securely and are not stored in source code or public repositories.
• Generated images (PNG/ZIP exports) are automatically deleted within 24 hours of generation unless a shorter retention period applies for operational reasons.

5. Data retention

• LinkedIn tokens: Removed immediately when you disconnect your LinkedIn account in Scouthook or revoke access through LinkedIn.
• Profile and post-related data: Retained until you request deletion or delete your account, subject to legal or security requirements.
• Full account deletion: Available on request. We will remove your data within 30 days of a verified deletion request, unless we must retain certain information where required by law.

6. Your rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you;
• Correct inaccurate data;
• Delete your account and associated data (see Section 5);
• Withdraw LinkedIn authorization at any time via LinkedIn’s app settings or by disconnecting in Scouthook.

To exercise these rights, contact us at the email addresses listed in Section 1.

7. LinkedIn API compliance

Scouthook is designed to comply with LinkedIn’s API Terms of Service and Developer Policy. Data obtained through LinkedIn APIs is used only for the purposes described in this policy (for example, publishing content you initiate) and not for undisclosed or incompatible uses.

8. Contact

General and privacy inquiries: privacy@scouthook.com. If that mailbox is not yet active, use your usual Scouthook contact email so we can respond within 48 hours for LinkedIn-related questions.

For questions specifically about LinkedIn data, we aim to respond within 48 hours.

9. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email (if we have your address) or through an in-app notice. The “Last updated” date at the top will reflect the latest revision.