EFFECTSENGINE / VISUAL STUDIO
Privacy & local storage
This page describes the behavior implemented in this EffectsEngine codebase. The operator should add their identity, contact details and provider-specific policies before public deployment.
Your creative work stays on this device
Editing, rendering and exports run in your browser. Projects are autosaved to this origin’s browser storage. The editor can cache its application files for offline use. Export a .effects backup before clearing browser data or changing devices. Network-menu links open the selected app separately; they do not transfer your project.
The shared advertising sidebar
When enabled and the desktop sidebar is visible, EffectsEngine requests placements from the configured PicPlayer ad manager. Requests contain the public app ID, placement ID and applicable consent information—not project names, canvas pixels, images or document contents. The manager receives ordinary connection information such as an IP address and browser request headers, and may record placement decisions and rendering, viewability, click or failure events.
The shared SDK does not create persistent advertising identifiers and omits credentials on its manager API requests. Its default mode allows contextual text ads. Third-party network creatives require an explicit permission signal from the publisher’s consent platform and a compatible manager configuration. Creative frames are sandboxed separately from the editor and the administrator interface.
Your choices
Use Ad choices in the sidebar or profile menu to withdraw network permission or hide advertisements on this device. The hide preference is stored locally and can be reversed in that dialog. Global Privacy Control and Do Not Track prevent the SDK from granting network permission; contextual text ads may still be shown. The built-in dialog does not grant network consent and is not a consent-management platform.
External services
Opening an app through the Network menu takes you to a separate site with its own policies. This EffectsEngine package does not implement account login, cloud synchronization or a live consent provider. Those services must be configured and reviewed by the deploying operator.