Privacy Policy

We process the request and product data needed to serve browsing, search, prompt detail pages, and copy actions. If you choose to sign in, Inspia stores your email, display name, provider details, sessions, and necessary authentication records in its own account system. Authentication cookies are functional and separate from anonymous analytics.

Google processes Google sign-in. Resend delivers email sign-in codes and account-deletion confirmation links. Those services receive only the data needed for the action you request. Inspia does not use your Google account to call unrelated Google APIs.

You can edit your display name, sign out, or request permanent account deletion from the Account page. Deletion requires a short-lived confirmation link sent to your email and removes the Inspia account, linked sign-in providers, active sessions, and related verification records.

Saving prompts requires an Inspia account. Saved prompt identifiers are stored under your Inspia user ID so they are available across your signed-in devices and are not shared with other users. Signed-out visitors do not create a local Saved collection.

Images you explicitly save with the Inspia extension are also stored under your account with their source page, title, and alt text. An Analyze or Generate action does not add the image to Saved.

Signing out removes Saved prompts from this browser's memory but does not delete them from your account. Confirmed account deletion removes the account's Saved rows and schedules private uploaded and generated media for removal from Inspia's object storage.

The image Discover feed can use your recent views, prompt opens, successful copies, uses, and saves to adjust later recommendations. A signed functional cookie keeps a limited set of prompt identifiers and actions for up to 30 minutes of inactivity. This short-term state is not applied to another account.

When you are signed in, your account-owned Saved prompts also inform recommendations. We also store a summary of your aesthetic preferences in your account, based on prompt opens, copies, and uses reported from the image Discover feed. This summary works across signed-in devices and gradually loses influence without new activity. Temporary prompt identifiers, action strengths, and timestamps prevent duplicate contributions; expired entries are cleaned up during later feedback processing.

Private drafts, clipboard text, uploaded reference images, and private generated results are not included in this recommendation state or sent to analytics or model providers for homepage ranking. You can clear site cookies to remove the short-term state and remove Saved prompts from your account. Clearing cookies or signing out does not delete your account's aesthetic summary. Account deletion removes the summary and its related duplicate-prevention records.

Inspia Capture is an optional Chrome extension that lets you capture a visual reference from a webpage and prepare it for use in Inspia. It requests access to HTTP and HTTPS pages because its core feature is an in-page image toolbar and context-menu capture flow. The extension checks visible image dimensions to identify eligible references.

A page load or image hover does not upload image data. Image bytes are read only after you explicitly choose Save, Analyze, or Generate. The extension does not read passwords, form fields, cookies through the Chrome cookies API, or page content unrelated to the image you selected. It may send the selected image, image URL, page URL, page title, and image alt text to Inspia to perform the requested capture or workflow action.

Private image uploads, image-to-prompt analysis, generation requests, workflow status, assets, and results are handled by Inspia under your account access controls. Create reference uploads appear in private Assets by default. Images explicitly saved with the extension appear in Saved, while Analyze and Generate inputs appear only in their Workflow. The same private file can be reused across these relations without copying it. Removing one relation preserves any other Saved, Assets, or Workflow reference. The extension uses the Inspia website session for authentication; it does not use Chrome Identity and does not store access tokens, refresh tokens, or bearer tokens. One current capture and editable prompt drafts may be kept in Chrome local storage for recovery. You can remove this local data by clearing the extension data or uninstalling the extension.

When you request image analysis or generation, Inspia may provide the selected content to the providers required to complete that request and to its private asset storage. It is not used for advertising or sold. Account deletion and privacy requests can be made through the Account page or by contacting [email protected].

Inspia uses a self-hosted Umami analytics service to understand anonymous website usage. The tracker respects Do Not Track.

Inspia does not send prompt text, edited prompt content, clipboard content, raw search terms, email, name, account identity, arbitrary page text, or error text to Umami. It receives only sanitized routes, anonymous item identifiers, and low-cardinality product events. Session replay and heatmaps are disabled.

Cloudflare Browser Insights provides separate, narrow performance telemetry. It is independent of Umami product analytics. It does not receive prompt or clipboard content, search terms, email, account identity, arbitrary page text, or error text.

For questions about privacy or analytics, email [email protected]. See our Contact page for safe ways to include useful context in your message.