pinkcel

Privacy Policy

Effective: October 18, 2026

The short version: pinkcel is local-first. Your projects live in your browser and — if you choose — in your own Google Drive. Our servers never receive, store, or read your project files. We run no third-party analytics and set no tracking cookies.

What runs where

The pinkcel editor (app.pinkcel.com) runs entirely in your browser: drawing, rigging, animation, rendering and export all happen on your device. Project data is stored locally in your browser (localStorage and IndexedDB) for autosave and preferences (e.g. interface language).

Google sign-in and Google Drive (optional)

If you click “Sign in”, we use Google Identity Services to authenticate you. We request the minimal drive.file permission: pinkcel can only see and manage files that pinkcel itself created in your Drive — it cannot read the rest of your Drive. Files you save go directly from your browser to your Google Drive; they never pass through our servers.

So that Google's sign-in window can open right away, the editor downloads Google's sign-in script a moment early: when you point at or choose “Sign in” or a Google Drive command, or when an earlier sign-in is being restored. Until you sign in, Google sees only that ordinary download request (your IP address and browser); the editor loads nothing from Google otherwise.

From your Google profile we use your name, e-mail and avatar solely to show who is signed in. Our account service keeps your e-mail together with your plan (free or Pro) and, while a sign-in session is active, your name and avatar URL; the session record is deleted when you sign out, and the account record on request at support@pinkcel.com. You can revoke pinkcel's access at any time at myaccount.google.com/permissions. Google's own processing is governed by the Google Privacy Policy.

What our servers do see

Like any website, our web server keeps standard technical logs (IP address, request path, browser user-agent, timestamp) used only for security and keeping the service running. Logs are rotated and are not used for profiling or advertising.

Cookies and analytics

We collect a small amount of first-party, cookieless usage statistics so we can see whether the site and the editor are used at all and which parts are worth improving. Our own script sends to our own server: the page you are on, how long it stayed visible, the site that referred you (or the source tag of the link you followed, such as utm_source=chatgpt.com), a coarse device and browser type, and — in the editor — which features are used (a tool was picked, an export was made). It never includes your drawings, files, project names or any other content.

The editor also reports a few technical signals so we can find what breaks or gets in the way: when something goes wrong, the type of error and where in our own code it happened (never your files or their names), and for Google sign-in or Google Drive problems a short error code from a fixed list (such as "popup blocked" or "network"), never Google's message, your e-mail or file ids; how long the editor took to load and whether your browser supports WebGL; and signs of trouble, such as repeated quick clicks on one button or many undos in a row. They are collected and counted exactly like the usage statistics above.

Visitors are counted with a daily-rotating hash of your network (the first three parts of an IPv4 address, the first three groups of an IPv6 one) and browser signature. It is not stored in your browser, it cannot identify you across days, and it is never shared with anyone. If you are signed in, feature usage is associated with your account so we can understand how signed-in users work; sign out and you are counted as an anonymous visitor again. We honor the Global Privacy Control signal: when your browser sends it, nothing is collected.

No third parties are involved and no cookies are set — not for analytics, not for advertising. The only browser storage we use is strictly functional (your language choice, your local autosave). After you sign in, a random session token is also stored in your browser's localStorage so you stay signed in across page reloads; it is strictly necessary for the sign-in feature, involves no tracking, and is deleted when you sign out. That's why there is still no cookie banner here — there is nothing to consent to.

Feedback

If you send us feedback from the editor, we store your message, its type (idea, problem, question) and a little technical context so we can understand and fix what you report: the app version, interface language, active tool, window size and a coarse device, browser and operating system type. Feedback is anonymous unless you enter an e-mail address in the optional reply field; we then keep that address only to answer you. We do not attach your account or your IP address to the message. To have a message deleted, write to support@pinkcel.com.

Children

pinkcel does not knowingly collect personal information from children. Signing in with Google is optional and subject to Google's own age requirements.

Changes

If we ever add features that change what data is processed (for example sharing links or paid subscriptions), this policy will be updated first and the effective date above will change.

Contact

Questions about privacy: support@pinkcel.com.