Privacy Policy

We may collect:

• Account information, such as name and email address
• Billing information, if you subscribe to a paid plan
• Product data imported or uploaded by users, including product names, prices, descriptions, images, URLs, and catalog information
• Branding assets uploaded by users, such as logos, images, fonts, and design elements
• Integration data from connected third-party services, such as Meta/Facebook catalogs, only after user authorization
• Basic technical and usage data, such as device, browser, IP address, and activity inside the platform
• Marketing attribution and conversion context, such as referral pages, campaign parameters, click identifiers, event type, event time, source URL, IP address, browser user agent, and hashed matching identifiers when optional marketing consent allows it

We use data to:

• Provide and operate Pansyer Feed Studio
• Create and manage product catalogs
• Generate marketing visuals and templates
• Sync and import data from connected integrations
• Process payments and manage subscriptions
• Provide support
• Improve performance, reliability, and user experience
• Measure and optimize advertising performance when optional marketing consent allows conversion tracking
• Prevent abuse, fraud, or unauthorized access

We do not sell user data.

If you connect a Meta/Facebook account, Pansyer Feed Studio may access:

• Business information
• Product catalogs
• Product details and related media assets
• Catalog-related metadata needed to import and manage products

We use this data only to provide the requested functionality inside Pansyer Feed Studio. We do not collect personal data about your ad audiences, website visitors, or customers through the Meta catalog integration. Optional advertising conversion tracking is described separately below. You can disconnect the Meta integration at any time.

Users retain ownership of all content they upload or import into Pansyer Feed Studio.

This includes product data, images, logos, fonts, templates, and brand assets.

Users are responsible for ensuring they have the legal right to use any content uploaded or imported into the platform.

We may share data only with trusted service providers needed to operate Pansyer Feed Studio, such as hosting, payment processing, analytics when enabled, email delivery, and infrastructure providers.

When optional marketing consent allows it and sale/share-style opt-out is not active, we may send limited server-side conversion events to advertising platforms such as Meta for ad measurement, attribution, and optimization. These events may include event name, event time, source URL, value or currency where relevant, campaign or click identifiers, IP address, browser user agent, and hashed matching information such as email, account ID, name, phone, city, state, postal code, or country when available.

We may also disclose data if required by law or to protect the security and integrity of the platform.

We do not sell, rent, or trade user data.

We store source uploads, hosted exports, rendered media, image derivatives, workspace assets, profile images, staging uploads, audit/history records, and operational backup metadata according to the app storage lifecycle registry.

Private source uploads and render caches are not intentionally published. Hosted export URLs and rendered public assets are public only when publication or template/media behavior requires it.

Broad storage purge behavior is disabled. Cleanup is manifest-based and review-token-gated.

We use reasonable technical and organizational measures to protect user data.

No online service can guarantee absolute security, but we work to protect data from unauthorized access, loss, misuse, or disclosure.

Active workspace, catalog, source upload, hosted export, render, derivative, profile, and asset data is retained while needed to provide the service or until deletion is requested or performed in the product.

Completed and stale upload staging objects, render cache entries, archived notifications, and workspace activity are governed by configured lifecycle windows and cleanup workers.

If an account or workspace is deleted, eligible data is deleted or de-identified after confirmation. Some backup, audit, security, billing, and abuse-prevention records can remain for limited retention periods.

Operational database backups and R2 inventory manifests may persist after live deletion until the applicable backup retention window expires. Backup data is restored only for operational recovery, security, or legal needs.

Users may request to:

• Access their personal data
• Correct inaccurate data
• Delete their data
• Disconnect third-party integrations
• Stop using the service

To make a request, contact us at: start@pansyer.com

Pansyer Feed Studio uses cookies and similar technologies for required product functionality, including sign-in, security, workspace routing, editor state, notification counts, route recovery, and saving cookie preferences.

Optional analytics and marketing technologies are off unless you allow them. If marketing consent is allowed, Pansyer may store marketing attribution in a first-party cookie and send consent-gated server-side ad conversion events, including through Meta Conversions API. Browser marketing pixels are not loaded by default.

If your browser sends a Global Privacy Control signal, sale/share-style marketing tracking stays off for that browser.

• Required product cookies: always on because the service cannot run correctly without them.
• Analytics: optional, used only for aggregate usage and performance measurement if analytics tools are enabled after you allow them.
• Marketing: optional, used for first-party attribution storage and server-side ad conversion events after you allow them.
• Meta Conversions API: optional, server-side conversion events may include hashed customer matching information, IP address, user agent, event source URL, event ID, value, currency, and campaign or click identifiers when available.

To change optional choices, open Cookie preferences.

Pansyer Feed Studio is not intended for children under 16. We do not knowingly collect personal data from children.

We may update this Privacy Policy from time to time. The latest version will always be available on this page.

Continued use of Pansyer Feed Studio after changes means you accept the updated policy.

For privacy questions or data deletion requests, contact:

start@pansyer.com