Skip to main content
Security and data boundaries

What Listsy stores, sends, and keeps separate

A plain-language account of Listsy's current private-file, credential, Etsy OAuth, billing, access, and deletion boundaries.

Short answer

Supabase holds Listsy's account and product records, while generated and uploaded files stay in private Cloudflare R2 storage. Vercel serves the app, FAL handles generation jobs, Polar handles billing, and Etsy receives only the seller-directed draft work. Service credentials stay server-side, and private files use short-lived signed access.

Workspace records
Supabase with workspace checks
Artifact files
Private Cloudflare R2 storage
File access
Short-lived signed links
Etsy action
Connected-shop draft operations
01

Product records and artifacts stay tied to a workspace

Listsy stores account details, workspace membership, seller briefs, artifact metadata, listing copy, QA results, job state, and credit records. Generated and uploaded file bytes stay in private object storage. Product records and files are checked against the authenticated workspace.

Public content pages do not expose workspace data. Short-lived signed links are used for private files, and application routes repeat resource checks instead of treating the browser URL as authorization.

02

Each provider receives only the data needed for its job

Provider keys for generation, storage, billing, queues, and Etsy stay in server-side services rather than public JavaScript. The browser receives signed-in application data and short-lived file links, not the credentials used to operate those services.

PNG processing, proof views, ZIP packaging, and draft checks run separately from generated-content jobs. That separation makes it easier to identify which provider received data, which step failed, and whether a retry is safe.

Data or actionProviderPurposeBoundary
Account, workspace, product, job, QA, and credit recordsSupabaseAuthentication and relational application stateEvery private resource is checked against the signed-in workspace
Generated and uploaded artifact bytesCloudflare R2Private file storageThe app uses short-lived signed links instead of public buckets
Dashboard and review interfaceVercelServe the Listsy web applicationGeneration, storage, billing, and marketplace secrets are not public client settings
Seller brief and generation inputsFALGenerate launch artwork and optional mediaThe generation job does not need Etsy OAuth credentials or Etsy buyer data
Subscription and payment workflowPolarCheckout, billing status, and subscription managementListsy records plan and credit events rather than handling card details itself
Connected-shop draft fields and mediaEtsy APICreate, refresh, and read back seller-directed draftsThe workflow does not request Etsy buyer, order, or payment data
03

Etsy access is limited to the seller-directed draft workflow

A seller connects an Etsy shop through OAuth. Listsy uses the connection to create or refresh drafts, attach the selected files and media, and read the draft state back. It does not publish automatically.

Listsy does not request or process Etsy buyer, order, or payment data for this workflow. Disconnecting a shop removes the stored connection credentials for that shop according to the current privacy policy.

04

Billing and generation credits have separate records

The billing provider handles subscription and payment status. Listsy records the plan and credit events needed to run the service. Provider or technical failures release reserved credits instead of committing a completed charge for an unusable result.

Payment and webhook secrets remain in server-side environments. They are not placed in public client configuration.

05

Users keep practical account controls

You can disconnect an Etsy shop and request account or content deletion through support@listsy.app. Disconnecting a shop removes the stored OAuth connection credentials for that shop. Account and workspace records remain while the account is active and may be retained when security, legal, or accounting obligations require it.

Listsy does not currently promise one fixed deletion deadline for every record type. The privacy policy states the applicable retention boundary, and support is the contact for a deletion request or a question about a specific record.

No system can promise absolute security. Report a suspected security issue to developer@listsy.app without sending credentials or private buyer data.

  • Use a unique password and protect the email account tied to Listsy.
  • Review connected Etsy access and disconnect it when no longer needed.
  • Do not paste passwords or access tokens into support messages.
  • Open the final Etsy draft before publishing.

Questions worth answering

Sources checked

Policy and marketplace details can change. These are the pages used for this review. Check Etsy directly before making a listing decision.

Next step

Need a security or data answer?

Use the support page for account help or email the developer address for security and integration questions.

Contact Listsy support