Skip to workspace

Privacy policy

How this preview handles local SVG work, browser processing, AI inputs, accounts and cookies.

Last updated: 2026-11-19

Browser editing and exports process source content on your device. Image tracing and SVG validation, minification and recoloring run locally in browser background workers without uploading source content. AI generation sends submitted instructions and, for refinement, the supplied SVG to the configured model provider. This notice describes the current preview, not a finalized public-launch policy.

Processing on your device

Code-card rendering, static SVG preview, element editing, vector resizing/cropping, PNG/JPG/WebP/PDF/ICO/DXF export and batch export run in the browser. These workflows do not intentionally upload the source artwork to an application API. Downloads are saved on your device. Loading the application itself still makes normal page and asset requests.

SVG drafts and AI text/settings are kept in this tab’s memory for supported page navigation. The application does not automatically persist these source drafts in localStorage or sessionStorage. Refreshing, closing the tab or a full authentication redirect can clear them.

Processing on this server

The public preview does not send image-tracing or SVG-processing input to application endpoints. A worker runs locally and is terminated after each task or a 60-second limit. Loading pages, JavaScript and WebAssembly still makes normal network requests. Hosting services may retain access/security logs. AI, account storage, sign-in and payments remain closed in this public release.

Explicit project saves and palettes

Choosing Save project uploads the static SVG and project name to the configured account database. Saved versions retain the artwork and timestamps; color presets retain their names and HEX colors. Prompts and original raster inputs are not saved with a project. The project is private to its account in the application. This local preview is not production cloud storage.

Archive hides a project from the active list and is reversible; it does not erase its versions or free its budget. No automatic history expiry or self-service permanent deletion is implemented. Project data remains in the configured database and any operator-created backups until a reviewed retention/deletion process is provided.

Anonymous tool observations

The application records UTC day, tool name, event type (start, success, failure or download request) and aggregate count. The observation table does not store artwork, prompts, account identity, a persistent visitor identifier or URL query strings. An IP-based rate bucket and random event IDs exist temporarily in server memory for abuse control and duplicate suppression, not in the observation table. Do Not Track and Global Privacy Control suppress these client observations. Counts are not unique visitors, guaranteed physical downloads or billing evidence. Optional analytics services below have separate behavior.

AI providers

Only a submitted generation or refinement request sends instructions and any supplied refinement SVG to the configured provider. The current integrations are HiAPI and an explicitly selected OpenAI route. Provider processing, retention and permitted use depend on that provider’s actual terms and configuration. Do not treat the preview as confidential storage or submit sensitive material without the required authorization.

The local AI service retains a bounded in-memory request/result map for duplicate-request handling. It is cleared when the server restarts or when the next eligible request resets the hourly window; expiry is not an exact scheduled deletion guarantee. Public account quotas and durable task history are not connected.

Accounts and messages

Registration stores account identity and authentication records, including name and email. Session records can include IP and browser information. A configured email provider receives the recipient and verification/reset message when that feature is used. Account records persist separately from temporary conversion data; closing the tab does not delete an account.

Cookies, site preferences and optional services

Essential sign-in cookies maintain sessions. A first-party utm_source cookie can retain a sanitized referral-source label for up to 30 days when a tagged link is opened. The locale cookie remembers language; browser storage may hold theme preferences. Clearing cookies may sign you out and does not erase server-side account records.

The application can load analytics, advertising or support integrations if an administrator configures them. They can process visitor, device or support information under their own policies. The enabled providers, identifiers, consent requirements and retention must be inventoried before public launch; this preview does not claim that all deployments are tracker-free.

Control, requests and preview limits

Do not submit files you are not authorized to share. Download outputs you want to keep. Profile settings allow supported account changes; the local preview offers explicit project history but has no self-service permanent project or account-erasure workflow. Privacy and data requests can be sent to support@svglume.com; see contact for what to include. Requests require review and do not trigger automatic deletion. Operator identity and a fully verified rights-request procedure remain prerequisites for public account service.

See help and the terms for the current service scope.