Pictobank Privacy

This page explains what Pictobank processes across Free, Storage+, Local Processing, share links, account systems, support, and email.

Privacy by Workflow Design

Pictobank separates temporary Free processing, saved Storage+ workflows, and device-first Local Processing so each workflow keeps only the data needed to operate.

Temporary Free Processing

Free compression is designed for temporary processing and download. Compressed free images are not kept as permanent cloud storage unless you choose a saved Storage+ workflow.

Storage+ Cloud Workflows

Storage+ stores exports, folders, Vault metadata, share page records, and snapshot files that you choose to save or share. These files persist until deleted, revoked, expired, or otherwise removed under product rules.

Local Processing

Local Processing runs heavy private workloads on your device where supported. License activation, verification, recovery, replacement, and account-linking still use Pictobank operational systems.

Share Links

Share links are accessible by possession of the link while active. Shared files, metadata, events, and snapshots may be stored so the share page can open, download, expire, and be managed.

Account and Profile Data

Pictobank may store account email, user ID, plan, Storage+ status, billing state, profile records, settings, support tickets, and product ownership links.

Billing Data

Payments, subscriptions, invoices, checkout sessions, billing portal access, and payment method handling are processed by Stripe. Pictobank stores payment references and status needed to operate paid access.

Email and Support Communications

Pictobank uses email for license delivery, recovery, support, admin alerts, billing notices, account operations, and product reliability messages. Support tickets store your email and message content so we can respond.

License Logs

Local Processing recovery, activation, verification, replacement, revocation, and account-linking events may be logged without storing plaintext license keys in operational event tables.

Analytics, Reliability, and Abuse Prevention

Usage, upload, compression, sharing, download, email, purchase, error, and security events may be used to understand product reliability, enforce limits, prevent abuse, and improve operations.

Advertising and Google AdSense

Free Pictobank workflows may be supported by advertising, including Google AdSense-compatible placements or other third-party advertising vendors. Advertising partners may use cookies or similar technologies to measure, limit, personalize, or deliver ads according to their policies.

Cookies and Browser Storage

Pictobank uses cookies, local storage, and browser storage for authentication, settings, workflow state, local license state, analytics session IDs, advertising measurement, and product preferences.

Retention and Deletion

Temporary processing data is kept short-lived where possible. Storage+ data persists until deleted or expired. Share snapshots expire according to share settings and cleanup systems. Operational logs may be retained for security, billing, support, and reliability.

Third-Party Providers

Pictobank uses providers including Stripe, Supabase, Resend, Cloudflare, analytics services, Google AdSense-compatible advertising systems, and third-party advertising vendors for payments, auth, storage, email, hosting, security, analytics, and monetization.

Security Safeguards

Pictobank uses operational safeguards such as account checks, license hashing, safe event logs, throttles, abuse prevention, and admin-only diagnostics to protect users and the platform.

User Responsibilities

You are responsible for the files you process, the links you share, the recipients you choose, the accuracy of support information you provide, and securing your account access.

Contact

Use the support or contact page for privacy questions, account requests, billing questions, license recovery, abuse reports, advertising questions, or data concerns.