Last updated 18 November 2026
Privacy Policy
Draft, not yet reviewed by a lawyer. Final text and company details come before launch.
1. Who we are
[Company name] OÜ, registered in Estonia under registry code [registry code], at [street address], [city], Estonia, is the controller of your personal data when you use pikisel.art, the Studio, Community, the Blog, Support, the API and the MCP server. Write to support@pikisel.art about anything in this policy.
We collect as little as the Service needs, do not sell personal data, and do not use your content to train AI models.
2. What we collect
- Account: your email address, your username, your password, kept only as a salted hash we cannot turn back into it, and your birthday, which we ask only to check your age: no page shows it, not even to our staff, and only your data export holds it.
- Two-step verification, if you turn it on: your authenticator app’s secret, kept encrypted, and your backup codes, kept only as keyed hashes. For a staff account, its passkeys: their public keys, names, and when each was added and last used.
- Signing in: a record of each sign-in, so that signing out ends it on our side too (no IP address); a random mark for each browser your account has signed in from (no IP address), so that wrong passwords elsewhere cannot lock you out there; sign-in events with their IP address and browser, for security (staff can see them); counts of wrong passwords and codes in a row, by account, or by a keyed hash of an email address being confirmed; and the security notices we mail you, listed in Settings.
- A two-step recovery, if you ask for one: a hash of the browser it was asked from, its times, and a hash of each Cancel link we mail.
- Keys and apps, if you use them: for each API key you make, the name you give it, its last four characters so you can tell your keys apart, what it may do, its daily credit limit, the country it was made from, and when it was made, last used, expires and was removed, and why; the key itself is kept only as a hash we cannot turn back into it. For each app you connect, the name and web address it gives itself, the address it sends you back to, what you allowed it, its daily credit limit, and when you connected it, it was last used and it was disconnected, and why; of the tokens it holds, only its refresh token is kept, as a hash. And a record of each call made with a key or an app that spends, writes, downloads or fails: when, which key or app, what it asked for (such as a drawing, an export or a change to an artwork; the words of a prompt stay with the drawing, not here), how it ended, the credits it took, the IP address it came from and its country, and the name, version and program it gave. Calls that only read and succeed appear only in our server logs, kept for 1 day. When an app runs on its maker’s servers, as most AI assistants do, that IP address is its maker’s, not yours. Our staff can see this record, to answer you and stop misuse. Making or removing a key, and connecting or disconnecting an app, are sign-in events too, and we email you about each new one.
- Your content: what you draw and save, your prompts (typed in the Studio, or sent by your own code or an app you connected), the images you import, how a drawing was made (how many pixels were placed with the Studio’s own tools, and whether it used the AI in the Studio or an imported image), what you share to Community, which is public with your username, what you chose for each shared artwork (whether others may draw on a copy, and whether we may feature it), on a copy, the artwork it was made from, and the shared artworks you like.
- Evidence: the confirmations you give (which text, when, a keyed hash of your IP address, your browser’s user agent, and your username at that moment).
- Payments: your credit balance and its history; and, when you buy credits, what you bought, the amount, the receipt, the payment provider’s reference to it, and the country your IP address is in when you pay, as tax evidence of where you are.
- AI drawings: a record of each one you ask for: when, which model, its credits and how it ended, with the IP address it was asked from.
- Support: the requests and messages you send us.
- Technical: a keyed hash of your IP address, and your browser, with each view of a Blog post; when you open a shared artwork or pass it on, a keyed hash of your IP address and browser with the day, and one of your IP address with the day, so that each visitor counts once a day in its views and shares; your IP address in rate-limit counts that expire within a day; and error reports, with personal data removed. With the confirmations you give, only a keyed hash of your IP address is kept.
- Usage: product events such as “Studio opened” or “artwork shared”; which share button was pressed on a shared artwork or a blog post, and where, never who pressed it; on the live site, page views counted by Vercel Web Analytics without cookies: the page’s address, the site you came from, your country, region and city, and your browser, system and kind of device, telling visits apart only within a day, by a hash it then discards; and your cookie choices.
We get this from you, from your browser when you use the site, and from your own code and the apps you connect when they call us for you. Please do not put other people’s personal data in your prompts or imported images.
3. Why we use it, and on what basis
- To provide the Service you asked for (contract): your account, signing in and two-step verification, drawing, downloads, the API, the MCP server and the apps you connect to them, the likes you give, payments, receipts, support, and the emails these need.
- To meet legal duties (legal obligation): checking your age, accounting and tax records, sanctions compliance, and answering lawful requests.
- To keep pikisel safe and fair (legitimate interests): security, rate limits, the captcha, refusing breached passwords and throwaway email addresses, telling you about sign-ins and changes to your account, preventing fraud and abuse, linking accounts that act together to get around a limit or a ban, investigating abuse and keeping its records, keeping likes and counts honest, checking content against our rules, following up copyright reports, keeping evidence of the confirmations you gave, keeping a record of what each key and app did to give it to you in your data export, answer you about a spend and stop misuse, checking where you are when you make a key or connect an app, and fixing errors.
- To improve and present pikisel (legitimate interests): counting how features are used and how often what is shared is passed on, from our own product events; counting page views without cookies; showing on a shared artwork’s page how many people viewed, liked and passed it on, each visitor once a day, so that a reload or a robot adds nothing; and showing how a work was made and, in totals that name no one, how much is drawn on pikisel.
- Copies of shared artworks (contract): a copy’s page names the artwork it was made from and its maker while that artwork is shared, as its maker’s licence says (Terms, section 7).
- Featuring your work (consent): only an artwork you let us feature, with your username, and you can withdraw at any time from the artwork (Terms, section 7).
- The newsletter (consent): only if you ticked it at sign-up, and you can withdraw at any time.
Where we rely on legitimate interests, you can object (section 9).
4. AI and automated checks
- When you ask an AI model for something, what you describe and the images you send go through OpenRouter to the model’s maker, who returns the result. They process it under their own terms, which they may change, and may keep it for a limited time to detect abuse; they are listed with links in section 16 of our Terms. This is the same in the Studio, through the API and through an app you connect. We do not use your content to train AI models.
- From an AI assistant or your own code. When you use pikisel from an AI assistant, what you write to it goes to the assistant’s maker, under its own terms. We receive what the assistant sends us in its calls, such as a drawing’s description; we do not ask for or read your conversation with it. What we send back, such as a drawing, an artwork’s name or your balance, reaches the assistant and its maker, who may keep it with your conversation and use it as their terms and your settings there allow, which may include training their models. You choose the assistant; we do not control it and are not responsible for what its maker does. Our promise not to train AI models on your content is ours alone.
- We check prompts and names automatically against our rules, and new passwords against known breaches (section 5). Your birthday checks that you are 18 or older. A refusal only stops that request; it has no legal effect on you. If you think a check was wrong, you can ask Support to look at it.
5. Who receives it
Our service providers process data for us, under contract, to run pikisel. The AI model makers also use what they receive under their own terms (section 4 and the Cookie Policy):
- Vercel
- Runs the website and its functions, and counts page views on the live site without cookies (Web Analytics).United States company; functions run in Frankfurt, Germany
- Supabase
- Our database and private file storage.Frankfurt, Germany
- Hetzner
- Our server for background work: the deletions this policy promises, and mail that waits for its turn.Germany
- Cloudflare
- Stores and delivers the public images of what you share, and the preview cards of their links, runs the check that a sign-up or sign-in comes from a person (Turnstile), runs our DNS and forwards our email. It sees the IP address of whoever loads an image or the check.United States company; worldwide network
- Upstash
- Counts requests for rate limits, by account, key, app and IP address, and how many times a download link was used. The counts expire on their own, within a day.Cloud service
- Resend
- Sends our emails.United States
- OpenRouter
- Passes your AI requests (what you describe and the images you send) to the model makers, and returns the result.United States
- AI model makers
- Make the drawings: Google (Nano Banana 2.1, Nano Banana 2 Lite, Nano Banana Pro), OpenAI (GPT Image 2.6 Flare, GPT Image 2.6 Sunburst). They receive your request through OpenRouter, under their own API terms.United States
- Apps you connect
- Only the apps you connect, and only what they ask us for you and what we answer. They are not our service providers: you choose them, and their makers use what they receive under their own terms.Where their makers run them
- Have I Been Pwned
- Tells us whether a password you set is in a known breach. It receives only the first five characters of the password’s SHA-1 hash, never the password or your email.Australia
- Sentry
- Records errors so we can fix them, with personal data removed before it is sent.European Union
- Our promotion
- Only for an artwork you let us feature: the social networks, ad platforms, agencies and printers that make or carry our promotion receive the artwork and your username.Worldwide
When you buy credits, the payment provider that takes your payment receives what it needs for it, under its own privacy terms. We also share data with authorities when the law requires it, with advisers bound to confidentiality, and with a company that takes over pikisel, under this policy.
6. Outside the European Economic Area
When an app names itself by a web address, as most AI assistants do, our server reads the short document at that address to learn the app’s name and where it may send you back, and keeps it for up to an hour. That request carries nothing about you: not your account, your email or your IP address. We do not load an app’s logo from its maker’s site.
Some providers above are outside the European Economic Area or work worldwide. When your data goes outside it, we rely on a European Commission adequacy decision, including the EU–US Data Privacy Framework for providers certified under it, or on the Commission’s standard contractual clauses. Write to us for a copy of the safeguards that apply.
When you connect an app or call the API from your own code, what you ask for goes wherever that app or your code runs, because you asked for it; the app’s maker handles it under its own terms.
7. Public by design
- What you share to Community is public with your username until you stop sharing. Nothing you draw has a public link until you share it. A download link your app asks for is private and short-lived: it works for 15 minutes and 3 downloads, for whoever has it, so treat it as a secret.
- Others can save or screenshot what they saw while it was shared; we cannot take back those copies.
- Wherever anyone shares a shared artwork’s link, its preview shows the artwork, its name and your username; the site it is shared on keeps its own copy of the preview, under its own rules.
- If you let others draw on a copy, people with an account can make one. A copy stays with them after you change your mind, and while your artwork is shared its page names you.
- A shared artwork’s page, and its card in Community, show how many people viewed, liked and passed it on. The numbers name no one: the site shows nobody, its maker included, who viewed, liked or passed it on. Our staff can see who liked what, to keep the counts honest.
8. How long we keep it
- Account data, with your birthday, two-step verification and passkeys: until the account is deleted, 30 days after you ask, unless you sign in meanwhile and keep it. A staff account’s passkeys also go with its staff role.
- Sign-in events, with their IP address and browser: 90 days. A sign-in’s record: until you sign out, and 14 days at most. A browser’s mark: until 400 days after it was last seen. Counts of wrong passwords and codes: 90 days after the last one. Security notices: 90 days. A two-step recovery: until it ends. A sign-in waiting for its code: one day. A passkey’s challenge: 5 minutes.
- Your keys and apps: until you remove them, they end, or the account is deleted; after that, their names, dates and why they ended, 90 days. The record of calls made with them: as long as your account, except the IP address and the program a call came from, which go after 90 days; a call refused before we knew whose it was, 90 days. An app’s request to connect and its one-time code: 10 minutes, swept within a day. The tokens an app holds: its refresh token, as a hash, until it ends; the short-lived access tokens are not stored. A download link: nothing is kept after it expires but a count of its uses, which expires with it.
- The Idempotency-Key an app or your code sends with a call that makes an artwork or a layer, kept with which of your API keys sent it, a fingerprint of that call and what it made, so that sending it again makes nothing twice: 24 hours, swept within a day.
- The IP address a paid AI drawing was asked from, kept with its record against abuse and fraud: 90 days.
- The confirmations you gave: kept after account deletion, without your email, for copyright and legal follow-up, for as long as a claim about them can be brought. A confirmation keeps the username it was given under, because it is the evidence of who gave it.
- Payments and receipts: kept after account deletion, without your account, for as long as accounting and tax law requires: at least seven years, and ten for the records of EU VAT on digital services.
- Records of an investigation, a breach of our Terms or a dispute: while it lasts, and after it for as long as a claim about it can be brought.
- Drawings you have not saved, made in the Studio or through a key or an app, with their prompts: 30 days. Saved ones: until you delete them or the account. A deleted artwork stays in Recently deleted for 30 days, where you can put it back, and is then deleted.
- What you share to Community: the public copy goes when you stop sharing, delete the artwork or the account, or when our team takes it down. Copies held by the delivery network usually go with it within minutes.
- Support requests: deleted with the account, apart from what the confirmations above keep.
- Blog page views: one year; deleting the account takes their hashed IP address and browser at once. Our record of your cookie choices: two years (the cookie in your browser: one year). Product activity: 13 months, then deleted. It is what you open, make and share in the Studio, counted for our own figures; if you delete the account first, it is kept without your account for the rest of that time.
- What you chose for a shared artwork: with the confirmations above. A copy someone made of your artwork is theirs, kept as their own artworks are.
- Your likes: until you take one back, or the account or the artwork is deleted. The hashes behind a shared artwork’s views and shares: deleted within two days; its counts name no one and stay with the artwork.
- What we made while you let us feature an artwork: for as long as it is published. Printed material we have handed out is beyond our reach.
- Page views counted by Vercel Web Analytics: as numbers that name no one, for Vercel’s reporting window, 12 months on our plan.
- Backups are overwritten on their own schedule.
9. Your rights
You can ask to see, correct, export or delete your data, to restrict or object to how we use it, and withdraw a consent at any time. Export everything as JSON (your keys, never the keys themselves, your apps and the record of their calls included) and delete your account in Settings, which removes your keys and disconnects your apps at once; for the rest, write to support@pikisel.art. We answer within one month, or within three where the GDPR allows it for complex or many requests, and then we tell you why within the first month. We may ask you to confirm a request from the email on your account. A deletion leaves what section 8 says we keep, and what the law or an open investigation or dispute requires. As the GDPR allows, we may refuse, or charge a reasonable fee for, requests that are manifestly unfounded or excessive, in particular repeated ones.
You can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or to the authority where you live.
10. Children
pikisel is only for people aged 18 or older, and we ask for your birthday at sign-up to check it. We do not knowingly collect data from children; if we learn that we have, we close the account and delete its data, except what the law makes us keep.
11. Security
We protect your data with technical and organisational measures suited to the risk. No system is perfectly secure, and we cannot promise that yours will never be reached by someone who should not reach it.
12. Changes
We may change this policy and post the new version here, with its date. When a change matters to you, we tell you in the product or by email, and we tell you before we use your data for a new purpose.
13. Contact
[Company name] OÜ, [street address], [city], Estonia. Email support@pikisel.art.