Pictobank Service Providers

The verified external services that support Pictobank, what each one does, the data involved, when it is used, and whether it is always active or conditional.

Back to Workspace Privacy Policy

Pictobank Service Providers

•••

Last updated: July 2026

1. Fly.io

State: Active. Category: Application hosting and compute. Purpose: Runs the Pictobank web application and server workflows, including temporary server-side processing where a requested workflow requires it. Data: Web requests, network and device information, request headers, operational logs, and data submitted to server workflows. When used: When a browser connects to Pictobank or a requested workflow uses Pictobank server infrastructure.

2. Supabase

State: Active. Category: Authentication, database, and managed storage. Purpose: Supports sign-in, account and entitlement records, operational data, Storage+ Vault records, saved files, share workflows, and first-party product analytics. Data: Account identifiers and email, profile and entitlement records, saved files and metadata, share records, support and operational records, and product event data. When used: When account, saved Storage+, sharing, support, license, security, or first-party measurement features use those records.

3. Stripe

State: Conditional. Category: Payments and subscription billing. Purpose: Provides checkout, subscription management, invoices, the billing portal, and payment-method handling. Data: Billing contact and transaction information entered in Stripe, plus customer, checkout, subscription, invoice, and payment status references shared with Pictobank. When used: When a user starts or manages a paid purchase, subscription, invoice, or billing session.

4. Resend

State: Conditional. Category: Transactional email delivery. Purpose: Delivers requested Direct Email messages and operational messages such as license delivery, recovery, account, support, and reliability notices. Data: Sender and recipient addresses, subject, message text or HTML, and delivery or idempotency metadata needed to send and diagnose the message. When used: When Pictobank sends a requested or operational email through the configured email delivery service.

5. Google AdSense

State: Conditional. Category: Advertising and ad measurement. Purpose: May supply and measure advertising in eligible free workflows when the ad provider is configured and a placement is allowed to render. Data: Browser, device, network, cookie, consent, ad-request, and measurement information handled under Google's advertising policies. When used: Only when Google AdSense is configured for the environment and an eligible ad placement is requested or displayed.

Service Providers documentLast updated: July 2026

This page is structured for reading, printing, and section review. Plain-language helpers explain context but do not replace the controlling policy text.

Reading the register

Active and conditional are different states

Active providers support the application or its managed data layer. Conditional providers receive data only when the related workflow or placement is used.

Active

Part of the running application or its managed account, data, and storage infrastructure.

Conditional

Used only for a related billing, email, or eligible advertising interaction.

First-party analytics

Pictobank product events are collected by Pictobank and stored in Supabase; no separate analytics vendor is listed.

Verified register

Current service providers

This register names providers verified in the running product configuration or source integration.

Fly.io

State: Active
Category: Application hosting and compute
Purpose: Runs the Pictobank web application and server workflows, including temporary server-side processing where a requested workflow requires it.
Data: Web requests, network and device information, request headers, operational logs, and data submitted to server workflows.
When used: When a browser connects to Pictobank or a requested workflow uses Pictobank server infrastructure.

Supabase

State: Active
Category: Authentication, database, and managed storage
Purpose: Supports sign-in, account and entitlement records, operational data, Storage+ Vault records, saved files, share workflows, and first-party product analytics.
Data: Account identifiers and email, profile and entitlement records, saved files and metadata, share records, support and operational records, and product event data.
When used: When account, saved Storage+, sharing, support, license, security, or first-party measurement features use those records.

Stripe

State: Conditional
Category: Payments and subscription billing
Purpose: Provides checkout, subscription management, invoices, the billing portal, and payment-method handling.
Data: Billing contact and transaction information entered in Stripe, plus customer, checkout, subscription, invoice, and payment status references shared with Pictobank.
When used: When a user starts or manages a paid purchase, subscription, invoice, or billing session.

Resend

State: Conditional
Category: Transactional email delivery
Purpose: Delivers requested Direct Email messages and operational messages such as license delivery, recovery, account, support, and reliability notices.
Data: Sender and recipient addresses, subject, message text or HTML, and delivery or idempotency metadata needed to send and diagnose the message.
When used: When Pictobank sends a requested or operational email through the configured email delivery service.

Google AdSense

State: Conditional
Category: Advertising and ad measurement
Purpose: May supply and measure advertising in eligible free workflows when the ad provider is configured and a placement is allowed to render.
Data: Browser, device, network, cookie, consent, ad-request, and measurement information handled under Google's advertising policies.
When used: Only when Google AdSense is configured for the environment and an eligible ad placement is requested or displayed.

Last updated: July 2026