Privacy Policy

Picnjoy is an AI image generation platform. Subscribers run a workspace with campaigns, themes, and credits. Visitors open a campaign via link or QR Code in a mobile browser, sign in with a magic link, submit a selfie, and receive generated images.

We are not a social network, image bank, or generic photo editor. The focus is campaign operations with subscriber-defined themes, a moderated per-campaign feed, and data isolated by workspace.

The subscriber administers the workspace: configures campaigns, themes, access rules, credit budgets, and feed moderation. Picnjoy provides the platform (access, storage, image generation, payments, and photo delivery).

The campaign organizer is responsible for informing participants about the experience, including when minors are under their supervision. Visitor acceptances in the campaign flow are distinct from the subscriber Terms of Service published on this page.

From a campaign visitor: email (required via magic link); name only when the campaign enables name collection; records of terms acceptance and selfie-processing consent; selfie and visitor-submitted attachments, processed temporarily; generated images and generation details.

From the subscriber: account data (name, email, and authentication) and payment data processed via Stripe for subscriptions and credit packs. We also process workspace configuration (campaigns, themes, members, and metrics).

A visitor's email authenticates campaign access (magic link), links photos to their gallery, and operates the experience. Subscriber account emails are used for authentication, billing, security, and service messages.

We do not sell emails or share them with third parties for spam. Marketing emails are sent only when the visitor grants the optional consent described in section 7, and can be cancelled at any time.

The selfie and additional images submitted by the visitor are stored temporarily, only to generate the result. When generation finishes, fails permanently, or the participant leaves the flow, those files are deleted.

After that, neither the campaign administrator nor Picnjoy staff can access the visitor's original images. Each new generation requires a new capture.

Reference images included by the subscriber in themes are not visitor selfies: they remain theme assets and are therefore the subscriber's responsibility.

AI-generated images remain available for viewing, download, and sharing in the visitor gallery and, if the visitor approves, in the campaign feed. The workspace administrator may archive images to remove them from the public feed; after archiving, the visitor cannot republish that item.

This policy does not set a single retention deadline for generated images: they remain for as long as needed to provide the service and the product's gallery, feed, and archive features, or until deletion or request under applicable law.

There are three distinct acceptances in the visitor flow, presented by Picnjoy: (1) general experience terms; (2) optional consent to receive Picnjoy marketing emails, for the purpose of sending news, offers, and promotional communications about the platform — this consent is not required to join the campaign, may be refused without affecting access, and, if granted, may be withdrawn at any time; (3) specific consent for selfie processing before the camera opens. Granted acceptances are recorded with timestamp and version.

When an administrator operates the camera from their own account, the acceptances needed for the flow may be recorded automatically, without repeating the same confirmation screen.

Visitor images, generated images, and personal data are not used by Picnjoy to train artificial intelligence models. Processing uses generation providers under service contracts; your images do not enter Picnjoy's ongoing model learning.

Data is isolated by workspace. In the panel, the workspace administrator sees campaign member emails, metrics, and AI-generated images — never the visitor's original selfies. Those originals are used only in internal generation processing and are then destroyed; they do not enter the Picnjoy or subscriber dashboard.

Picnjoy may access technical information needed to operate the service (for example, generation status and already generated images), without access to original selfies in the panel.

Generated images are delivered securely and in an authenticated way. Publication on the public feed requires the visitor's explicit approval and respect for administrator archiving.

When a subscriber configures themes with brand elements (logo, visual identity, or reference images), those elements are applied only in the context of that campaign or theme. We do not use client brands for other purposes.

We do not sell personal data. We use providers necessary for operations: payment processing (Stripe), cloud and storage infrastructure, AI generation providers, and service email (magic link and account messages), under contract and for service purposes.

We apply appropriate technical and organizational measures, including workspace isolation and authenticated image access. Visitor selfies are temporary, as described in section 5. Account, payment, campaign configuration, and generated-image data follow retention needed for the service and legal obligations.

Infrastructure backups may exist. Specific backup timelines are not published on this page; data-subject requests are handled through the contact channel below.

You may request access, correction, anonymization, portability, or deletion of personal data, and information about processing, to the extent provided by LGPD and other applicable rules. Contact us at the email below. Some actions on generated images may occur as archiving or visibility removal, depending on product capabilities and the law.

Campaigns may involve minors under the organizer's responsibility. Supervision and guardian consent are the subscriber/organizer's duty. We do not require special categories of sensitive data to generate images.

We may update this policy. The current version will be on this page with the date of the last update.