Effective date: August 14, 2026
WebMotion Capture converts the visible browser viewport selected by the user into structured design data for Adobe After Effects. This policy explains what information the Chrome extension handles, why it is needed, where it goes, and how users can remove it.
This policy applies to the WebMotion Capture Chrome extension.
WebMotion does not capture webpages automatically or in the background. Processing begins only after the user deliberately selects Direct Send or Collect.
When the user starts a capture, the extension may locally process:
A screenshot of the visible browser viewport.
Visible webpage text, typography, images, SVGs, icons, visual assets, backgrounds, charts, media, layout, geometry and computed styles required to reconstruct the design.
Accessibility labels, semantic roles and short element identifiers needed to create understandable editable layers.
Visible, non-password form-control text and selected options when required to reproduce the visible interface.
The selected page’s sanitized URL, hostname, title, capture time and viewport information.
Sanitized image and asset URLs required to retrieve visual resources from the original webpage.
Canonical scene, paint-order, geometry and resolver diagnostics used to create and troubleshoot the capture.
The user’s locally stored capture-disclosure choice.
A randomly generated local pairing credential, connection protocol state, temporary Direct Send packages and retry status.
Password-field values, hidden-input values, file-input values, URL credentials, query parameters and URL fragments are excluded from persisted capture data.
A screenshot is a literal image of the visible browser viewport. It may contain private information displayed on the selected page. Users should capture only content they own or are authorized to process.
Under the Chrome Web Store’s standardized disclosure categories, WebMotion Capture handles:
Web history: the sanitized URL, hostname and title of the specific page selected by the user for capture.
Website content: the visible screenshot, text, images, layout, styles and other visual information needed to reconstruct the selected design.
WebMotion does not use this information to build a browsing profile or track browsing activity across websites.
Captured information is used only to:
Create a portable WebMotion capture package.
Reconstruct the selected webpage design as editable layers in Adobe After Effects.
Transfer a user-requested capture to WebMotion Builder on the same computer.
Retry an interrupted local Direct Send transfer.
Diagnose capture and scene-generation results using sanitized local diagnostics.
WebMotion does not use captured information for advertising, analytics, profiling, behavioral tracking, credit decisions or any purpose unrelated to its website-to-After-Effects functionality.
When the user chooses Direct Send, the extension transfers the capture only to WebMotion Builder running with Adobe After Effects on the same computer.
The transfer uses the authenticated loopback address:
http://127.0.0.1:43821
The local connection uses origin restrictions, randomly generated credentials, one-use challenges and authenticated request and response proofs.
Direct Send does not upload the capture to a WebMotion-operated internet server.
When the user chooses Collect, the extension creates a portable ZIP package and saves it to the user’s computer through Chrome’s Downloads feature.
The package may contain:
Structured WebMotion design data.
A reference screenshot.
Captured visual assets.
Sanitized observation, paint and resolver diagnostics.
The downloaded package remains under the user’s control until the user moves or deletes it.
When necessary to complete a capture, WebMotion may request an image or visual resource from the original webpage or resource host.
These requests are made only to retrieve assets needed for the user-selected capture. WebMotion does not use them for tracking, advertising or analytics.
The original webpage and resource providers may apply their own privacy policies to those requests.
WebMotion uses the following Chrome permissions only for its disclosed capture functionality:
activeTab: temporarily accesses the webpage explicitly selected by the user.
scripting: runs the capture collector in the selected active page.
downloads: saves user-requested Collect ZIP packages.
storage: stores local settings, disclosure acceptance and the local Direct Send pairing credential.
alarms: schedules retries for interrupted Direct Send transfers.
unlimitedStorage: temporarily stores large pending Direct Send packages in local IndexedDB.
debugger: applies and verifies mobile device metrics, touch emulation and viewport capture only when the user activates Phone mode.
Host permission for 127.0.0.1: communicates only with WebMotion Builder’s local authenticated bridge.
When Phone mode ends, WebMotion clears its device-emulation overrides and detaches the Chrome debugger connection. The debugger permission is not used for background monitoring, remote debugging or unrelated browsing activity.
WebMotion Capture does not send captures to WebMotion-operated internet servers.
The developer does not automatically receive:
Captured screenshots.
Website text or images.
Browsing URLs.
WebMotion packages.
Adobe After Effects project content.
Captured information is not sold, rented, shared with advertisers or made available for human review.
If a user voluntarily sends a capture or project to WebMotion for technical support, that information is handled only for the support request authorized by that user.
WebMotion stores information locally as follows:
Settings, disclosure acceptance and the local pairing credential remain in Chrome extension storage until the user clears the extension’s data or uninstalls the extension.
Direct Send packages remain temporarily in local IndexedDB while a transfer is pending.
A successfully transferred Direct Send package is removed from the Chrome transfer queue.
An interrupted or failed transfer may remain locally for retry until it succeeds, the extension’s data is cleared or the extension is uninstalled.
Downloaded Collect packages remain until the user deletes them.
Files imported into Adobe After Effects remain under the user’s control until the user removes them.
WebMotion does not maintain a remote server copy of these captures.
WebMotion limits webpage access to user-initiated capture actions and uses the narrowest Chrome permissions needed for its features.
Direct Send is restricted to the local computer and uses authentication and integrity checks to prevent unauthorized local applications from impersonating the WebMotion Builder connection.
Users should treat captures from private or authenticated webpages as sensitive files. No local storage or transfer system can be guaranteed completely secure.
WebMotion Capture does not download or execute remote JavaScript or WebAssembly.
All extension functionality is included in the extension package reviewed by the Chrome Web Store. External webpage resources may be retrieved as data or visual assets, but they are not executed as extension code.
Users can:
Cancel a capture before any page information is processed.
Choose Collect instead of Direct Send.
Clear WebMotion Capture’s Chrome extension data to remove settings, pairing information and pending local transfers.
Uninstall WebMotion Capture to remove its Chrome-managed local storage.
Delete downloaded Collect packages independently.
Remove imported WebMotion files and After Effects project content independently.
WebMotion does not capture webpages in the background.
WebMotion Capture’s use and transfer of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information is used only to provide or improve WebMotion’s clearly disclosed website-to-After-Effects capture functionality.
WebMotion does not use or transfer captured information for personalized advertising, retargeting, unrelated analytics, creditworthiness, lending, profiling or any unrelated purpose.
This policy may be updated when WebMotion Capture’s functionality, data practices or legal obligations change.
The effective date at the top of this page identifies the latest revision. Material changes to data handling will be disclosed as required before the changed practices take effect.
For privacy questions or deletion assistance, contact:
m.elazrouri@gmail.com