Effective: September 25, 2026; last updated: November 7, 2026
This policy applies to the Pixel Studio image editor at
pixels.mrhalk.com and its related account,
cloud sync, sharing, and AI features.
1. Information we process
-
Local editing data: When you are signed out, projects, sessions,
autosaves, preferences, and PWA caches are mainly stored in your browser. Pixel Studio
does not automatically upload local images unless you choose an online feature
described below.
-
Account data: When you sign in with Google, Google and Supabase Auth
provide basic identity data such as an identifier, email address, display name, and
avatar. Pixel Studio requests only the openid, email, and profile scopes needed for
sign-in, and does not request Google Drive or Google Photos access.
-
Pixel Studio cloud projects: When you choose Pixel Studio cloud storage, we
process the project name, complete editable project file, thumbnail, size, revision,
digest, and sync status. Project content is kept in private object storage. Each
project retains up to its 20 most recent revisions; older revisions are removed
after a successful new save. Deleted projects move to Trash and can be restored for
30 days; expired projects and their cloud files are removed by scheduled cleanup.
-
AI and shared content: Image AI sends the image, mask, and prompt
needed for the operation through the Pixel Studio Worker to the model provider used
by that feature. Edit Chat sends your prompt and adjustment settings, not your image.
Providers process data under their own policies. Public image and recipe shares are
uploaded to public storage and may be accessed by anyone with the share link.
-
Custom AI API keys: A custom key you enter stays in this tab's
memory and is sent through the Worker to your selected provider only when you use
that AI feature. Pixel Studio does not save it in browser storage or its application
server. You will need to enter it again after closing the tab.
-
Technical and usage data: The application records request times,
action or model names, status, estimated cost, and administrative audit events. IP
addresses are used during request handling for rate limits and abuse prevention and
are not included in new usage records. Application error logs do not retain raw
upstream provider responses. Administrative API tokens are stored only as
irreversible hashes with metadata; the original token cannot be displayed again.
AI prediction ownership records are used to restrict polling and cancellation to the
account that started the run, then removed after up to seven days.
-
Data transfer choices: Before each type of online feature is used
for the first time, Pixel Studio explains what will be sent and who receives it. You
may allow it for the current session or remember the choice on this device. You can
review and revoke remembered choices in API settings.
2. Specific use of Google Account data
Pixel Studio uses Google Sign-In for identity authentication. The sign-in flow
may provide a stable Google subject ID, email address, display name, and profile image
URL. We use this information to create or find your Pixel Studio account, show account
details, attach cloud projects and personal API tokens to the correct account, and
perform account security and administrative actions.
You can separately connect Google Drive. Pixel Studio uses the drive.file permission to
save and reopen its editable projects in the Drive account you connect and to check
storage usage. A project can include originals, layers and editing data. The Worker
retains the linked account identifier, verified email, encrypted refresh credential,
project revisions and transfer state to support sync and resume. Your browser may
cache verified project chunks during use. You can disconnect in account settings or
revoke access in your Google Account settings. Saved files stay in your Drive, where
you can manage or delete them. Pixel Studio handles data received through Google
Workspace APIs in accordance with
Google's Limited Use requirements.
Supabase Auth retains the identity record, while necessary account snapshots and status
are stored by the Pixel Studio Cloudflare Worker in access-controlled database storage.
Pixel Studio does not sell Google user data, use it for targeted advertising, use it to
train AI models, or send it to an AI provider. Signing in alone does not upload your
images; images are uploaded only when you choose a cloud, sharing, or AI feature.
Identity data is retained while the account is active. If you request account and
related data deletion, we process it subject to reasonable verification, provider
constraints, and legally required retention. You can revoke access in your Google
Account's third-party connections and use the support contact shown on the Google OAuth
screen to request deletion.
3. How we use information
We use this information to authenticate accounts, sync and restore projects, provide AI
and sharing features, enforce quotas and rate limits, protect the service, investigate
errors, and maintain administrative and audit records. We do not sell personal
information or use your images for targeted advertising.
4. Service providers
Pixel Studio uses Google for sign-in and optional Drive storage, Supabase for authentication, and Cloudflare for
website hosting, Workers, databases, caching, and object storage. When you choose an AI
feature, required content may be processed by Replicate or the model or service provider
identified by that feature. Each provider processes data under its own policies and our
service configuration.
5. Retention and security
Local data remains until you clear browser data or use an in-app clearing control.
Public image and recipe share links expire after about 30 days and are removed by
scheduled cleanup. Pixel Studio cloud projects are retained until you delete them, can
be restored from Trash for 30 days, and then receive scheduled permanent cleanup.
Google Drive project files are managed or deleted by you in Drive; disconnecting Drive
does not delete those files. AI inputs
that need staging are kept in private storage and fetched through signed URLs valid for 10 minutes.
They are removed when the Worker observes a prediction completing, failing, or being canceled, with
scheduled cleanup as a fallback. Temporary uploads also receive scheduled cleanup. Security, cost, and audit records may be
retained for longer where necessary. We use encrypted transport, private storage,
short-lived signed URLs, and access controls, but no online service can guarantee
absolute security.
6. Your choices and controls
You may remain signed out and edit locally. You may also delete or restore Pixel Studio
cloud projects, disconnect Drive, revoke
personal tokens, sign out, and clear account data stored on your device. You can revoke
Pixel Studio's sign-in access in your Google Account settings. For account or privacy
requests, use the support contact shown on the Google OAuth screen. This policy remains
publicly available even if you cannot sign in.
7. International processing and children
Service providers may process information outside your location. Pixel Studio is not
directed specifically to children below the age of digital consent in their location. A
guardian who believes a child provided information improperly should use the support
contact to request deletion.
8. Changes to this policy
We may update this policy as features or legal requirements change. We will change the
“last updated” date on this page and, where reasonable, provide an in-app notice for
material changes.
9. Contact and deletion requests
For privacy questions, sign-in revocation, or a request to delete your account and
related data, email haley@mrhalk.com. This contact
remains available even if you cannot sign in.