JUCEY Extension — Privacy Practices

Last updated: May 25, 2026

1. Anonymous engagement signals (default ON)

When you scroll a LinkedIn or X feed and a post stays visible for at least 0.8 seconds, we record:

• The platform (LINKEDIN or TWITTER).
• The author’s public handle (e.g. @elonmusk).
• Any hashtags visible on the post.
• How many milliseconds the post was on screen.
• Whether you clicked Like, Repost, or Comment on it.

We use this to point our paid scraper at the creators and hashtags real users actually read — nothing else. We never store the post URL, post body, post id, author display name, or your identity in this dataset. Raw rows are deleted automatically after 7 days; only an anonymised, per-author rollup is kept.

You can turn this off any time in the extension’s Options page (“Share anonymous engagement signals”). When off, no engagement data leaves your browser.

2. Trend pool post metadata (default OFF — opt-in)

If — and only if — you explicitly enable “Contribute post metadata to the JUCEY trend pool” in Options, the extension also pools the following public surface fields of posts you scroll past:

• Post URL (e.g. https://x.com/jack/status/1234...).
• Author handle and display name as shown on the post.
• Hashtags + media types (image / video / poll / article).
• Public engagement counts (likes / comments / reposts).
• The post’s public timestamp.

We still never store the body of the post, and the pooled record is not tied to your account— we only increment an aggregate “contributors” counter so we know roughly how many JUCEY users have seen each post. Pooled rows expire after 28 days and are deleted by an automated cleanup job.

Toggle this off any time and we immediately stop pooling. Already- pooled rows that refer back to public LinkedIn / X URLs will roll out via the 28-day TTL; you can email dpo@jucey.app to request earlier deletion.

3. Engagement learning (default ON, per-user only — never pooled)

When you like, repost, comment on, or bookmark a post on LinkedIn or X, the extension records the action together with the post body, the author, hashtags, and (for comments) the text you wrote. We feed this into your own voice and interest profile so JUCEY gets better at writing in your voice about the things you actually care about.

Specifically:

• Comments you write are the highest-value signal — they’re your actual words on a target platform. Phrases extracted from them are added to your preferredPhrases list with a weighted-decay model (frequent phrases stick, stale ones fade).
• Likes / reposts / bookmarks reveal what topics you’re drawn to. Hashtags + keywords from those posts feed your recurringThemes so the prompt knows what subjects to lean into.
• Recent engagement snippets (capped to 12, ~300 chars each) are kept in your voiceProfile as on-platform context the AI can cite.

This data is per-user only. Engagement rows are scoped to your account, never pooled, never shared with other JUCEY users, and deleted automatically after 90 days. Account deletion wipes the entire history immediately (cascade).

Toggle off any time via Options → “Learn from posts you like, repost, comment on, or bookmark”. Already-learned signal stays in your voice profile (because you’d notice if the AI suddenly forgot how you write); email dpo@jucey.app for a full reset of preferredPhrases / recurringThemes / engagement rows.

4. Public-content-only boundary

The launch extension does not request Chrome’s cookies permission, read LinkedIn or X session cookies, or send social-network credentials to Jucey or its processors. Jucey uses public post/profile evidence plus actions you explicitly take in the extension.

Because LinkedIn does not expose private author-only impression analytics publicly, Jucey does not claim those numbers unless they come from a separate, explicit user-provided source. Public likes, comments, reposts, and visible view counts may still be used as labeled reach signals.

5. Saved clips (always explicit)

When you click the orange JUCEY button on a post, the post body, author, and your juiciness rating are sent to your private JUCEY library. This is the only path on which we ever transmit a post body, and it’s always initiated by an explicit click. Saved clips are visible only to you.

6. Diagnostic telemetry (default ON, anonymous)

We record event names like popup_opened and clip_saved with no payload other than the extension version. This is purely so we can detect bugs and crashes. Toggle off in Options if you’d prefer not to share these.

7. Permissions

• storage — saves your JUCEY API token + UI settings locally in chrome.storage.local.
• scripting — injects the Save / Watch buttons on LinkedIn and X tabs that are already open at install time, and re-runs the silent token mint on the jucey.app tab when the user signs in. Limited to the host_permissions declared below.
• alarms — runs an hourly opportunistic refresh of the scoped JUCEY API token.
• contextMenus — right-click → Save to JUCEY / + Watch this author. Menu items appear only on the declared host pages.
• Host permissions: linkedin.com, x.com, twitter.com (legacy redirect to x.com), youtube.com, substack.com, and jucey.app. Nothing else.

8. Your rights

You can revoke the extension’s access at any time (Options → Reset extension data, or remove the extension entirely). For data deletion, account export, or any other GDPR / CCPA request, email dpo@jucey.app.