Start with 300 bonus credits if you go Premium in the first 72 hours. See plans

Privacy

What Yumee knows

As little as we can, and this page is the whole list. It is short because the list is short, not because anything has been left out.

Last updated

What we store, and why

An account is a small record and a few things that belong to it. This is all of them, each with the reason we keep it and the legal basis the GDPR asks for: contract (Art. 6(1)(b): what running your account and the apps needs), legitimate interest (Art. 6(1)(f): keeping accounts safe and knowing which apps are in use) or legal obligation (Art. 6(1)(c): what accounting and tax law makes us keep).

What Why we keep it Legal basis
An e-mail address, or a handle Whichever you signed up with. It is how you sign in, and the e-mail is how you get back in if you lose your password. Contract
Your password, scrambled Never the password itself: we keep a one-way hash of it, so nobody, us included, can read or tell you your password. Contract
A display name, a time zone, a language The name and time zone only if you set them; the display name does not have to be your real name. The language is English unless you ask us for another. Contract
Sessions For each browser you sign in from: when it started and was last used, its IP address and the browser's description of itself, so you can see and sign out every place you are signed in. Legitimate interest: security
Devices For each desktop app you pair: the computer name it reports, its system and the app's version, so your device list can name the computer you want to remove. Contract
What you own Which apps, on which plan, since when and until when. Contract
Credits and payments Your balance and its history, a record of each payment and refund, and any withdrawal statement you send us (the name and e-mail address you give in it). See Credits and payments. Contract; the payment records and withdrawal statements also legal obligation
Welcome credits and offers A one-way hash of your address, so each mailbox gets the welcome credits once; which offers your account used; an offer to come back after a plan ends, and whether you want offer e-mails. See Credits and payments and E-mail. Legitimate interest: fair use of free credits, and telling customers about our own service
Items you mark as listed in Vintee Only when you press Mark as listed: for that item its code, title, brand, size, category, price, status (listed, reserved or sold), the sold price and the dates, and one small preview picture (a JPEG of at most 1024 pixels with its metadata removed). It is what lets your Listings and your labels work on any computer. Kept until you remove the item or delete the account. Contract
What you keep in Hookee The hooks you saved and the versions of a hook you chose to keep (their text). Kept until you remove them or delete the account. What you type into the search is used to answer it and is not stored. Contract
Which apps you opened, and when See the next section. It is the thinnest record we keep, on purpose. Legitimate interest: knowing which apps are used, and your dashboard
Sign-in attempts What was typed as the name or e-mail, the IP address, the time and whether it worked. It lets us slow down anyone guessing passwords and answer "was my account broken into?". Legitimate interest: security
Signing in with Google Only if you use Continue with Google or connect Google on your account page: the number Google gives your Google account (it never changes), the e-mail address Google reported when it was connected, and when it was connected and last used. If you make your account with Google, the name Google gives becomes your display name, and the address counts as confirmed. We never see your Google password. Contract
Networks you signed in from For each network: the IP address with its last part removed (the first three of the four numbers of an IPv4 address, the first half of an IPv6 address) and when it was first and last used. A sign-in from a network your account knows asks for nothing more; one from a new place asks for a code we e-mail you. Legitimate interest: security
Remembered devices Only when you tick Remember this device: a scrambled copy of a random key your browser keeps, which browser and system it said it was, and when it was remembered and last used, so signing in there asks for no code for 30 days. Legitimate interest: security
Sign-in codes A code we e-mail you for a sign-in from a new place is kept only as a one-way hash, with how many tries and e-mails it took, so it can be checked once and nobody can guess it. Legitimate interest: security
A log of changes to accounts When an account was made, its e-mail address or password changed, a device was paired or signed out, and what we changed by hand (credits given or taken back, a plan, a suspension), each with the time and the IP address it came from; for an e-mail change, the old and the new address. It lets us answer "what happened to my account?". Legitimate interest: security

Which app, and when, and nothing else

When you open an app, it tells us that it was opened: your account, which app and version, the kind of computer and the time. Each day that becomes a single line per app, which is what your dashboard shows when it says you used something on forty-one days.

We learn that an app was opened. We learn nothing about what you do inside it: no screens, no clicks, no text, no numbers you typed.

Credits and payments

Your account keeps a credit balance and its history: what came in (a pack, your plan, a refund) and what each piece of work cost, with the app and the kind of work, never its content.

Purchases are processed by Stripe (Stripe Payments Europe, Ltd., Ireland). Stripe handles your card on its own pages and keeps what the law requires it to keep. For fraud prevention, anti-money-laundering and identity checks Stripe acts as a controller in its own right, under its own privacy notice (stripe.com/privacy). We keep Stripe's ids for you and each payment, the amount, and which plan or pack it was for.

Every mailbox gets the welcome credits once. So that deleting an account and signing up again with the same address does not bring them back, we keep a one-way hash (SHA-256) of the address in a simple form (lower case, without a +tag, and for Gmail without dots) and the date it was used. The hash cannot be turned back into the address and is not linked to any account, so it stays after an account is deleted.

When an offer applies to you (bonus credits for a plan bought soon after signing up or after a plan ended, or a seasonal discount), we note which offer your account used, when, and on which plan, so each offer is used once. When a paid plan ends, we note that the account may get one offer to come back, for how long, and whether we e-mailed it. These notes go when the account is deleted.

AI work in the apps

When an app runs an AI step, it sends only what that step needs, through us, to Ollama (Ollama Inc., United States) or Google (the Gemini API):

  • Framee: downscaled still frames from a clip, laid out as contact sheets (up to four per request), and downscaled copies of photos without their metadata (up to eight per request); for the passes that compare or review them, the earlier results as text;
  • Vintee: downscaled copies of your photos without their metadata, in batches (up to 48 per analysis request and 60 per grouping request), and as text the garment's details and, for pricing and writing, some of your own earlier prices and listings;
  • Hookee: when you ask for versions of a hook, the description of your video that you typed and the hook you chose, as text;
  • Yutee: the text of the transcript only, never the video or its sound.

Your footage, whole videos, original photos and your photos' location data never leave your computer. We pass the request on and keep neither it nor the answer; we keep only which task ran, on which model, how big it was, what it cost, how long it took and whether it worked (when it did not, the provider's short error message). We do not use anything you send to train AI models.

Google does not use this data to train its models; it keeps requests for up to 55 days to detect abuse, then deletes them. Ollama processes requests under its own terms and privacy policy (ollama.com/privacy). Still frames can show people, and transcripts contain people's words, so only start AI work on material you are allowed to share this way. Captionee transcribes on your own computer and sends nothing.

Bridgee runs in After Effects on your computer and lets your own AI assistant, Claude, work in your project. What Bridgee shows Claude (your brief, the comps and layers of the open project, and small pictures of the frames it renders) goes from your computer to your own Claude account at Anthropic, under the terms you agreed with Anthropic, and never to us. When Claude looks for stock photos or videos, only the search words go through our server to Pexels or Pixabay, with nothing that identifies you; a picture you then use is downloaded by your computer straight from them.

What we never store

  • Card numbers. You type them into the payment provider's own checkout, and they never reach us.
  • Your location. An IP address implies a rough one, and that is as close as we get.
  • Contacts, calendars, files or anything on your clipboard.
  • What the desktop apps keep on your computer. It stays there; the one exception is the Vintee summary and preview you choose to keep in your account (see What we store).

Cookies and browser storage

yumee_sid keeps you signed in. It holds a random identifier and nothing else, is set when you sign in, and stops working when you sign out or the session ends. Scripts on the page cannot read it.

yumee_lang holds your account's language, en or sk, so every page shows the same one.

yumee_td is set only when you tick Remember this device as you sign in. It holds a random key for each account remembered on this browser (up to five) and nothing else, and lasts 30 days. yumee_oauth is set when you use Continue with Google and holds a random key for an hour, so the answer coming back from Google is accepted only by the browser that asked for it. Scripts on the page cannot read either.

In your browser's storage, yumee.mascot.v2 keeps the pictures of our mascot so they appear without a flicker. It holds no information about you, and your browser can clear it at any time.

When you close the offer line above the page header, an entry named yumee.offer.hidden: and the offer keeps it closed in this browser. It holds nothing about you.

There is no cookie banner because there is nothing to ask you about: everything above does a job you asked for, none of it tracks you, and none of it is shared with anybody.

Trackers and analytics

There are none: no analytics, no advertising pixels, no heat maps, no session recording, no embedded widgets. Our pages load their scripts, styles and fonts from our own server, with two exceptions:

  • the checkout itself happens on the payment provider's own pages;
  • our host's network may show a short automated "are you a person?" check, provided by Google reCAPTCHA, to a visitor it suspects of being a bot.

E-mail

We only write when something you did needs it, or when the law or our terms ask us to tell you something: confirming an address, resetting a password, sending a code when you sign in from a new place (with the browser and the time, so you can tell whether it was you), telling you your password or address was changed, confirming a purchase, a refund, a withdrawal or a complaint, telling you at least 30 days ahead about a change to the price or the terms of a plan you pay for, and warning you 30 days before an unused free account is deleted. There is no newsletter. An account without an e-mail address never gets anything from us.

The one exception is an offer: when a paid plan of yours ends, we may send you one e-mail offering bonus credits if you come back. You get it at most once. We send it because we have a legitimate interest in telling a customer about our own service after a purchase, and you can say no at any time: in the e-mail itself with one click, or with the "Offer e-mails" switch on your account page. Saying no is kept on your account, with the date.

When you write to us with the form on the support page, we keep what you wrote (the topic, the subject, the message, the address to answer to and your account) and send it to our inbox, so we can answer you and nothing gets lost.

Where it lives

On servers in the European Union run by our host, Hostinger. Our host's network serves the pages to you from locations around the world, so a page you load may pass through a server near you outside the EU; the data itself stays on the servers in the EU. We make a copy of the data every day and keep the newest fourteen, so something deleted can remain in a copy for up to two weeks. Our host also keeps backups of its own.

Who handles it

The Yumee team, and the companies below, each for its own part and nothing more. We do not sell anything to anybody.

Who What reaches them
Hostinger Our servers and database in the EU, and the network that delivers the pages. Everything on this page is stored there.
Stripe Your payment, if you buy something, and, to set up your customer record the first time you do, your e-mail address, your display name (or handle) and your account number. Card details go straight to Stripe. A controller in its own right for fraud prevention and legal checks.
Resend Your e-mail address and the text of the e-mails we send you.
Google What an app sends for an AI job you start (Gemini API). If you sign in with Google, Google also learns that you signed in to Yumee, and tells us your Google account's number, e-mail address and name (see What we store); that happens on Google's own pages, under Google's own privacy policy.
Ollama What an app sends for an AI job you start.
Pexels The words of a stock search Bridgee makes for you, sent from our server with nothing that identifies you, and your computer's address when it downloads a picture you use.
Pixabay The same as Pexels, for its own pictures and videos.

Outside the EU

Your account data is stored in the EU, but some of the companies above are outside it or belong to groups that are, so what reaches them may be processed abroad:

  • Resend (United States) stores its account data and e-mail logs in the United States, under the European Commission's standard contractual clauses;
  • Google and Stripe are certified under the EU–US Data Privacy Framework and also use the standard contractual clauses;
  • Ollama (United States) is not certified under the Data Privacy Framework and we have no data processing agreement with it, so what an app sends it for an AI job is processed in the United States without those safeguards. We send it as little as each job needs and nothing that identifies your account.

How long we keep it

  • Sessions end when they expire or when you sign out; the record of an ended session is cleared out a week or more later.
  • A pairing code expires ten minutes after an app asks for one.
  • Sign-in attempts are deleted after 90 days.
  • Requests our security refused in a way no Yumee app ever would (a forged token, a page that is not yours, a flood of tries) are logged with the IP address and account and deleted after 90 days. When they add up, the address and the account are paused automatically; a pause, and a review you ask for, is kept as a record until the account is deleted.
  • Each record of an app being opened is deleted after 90 days; the daily summary (one line per app per day) is kept while your account exists.
  • Your credit history and the log of AI tasks (which task and model, its size, cost, time and outcome) are kept until the account is deleted; a request our server refused before it reached a provider is deleted after 90 days.
  • Error messages from our own servers are kept for 90 days after they last happened, with e-mail and IP addresses masked.
  • An item you marked as listed in Vintee is kept until you remove it or delete the account.
  • A hook you saved in Hookee, and a version you kept, stay until you remove them or delete the account.
  • The results of a Bridgee stock search are kept for one day, so the same search is not sent twice; they are filed under a scrambled key, never with who searched.
  • If you turn on two-step sign-in, its secret is kept encrypted and your recovery codes only as one-way hashes; turning it off or deleting the account deletes them.
  • A network you signed in from is forgotten 90 days after it was last used. A remembered device is forgotten after 30 days, or sooner when you forget it on your account page, change or reset your password, or turn two-step sign-in on or off.
  • An e-mailed sign-in code works for ten minutes; its record is deleted an hour after that. A sign-in with Google that was started but not finished is deleted after ten minutes, and a new account from Google that you did not confirm after fifteen.
  • The link to your Google account is kept until you disconnect it on your account page or delete the account.
  • Payment records and withdrawal statements are kept as long as Slovak accounting and tax law requires (ten years), even after an account is deleted; they are then no longer linked to it.
  • The log of changes to accounts (it holds IP addresses) is kept for 24 months; when an account is deleted, its entries go with it.
  • Messages sent with the contact form are deleted after 24 months.
  • A free account nobody has used for 24 months (no sign-in, no app, no session) is deleted, after a warning e-mail 30 days before, if it has an address. Accounts with a plan or a purchase are kept.
  • The one-way hash that marks a mailbox's welcome credits as used is kept for good; it names nobody. Which offers an account used, and its offer to come back, are kept until the account is deleted.
  • The daily copies of the data are replaced after fourteen days.
  • Everything else is kept until you delete your account (on your account page) or ask us to.

Age

Yumee is for people aged 18 or over. We do not knowingly keep data about anyone younger; if you think we do, write to us and we will delete it.

Your rights

Under the GDPR you can ask us, free of charge, for:

  • access: a copy of what we hold about you (Art. 15);
  • rectification: correcting what is wrong (Art. 16);
  • erasure: deleting it, except what the law makes us keep (Art. 17);
  • restriction: keeping it but not using it while something is sorted out (Art. 18);
  • portability: your data in a file another service can read (Art. 20);
  • objection: to anything we do on the basis of legitimate interest (Art. 21).

Write to contact@yumee.org. You get an answer within a month. We may first ask you to show that the account is yours, so that nobody else can ask for it.

Getting it, or getting rid of it

Both are on the support page. An export is a file with your account, devices, what you own, your day-by-day usage, your credit history, your payments and refunds, any withdrawal statement you sent us and the items you marked as listed in Vintee. You can delete your account yourself, at any time, at the bottom of your account page. Deleting it removes it and everything that belongs to it, in the web apps too, except the payment records and withdrawal statements the law makes us keep, and cannot be undone.

You can also complain to the supervisory authority, the Office for Personal Data Protection of the Slovak Republic (Úrad na ochranu osobných údajov SR, dataprotection.gov.sk), directly or after writing to us.

If any of this changes, this page changes the same day, and so does the date at the top.

Controller

The controller of your personal data under the GDPR, and the seller of everything bought on this site.

Also worth a read: