Privacy Policy

Editor and poster data

When you use the editor, your selected image file, image transform, layout choices, preview state, and generated PDF are processed locally in your browser. During checkout, temporary poster data may be saved in your browser storage so your project can be restored after payment. We use this data only to provide the editor and export flow.

Server-side export records may include layout metadata such as rows, columns, tile size, paper size, orientation, display unit, poster dimensions, sheet count, payment tier, entitlement or grant identifiers, and a client event identifier. These records help us confirm export access, prevent misuse, troubleshoot checkout/export issues, and understand aggregate product usage. They do not include your uploaded image file, final PDF, or poster text from your private project.

Account, pass, and access data

If you sign in, buy a pass, claim a token, or receive a free export grant, we may collect account identifiers such as your email address, user ID, entitlement status, grant status, product type, checkout intent, claim token hash, anonymous browser identifier hash, activation and expiration times, and download/export counts. We use this to provide paid and free access, restore eligible purchases, enforce limits, prevent fraud, and support your account.

Payment data

Payments are processed by Stripe. We do not store full card numbers, bank account details, or full payment credentials. Stripe may send us limited purchase records such as payment status, product purchased, receipt information, checkout session ID, transaction identifiers, amount, currency, and related webhook events. We use this to complete purchases, provide access, handle refunds or disputes, and maintain financial records.

Reviews and support

If you leave a review, we collect your rating, comment, optional display name, user ID, consent to publish, and review status. Published reviews may show your display name, rating, and comment. If you contact support, we collect the information you choose to send, such as your email address, message, screenshots, order details, or project details needed to answer your request.

Analytics, ads, and diagnostics

We use analytics and diagnostic data to understand page performance, editor usage, checkout completion, exports, errors, and aggregate traffic sources. This may include page views, event names, referrer and campaign parameters, country-level analytics, browser type, device type, user agent, file size in megabytes, image dimensions, layout metadata, and timestamps. If ads are enabled, advertising partners such as Google AdSense may use cookies or similar technologies to show and measure ads on public pages.

Tool inputs

The idea search tool may receive a search query and result limit. The link generation tool may receive layout inputs such as paper size, rows, columns, target width, target height, unit, optimization preference, tile orientation, print mode, and display unit. It may also receive an optional image URL and optional UTM campaign fields if the user or ChatGPT provides them.

Tool outputs

The idea search tool returns public PrintTiler idea-card metadata, including titles, categories, descriptions, poster text, style tags, tone tags, audience tags, public idea URLs, public poster asset URLs, and ready editor URLs. The link generation tool returns a PrintTiler editor URL, a short layout summary, paper size, rows, columns, orientation, print mode, sheet count, poster dimensions in millimeters and inches, and the reason the layout was selected.

How ChatGPT app data is used

We use ChatGPT app tool inputs only to search public idea cards, compute poster layouts, and return editor links. If an optional image URL is included, the URL is placed in the returned editor link so your browser can try to load that hosted image when you open the editor. Do not provide private, sensitive, or access-controlled image URLs to the tool.

Your use of ChatGPT is also subject to OpenAI's terms and privacy practices. OpenAI may process your conversation and tool-call data before and after the request is sent to PrintTiler.