Privacy Policy

Yungle is built privacy-first and hosted entirely in the EU. This policy explains what we collect, why, and the rights you have under the GDPR. Yungle is the data controller for your account data.

What we collect

Account data: your email address and sign-in sessions.
Content: the files you upload and their metadata (name, size, type). File bodies are encrypted at rest.
Transfer data: sender/recipient emails and an optional message, for as long as a transfer lives.
Contacts: names, company, email addresses and phone numbers you choose to save in your address book — details about other people, provided by you.
Billing data: subscription status and payment records (handled by Mollie — we never see full card details).
Technical data: limited logs and rate-limit counters (e.g. IP address) needed for security and abuse prevention.
Usage statistics: anonymous, aggregate page views collected without cookies or device fingerprinting, so we can see which pages are used.
Referrals: if you joined through someone’s invite, which invite code you used (so both of you can be rewarded), and a one-way hash of the card or bank account used for the free month (so each card gets one). The person who invited you sees a count, never who you are.
Affiliates: if you join the affiliate programme, your payee details (name, address, country, VAT number, PayPal address) and your commission records. Clicks on affiliate links are counted per day without cookies or IP addresses.
Bandwidth totals: how many bytes your account has served each month. A running total only — no record of which file, when, or by whom, and it is deleted with your account.

How your files are protected

Every file is encrypted at rest with a unique per-file key (envelope encryption, AES-256-GCM). Those keys are themselves encrypted by a master key held outside the database. Because keys are per-file, we can honour a deletion or takedown by destroying a single key, making that content permanently unrecoverable. Files are stored on Hetzner, an ISO 27001-certified, renewable-powered cloud provider, within the EU (Germany). Your data is never transferred outside the EU/EEA.

Why we process it (legal bases)

To provide the service you asked for — performance of our contract with you.
To keep Yungle secure and prevent abuse — our legitimate interests.
To take payment for the paid plan — performance of contract.
To meet legal obligations, such as responding to lawful takedown notices.

Retention

Free transfers and their metadata are deleted 7 days after creation. Paid collection files are retained for as long as the plan is active. If a plan lapses, content is kept for a further 90 days and then deleted; the account holder is emailed the date. Deleting your account erases your files, keys, and personal data immediately. Copies in our encrypted backups are not edited one by one; they age out on their own, within 14 days for the database and 30 days for file data. We keep minimal billing records where required by law and a tombstoned audit trail of security-relevant events.

Contacts are the exception to everything above expiring: they have no time limit and are kept until you delete them, or until you delete your account. You can delete any contact at any time, and export the whole address book as JSON from your account settings.

Contacts you save about other people

Your address book holds details about people who may never have used Yungle. For that slice of data you decide what is stored and why, so you are its controller and we process it on your behalf under our data-processing agreement — please only save details you have a lawful basis to keep. If one of your contacts asks you to correct or remove their details, you can do it yourself from the Contacts section; if they contact us instead, we will point them to you and help you action it. Contacts are visible to anyone you have added to your workspace, and they are never used to advertise, profile, or contact anyone on our own behalf.

Apps you connect: the API, the CLI and AI assistants

You can connect other software to your account: your own code with an API key, the command-line client, or an AI assistant such as ChatGPT, Claude or Cursor through our MCP server. Each one sees only what you allow it to — read access, creating links, or emailing recipients, which is a separate permission you grant on its own.

What we store: the name of each key or connected app, the permissions you gave it, when it was last used, and a one-way hash of its credential — never the credential itself.
Sign-ins by connected apps last an hour and renew themselves; an app unused for 30 days has to be connected again. You can revoke any key or app at any time under Settings → API keys, which takes effect immediately.
Webhooks you set up send event details (for example, that a transfer was downloaded, with the recipient address) to the URL you chose. We keep the delivery log for 30 days so you can debug an integration.
We do not send your data to any AI provider. When you connect an AI assistant, that assistant reads your data through the permissions you granted, and its provider handles what it receives under your own agreement with them.

The browser extension

Yungle for Chrome and Firefox sends files from your browser the same way the website does. It is a connected app like the ones above, signed in with your permission.

What it can reach: yungle.co, to sign in and send. Gmail and Outlook on the web only if you switch on the compose button, and there only to add that button and put the link into the email you are writing.
What it never does: read, store or send your emails, your mail contacts or your browsing history. Nothing on a page leaves your browser unless you pick it and press send.
What it keeps in your browser: its sign-in (which lasts an hour and renews itself, like any connected app) and your settings. Signing out, or removing the extension, ends that sign-in; you can also revoke it under Settings → API keys.
It contains no analytics or tracking of its own. Files you send through it are handled exactly like files sent from the website.

Sub-processors

We share the minimum necessary with a small set of providers. Almost all store data in the EU; where one does not, it says so:

Hetzner Online (Germany) — encrypted object storage & hosting.
Mollie (Netherlands) — payment processing for the paid plan.
Brevo (EU) — transactional email (sign-in links, invites, notifications).
Cloudflare (R2 storage, EU jurisdiction) — nightly offsite backups of the database and of the already-encrypted file data, kept in the EU. Cloudflare is a US company.
Simple Analytics (Netherlands) — cookieless, privacy-first page statistics on our public pages. No cookies, no cross-site tracking, no personal data or device fingerprints collected. The script is served from yungle.co and page views are passed on by our own server without your IP address, so your browser never contacts Simple Analytics directly.
OpenAI (United States) — only for visits that came from a ChatGPT ad: a report that the ad led to a sign-up, a first transfer or a plan, with OpenAI’s own ad reference and nothing about you. See “If you arrive from an ad in ChatGPT”.
PayPal (Luxembourg; a US company) — affiliate payouts only. It receives an affiliate’s PayPal address and the amount paid, nothing about customers.
The EU VIES service (European Commission) — when a business enters a VAT number, we check it there to apply the reverse charge. Only the VAT number is sent.

Your rights

Under the GDPR you can access, correct, export, or erase your personal data, and object to or restrict certain processing. You can export your data as JSON from your account settings, and delete your account there at any time. To exercise other rights, contact hello@yungle.co. You also have the right to complain to your national data-protection authority.

How we measure the site

We keep our own counts of how Yungle is used — pages viewed, accounts created, uploads finished, plans started — on our own servers, in our own database, in the EU. These are counts and totals. They contain no email address, no IP address, no filename, and no share link, and nothing in them identifies the people you send files to.

When you are signed in, an event is tied to your account’s internal id, so we can see how a feature is used over time and help you when something goes wrong; our administrators can see that list for your account. Visits by people who are not signed in are not tied to anyone.

There is no durable identifier that follows you between visits, and none of it is shared with anyone, with one exception below. Individual records are deleted after about thirteen months; what remains after that is daily totals, which are not about any particular person.

If you arrive from an ad in ChatGPT

Yungle advertises in ChatGPT. When you click one of those ads, the link carries a reference chosen by OpenAI. We keep it for that visit in a first-party cookie, and if you sign in we store it on your account for up to 30 days. If, within that time, you create your account, send your first transfer, or start a paid plan, our server tells OpenAI that the ad led to it: the reference, which of those three it was, when, and for a plan its price.

Nothing else is sent: no email address, name, IP address, files, file names or anything you type.
No OpenAI code runs on our site and OpenAI sets no cookies here; the report is made by our server, not your browser.
OpenAI (a US company) uses it to count how its ads perform for us. Our legal basis is our legitimate interest in knowing whether our advertising works.
If you did not arrive from such an ad, nothing is sent at all. To object, email hello@yungle.co and we will stop reporting for your account.

Cookies

Yungle sets only first-party cookies, all readable by our own server alone. All but one are strictly necessary for something you asked for:

yungle_session — keeps you signed in.
yg_ws — which of your workspaces you are looking at.
Unlock cookies — remember that you entered the password for a protected transfer or collection, briefly.
yg_sender — remembers an email address this browser has confirmed for sending, for 90 days, so you are not asked again each time.
yg_viewer — lets someone reviewing a collection without an account keep their favourites and comments, for a year. Set only when they react to a file.
yg_next and yg_device — carry you back to the right place after signing in, and link a sign-in to the command-line client. Minutes, not days.
yg_ad — only if you arrive from an ad in ChatGPT: the ad’s reference, for that visit. It expires when you close your browser. See “If you arrive from an ad in ChatGPT” above.

The one measurement cookie, yg_ft, records which page a visit began on so we can tell which parts of the site are useful. It expires when you close your browser and is never set on a customer’s own domain. We use no third-party cookies and no tracking pixels, and none of our cookies follows you to other sites.