Privacy Policy

What this site is

Screenstuck presents brand collections of community clips and links to the original creators, products and services, including destinations such as YouTube or Spotify. We measure how those pages are used so we can operate the service and understand which clips and ads work.

Connected platform data

Google sign-in identifies your Studio account. YouTube, Instagram, TikTok and X connections separately verify the accounts that publish your clips. Only features and permissions enabled for a platform are offered. Screenstuck does not provide private TikTok, Instagram or X analytics through the current creator-verification connections.

We use permitted account identifiers, handles and available profile information to link your account, check video authorship and show creator credit. We use available post links, titles, captions, thumbnails and media identifiers to import and preview the video you select. We store encrypted OAuth credentials where supported so the authorized feature can work. We do not receive your social account password or request access to private messages.

Only separately authorized YouTube brand connections provide private channel analytics. API data is not sold, used for ad targeting or used to train general-purpose AI models. It is shared only as needed to provide the feature you request, including with the authorized brand team and service providers, or where required by law. Our optional Meta ad measurement uses Screenstuck viewing events. It does not include connected-account access tokens or private source-platform analytics.

Screenstuck’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. People do not read Google user data except with your affirmative agreement for specific information, as necessary for security or applicable law, or as otherwise permitted by those requirements.

Remove a creator connection in My accounts to delete its stored credentials from Screenstuck. Revoke the app’s permission in the platform settings linked above to stop platform access. These are distinct actions. Brand owners manage YouTube reporting connections in their brand workspace. To request deletion of other stored account data, follow our data deletion instructions.

Studio and Google sign-in

Google sign-in shares your Google account identifier, verified email and name with Screenstuck. We use these to authenticate you, match email-bound invitations and enforce workspace roles. Signing in does not connect YouTube automatically. A separate consent step is required for each channel.

We store your account and workspace memberships until they are removed or you request deletion. Secure sign-in sessions last up to 30 days. Your name and email are visible to fellow workspace members. Owners manage memberships and connected accounts. Editors manage videos and calls to action. Viewers can read workspace content and analytics. Invitation links expire after seven days.

Sign out to end the current browser session. Contact contact@screenstuck.com to request account deletion. We handle deletion requests within seven days. Workspace content belongs to the workspace and may remain when a teammate leaves.

Clip submissions and review

Creator submissions require ownership verification for the source account. If you choose the optional native sign-in for YouTube, Instagram, TikTok or X, we read your provider account identifier, handle and the post information needed to confirm authorship. We store encrypted access and refresh credentials where supported. Alternatively, we read a temporary verification code from your public profile bio. Bio codes expire after 30 minutes and verified bio accounts after 30 days. Connected accounts require renewal after up to 30 days. Access may end sooner if revoked. Remove accounts in My accounts to delete their stored credentials. This does not revoke platform-wide permissions. You can also revoke those in the platform’s own app settings.

Apify processes public profile and video links for metadata imports and bio-code verification. We send the public link to a hosted scraper, then read the account’s permanent platform identifier, handle, bio and available video details. No social password or platform access token is sent to Apify. Lookup records in Screenstuck are retained for up to 24 hours and removed on the next lookup. Verified account identifiers remain until removed, and submission ownership and licence records remain with the submission. Apify also stores scraper runs and their public results under its service retention settings. We do not load an Apify connection script in your browser.

We retain a record of the verified provider account, verification method and time with submitted clips so the brand can assess their provenance. Disconnecting an account does not erase that historical submission evidence. These ownership connections do not grant us permission to post, edit your social account or read private messages. Temporary clip links and text are saved in this browser tab to let you return after verification. Original files and licence consent are not saved in browser storage.

When you submit a clip, we store your account identifier, selected brand, source link, available post details, uploaded original, playback copy, thumbnail, review history and the exact licence wording, version and time you accepted. Your name and submission are visible to the selected brand’s team. Other creators cannot see your private submissions. Imported creator credit and clip details may appear publicly when the brand publishes the clip. For submissions with the business Content Licence, Momentist, Inc. and the selected brand may also use and edit submitted content for business, advertising, marketing and content/performance analysis, including outside Screenstuck. Brands are responsible for their own uses and applicable privacy obligations. The content licence does not replace a lawful basis for personal-data processing or opt you into unrelated tracking or advertising cookies.

Original uploads use private storage and are scheduled for deletion after 30 days. Playback copies and review records are retained for the submission and collection until deleted. You can withdraw a clip to remove it from review and the public collection, or contact us to request file deletion. Withdrawal does not itself revoke an agreed business Content Licence. Applicable privacy and data-protection rights remain available. Licence acceptance records may be retained where necessary to document permissions and resolve rights disputes, subject to applicable law. Loading a source embed connects your browser to YouTube, Instagram, TikTok or X, whose own privacy practices apply.

Connected YouTube channels

When a promoted channel owner connects through Google, Screenstuck uses YouTube API Services to verify the selected channel and read views, watch time, subscriber gains and losses, and external traffic sources. Workspace members and Screenstuck administrators use these reports to review channel performance in the context of promotion. These reports do not identify individual viewers or prove that Screenstuck caused a subscription.

We store the channel ID, channel name, handle and artwork, granted permissions, connection timestamps and encrypted authorization credentials in our hosted database. During brand setup, you review the channel before its name and artwork become your brand profile. Pending setup credentials are encrypted, expire after twenty minutes of review, and are removed when you finish, cancel, sign out or start again. Expired attempts are also cleared when a new setup begins. Reports are fetched on demand and are not saved in our database. Authorization cookies keep the connection process secure and let the connecting browser manage its connection for 30 days. We do not collect Google passwords or request permission to edit channels, read Gmail or access revenue.

YouTube data is not sent to Meta, used for advertising targeting, sold or used to train AI models. Screenstuck’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. See also the Google Privacy Policy.

Workspace owners can disconnect channels in Studio, under Accounts. You can also use Disconnect YouTube in the browser that connected the channel to delete the saved connection and credentials and request revocation at Google. Disconnecting removes the saved connection credentials. Your Studio brand, content and channel claim remain so disconnecting cannot allow another person to claim your Studio. Contact us to delete the brand and claim. This does not delete anything on YouTube. You can revoke access through Google Account connections at any time. If the browser session has expired, contact contact@screenstuck.com to request deletion. We handle deletion requests within seven days. Authorization is checked before reports are loaded.

Information we collect

• Random identifiers for a click, a viewing session and a returning browser. They are not linked to your name or an account.
• Usage events: which clip was shown, how much of it played, buffering and errors, feed continuation, and which destination link was tapped.
• Interaction diagnostics: touch and click positions within the player and linked privacy page, bounded gesture paths, sampled control sizes, visibility and obstruction, and whether playback, sharing, navigation requests or privacy saves responded. Privacy-choice values are not included in these traces. These first-party diagnostic traces currently have no automatic expiration or fixed retention period, are not sent to Meta, and do not include typed text or screen recordings. The current tab can retain a bounded amount of undelivered usage events and diagnostic batches in session storage until delivery is acknowledged. Older entries may be discarded when the queue fills, and closing the tab or clearing browser data removes this recovery copy. Tab session storage also connects a privacy-page interaction to the player visit that opened it.
• Technical data: IP address, User-Agent, browser, operating system and version, device model, viewport dimensions in CSS pixels, coarse country and region, network operator, and page referrer.
• Advertising data: campaign, ad set, ad, creative, placement and source parameters in a link, plus a Meta click identifier (fbclid) when Meta supplied one.

Watching clips does not require a name, email address, phone number or account. If you email us, we receive your email address and the information you include so we can respond to your enquiry. We do not use the Meta Pixel or any third-party analytics script. A small first-party script records playback events. The current tab also uses session storage to keep reloads in the same viewing path. We do not use script-based fingerprinting.

Cookies

• ss_vid is a random first-party browser identifier used for first-party reach and repeat-visit measurement. It lasts up to 400 days and page scripts cannot read it.
• When Meta ad measurement is on, _fbp identifies the browser for Meta matching and_fbc retains a Meta click identifier when one is available. They are first-party, server-readable cookies lasting up to 90 days. No Meta script runs on the page.
• ss_meta_optout saves an opt-out for up to 400 days. Opting out removes _fbp and_fbc. Browser limits or clearing site data may shorten any of these periods.

How we use it

We use the information to run the player, measure viewing, sound, sharing and destination interactions, prevent scanners and test traffic from distorting results, improve clips, and measure and optimise ads we run. We do not use it to build a profile of your activity across unrelated sites.

Third parties

Our service provider is Microsoft Azure (Container Apps, Azure Database for PostgreSQL, Blob Storage, Front Door and Log Analytics), hosted in the United States. An app whose in-app browser opens Screenstuck may inject its own code and observe the page under that app's privacy policy. Destination links lead to sites with their own policies.

Ad measurement with Meta. When the choice above is on, our server can send Meta Platforms, Inc. selected Conversions API events: visible clip start, an engaged view, successfully turning on sound, pressing Share, starting another clip, reaching selected feed depths, a primary destination CTA tap without a watch requirement, and a separate brand-link destination tap only after a qualifying watch. Legitimate human events may be sent even when the current link has no fbclid. We exclude marked QA traffic, desktop traffic used by our campaign path, known scanners and browsers reporting automation.

A report can include _fbp, _fbc, IP address, User-Agent, the Screenstuck source URL, the page referrer, and clip and ad fields. Where ss_vid exists, our server derives a Meta-dedicated, one-way SHA-256 external_id. The raw ss_vid is not sent. Meta uses these fields to match, attribute, measure and optimise ads. Nothing in the browser sends directly to Meta.

Your choices and Global Privacy Control

The control at the top of this page stops future Meta sharing from this browser, removes the Meta cookies, and cancels or redacts pending unsent Meta events that we can associate with its ss_vid. Internal service measurement continues. Events already sent or in flight cannot be recalled. You can allow future measurement again, but old click records remain blocked from Meta so events collected while opted out are not replayed.

We also honor the Sec-GPC: 1 Global Privacy Control signal automatically. GPC overrides the on-page allow choice while the signal is active. We do not respond to the older Do Not Track signal because it does not express the same opt-out request.

Reviewing or changing your information

We do not link contact enquiries to viewing identifiers, so we cannot reliably look up pseudonymous viewing records by person. Use the browser choice above at any time. Questions: contact@screenstuck.com.

Retention

Raw event and click records are kept for 13 months, then only aggregated statistics remain. A pending Meta outbox payload is kept for no more than seven days and its matching fields are redacted after delivery, permanent failure or opt-out cancellation. Cookie periods are described above. Contact correspondence is retained as needed to respond to and resolve your enquiry and meet applicable legal obligations. It has no fixed deletion schedule.

California residents (CCPA/CPRA)

As of the effective date, Momentist, Inc. is not a “business” covered by the CCPA/CPRA for this service (revenue below the threshold). We nevertheless provide and honor the privacy choice above and revisit this section if the service or applicable requirements change.

Changes

Changes to this policy are posted on this page with a new effective date.