Privacy Policy

The service

PrintFlow AI is available as a Free plan and paid Pro and Scale plans via Stripe Checkout. Stripe processes billing and subscription data when you start checkout, manage a subscription, or complete a purchase.

Controller

The controller of personal data (where the GDPR or similar law applies) is:

Email: support@printflow-ai.com

Business and tax registration details for the operator will be updated on this page after registration, where relevant for transparency.

What the app does (summary)

Signed-in users can submit structured product briefs and receive AI-generated listing-related text. History, settings, usage limits, and plan status are stored in a database. Signed-in users can also rate a generated listing pack (helpful or not helpful), optionally pick one reason and add a short note; that rating, reason, and note are stored in our database (Supabase). Optional walkthrough or feedback requests may be collected through a form on the marketing site.

Optional guided walkthrough form

If you use the optional request form, we store the information you provide (email, optional Etsy shop URL, niche, free text) in our database (Supabase) to handle onboarding, interviews, or feedback. Public signup does not depend on this form.

Entries are kept only as long as needed for these purposes and reasonable follow-up, then reviewed and removed where appropriate.

Support tickets

If you send a report through the in-app support form, we store it in our database (Supabase) to handle and technically investigate your request. This includes your account reference and email address, the category, subject and message you write, the current sanitised in-app route, the app version and your plan, and basic device details (browser, viewport size, language, timezone, and online/offline status).

A screenshot is included only if you add one yourself. Screenshots are kept in a non-public storage bucket and are automatically removed after 90 days; the ticket record itself is retained in line with the general approach described under Retention.

We do not automatically attach passwords, cookies, authentication tokens, full prompts, or generated content to a support ticket.

Anthropic (support reply drafts)

To prepare a reply to an open support ticket, the category, subject and message of the ticket and the in-app page path it was sent from (without query parameters) are sent to Anthropic (Claude), which writes a draft reply. Your email address, screenshots and device details are not sent. Every draft is reviewed by us, and we send each reply ourselves; nothing is sent to you automatically. The legal basis is the handling of your support request (Art. 6(1)(b) GDPR). We use Claude through our own Claude subscription, provided in the EEA by Anthropic Ireland, Limited and otherwise by Anthropic, PBC (United States). Anthropic is not our processor here: it processes this content as a separate controller under its own terms and privacy policy (anthropic.com/legal/privacy), including any transfer to the United States. We have switched off the use of our chats for training Anthropic's models.

Categories of personal data

Depending on how you use PrintFlow AI, we may process:

• Contact and account data: email address and authentication-related data (e.g. session information via Supabase).
• Product and app content: product briefs, generated listing packs and history, workflow mode selections, brand voice data, shop defaults.
• Usage and plan status: generation counts and plan metadata.
• Support ticket data: when you use the in-app support form — the category, subject and message you enter, your email address, the current sanitised route, app version, plan, basic device details (browser, viewport, language, timezone, online status), and an optional screenshot you choose to attach.
• Internal service notes: for service management purposes, the operator may keep internal administrative notes about accounts (for example support history or access changes). These notes are accessible to you under your right of access (GDPR Art. 15).
• Etsy shop data (closed beta, only if you connect a shop): Etsy user ID, shop ID and name, encrypted Etsy tokens, listing texts and shop policies you import, and a write-back log without texts; see Etsy shop connection below.
• Stripe-related metadata: customer and subscription metadata for paid subscribers.
• Technical logs: server and infrastructure logs for security and operations.
• Optional analytics & performance (after consent): in-app product events (PostHog), web analytics (Vercel Web Analytics), and performance signals (Vercel Speed Insights), only if you opt in via the cookie banner or preferences panel.
• Consent preferences: your analytics choice is stored in the browser under the key printflow-ai.consent.v1 (JSON in local storage, not only HTTP cookies), together with the date of your choice. The choice (accept or reject) is kept for 12 months; after that, or when we add or change optional tools, we ask again.
• Error diagnostics: technical error reports (Sentry), including stack traces and request metadata as configured below. This is separate from the optional analytics category and may run to keep the service reliable.

Purposes of processing

• Account creation and login.
• Providing the generator and related features.
• Storing history and user settings.
• Enforcing usage limits and plan rules.
• Support communication.
• Security and abuse prevention.
• Product analytics and performance measurement when you consent (see Analytics & Performance section).
• Error monitoring and reliability (Sentry).
• Billing and subscription management (Stripe).

Legal bases

• Performance of a contract (Art. 6(1)(b) GDPR): account, login, generator, history and settings, usage limits, billing, support requests and service emails you need to use PrintFlow AI.
• Legal obligation (Art. 6(1)(c) GDPR): keeping billing and accounting records for the statutory retention period.
• Legitimate interests (Art. 6(1)(f) GDPR): security and abuse prevention, rate limiting, error monitoring (Sentry), an anonymous count of page loads, and pseudonymous server-side product events about billing and lifecycle steps (see Analytics & Performance). Our interest is operating a secure, reliable and economically viable service. You can object at any time (Art. 21 GDPR, see Your rights).
• Consent (Art. 6(1)(a) GDPR): optional analytics and performance tools in your browser, and marketing emails where you opted in. Storing or reading information on your device for these tools is based on your consent under § 165(3) of the Austrian Telecommunications Act 2021 (TKG 2021) and, for visitors from Germany, § 25(1) TDDDG. Strictly necessary storage (login session, security, your consent choice, app state) does not require consent (§ 165(3) TKG 2021, § 25(2) no. 2 TDDDG).

You can withdraw consent at any time with effect for the future via Cookie settings(site footer or the account menu in the app) or, for emails, via the unsubscribe link. Withdrawal does not affect processing that happened before it.

Emails

We send emails with Resend. Account and security emails (sign-up confirmation, password reset, email change) and service emails (for example when a trial ends) are sent because they are needed to provide your account (Art. 6(1)(b) GDPR); they contain no tracking.

Product emails (welcome, tips, trial reminders, upgrade information) are sent only if you opted in, at sign-up or later by resubscribing (for example under Settings → Email preferences). In these emails we measure whether an email was opened (a small invisible image) and which links were clicked (links pass through Resend's tracking address before reaching our site), to understand which emails are useful. This is covered by your opt-in (Art. 6(1)(a) GDPR; § 165(3) TKG 2021 / § 25(1) TDDDG). You can withdraw at any time with the unsubscribe link in every product email or under Settings → Email preferences; opens and clicks are then no longer recorded. Open/click data is kept for as long as Resend retains email event logs.

Tool suggestions to blogs, channels and newsletters: if a website, blog, channel or newsletter publicly invites tool submissions or review requests and names a contact address for that, we may send that address one single message suggesting PrintFlow AI. We take the address only from that page, write to each website at most once, and keep no list of addresses; only Resend's sending log holds it for as long as Resend retains email logs. The legal basis is our legitimate interest in presenting our product to people who ask for such suggestions (Art. 6(1)(f) GDPR). You can object at any time by replying "no thanks"; we then never write again.

OpenAI (AI generation)

To generate text, the portions of your brief and related inputs needed for a given run are sent to OpenAI. Do not enter special categories of personal data or sensitive information in briefs unless it is truly necessary for your listing draft.

Analytics & Performance (optional)

These tools load and run only after you accept optional "Analytics & Performance" in the cookie banner, save that choice in preferences, or use an equivalent "Accept all" flow. If you reject optional analytics or never opt in, we do not initialize these products in your browser for that session (subject to normal browser caching behavior after you later change your mind).

• PostHog (PostHog Inc., data hosted in the EU) — custom in-app product events (for example generation and billing flows), page views and automatic capture of clicks with element text and attributes masked, and heatmaps (aggregated click, mouse-movement and scroll positions per page). PostHog uses cookies and local storage on your device once enabled. Surveys, in-app messaging, experiments and PostHog exception capture are switched off.
• Vercel Web Analytics — privacy-oriented, aggregated web analytics provided by Vercel.
• Vercel Speed Insights — Real User Monitoring style performance metrics (for example Core Web Vitals signals), provided by Vercel.

Session replay: after optional analytics consent, PostHog records a sample of sessions (page structure, clicks, scrolling and navigation) so we can see where people get stuck. All text and form inputs are masked before leaving your browser, so typed content, briefs and generated copy are not recorded; browser console output and network request details are not recorded either.

Server-side PostHog (independent of the cookie banner): our servers send a small, fixed set of operational events to PostHog (EU) — for example checkout started/completed/failed, billing portal opened, subscription changed or cancelled, payment failed, and activation email sent/skipped. These events contain your pseudonymous account ID (Supabase user ID) and an allowlist of technical properties such as plan, Stripe price and customer ID, amount, currency and error codes. They do not include your IP address or location. We never send email addresses, card data, billing addresses, prompts, or generated copy. Nothing is stored on or read from your device for these events. Legal basis: legitimate interests (Art. 6(1)(f) GDPR) in understanding whether billing and onboarding work. You can object at any time by emailing us; we will then exclude your account from these events.

Anonymous page-load count (independent of the cookie banner): when you open one of our public pages, our server may count that page load and send it to PostHog (EU) as a single anonymous event: the page path (with any IDs removed), whether you came from another website and that website's domain, and campaign parameters from the link (utm_source, utm_medium, utm_campaign). Each count gets a new random ID, so two page loads cannot be linked to each other or to you; no person profile is created. We do not send your IP address, your browser details or any cookie value, and nothing is stored on or read from your device for this count; your browser type is only checked on our server to leave out bots and is then discarded. Legal basis: legitimate interests (Art. 6(1)(f) GDPR) in knowing how many people visit our pages, including those who decline optional analytics.

We still process personal data elsewhere when you use the product (for example account email in Supabase, briefs you submit, and AI processing). Analytics consent only controls the optional tools listed above.

Sentry (error monitoring)

We use Sentry to capture and diagnose technical errors (for example error types, stack traces, and request metadata). This helps us keep the service stable and investigate incidents. Sentry is not used for marketing attribution, and we do not enable Sentry Session Replay in this codebase.

• Default PII: Sentry is initialized with sendDefaultPii: false so the SDK does not automatically attach categories of personal identifiers Sentry treats as default PII.
• Scrubbing: we apply a beforeSend hook to strip query strings from request.url, redact common sensitive HTTP headers (including Cookie, Authorization, and Set-Cookie), redact cookie payloads on the request object where present, and apply best-effort redaction of obvious email-like strings in some event fields. This is not a guarantee that no personal data ever appears in an error payload (for example if an error message itself contains data you entered).
• User linkage: we do not call Sentry.setUser in our application code.

See Sentry's privacy documentation for how Sentry processes data on their side, and consider this policy together with your own device and network environment.

Processors and services

The following providers are involved in delivering the service (each has its own privacy terms):

• Vercel — hosting and application delivery; optional Vercel Web Analytics and Vercel Speed Insights when you consent
• Supabase — authentication, database, user-related storage
• Stripe — payments and subscriptions once paid checkout is enabled
• OpenAI — AI text generation
• Anthropic — AI-written draft replies to open support tickets (category, subject, message and page path; no email address). Anthropic acts as a separate controller, not as our processor (see Anthropic (support reply drafts))
• PostHog — product analytics: in your browser only after consent; pseudonymous server-side operational events as described above (EU hosting)
• Sentry — error tracking
• Resend — transactional and marketing email delivery (welcome, first-pack, and other service emails) and receiving emails sent to our contact address
• Etsy — independent controller, not a processor: source of your shop data and recipient of changes you approve, only if you connect a shop (closed beta)
• Upstash Redis — temporary storage of rate-limit counters (user identifiers stored for short durations to enforce generation limits)

We use these providers as processors under data processing agreements (Art. 28 GDPR) where they act on our behalf; Etsy is not one of them (see Etsy shop connection). Several of them are based in the United States or may process data there (in particular Vercel, Stripe, OpenAI, Resend, Upstash and Sentry). Such transfers rely on the EU–U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR). PostHog data is hosted in the EU; Sentry error events are sent to Sentry's EU (Germany) region.

Cookies, local storage, and similar technologies

We use necessary cookies and similar technologies to operate PrintFlow AI, including authentication and session management (for example via Supabase), security, and core app functionality. We also store your analytics consent choice in your browser's local storage under printflow-ai.consent.v1 (JSON: your choice, the date of the choice, and a policy version). That entry is not the same thing as an HTTP cookie, but it is still local storage on your device and can be cleared with other site data. It contains no identifier and is honoured for 12 months; we ask again after that or when the set of optional tools changes. If you withdraw analytics consent, PostHog identifiers stored in your browser are deleted and the page reloads so that no optional tool keeps running.

If you enable optional Analytics & Performance, PostHog may persist client identifiers using local storage and cookies as configured in our PostHog client setup. Vercel Web Analytics and Speed Insights are loaded from your browser only after that consent path.

Stripe may set cookies or use similar technologies when you use billing flows (for example Checkout or the customer portal), consistent with Stripe's own policies.

• sb-<project>-auth-token (may be split into .0, .1, …)

  Necessary · Cookie

  Supabase login session

  Duration: Until logout, at most 400 days

• printflow-ai.consent.v1

  Necessary · Local storage

  Your cookie choice, its date and policy version (no identifier)

  Duration: 12 months, then we ask again

• pf:active-generation:v1:*, pf:onboarding:wizard:v1, printflow:new-product-reuse-prefill

  Necessary · Session storage

  Recovering an in-progress generation, onboarding draft or prefilled form in this tab

  Duration: Until the tab is closed

• printflow-ai.generations.v1

  Necessary · Local storage

  Generation history saved in this browser by older app versions (read and imported into your account)

  Duration: Until you delete it or clear site data

• printflow:onboarding:v1:dismissed:*, printflow_email_verified, printflow-ai.generations.supabase-import.v1.*

  Necessary · Local storage

  Dismissed onboarding hints (set by older app versions only), email-verification status and a one-time history import

  Duration: Until you clear site data

• ph_<project-key>_posthog

  Optional (consent) · Cookie and local storage

  PostHog pseudonymous visitor and session ID

  Duration: Up to 12 months; deleted when you withdraw consent

• __ph_opt_in_out_<project-key>, ph_* (other PostHog keys)

  Optional (consent) · Local storage

  PostHog opt-in state and session data

  Duration: Deleted when you withdraw consent or consent expires

• pf:onboarding:started:v1

  Optional (consent) · Session storage

  Prevents counting the start of onboarding twice in analytics; only written after you consent

  Duration: Until the tab is closed

• printflow_utm_first_touch

  Optional (consent) · Session storage

  Campaign source of this visit (utm_* parameters) for analytics

  Duration: Until the tab is closed

• printflow_signup_completed_tracked_*

  Optional (consent) · Local storage

  Prevents counting the same sign-up twice in analytics

  Duration: Until you clear site data

You can reopen and change optional analytics choices using Cookie settings in the site footer (marketing and legal pages) and in the account menu of the signed-in app.

We do not claim that "no personal data is processed" simply because analytics are optional — account, product, AI, billing, and error data may still be processed as described elsewhere in this policy.

Retention

Data is retained only as long as needed for the purposes described in this policy. The following indicative periods apply:

• Account and profile data: retained while your account is active; deleted within 30 days after account deletion (except where retention is required by law or for dispute resolution).
• Generated content and history: retained while your account is active; deleted with your account on request or after account deletion.
• Billing and subscription records: retained for 7 years from the date of the relevant transaction, as required under Austrian and EU tax and accounting law.
• Rate-limit counters (Upstash): temporary; automatically expire within minutes to hours depending on the window.
• Error and security logs: typically retained for up to 90 days.
• Etsy connection (closed beta): connection record and encrypted tokens until you disconnect or delete your account (refresh tokens are usable for at most 90 days); write-back log until account deletion; listing notes and imported briefs until you change them, delete the pack or delete your account.
• Analytics data (PostHog, after consent): subject to PostHog's own retention settings and your right to withdraw consent.

You can request deletion of your account data at any time as described under Account and data deletion below. Statutory retention obligations may prevent immediate deletion of some records.

Your rights

Where applicable law provides them, you may have the right to:

• access your personal data;
• rectify inaccurate data;
• request erasure;
• request restriction of processing;
• object at any time to processing based on legitimate interests (Art. 21 GDPR), for example the server-side product events;
• withdraw consent at any time with effect for the future (Art. 7(3) GDPR), for analytics via Cookie settings;
• data portability;
• lodge a complaint with a supervisory authority — in Austria, the Austrian Data Protection Authority (Datenschutzbehörde).

Account and data deletion

You can delete your account directly in the app under Settings → Account. Alternatively, you can request deletion of your account or personal data by emailing support@printflow-ai.com from or clearly identifying your account email. We will respond subject to technical and legal constraints (for example statutory retention once billing is active).

Support

General support: Support.

This deployment also exposes a public support email: support@printflow-ai.com (may differ from the address above).