Hosting and compute
Infrastructure providers may host Pixilo, customer stores, deployment archives, running services, task queues, and operator tools.
Databases
Database providers or managed database services may store platform account and billing records and each customer store's separate data.
Email providers send login links, verification codes, receipts, invoices, order updates, support messages, launch notices, and marketing messages where allowed.
Federated identity
When an owner chooses Continue with Google, Google Identity Services verifies the Google account and returns a signed identity assertion. Pixilo stores the stable Google subject, verified email, link state, and security audit—not the raw ID token, Google password, access token, or refresh token.
Payments and invoicing
Payment and invoice providers process hosted checkout, saved payment methods, recurring charges, payment-status events, receipts, invoices, and reconciliation records.
Storage and backups
Storage providers may hold images, uploads, release-verification records, reports, backup files, and restore evidence under retention policies.
Monitoring and security
Monitoring, logging, security, and verification systems may process operational details needed to detect incidents, verify releases, and keep stores reliable.
Analytics
Analytics providers may receive consented usage events after cookie consent, depending on the configuration enabled for the platform or store.
Provider controls
Before a provider receives personal information, Pixilo should document the service purpose, data scope, access, security duties, incident cooperation, retention or return/deletion terms, permitted subcontracting, and appropriate oversight. Actual contractual and cross-border requirements remain subject to legal review.
Updates
Pixilo may change providers as the product evolves. Material provider or purpose changes should be reflected in this policy or operator documentation.