Privacy Policy

This policy applies to visitors, registered users and customers of the Service. It covers the public website, authenticated product, support functions and payments. Third-party services linked from IconFlow have their own privacy notices.

The data processed depends on how you use IconFlow. We seek to limit it to what is needed for the purposes described below.

• Account and profile data, such as email address, authentication identifier, name where supplied, language and interface preferences.
• Authentication and security data, including session tokens, login events and information needed to prevent abuse.
• Product data, including generation settings, prompts, generated icons or logos, exports and usage history needed to provide the Service.
• We process account identifiers, email, supplied names, language, preferences and sessions; prompts, descriptions, source texts or batch manifests, settings, outputs and histories; Support messages and optional diagnostics (browser, device, screen, route, version); billing addresses, tax data, payment references and statuses, invoices and credit movements; technical request, security and optional analytics data.
• Billing and transaction data, such as the selected credit pack, currency, amount, billing address, tax information, Stripe customer and invoice references. IconFlow does not receive full card credentials.
• Technical data supplied in ordinary network requests, such as IP address, browser, device, operating system, language, timestamps and requested routes.
• Optional analytics data described in section 6, but only after analytics consent.

• Create and secure accounts, authenticate users and maintain sessions.
• Generate, save, display and export requested icon and logo assets.
• Provide purchased credits, invoices, customer support and service communications.
• Calculate tax, prevent fraud, enforce usage limits and meet accounting or other legal duties.
• Maintain reliability, investigate errors and protect the Service and its users.
• With consent, understand acquisition, signup, onboarding, activation and purchase paths and improve product usability.

Data enables authentication, generation and export, purchases and credits, support, abuse prevention and security. Swiss FADP requires proportionality and transparency. Where GDPR applies: contract performance for account, generation, purchase and Support; legal obligations for accounting and required requests; legitimate interests for security and legal defence following balancing; consent for optional analytics. The necessary Service licence does not authorise a new training or public marketing purpose.

Supabase handles authentication, application data and storage. If you choose Google OAuth, Google and Supabase exchange identity attributes needed for login. Stripe processes payments, billing and taxes, including for its own obligations; we receive necessary references and statuses and do not request card data in Support. Not all their roles are exclusively those of a processor.

OpenAI is our AI processing provider and processor for relevant processing. We send necessary prompts, descriptions, source texts/manifests, customisation context and outputs for refinement. Under OpenAI API rules, content is not used for model training by default unless the API customer expressly enables sharing. Our text Responses calls disable response storage; images use the Images API. This does not remove all retention: abuse-monitoring logs generally up to 30 days, legal/security exceptions and other function-specific retention may apply. No zero retention, ZDR/MAM or exclusively European location is promised.

Resend is intended for service emails; Mailpit is used in local development. If enabled, Telegram staff alerts may contain ticket number, category and subject, name/email and a message excerpt up to 240 characters. If Trustpilot after-sales invitations are enabled, a copy of the payment email may be sent with credits and possibly an invoice link; analytics consent does not cover this sharing. Unsplash images or Google favicons in emails may cause email-client requests. Authorities or advisers may receive necessary data where an obligation or legal defence justifies it.

IconFlow uses PostHog Cloud EU only after you accept analytics. Before that choice, the browser SDK is not initialized, analytics events and identification are not sent, PostHog storage is not created and session replay does not start. Rejecting analytics does not prevent account creation or ordinary use of the Service.

The implementation sends selected events rather than automatically capturing every click or form. It can measure sanitized page views, navigation choices identified by a stable application-route name, email or Google signup start and authoritative authenticated completion, onboarding completion, first successful logo generation, pricing views, checkout start and confirmed one-time credit-pack purchases. Event properties are limited to bounded operational values such as signup method, product surface, content mode, quality, plan, one-time billing period and currency, plus browser or device information added by the service.

Analytics may also measure batch creation, successful sample and full-batch generation, and successful exports. Properties are limited to operational values such as input method, sample size, item count, quality, content mode, workflow and export format.

Page and landing URLs are reduced to paths without query strings or fragments, and referrers are reduced to their origin. Only sanitized UTM source, medium, campaign, term and content values are retained as acquisition properties. SDK-generated current, initial and session-entry URL properties, including replay network request names, are stripped of query strings and fragments before sending. Authenticated analytics is associated with the stable internal Supabase authentication UUID so the journey from signup through activation and purchase can be understood. Names, email addresses, phone numbers, addresses, passwords, authentication tokens, support messages, prompts, descriptions, filenames, generated content, Stripe session or invoice identifiers, full billing details and card data are not intentionally sent to PostHog.

After Stripe confirms a one-time credit-pack payment through the signed invoice.paid webhook, the backend may send purchase_completed only when the user's current server-side analytics consent is granted for the current policy version. Delivery is deduplicated with a secret-derived identifier and includes only plan, one-time billing period and currency. Stripe and the IconFlow database remain authoritative for payment and credits.

Analytics is used to improve signup and onboarding, identify usability problems, measure activation, improve product features, understand conversion paths and acquisition channels, and assess reliability where the selected events support it. PostHog failures do not block product functions.

Necessary storage supports Supabase sessions, security, theme and analytics choice. The iconflow_analytics_consent cookie remembers that choice for about 180 days. After agreement PostHog uses localStorage for identity/session; a rejection marker may remain after withdrawal. localStorage remains until deletion or browser cleanup without a fixed period; session duration depends on authentication configuration. These periods do not determine server retention.

Stripe processes checkout, payment credentials, billing details, tax and transaction records under its own privacy terms. IconFlow receives references and status information needed to issue credits, invoices and support purchases. With current analytics consent, PostHog may receive the bounded checkout-start and purchase-completion fields listed in section 6, but not Stripe session, customer or invoice identifiers, card credentials or full billing information. Stripe and the IconFlow database remain authoritative for transaction processing and credits.

Periods depend on account and requested-function needs, Support cases and disputes, security and legal obligations. Accounting documents subject to Swiss retention requirements are kept for 10 years from financial-year end; this does not cover all data. The direction of asset availability up to 24 months and possible deletion after more than 12 months of inactivity is neither an access guarantee nor an automatic erasure schedule. Provider settings and backup ageing also matter.

Request closure or erasure through Support or email. Account deletion, assets, legally retained evidence, provider data and backups are distinct. Valid paid credits and open disputes require prior handling; complete erasure by a fixed date is not promised. Access controls protect the Service without absolute security. Breaches are notified to authorities and individuals under applicable legal conditions.

Subject to legal conditions, request access, rectification, erasure, delivery/transmission, objection or restriction and withdraw consent without retrospective effect. Proportionate identity checks may be necessary; legal exceptions apply. We respond within statutory deadlines, normally 30 days for Swiss access requests. You may approach the Swiss FDPIC or your country’s competent authority where applicable. Contact us for review of a disputed automated restriction.

Where GDPR applies, we normally respond within one month of receiving your request. A lawful extension of two further months may be necessary because of complexity and request volume; we explain the reasons within the first month. Refusals include reasons and applicable complaint and judicial-remedy information. These statutory periods are separate from a general Support response time.

The Service is intended for people aged 18 or older with required capacity; we do not claim technical age verification. Contact us if a minor’s data was supplied so appropriate measures can be considered.

We inform you of material changes as required by law and seek a new choice where optional purposes require it. Revision is not proof of past acceptance. Translations retain their informational and legal effect; French precedence for the terms does not remove this effect. Questions and requests: [email protected].

SynerTech Labs SNC, c/o Thomas Lerch, Rue Saint-Maurice 5, 2852 Courtételle, Switzerland, is the controller for IconFlowLabs processing. Data protection contact: [email protected].