Privacy Policy

Two different data categories

FigureFlow separates (A) scientific or research content from (B) account, billing, support, and infrastructure metadata. Using sign-in or payment does not itself send your scientific content to account or billing services.

Scientific and research content

CSV/XLSX files, table contents, sample identifiers, chart datasets, calculated statistical values, annotations, generated figures, Download Center snapshots, exported Project content, and Package V2 scientific content are processed in the browser. FigureFlow does not intentionally send them to Supabase, Polar, or the private support store merely because you authenticate, purchase Pro, or manage billing.

Browser storage

IndexedDB is the authoritative browser store for autosaved Projects, with a validated localStorage fallback or migration path where supported. localStorage also stores limited preferences and browser-local features such as layout choices, personal styles, and templates. The Download Center and Project state may contain scientific content and remain on the device unless you deliberately export or download them.

Supabase account data

Supabase processes account identifiers, email, authentication and session metadata, Google or email/password sign-in state, confirmation and recovery state, profile data, and the minimum customer or entitlement mapping needed for commercial access. FigureFlow uses cookie-based Supabase sessions so the signed-in state can be verified by the server.

Polar billing data

Polar processes customer and billing identity, checkout, product and order information, subscription state, invoices, tax and payment-related metadata, and provider identifiers needed to resolve Pro access. Payment-card handling belongs to Polar and its payment processors; FigureFlow does not store full card numbers.

Private support reports

A support report is sent only when you explicitly submit the form. FigureFlow may store the selected category, description, optional reply email, server-derived signed-in account identifier, and—if you leave diagnostics enabled—build version, locale, browser user-agent, viewport size, sanitized pathname, and submission time. The form does not automatically attach research files, filenames, tables, values, statistics, annotations, Projects, Packages, screenshots, clipboard content, or URL queries.

Cookies and infrastructure metadata

FigureFlow uses authentication/session cookies and a one-year locale-preference cookie. Vercel and other network infrastructure necessarily receive request metadata used to deliver and protect the service, which may include IP address, request path, browser or device information, timestamps, response status, and security or performance logs.

Anonymous product analytics

When production analytics is configured and you have not disabled it, FigureFlow uses PostHog to receive a small allowlist of anonymous product events such as opening the editor, completing an import, selecting a chart type, running an analysis, or completing an export. Events may include only coarse metadata such as locale, chart or file type, statistical method ID, table-count bucket, plan category, export format, source area, device class, success, or a fixed failure category.

Analytics never includes research content, filenames, worksheet, table, column or group names, titles, captions, annotations, reference-line labels, raw or calculated scientific values, p-values, Project or Package content, generated artifacts, screenshots, email, account or billing identifiers, tokens, arbitrary URLs, query strings, or free text. FigureFlow disables automatic capture, page views, session replay, heatmaps, form capture, surveys, feature flags, and person profiles. You can disable or re-enable analytics below. The preference is stored only in this browser and is not part of Start Over, a Project, or a Package.

Purposes, processors, and sharing

Account data is used for sign-in, recovery, account support, and secure entitlement resolution. Billing data is used for checkout, subscription administration, invoices, tax, fraud prevention, and access grants. Support data is used to investigate and reply to reports. Anonymous product-event metadata is used to understand feature adoption and reliability. Supabase, Polar, Vercel, PostHog, and their relevant subprocessors handle data only for these operational purposes under their own terms. FigureFlow does not sell research data or use it for advertising.

Retention

Browser-local data remains until you clear it, replace it, use the available removal controls, or browser storage is removed. Account, billing, entitlement, transaction, and support records are kept only as reasonably needed to provide the service, resolve requests, maintain security and financial records, and meet legal obligations. Provider-controlled retention may also apply.

Security, requests, and contact

FigureFlow uses reasonable technical and organizational safeguards, but no internet or browser storage system is completely secure. Depending on applicable law, you may request access, correction, deletion, or other available rights for account or support information by contacting figureflow.office@gmail.com. Some billing or transaction records may need to be retained for legal, tax, fraud-prevention, or dispute purposes.