Deployment template: the operator must review this description, identify itself, add contact and retention details, identify its actual advertising and identity providers, and publish its policy before public use. Hosting and service practices depend on the deployment.
DrawDomain processes vector documents in your browser. It stores open-document recovery data in IndexedDB, with localStorage as a fallback. Use File → Clear local recovery data to remove the current recovery snapshot. Later editing or opening and closing tabs creates new recovery data. Exported files are downloaded to your device.
When a ZenID backend is configured, the editor checks your sign-in status through its own server. Signing in redirects to the configured ZenID service. The server uses HTTP-only cookies to manage the sign-in flow and session. The profile shows your display name or email; authentication tokens are kept on the server, not in browser storage.
This DrawDomain integration does not upload documents when you sign in. Network links and Browse DocDome open the separate selected application in a new tab. Those services handle data according to their own policies.
When enabled, a desktop advertising sidebar uses PicPlayer’s shared ad manager. The sidebar is hidden below a viewport width of 1280 pixels and does not cover the canvas. The supplied browser integration does not send drawing contents, canvas pixels, image files, document names, clipboard contents or signed-in profile details to that manager.
Ad requests contain the public application ID “drawdomain,” placement IDs, consent flags and permitted network IDs, consent strings when supplied by a consent platform, and identifiers for failed ad sources. Delivery reports use temporary ad-decision tokens and events such as a reported fill, viewability, failure and direct-ad click. As with other network requests, the receiving service also receives connection information such as an IP address and browser request headers. The sidebar itself does not create persistent advertising identifiers or send account cookies to the manager.
The default is no advertising consent: only eligible contextual text creatives may be selected. Remote-image and third-party network creatives require explicit network permission passed from a connected consent platform. Browser Global Privacy Control or Do Not Track signals restrict the sidebar to contextual mode. If the manager is unavailable or has no eligible inventory, the sidebar can show a local informational card instead of a paid advertisement.
Use Ad choices in the sidebar to open a connected consent platform’s preferences. Without one, an explanatory panel offers Use contextual ads only, which immediately removes previously consented ad frames for this visit. That panel never grants advertising consent and does not replace a consent-management platform. A connected platform must save and apply choices across visits; this local fallback does not save a consent record.
The operator must identify the actual enabled networks, their purposes, privacy policies, retention practices and applicable consent arrangements here. Approved providers may process additional information inside their isolated advertising frames according to their policies. No live advertising account or production consent platform is supplied in this code package.
The supplied editor adds the advertising integration described above, not a separate analytics product. The operator should disclose hosting logs, any additional integrations, retention periods, and how users can contact it here before deployment.