PicX Studio

Privacy Policy

How PicX Studio collects, uses, shares, and protects your information — including what is handled when you use PicX through ChatGPT or another AI assistant.

Effective date: 12 November 2026 · Last updated: 14 November 2026

1. Who we are

PicX Studio (“PicX Studio”, “we”, “us”) is an AI image and video generation platform. PicX Studio is operated by Elias Slettemark LLC, a Wyoming limited liability company, 312 West 2nd Street #3964, Casper, WY 82601, USA. This Privacy Policy explains what personal data we collect, why we collect it, who we share it with, how long we keep it, and the rights you have over it.

It applies to picxstudio.com, the PicX Studio web application, our public API at api.picxstudio.com, our Model Context Protocol (MCP) connector at mcp.picxstudio.com, and our plugins and integrations for AI assistants such as ChatGPT, Codex and Claude.

For the purposes of the EU/UK General Data Protection Regulation (GDPR), Elias Slettemark LLC is the data controller for the personal data described here. You can reach us about any privacy matter at [email protected].

2. Information we collect

2.1 Account information

When you create an account we collect your email address, your display name, and a provider identifier from your sign-in method. You sign in with Google or with a one-time code we email you. We never receive or store your Google password, and email sign-in uses no password at all.

2.2 Prompts, uploads and generated content

To produce a generation we process the prompt text you write, any reference image, video or audio file you upload, the model and settings you choose, and the resulting output. Generated output is stored on our content delivery network so you can access it from your media library.

2.3 Billing information

Elias Slettemark LLC sells every plan and credit pack. Card payments are processed by Stripe and crypto payments by OxaPay; subscriptions bought before November 2026 through an earlier payment provider continue to be billed there. We receive a transaction record: the plan or pack purchased, the amount and currency, the payment method type and the payment status. We do not collect or store your full card number, CVV, or bank credentials — those are handled by the payment provider. If you dispute a charge, we give the payment provider the records it needs to decide the dispute: your account email and signup date, your purchase and delivery records, and how the purchased credits were used.

2.4 Usage and technical data

  • API and application request logs: endpoint called, model used, credits charged, response status, latency, and timestamp.
  • Device and connection data: IP address, browser and operating system, referring URL, and pages viewed.
  • Product analytics, only if you accept analytics cookies: pages viewed and actions taken in the product, and, through PostHog, session recordings of how pages are used. Recordings mask what you type into form fields.
  • Credential metadata for API keys and connector grants: the key prefix, scopes, creation and last-used time. We store only a cryptographic hash of an API key, never the key itself.

2.5 Support communications

If you contact support, we keep your message and our reply so we can resolve the issue and maintain a service history.

PurposeData usedGDPR legal basis
Create and operate your accountAccount informationPerformance of a contract
Produce the generations you requestPrompts, uploads, settingsPerformance of a contract
Charge credits, take payment, prevent abuse of limitsBilling and usage dataPerformance of a contract; legitimate interests
Keep the platform secure and prevent fraudTechnical and usage dataLegitimate interests; legal obligation
Fix faults and improve the productAggregated usage and error dataLegitimate interests
Analytics and session recordings (Google Analytics, PostHog)Usage events, device data, session recordingsConsent where the law requires it (EU/EEA, UK, Switzerland); elsewhere legitimate interests. Change it in Cookie settings
Send service and account noticesAccount informationPerformance of a contract
Send product and offer emailsEmail addressLegitimate interests, or consent where the law requires it — unsubscribe from any email
Answer support chats (an AI assistant answers first and a person takes over when needed)Chat messages and attachments, name and email address you give, your account details when you are signed inPerformance of a contract; legitimate interests
Respond to payment disputesAccount, purchase and usage recordsLegitimate interests
Meet tax, accounting and legal dutiesBilling recordsLegal obligation

4. Using PicX Studio through ChatGPT and other AI assistants

PicX Studio can be connected to ChatGPT, Codex, Claude and other MCP-compatible assistants. This section describes exactly what happens to your data in that setup, because the data path differs from using our website directly.

4.1 How the connection is authorised

Connecting PicX to an assistant uses OAuth 2.1 with PKCE. You are taken to a PicX consent screen that names, in plain language, exactly what the assistant is asking permission to do — for example generating images, editing images, generating video, or uploading files. A connection is only created after you approve it. The assistant never receives your PicX password, and it never receives one of your long-lived PicX API keys. It receives a short-lived access token limited to the permissions you approved.

4.2 What we receive from the assistant

We receive only the parameters of the specific tool call the assistant makes — for example the prompt text, a model choice, a resolution, or the URL of an image to edit. We do not receive your chat history, and we do not receive any part of your conversation that is not passed into a PicX tool call. We have no access to your ChatGPT account, your other connectors, or your files outside what you pass to PicX.

4.3 What we send back

We return the result of the tool call: generated media URLs, generation status, model name, credit cost, and where relevant your credit balance or plan limits. Tool responses are deliberately scoped to what the request needs. We do not place authentication secrets, internal system identifiers, debugging payloads, or other users’ data into tool responses.

4.4 Credits and spending controls

Generations started from an assistant consume credits from your existing PicX balance, exactly as they would on our website. A connector grant carries a per-session credit ceiling, and higher-cost requests require explicit confirmation before any credits are spent.

4.5 Disconnecting

You can revoke a connection at any time from the assistant, or by contacting us. Revoking a connector grant immediately invalidates the credential behind it and does not affect API keys you created yourself. Once revoked, the assistant can no longer act on your account.

Your use of ChatGPT or any other assistant is also governed by that provider’s own privacy policy, which we do not control.

5. AI model providers and other processors

We do not run generative models on our own hardware. To fulfil a generation we send your prompt and any reference files to the provider that runs the model you chose. We share personal data only with the service providers below, and with contractors who build and operate the service on our behalf, each limited to what they need to do that work.

CategoryProvidersWhat they receive
AI model developersGoogle (Gemini, Imagen, Veo); OpenAI (GPT Image); ByteDance (Seedream, Seedance); Alibaba (Wan, Qwen); Kuaishou (Kling); MiniMax (Hailuo); xAI (Grok Imagine); Black Forest Labs (FLUX); ElevenLabs (voice and sound); Suno (music); and the other models listed in the studioPrompt text, reference files, model settings
Text, vision and speech toolsGoogle (Gemini API); OpenRouter; Smallest (speech-to-text and voice)Prompt text, images or audio you submit to those tools
Servers, database and cacheContabo (virtual server in Seattle, USA)All account and application data
CDN, DNS, security and media storageCloudflare (including R2 storage for media, uploads and database backups)Generated media and uploads, request metadata, IP address
MCP connector serverRailwayConnector requests and tokens
Earlier database copySupabaseAccount data from before mid-October 2026, kept read-only as a backup until it is deleted
Sign-inGoogle (Google Sign-In)Email address, provider identifier
PaymentsStripe (cards); OxaPay (crypto). Older subscriptions: Dodo Payments, WhopBilling details, transaction records, dispute evidence
EmailResendEmail address, message content (sign-in codes, receipts, product email)
Support chatFly.io (chat server); Moonshot AI (Kimi model that drafts the assistant's answers). Transcripts are stored on our own serversChat messages and attachments, name and email address, the page the chat was opened on
AnalyticsGoogle Analytics; PostHog (EU)Pseudonymous usage events, session recordings, IP address
Error monitoringSentryError reports, which can include request details and IP address

Each model provider processes your content under its own terms. Where a provider offers a no-training or zero-retention configuration for API traffic, we prefer it. We cannot, however, guarantee the internal retention practices of a third-party provider, so please do not submit sensitive personal data, health data, financial account data, or government identification in a prompt or upload.

We may also disclose data where we are legally required to, to enforce our terms, to protect our rights or the safety of others, or to a successor entity in a merger or acquisition (in which case we will notify you).

We do not sell your personal data, and we do not share it for cross-context behavioural advertising.

6. Your content, and model training

You keep ownership of what you create. See our Terms of Service for the licence terms that apply to generated content.

PicX Studio does not use your prompts, uploads, or generated content to train any AI model. We do not sell your content, and we do not publish it. Content you explicitly choose to make public — for example by sharing a generation or submitting it to a public gallery — is visible to others until you make it private again or delete it.

7. How long we keep data

  • Account data — for as long as your account is open, then deleted within 30 days of a verified deletion request.
  • Generated media and generation history — until you delete it, or until your account is deleted.
  • Request and usage logs — retained on a rolling basis for security, abuse prevention and billing accuracy, then deleted or aggregated so they no longer identify you.
  • Billing and tax records — retained for the period required by applicable tax and accounting law, which can extend beyond account closure.
  • Revoked API keys and connector grants — the hashed record is retained for audit purposes; the credential itself stops working immediately.

8. Security

We protect data in transit with TLS. Media, uploads and database backups in Cloudflare R2 are encrypted at rest by Cloudflare. Access to production systems is limited to the people who run the service. API keys are stored only as cryptographic hashes, and connector credentials are scoped and expiring. If a breach affects personal data, we will notify affected users and regulators as required by law. More detail is in our Security Policy.

To report a vulnerability, email [email protected]. We aim to acknowledge reports within 48 hours.

No method of transmission or storage is completely secure. You are responsible for keeping your account credentials and API keys confidential.

9. International data transfers

We are based in the United States, our servers are in the United States, and our providers are located in several countries, including the United States and the European Union. Where personal data is transferred out of the EEA, the UK or Switzerland, we rely on an appropriate transfer mechanism, such as the European Commission’s Standard Contractual Clauses or a finding of adequacy, together with additional safeguards where required.

10. Your rights

Depending on where you live, you may have the right to access a copy of your data, correct inaccurate data, delete your data, restrict or object to processing, withdraw consent, receive your data in a portable format, and not be discriminated against for exercising these rights.

How to exercise them: email [email protected] from the address on your account, stating what you would like to do. We will verify the request and respond within 30 days. If we need longer for a complex request, we will tell you why. There is no charge for a reasonable request.

Deleting your account: email [email protected] with the subject line “Delete my account”. We will confirm your identity, then permanently delete your account, generated media, generation history and personal data within 30 days, except records we must keep for tax or legal reasons. Deletion is irreversible, so download anything you want to keep first. Unused credits are forfeited on deletion and are not refundable.

California residents: the rights above cover the CCPA/CPRA rights to know, delete, correct, and opt out of sale or sharing. We do not sell or share personal information as those terms are defined, so there is nothing to opt out of, but you may still submit a request. You may use an authorised agent.

EEA and UK residents: you may lodge a complaint with your local supervisory authority. We would appreciate the chance to resolve it with you first.

11. Cookies and similar technologies

We use cookies and similar technologies (browser storage) in three groups. If you visit from the EU/EEA, the UK or Switzerland (or we can’t tell where you are), a banner asks you to choose on your first visit, and nothing outside “Necessary” that stores anything on your device runs until you accept it. Until you choose, we count visits with PostHog in cookieless mode: nothing is stored on your device, there are no session recordings, and it stops if you reject. Elsewhere, analytics are on by default and you can switch them off. “Accept all” and “Reject all” are equally available, “Settings” lets you choose per group, and your choice is kept for 12 months, after which we ask again. You can change it at any time: (also linked in the site footer). Withdrawing consent stops those tools on the page and deletes the cookies listed for them below.

11.1 Necessary (always on)

These make the service work and cannot be switched off here. Blocking them in your browser will prevent you from signing in and using the service.

NameSet byPurposeLifetime
tokenPicX StudioKeeps you signed in (HttpOnly; not readable by scripts)30 days
auth_statusPicX StudioTells the site that you are signed in30 days
picx_consentPicX StudioRemembers your cookie choice12 months
picx_referral_codePicX StudioOnly when you open a friend’s referral link: the code, sent with your sign-up so the invite is credited30 days
Short-lived sign-in statePicX StudioCompletes a Google or email sign-in you startedMinutes
__cf_bmCloudflareBot and abuse protection for our servers30 minutes
Browser storage (picx_*, theme, sidebar, drafts)PicX StudioYour theme and layout preferences, prompt drafts, the page to return to after sign-in, a checkout in progress. Stays in your browserUntil cleared, or the end of the tab session

Error monitoring (Sentry) sets no cookies; it receives error reports when something breaks, under our legitimate interest in keeping the service working.

11.2 Analytics (with your consent where the law requires it)

Google Analytics 4 and PostHog (EU), including PostHog session recordings in which all typed text is masked. They help us understand which pages and features are used. Google Analytics runs with advertising signals and Google signals off.

NameSet byPurposeLifetime
_ga, _ga_<id>Google AnalyticsDistinguishes visitors and sessions13 months
ph_<project>_posthog (cookie and browser storage)PostHogVisitor and session id, session recording state12 months
picx_utmPicX StudioThe campaign tags (utm_*) of the link you arrived from, handed to analytics; never stored after you reject analytics10 minutes, deleted when read
picx_ftPicX StudioWhere your first visit came from (campaign, ad platform or referring site, and the page you landed on), saved with your account when you sign up; never set without analytics consent90 days

11.3 Support chat

The support chat loads only when you open it (the help button or “Help & support”). It then keeps one item in your browser’s local storage so your conversation survives a page change; you can also email [email protected] instead.

NameSet byPurposeLifetime
sp_support_token (browser storage)PicX StudioKeeps your support conversation across pagesUntil you sign out or clear it

11.4 Payment pages

Checkout pages hosted by Stripe or OxaPay are on their own sites and set their own cookies, for payment processing and fraud prevention, under their own policies.

We do not use advertising or cross-site tracking cookies.

12. Children’s privacy

PicX Studio is only for adults: you must be at least 18 years old to use it. We do not knowingly collect personal data from anyone under 18. If you believe a minor has given us personal data, email [email protected] and we will delete it and close the account.

Our service links to sites and services we do not operate. We are not responsible for their content or privacy practices, and we recommend reading the privacy policy of any site you visit.

14. Changes to this policy

We may update this Privacy Policy as the product and the law change. We will update the “Last updated” date at the top of this page, and for material changes we will give additional notice — by email or an in-product notice — before the change takes effect. Continuing to use PicX Studio after a change takes effect means you accept the updated policy.

15. Contact us

Elias Slettemark LLC — operator of PicX Studio
312 West 2nd Street #3964, Casper, WY 82601, USA
Privacy and data requests: [email protected]
Security reports: [email protected]
Web: picxstudio.com

Start Generating Today

The AI image and video generator built by professionals. Describe it, and get studio-quality photos and videos in seconds.